Exchange 2010 Service Pack 2 (SP2) installation issues/problems

When I installed Exchange 2010 SP2 by the GUI, it gave me an error: Setup cannot use domain controller ‘<server>’ because it belongs to Active Directory site ‘<site>’. Setup must use a domain controller in the same site as this computer (<site>).

So how do you install Exchange 2010 SP2 forcing the setup to use the correct domain controller in the same site? Simple fix is to kick off the installation from the command line and watch it install from there.

  1. setup.com /mode:upgrade /domaincontroller:dcname.contoso.local

This works perfectly.

Also for any Unified Messaging rolls, I got this error: All the Unified Messaging language packs other than US English (en-US) need to be uninstalled before upgrading the Unified Messaging server role. Detected language packs: en-AU,en-US

Simple fix is to remove the second language pack, install service pack 2, then re-install the Service Pack 2 version of the Exchange UM language pack available from here:

Exchange Server 2010 SP2 UM Language Packs – http://www.microsoft.com/download/en/details.aspx?id=28191
Exchange Server 2010 SP3 UM Language Packs – http://www.microsoft.com/en-au/download/details.aspx?id=36769

  1. Go into Exchange Management Console, under Organization Configuration > click on Unified Messaging > then click properties the UM Dial Plan > click the Settings tab, and make a mental note of the current setting > temporarily change the Default Language to English (United States) 

    image

  2. setup.com /RemoveUmLanguagePack:en-AU
  3. setup.com /mode:upgrade /domaincontroller:dcname.contoso.local
  4. setup.com /AddUmLanguagePack:en-AU /SourceDir:"C:\UMLanguagePack.en-AU" (The source directory needs to point to where the Language Pack executable file is (.exe) that you downloaded from Microsoft)
  5. Change the default language of your dial plan back to what it was set to before.

That’s it!

We have had no problems with the installation of Exchange 2010 Service Pack 2, and we are running 2 sites with a DAG across both.

One Comment

  1. Justin G

    This worked perfect!

    A tip to to some other users who still may experience problems. I had to create this registry key and then restart the netlogon service. This made the server think it was in the same site as the domain controller specified. Afterwords, you can delete the key and restart the netlogon service.

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

    Add String value “SiteName” and changed the value to your AD Site.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s