Exchange-1

Exchange – Disable access for a mailbox

Sometimes, it can be usefull to disable access to the Exchange server for a specific mailbox. For exemple, in order to forbid Outlook Web App (Outlook on the Web for Exchange 2016) but you do not want to disable the user account. Or you can prestage the mailbox and only allow access to a specific date/ time.

This can also be used during a migration to another mail system: when the user is migrated, you can disable all access to force the user on the new messaging system. And prevent any email sent by the old Exchange.

Exchange Disable access

Exchange Disable access

Let’s see how to disable all access for a mailbox using ECP or Exchange Powershell:

Continue reading

Exchange-1

Exchange 2013 – Powershell No Mapping Unicode WinRM

Microsoft released the Cumulative Update 11 for Exchange 2013 and Exchange 2016 CU1 in December 2015. With these new packages, they changed the behavior of Exchange Management Shell, (Exchange Powershell).

Prior to 2013 CU11 and 2016 CU1, when you start the EMS, it will connect by default to the local Exchange Server. But with CU11, Exchange Powershell will be proxy to the server where the user’s mailbox is located. It means that when you start the EMS console, it will probably try to connect to another server.

When all your servers are up to date, in some circonstances, you can get an error when launching the EMS: “No mapping for the Unicode character exists in the target”:

Mapping Unicode error

Mapping Unicode error

If you get this error, do not panic and stay calm :). You can find some posts where you need to rebuild the powershell virtual directory, but do not do this! Let’s see how to resolve this issue easily.

Continue reading

Exchange-1

Exchange 2013 – Web Management Service doesn’t start

With Exchange 2013, you can have an issue where the service “Web Management Service” can not be started. Without it, you can’t install any Cumulative Update and some Exchange functionality are no more available.

Service not started

If you try to install a new CU, you get this error:

Error:
The following error was generated when "$error.Clear();
if (Get-Service WMSVC* | ?{$_.Name -eq 'WMSVC'})
{ Set-Service WMSVC -StartupType Automatic
Start-SetupService -ServiceName WMSVC
}
" was run: "Service 'WMSVC' failed to reach status 'Running' on this server."

When you look into the Service mmc and try to start manually the service, you get the error code -2147483640 :

Web Management Service Error

Web Management Service Error

Continue reading