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


SCCM 2012 – How to update SCCM Agent

When Microsoft release a new Cumulative Update for ConfigMgr 2012, the SCCM Agent is updated too with a new version. To fix some bugs and improvements, you need to deploy it on all your clients.

To do this, you can choose two solutions:

  • Use the CAB file in the folder [SCCMInstall]\hotfix\KB\SCUP and deploy it with SCUP, that means you are using Software Updates.
  • Deploy the new version with two packages, one for x86 and one for x64, included in the Cumulative Update. With this solution, you can easily update your client with no technical requisite.

We will see how to update clients with the second solution, using package.

Continue reading