Upgrading to Exchange 2010 SP2 - Microsoft Consulting Services - CloudServus - United States

Exchange 2010 Service Pack 2 includes a number of new improvements. For details on all of the features check out Technet. This post will walk through the steps to upgrade to SP2 from Exchange 2010 SP1.

•  Hybrid Configuration Wizard
•  Federated Delegation
•  Address Book Policies
•  Cross-Site Silent Redirection for Outlook Web App
•  Mini Version of Outlook Web App
•  Mailbox Replication Service
•  Mailbox Auto-Mapping
•  Multi-Valued Custom Attributes
•  Litigation Hold
•  Multi-Tenant Support

Prerequisites:

There were two issues that I ran into while installing SP2 on all roles of Exchange 2010:

• Client Access Server – Requires IIS6 WMI Compatibility feature
• Unhook Forefront from Exchange: My Edge Transport Server (Running Forefront Protection for Exchange and TMG) – Requires you to unhook Forefront from Exchange. This would also be the case if you are running Forefront on each Exchange server.

(These are the errors I experienced before stopping the Forefront services) Error:

Setup cannot continue with the upgrade because the ‘FSEAntispamSettings’ () process (ID: 5292) has open files. Close the process and restart Setup.

Click here for help… http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.2.247.1&e=ms.exch.err.Ex28883C&l=0&cl=cp

Error:

Setup cannot continue with the upgrade because the ‘IsaManagedCtrl’ () process (ID: 3196) has open files. Close the process and restart Setup.

Click here for help… http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.2.247.1&e=ms.exch.err.Ex28883C&l=0&cl=cp

IIS6 WMI Compatibility: To resolve the issue with the Client Access server install the IIS 6 WMI Compatibility pack. This must be done from the PowerShell because the GUI was greyed out for me.

1. Open Windows PowerShell with elevated permissions.

2. Run the following command: Import-Module ServerManager

3. Run the following command: Add-WindowsFeature Web-WMI

Unhook Forefront from Exchange: Anyone familiar with the old Antigen products certainly remembers this process for updates to Exchange.

1. Stop the Exchange and Forefront Services:
• Microsoft Forefront Server Protection Controller (this will actually stop #2
• Microsoft Exchange Transport
• Microsoft Forefront TMG Control (if applicable)
• System Attendant (if applicable)
• Information Store (if applicable)
2. From the Forefront install directory, run the following command: FSCutility.exe /disable
3. Run update…
4. Run FSCutility.exe /enable
5. Start all services, including the Forefront Controller which will start all the services set to “Manual”.

Once it is complete, you can install SP2 in your environment. It is possible to run SP1 and SP2 at the same time in your organization, but I am always a strong proponent of standardization, so I recommend upgrading all servers as soon as possible.

Order of Upgrade:

1. Client Access Servers
2. Hub Transport Servers
3. Unified Messaging (if installed)
4. Mailbox Servers
5. Edge Servers (if installed)

Schema Update:

The installation of SP2 includes a schema update. This can be run from the GUI as well as from PowerShell. I prefer to run it from the PowerShell so I can watch the status of the installation.

1. Download the bits from here. This will download an EXE file.
2. Run the EXE file to extract the contents.
3. Open a command prompt and navigate to the folder where you extracted the EXE. Type “setup.com /ps” or “setup.com /prepareschema”.

Begin the Installation:

1. Run Setup.exe.

2. On the Introduction Screen, click Next.

3. On the License Agreement screen, select I accept the terms in the license agreement. Click Next.

4. Once the Readiness Checks have completed you are ready to Upgrade. Click Upgrade.

5. On the Completion screen verify that there were no errors and click Finish.

6. Once the server is updated with Exchange 2010 SP2, you will see the Version changed in Exchange Management Console.