Please look at Jetze Mellema’s blog for some detailed info & at Dave Stork’s blog post for consolidated information on this service pack.

Changing the Active Directory schema is a big deal in some environments and you might not be able to do this just as part of the Exchange upgrade.

updating sp1 to sp2-43

Find the and it will copy the files it needs to start the installation. You accept the EULA And watch the wizard run the readiness checks In the lab we have our CAS/HUB servers on the same nodes, so the prerequisites are checked for both.

You then arrive at the welcome screen where you choose “Install Microsoft Exchange Server Upgrade” The setup then initializes You get to the Upgrade Introduction screen where you can read what Exchange is and does . The CAS servers in Exchange 2010 SP2 need the IIS 6 WMI Compatibility Feature.

An example of this is below for a the mailbox role server. and do so by evacuating the databases to the other nodes as to avoid service interruption.

The process to upgrade DAG member is described here: provides two Power Shell scripts to automat this for you.

That way you’ll have all of them on the same install base which is easier to support and trouble shoot.

Before I did this upgrade in production environments I tested this two time in a lab/test environment.

If you want to verify all your domain controllers immediately you can always force replication.

First CAS/HUB roles server (If you didn’t upgrade the schema manually) Additional CAS/HUB roles server … But then it completes and you can click “Finish” We’re done here so we click “Close” When you run the setup on the other server roles like Unified Messaging, Mailbox and Edge the process is very similar and is only different in the fact it checks the relevant prerequisites and upgrades the relevant roles.

There you can find some more information and links to the downloads, release notes etc.

You will also note that the Exchange 2012 Tech Net documentation has SP2 relevant information added.

If you had done the upgrade from the CLI you would have to run SETUP /m:upgrade /Install Windows Components and you would not have seen this error as it would have been taken care of installing the missing components. You can take care of that by installing this via “Add Role Services” in Server Manager for the Web Server (IIS) role.