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”:
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.
Mapping Unicode and WinRM errors
After CU11 installed, you can find at least two typical errors with the Exchange Powershell console, the Mapping Unicode as above, or WinRM cannot complete the operation:
Moreover, the Exchange Toolbox does not work anymore. You will have an error with the SerializationException runtime:
In fact, even with these errors, Exchange fonctionnalites continue to work. These errors are related to the WinHTTP Proxy setting on the server.
- Type this command to check if you server has a WinHTTP proxy set: netsh winhttp show proxy
- Reset the proxy configuration with : netsh winhttp reset proxy
After the modification, Exchange Management Shell and Exchange Toolbox are working again!
You can get more information about mailbox anchor and Powershell here.
Pingback: Office 365 – Import Export Role | Cloud Evangelist