Microsoft Exchange and Active Directory Blog
In the previous article, I had already shown how to create new virtual directories for OWA, for example. However, the Exchange Management Shell was always used to recreate them. But what happens if the Exchange Management Shell no longer starts? If the virtual directories have to be recreated and the Exchange Management Shell no longer starts, what ... Read more
Although the virtual directories for the various Exchange web services can be recreated via the "Exchange Admin Center", there are cases where this function reaches its limits. I have simulated such an error for this article. Even after resetting the directory for OWA with the Exchange Admin Center, OWA does not work: Not everything ... Read more
Ingo Gegenwarth has published a very interesting article regarding Exchange on HP Proliant Gen9 servers on his blog "The clueless guy". The article deals with possible performance problems when Exchange is installed directly on HP servers and the default BIOS settings are kept: Exchange performance:HP NUMA BIOS settings So for HP servers and Exchange we recommend ... Read more
In this article, I already presented a small script that checks the Exchange HealthCheck URLs. Since I use PRTG for monitoring in my private environment, I used a separate sensor for the HealthCheck URLs. PRTG comes with a whole range of sensors for Exchange Server, but due to the limitation of 100 ... Read more
A little tip on the side as the question has already been asked several times: Do I also have to consider .NET Framework when installing Exchange Updates (CUs)? Simple answer: Yes! Here is the somewhat more detailed answer: Unsupported NET Framework versions in conjunction with Exchange Server can be quite problematic, as has already been shown in the past: https://www.frankysweb.de/net-framework-4-6-1-nicht-auf-exchange-servern-installieren/ The NET ... Read more
The status of individual Exchange protocols can be easily determined via a URL. This is particularly interesting for load balancers, as it is easy to determine whether the protocol is available on the respective server. Querying the respective URLs is more meaningful than simply checking whether the port on the Exchange server is still open, but ... Read more
The .NET Framework 4.7 has been available for about a month and is expected to be distributed soon via Windows Update. Even though .NET 4.7 is already supported on Windows Server, you should be careful with Exchange Servers. Here is the current support matrix for Windows Server and .NET 4.7: The .NET Framework 4.7 is supported on the following Windows Server ... Read more
I have just uploaded the new version of the Message Tracking GUI and fixed two issues that have been bothering many users. The following issues have been fixed: On small screen resolutions, the window is now resizable and shows scrollbars when needed The recipients are now correctly entered into the CVS file The current version can be downloaded here ... Read more
During the migration from Exchange 2013 to Exchange 2016, the following error (version mismatch) may occur when moving user mailboxes from Exchange 2013 to Exchange 2016: A version mismatch was detected (Actual:6, Expected:5) The following message can then be seen in the Exchange 2013 server log: 2017-04-23T20:37:21.432Z,6,Default,Error,",", "RegisterMigrationBatch failed, exception at Microsoft.Exchange.Migration.MigrationServiceHelper.SafeInvokeImplMethod(Action method, MigrationServiceRpcMethodCode methodCode) at Microsoft.Exchange.Migration.MigrationNotificationRpcSkeleton.RegisterMigrationBatch(IMigrationNotification ... Read more
Today an important update was released for the following Exchange Server versions: Microsoft Exchange Server 2013 Service Pack 1 Microsoft Exchange Server 2013 Cumulative Update 14 Microsoft Exchange Server 2016 Cumulative Update 3 It is interesting to note that the Exchange versions are no longer completely up-to-date. There is already CU4 for Exchange 2016, as well as CU15 for ... Read more
