Here are the set of steps to go through, to ensure the Exchange 2010 Service Pack upgrades or the Exchange 2013 Cumulative Update installations happen smoothly
- Make sure the Execution policies are set to unrestricted by running the command :
You can run the command Set-ExecutionPolicy Undefined -Scope PolicyName
You receive error 1603 when you try to install the Exchange Server 2010 RU1
This is also applicable to Exchange 2013
- Since the server is already in production, the Windows OS updates and system requirements will already be met.
However, I would still suggest to go through the hotfixes section.
- Make sure we do not have anything additional installed that is unsupported.
Exchange Server Supportability Matrix
For example, the .Net framework and Windows Management Framework installed should fall into the supportability matrix. There are instances where admnistrators inevitably or unknowingly install one of the unsupported versions of .Net or WMF that prevents future upgrades.
Check the Powershell version by running the command $PSVersionTable
.Net framework version could be checked under the registry location :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full
- Interim Updates if any, need to uninstalled before Exchange 2010 Service Pack installation. For Exchange 2013, they need not be uninstalled, we can go ahead with the Cumulative Update installation.
If at all there are UM-LanguagePacks installed, they need to uninstalled before upgrading, for Exchange 2010 and Exchange 2013 both.
- Make sure we have the latest back-up of the Exchange databases and also system state backup of the AD environment
- Note down any customizations such as OWA, config files on servers, registry changes, Lync integration, or third party add-ons, prior to the installation.
- We could perform the PrepareAD in advance separately. This only needs to be done once for the whole environment.
setup.exe /preparead /IAcceptExchangeServerLicenseTerms
If this is not done, setup will automatically perform it at the time of the upgrade of the first server.
- Set the server to be upgraded to maintenance mode if it is mailbox role in Exchange 2013 ( with or without DAG) and if is a DAG member in Exchange 2010.
For Exchange 2010 :
Remove it from maintenance mode using the command below
For Exchange 2013 :
Use the steps as suggested in the article below,
Exchange 2013 Maintenance mode
Or the script ,
Exchange Server 2013 Maintenance Mode Script (Start)
For CAS, take the node to be upgraded out of the Load Balancer.
- Then proceed with the installation from GUI or from Administrator command prompt by pointing to the location where the files have been downloaded. Files should be downloaded from Microsoft Download Center
Setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms
- Make sure to use an elevated command prompt and to close all the other Exchange windows at the time of setup.
- Also make sure there were no pending reboots prior to beginning the installation.
- The order of installation for Exchange 2010 :
Client Access Server (if you have multiple sites, internet facing sites first)
The order of installation for Exchange 2013 :
Mailbox (Internet-facing site first)
- Post the installation we must reboot the Exchange server.
- I would also recommend to test the setup in a lab before installing it in production.