Exchange 2010 SP2 Setup Error

Got this error installing Exchange 2010 SP2 on Windows 2008 R2 with Exchange 2010 SP1 CAS/HUB/MBX role:

Mailbox role

Error: this server role can't be installed because the following roles aren't current: AdminToolsRole

Solution:

1. HKLM\Software\ExchangeServer\V14\AdminTools\ConfiguredVersion

    Change ConfiguredVersion from 14.1.218.5 to 14.2.247.5

2. Restart server and start Exchange 2010 SP2 Setup

Exchange 2010 SP2 Setup Failed while performing the action 'install'

Got this error installing Exchange 2010 SP2 on Windows 2008 R2 with Exchange 2010 SP1 CAS/HUB/MBX role:Some controls aren’t valid. Setup previously failed while performing the action “Install”. You can’t resume setup by performaing the action “BuildToBuildUpgrade”.

Cause:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\MailboxRole\Action
Action key is present with value data: Install

Solution:
Delete Action key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v14\MailboxRole

A fix for the interoperability issues between Exchange 2007 and 2010 EMC and IE9 is now available

http://blogs.technet.com/b/exchange/archive/2011/10/17/a-fix-for-the-interoperability-issues-between-exchange-2007-and-2010-emc-and-ie9-is-now-available.aspx

Exchange 2010 SP2 Upgrade Failed (Couldn't resolve the user or group Discovery Management)

I’ve upgraded my Exchange 2010 SP1 environment (1x CAS/HUB & 2x DAG member) to Exchange 2010 SP2 according to Upgrade Exchange 2010 to Exchange 2010 SP1 or Exchange 2010 SP2

1.       CAS/HUB Server: success

2.       Mailbox Server 1: success
3.       Mailbox Server 2: Mailbox Role Failed. I’ve rebooted the server and tried restarting Exchange 2010 SP2 setup which resulted in the same error:

Exchange 2010 SP2 Setup failed with error:

Couldn't resolve the user or group "AD-domain/Microsoft Exchange Security Groups/Discovery Management." If the user or group is a foreign forest principal, you must have either a two-way trust or an outgoing trust.
The trust relationship between the primary domain and the trusted domain failed.

 Solution:

1.       Disable Discovery Search Mailbox
2.       Enable Discovery Search Mailbox:

• Enable-Mailbox discoverysearch* -Discovery
• Give user(s) Full Access Permission on Discovery Search Mailbox

3.       Upgrade Mailbox Server 2 to Exchange 2010 SP2: success

Martijn

Exchange 2010 SP2 OWA Dutch translation issue

Exchange 2010 SP2 OWA contains a translation error when using OWA in Dutch: 'Berichten' (Mail) is now called 'Globale adreslijst' (Global address list).

I've reported this to MS. I will post an update if a solution is available.

Martijn

Third Party Migration Tools & Exchange 2010 Default Throttling Policy

While migrating from GroupWise to Exchange 2010 SP1 with Quest GroupWise Migrator for Exchange (GME) I've experienced throughput issues. GME throughput (GB/hour) was decreasing more and more. Event Viewer errors on Exchange Server:

Process Microsoft.Exchange.AddressBook.Service.exe (PID=1636). User 'Sid~XXXXX\name-of-migration-account~RCA~false' has gone over budget '346' times for component 'RCA' within a one minute period. Info: 'Policy:DefaultThrottlingPolicy_4debe28f-3b74-4c7d-83c7-0650cb781f87, Parts:AD:345;'. Threshold value: '100'.

Solution:
1) New-ThrottlingPolicy "Quest GME Throttling Policy" -RCAMaxConcurrency $null -RCAPercentTimeInAD $null -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null

2) Set-Mailbox name-of-migration-account –ThrottlingPolicy "Quest GME Throttling Policy"

3) Restart Microsoft Exchange Throttling service on Exchange Server

Re-Create the Discovery System Mailbox

According to Re-Create the Discovery System Mailbox:

'Multi-Mailbox Search uses a system mailbox to store discovery search metadata. This Discovery system mailbox has the display name SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}. Because system mailboxes aren't visible in the EMC or in Exchange address lists, they are rarely deleted inadvertently.
However, if the Discovery system mailbox is deleted accidentally, discovery managers will be unable to perform discovery searches or manage existing discovery searches. In this case, to enable discovery functionality, you must re-create the Discovery system mailbox.'

My comments:
However, the Discovery Search Mailbox has not been created after re-creating the Discovery System Mailbox. To create the Discovery Search Mailbox:

enable-mailbox discoverysearch* -Discovery