Chris’s Blog

I recently posted about the availability of Exchange 2010 SP1 and thought I would provide some feedback about the installation process.

Before installing SP1 for Exchange 2010, there are several updates and hot fixes that need to be installed first. An important thing to note is that all the Unified Messaging language packs other than US English (en-US) need to be uninstalled before upgrading the Unified Messaging server role. I have split these up then up by server role:

Hub Transport Role Prerequisites:
Microsoft Knowledge Base article 979099
Microsoft Office 2010 Filter Packs

Client Access Role Prerequisites:
Microsoft Knowledge Base article 982867 *requires a restart
Microsoft Knowledge Base article 979744 *requires a restart
Microsoft Knowledge Base article 983440 *requires a restart
Microsoft Knowledge Base article 977020
Knowledge Base article 979099

Mailbox Role Prerequisites:
Microsoft Knowledge Base article 979099
Microsoft Office 2010 Filter Packs

Unified Messaging Role Prerequisites:
Microsoft Unified Communications Managed API, Core Runtime 64-bit
Microsoft Server Speech Platform Runtime 64-bit
Microsoft Knowledge Base article 979099

In April I posted about some of the new features that will be available in Exchange 2010 SP1. The most notable of these is the ability to provision a user’s personal archive to a different mailbox database from their primary mailbox.

Many people have been eagerly awaiting the release of SP1, the good news is that it is now available for download. For more information, see this Exchange Team Blog entry.

To download Exchange 2010 SP1, click here.

I was running through the Exchange 2010 installation process earlier today, during the installation process, everything went really smoothly and I only had “green ticks”!

Once done, I opened the Exchange Management Console and saw the following error:

‘The following error occurred when searching for On-Premises Exchange server:[myservername.local] Processing data from remote server failed with the following error message: The user "domain\username" isn’t assigned to any management roles. For more…. It was running "Discover-ExchangeServer – USeWIA $true -SupressError $true’

It was rather confusing at first as I had completed the installation using an admin account that was a member of the Enterprise Admins group. Digging a little deeper, saw the following error in the event log:

After some further digging, I realised what had happened. A colleague of mine did the AD schema preparation using his admin account a few days ago, during that part of the process, the account being used was automatically added to the “Organization Management” AD security group. When I then resumed the installation process with my account, I was not a member of this group. To rectify the problem, I had to manually add my account to the “Organization Management” AD security group.