Article ID: 113720, created on Apr 18, 2012, last review on Aug 12, 2014

  • Applies to:
  • Operations Automation 5.4

Resolution

The Microsoft Exchange Server 2010 Service Pack 2 (SP2) Setup wizard may be used to perform an upgrade from the RTM version of Exchange 2010 or Exchange 2010 SP1 to Exchange 2010 SP2.

Important: Before upgrading, make sure that the Active Directory domain and forest functional levels are set to Windows Server 2008. For detailed instructions on how to raise the Active Directory domain and forest functional levels, refer to this Microsoft KB article http://support.microsoft.com/kb/322692.

Exchange 2010 server roles should be upgraded in the following order:

  1. Client Access
  2. Hub Transport
  3. Mailbox
  4. DAG

To upgrade CAS, HUB, and Mailbox servers, perform the following actions on each of the servers:

  1. Run the following command:

Setup.com /mode:upgrade

  1. For Exchange 2010 in Enterprise Mode (with or without SP1) managed by HMC, the first setup performs an Active Directory upgrade and restores the following address lists: Public Folders, All Contacts, All Groups, All Rooms, and All Users. This breaks HMC security, so the lists must be deleted and the Default Address List must be secured again immediately after the first Exchange 2010 SP2 is installed. To perform this, take the following actions:
    1. Go on the MPS node.
    2. Open the MPS Deployment Tool.
    3. Re-execute the Configure Exchange Address Lists security action under the Hosted Exchange > Exchange Provisioning Configuration node.
    4. Click the Start Deployment button.
Clear the value on MSExchResourceAddresslists:

  1. Open ADSIEDIT.msc.
  2. Connect to the –°onfiguration container.
  3. Under the –°onfiguration container, expand Services > Exchange.
  4. Right-click on the Exchange organization and click Properties.
  5. Clear the msExchResourceAddressLists attribute.

After upgrading Exchange 2010 servers with the CAS role, the following steps should be performed:

  1. Log on to the CAS server using an account that is a member of the Local Administrators or Domain Administrators group.
  2. Open Internet Information Services (IIS) Manager.
  3. Remove all bindings on IP address 127.0.0.1 from all websites except for the Default Web Site.
  4. Repeat steps 1-3 on each Exchange 2010 CAS server.

If you have BlackBerry service installed on the system, perform the operation described in the Configuring Permissions for BES Service Account (for Exchange 2007/2010 only) topic in the Parallels Operations Automation Hosted Exchange Deployment Guide after the upgrade.

To upgrade the DAG servers, perform the following actions:

  1. Log in to any of the DAG servers in the Exchange organization.

  2. Verify the health and status of the DAG by saving the following commands as a Windows PowerShell script (.ps1) file.
(Get-DatabaseAvailabilityGroup -Identity (Get-MailboxServer -Identity $env:computername).DatabaseAvailabilityGroup).Servers | Test-MapiConnectivity | Sort Database | Format-Table -AutoSize
Get-MailboxDatabase | Sort Name | Get-MailboxDatabaseCopyStatus | Format-Table -AutoSize
function CopyCount
{
$DatabaseList = Get-MailboxDatabase | Sort Name
$DatabaseList | % {
$Results = $_ | Get-MailboxDatabaseCopyStatus
$Good = $Results | where { ($_.Status -eq "Mounted") -or ($_.Status -eq "Healthy") }
$_ | add-member NoteProperty "CopiesTotal" $Results.Count
$_ | add-member NoteProperty "CopiesFailed" ($Results.Count-$Good.Count)
}
$DatabaseList | sort copiesfailed -Descending | ft name,copiesTotal,copiesFailed -AutoSize
}
CopyCount

  1. Perform a server switchover:
    Move-ActiveMailboxDatabase -Server <DAGMemberName>

  2. Prevent the DAG member from becoming a failover target:
    Set-MailboxServer -DatabaseCopyAutoActivationPolicy:Blocked

  3. If necessary, move the primary Active Manager role to another DAG member:
    Cluster group "cluster group" /move

  4. Upgrade to Exchange 2010 SP2, using the instructions provided earlier in this article.

  5. Enable the upgraded DAG member to become a failover target:
    Set-MailboxServer -DatabaseCopyAutoActivationPolicy:Value
    ("Value" should be either IntrasiteOnly or Unrestricted)

  6. Repeat steps 1–7 on each DAG member until all DAG members have been upgraded to SP2.

Important: When the upgrade is complete, perform the instructions provided in this KB article https://kb.odin.com/en/111617.

Known issues:
  1. Sometimes, a new Outlook profile cannot be configured for the Mailbox, generating this error: The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
  2. Sometimes, Outlook can stall during an operation and report this error: The Microsoft Exchange Server computer is not available.
These symptoms appear only if Exchange 2010 SP2 is deployed on Exchange CAS servers. To resolve such issues, follow the instructions provided in this KB article https://kb.odin.com/en/111653.

caea8340e2d186a540518d08602aa065 ac82ce33439a9c1feec4ff4f2f638899 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF