We have an existing Azure AD Connect synchronization with Microsoft 365 tenant. We did create…
What is an excellent way to check the Exchange Server before applying an Exchange Cumulative Update? Many issues can happen when you run the Exchange Cumulative Update on the Exchange Server, leaving the Exchange Server in a failed state. It’s good to know that the Exchange Server is in good condition before running the Exchange CU setup. Let’s look at how to check Exchange Server before installing the Cumulative Update.
Table of contents
Exchange Server Setup Assist PowerShell script
The Exchange Server Setup Assist script helps detect common configuration issues that cause Exchange Server Cumulative Update installation issues and other issues caused by a simple configuration change within an Exchange Environment.
The SetupAssist.ps1 PowerShell script will gather the following information on the Exchange Server:
- Current Logged on User and SID
- Are you running as an Administrator
- Member of Domain Admins
- Member of Schema Admins
- Member of Enterprise Admins
- Member of Organization Management
- Current PowerShell Execution Policy setting
- Exchange Services Status
- Computers Container Exists
- Checks to see if you are missing files in the installer cache
- More than 1 powershell.exe process is up and running
- If a reboot is pending. (Add -Verbose to see where)
- The current AD level of readiness for CU upgrading. Displays warnings if a mismatch is detected.
Download and prepare Setup Assist PowerShell script
Download SetupAssist.ps1 PowerShell script from GitHub and place it on the Exchange Server C:\scripts folder. If you don’t have a scripts folder, create one. Ensure that the file is unblocked to prevent errors when running the script. Read more in the article Not digitally signed error when running PowerShell script.
Run Setup Assist PowerShell script
Run PowerShell as administrator. Change the directory path to C:\scripts and run the script.
PS C:\> cd C:\scripts PS C:\scripts> .\SetupAssist.ps1 Setup Assist Version 22.01.14.0319 TestName Result Details -------- ------ ------- Exchange AD Latest Level Failed At Exchange 2019 CU10 Prepare AD Requirements Failed Schema Master: DC01-2019.exoip.local Schema Master Domain: exoip.local Schema Master Site: Default-First-Site-Name --------------------------------------- Local Server: EX01-2019.exoip.local Local Server Domain: exoip.local Local Server Site: Default-First-Site-Name User Administrator Passed exoip\administrator S-1-5-21-288954866-3807497283-1560389301-500 Organization Management Passed EXOIP\Organization Management S-1-5-21-288954866-3807497283-1560389301-1104 Domain Admins Passed EXOIP\Domain Admins S-1-5-21-288954866-3807497283-1560389301-512 Enterprise Admins Passed EXOIP\Enterprise Admins S-1-5-21-288954866-3807497283-1560389301-519 Execution Policy Warning RemoteSigned Exchange Services Passed Services Cache Files Passed Computers Container Exists Passed DC=exoip,DC=local DC DNS Host Name Passed DC01-2019.exoip.local Multiple Active Sync Vdirs Detected Passed Msi Cache File Passed IIS URL Rewrite Passed Installed Version 7.2.1993 Microsoft Visual C++ 2012 Passed Visual C++ 2012 Redistributable Microsoft Visual C++ 2013 Passed Visual C++ 2013 Redistributable Other Well Known Objects Passed Pending Reboot Failed HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations Valid Home MDB Passed -----Results That Didn't Pass----- TestName Details ReferenceInfo -------- ------- ------------- Exchange AD Latest Level At Exchange 2019 CU10 Latest Version is Exchange 2019 CU11. More Info: https://aka.ms/SA-ExchangeLatest Prepare AD Requirements Schema Master: DC01-2019.exoip.local Run /PrepareAD from this computer Schema Master Domain: exoip.local Schema Master Site: Default-First-Site-Name --------------------------------------- Local Server: EX01-2019.exoip.local Local Server Domain: exoip.local Local Server Site: Default-First-Site-Name Execution Policy RemoteSigned Pending Reboot HKLM:\SYSTEM\CurrentControlSet\Control\Session https://aka.ms/SA-RebootPending Manager\PendingFileRenameOperations Setup Log Reviewer Results -------------------------- Setup.exe Run Date: 12/12/2021 13:20:54 Setup.exe Build Number: 15.2.922.7 The most recent setup attempt completed successfully based off this line: [12/12/2021 13:37:15.0011]  The Exchange Server setup operation completed successfully. No Action is required.
The same as the above output, but in a screenshot.
The output shows the results:
- Passed: You’re all set.
- Warning: Look into it.
- Failed: Fix them!
In our example, it shows a warning which we can ignore. But, we have to fix the errors. To do that, we will:
- Prepare Active Directory and domains for Exchange Server
- Reboot the Exchange Server
After both tasks, we can install Exchange Server Cumulative Update on the Exchange Server.
You learned how to check Exchange Server with the SetupAssist.ps1 PowerShell script. Run the script before running Exchange Cumulative Update and fix the failed issues. You can also run the script before installing Exchange Server on a Windows Server to validate the overlooked prerequisites. It’s an excellent PowerShell script that you must have in your collection.
Did you enjoy this article? You may also like Exchange Server setup operation didn’t complete. Don’t forget to follow us and share this article.