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
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.
With an Office 365 business subscription, Microsoft provides a new service in order to make the migration easier: Import File. This service allows us to import PST files into Office 365 mailboxes with a web interface. For the moment, you can use it for free, but it will be available for purchase later in 2016.
However, if you try this function without prerequisites, you will get an error for each mailbox. On the status page, you will see this error: Please add Mailbox Import Export role for user running Import and check back in 60 minutes.
Status page import export error
Let’s see how to correct this error:
If you manage one or several file servers in your infrastructure, you may have the will to customize the Access Denied error message displayed to users. This feature can be used since Windows 8 and Windows Server 2012. It is called Access-Denied Assistance.
Access Denied Custom Message
Access-Denied Assistance can be useful if you want to simplify the process to grant folder permissions to users. Sometime, the user does not know the full path, neither rights needed.
With Access-Denied Assistance, shared folder administrator will receive an email with all information required. No more call for user access.
Let’s see how to do that with Server 2012 R2.
When you are deploying a “big” software update like KB2919355, with System Center Configuration Manager, you can have the error code 0x800f0821 on some computers.
The computer receives the update, downloads it and starts to install it but the installation will fail.
Installation failed 0x800f0821
This error is raised because the execution time was reached. Depends on computers and servers, you may or not have this error on all SCCM clients.
Let’s see how to change the configuration in SCCM.