Make sure no anti-virus or third party software ( backups) are running.
What do the Exchange Setup logs show?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
EXCHANGE SERVER 2019 CU 11 UPGRADE INSTALLATION STUCK AT STEP 5 WITH 100 % COMPLETE FOR MORE THAN 3 HOURS, any ideas why?
step 5 mailbox role: client access service
I had already run prepare schema and prepare AD.
Make sure no anti-virus or third party software ( backups) are running.
What do the Exchange Setup logs show?
Hi Community,
I managed to resolve the issue after hard work of thinking and researching henceforth, felt its good to share the guidelines or the methodology i used to resolve the issue.
In each exchange server affected,
Step 1: Prepare Schema & Prepare AD. I used AD with the exchange setup file to extend the schema.
Step 2: Remove or delete the content of the following registry key.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Here look for a key called PendingFileRenameOperations
Simply double-click this key and remove the data inside it, or you can remove the key completely.
In my environment i removed the content of the key.
My recommendation is to back up the entire registry key above before modifying it, just that if anything goes wrong, you can roll back.
Step 3: Start Exchange Management Shell as an administrator and run the following scripts:
.\UpdateCas.ps1 and .\UpdateConfigFiles.ps1
or UpdateCas.ps1 and UpdateConfigFiles.ps1
In my environment i used: UpdateCas.ps1 and UpdateConfigFiles.ps1
Step4: Restart the server.
After reboot, i remounted the exchange CU setup file and i was able to install it without issues. I noticed even the installation speed was increased significantly.
Important:
Before doing all that, the Exchange CU 11 update installation would show copying 16 exchange files
from the GUI, then after the steps above, the files would reduce to 10 that iscopying 16 exchange files
.
Environments can be different, but this can save majority.
On the other note I will also suggest you to power-cycle the server and start the upgrade setup again.
--If the reply is helpful, please Upvote and Accept as answer--