Note: We have learned that customers using Exchange Server 2013 and Exchange Server 2007 co-existence can experience an issue causing Exchange Server 2013 CU6 databases to failover. Please refer to...
Updated Jul 01, 2019
Version 2.0
Blog Post
These were are my issues with installing CU6:
1. An unexpected error has occurred and a Watson dump is being generated: A reboot is required to complete file operations on '{4934D1EA-BE46-48B1-8847-F1AF20E892C1}'. Reboot the machine, and then run setup again.
This happens on nearly every Exchange 2013 update, and it does usually go away after restarting the server, I guess the only way to prevent it is to restart the server BEFORE starting setup.
2. During the "Mailbox role: Transport service" step I got the Cannot start service MSExchangeServiceHost on computer '.' error. This was due this service and it's depency (Active Directory Topology service) being "Disabled". After changing the startup type,
they both started fine, but this issue kept repeating in several subsequent steps. All Exchange services were being 'restored' to Disabled at the beginning of each step, and every time Setup tries to start MSExchangeServiceHost even though it is disabled.
I "fixed" this by running this PowerShell script while running the CU6 setup:
do {
Get-Service *MSExchange* | Set-Service -StartupType Automatic
Sleep -seconds 5
} while ($true)
3. Setup re-creates the DiscoveryMailbox, which I forgot to delete, so I got the usual "Couldn't resolve the user or group "domain.com/Microsoft Exchange Security Groups/Discovery Management." error that apparently will never be fixed. Fixed it by deleting
the AD-account for this mailbox, and running setup again.
4. The "Default Frontend" receive connector had been stripped of it's ability to relay for anonymous users, which I had configured for it to receive outbound mail from Exchange Online (we use centralized mail transport), I had to add it back.
It is also quite annoying that:
- setup will not resume where it left off when an error occurs, but will do several steps again that were already done.
- setup just quits when it is ready, no message saying that it finished. Had to check the log to make sure it finished without error.
CU6 was by far the most time consuming (wasting really) Exchange update I've ever installed.