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

Manage Multiple Calendar Permissions with Exchange 2010 Shell

To edit all Calendars and set Default Calendar permission to Reviewer:

$Mailboxes = Get-Mailbox -ResultSize unlimited
$Mailboxes | ForEach {Set-MailboxFolderPermission $_":\Calendar" -User Default -AccessRights Reviewer}

Note:

• Use different Set-MailboxFolderPermission cmdlets when using Outlook in different languages (English, Dutch etc).
  Example cmdlet to use with Outlook Dutch client (calendar translates to agenda in dutch): Set-MailboxFolderPermission mailbox:\Agenda -User Default -AccessRights Reviewer
• The Set-MailboxCalendarFolder cmdlet configures publishing or sharing settings on a calendar folder of a specified mailbox. So, this cmdlet should be used when configuring Internet Calendar sharing.

Exchange Server 2007 SP3 does not update the Exchange Server Active Directory schema

Exchange Server 2007 SP3 does not update the Exchange Server Active Directory schema.

So, always run Setup.com /prepareschema once before installing Exchange 2007 SP3 on the first server.

Exchange 2010 Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC)

Strange issue today with an Exchange 2010 CAS/HUB/MBX Server. Event Viewer:

• Unable to initialize the Microsoft Exchange Information Store service.   - Error 0x96f.)
• MSExchange ADAccess 2114 Error: Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1360). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC).

Solution:

Default Domain Controllers Policy:
Computer Configuration/Windows Settings/Security Settings/Local Policies/User Rights Assignment: Manage Auditing and Security Log

Manage Auditing and Security Log contained only BUILTIN\Administrators

Manage Auditing and Security Log should contain at least:
AD-NetBIOS-Name\Exchange Servers, BUILTIN\Administrators

Exchange Database Corruption

Recently a customer was facing Exchange database corruption. Event Viewer:

Event Type:      Error
Event Source:    ESE
Event Category: Database Corruption
Event ID:          447
Description:
Information Store (2864) First Storage Group: A bad page link (error -338) has been detected in a B-Tree (ObjectId: 483242, PgnoRoot: 6816401) of database...

The safest way to solve this error was to create a new DB and then perform a mailbox move to prevent the use of eseutil /p which would probably result in some data loss. Troubleshooting steps:

1. Dismount DB
2. eseutil /mh: DB in Clean Shutdown status
3. Make offline DB backup
4. Mount DB to check if DB will mount (no problem in this case).
    Otherwise I had to use eseutil /p option.
5. Dismount DB
6. eseutil /k returned: 0 Bad Pages
7. eseutil /g returned:
    Database is CORRUPTED
    Operation terminated with error -1206 (JET_errDatabaseCorrupted)
8. Create new DB and enable Circular Logging
9. Move all mailboxes to new DB and disable Circular Logging

Quick jump to Exchange dirs from Exchange Shell

cd $exbin            jump to \Exchange Server\bin
cd $exinstall        jump to \Exchange Server\
cd $exscripts      jump to \Exchange Server\scripts

Autodiscover failed (0x800C8203)

Problem: Exchange autodiscover process did not work so Outlook automatic profile creation did not work. No problem manually configuring OL profile.

Outlook Test E-mail AutoConfiguration: Autodiscover to https://fqdn/Autodiscover/Autodiscover.xml failed (0x800C8203)

Everything ok after running: Test-OutlookWebServices -ClientAccessServer CAS-Server

Cause: Outlook retrieved wrong smtp address during automatic profile creation. Outlook automatic profile creation worked after correcting e-mail address and also Outlook Test E-mail AutoConfiguration.

Exchange 2007/2010 Move Mailbox process and not yet initialized mailboxes

After creating a mailbox it will be initialized when you access the mailbox for the first time with Outlook/OWA and default mailbox folders will be created in the language of the client.

The following options are available to change the language of the default mailbox folders after mailbox initialization:

1.    User runs Outlook with parameter: outlook.exe /resetfoldernames

2.    User changes default folder language from within OWA: Options, Regional Settings, Rename default folders so their names match the specified language

3.    Admin (Exchange 2010 only): Set-MailboxRegionalConfiguration mbx -Language xx-XX -DateFormat "d-M-yyyy"-LocalizeDefaultFolderName:$true

Language examples: nl-NL, en-US

Some time ago I did a GroupWise to Exchange 2007 migration with Quest Migration Manager for Exchange. I ran into one issue:

I had created 1000 mailboxes in one Exchange database which would be accessed with Outlook 2007 Dutch client. Before starting the mailbox migration from GW to E2K7 I distributed the mailboxes over 4 E2K7 databases with a mailbox move.

After migrating a mailbox I saw english mailbox folders under Outlook 2007 Dutch client. The following happened: move mailbox process created new mailboxes and moved the contents from the empty source mailbox. This resulted in default english mailbox folders. The solution was simple: first create mailboxes and distribute them directly over the 4 databases. Then perform mailbox migration from GroupWise to Exchange. Then access mailbox with OL 2007 Dutch client: only Dutch mailbox folders.

I've tested a mailbox move with Exchange 2010 SP1:

1.    Create mailbox (no access with OWA/Outlook)

2.    Move mailbox to another database

3.    Access mailbox with Outlook 2007 Dutch client: default mailbox folders in English language

4.    Set-MailboxRegionalConfiguration mailbox -Language nl-NL -DateFormat "d-m-yyyy"-LocalizeDefaultFolderName:$true

This step can be performed while Outlook is online and results in default mailbox folders in Dutch language.

So, a mailbox move initializes a mailbox which results in default mailbox folders in English language. Maybe Microsoft can build in an extra check? Mailbox move process should not move mailboxes which have not been initialized. Just delete and recreate is sufficient in this case. I have reported this ‘issue’ to Microsoft.

Rename default Outlook folders after Exchange 2007/2010 mailbox initialization

After creating a mailbox it will be initialized when you access the mailbox for the first time with Outlook/OWA and default mailbox folders will be created in the language of the client.

The following options are available to change the language of the default mailbox folders after mailbox initialization:

1.    User runs Outlook with parameter: outlook.exe /resetfoldernames

2.    User changes default folder language from within OWA: Options, Regional Settings, Rename default folders so their names match the specified language

3.    Admin (Exchange 2010 only): Set-MailboxRegionalConfiguration mbx -Language xx-XX -DateFormat "dd-MM-yyyy"-LocalizeDefaultFolderName:$true

     Language examples: nl-NL, en-US

The certificate is invalid for Exchange Server usage

After importing an Exchange 2010 third party SAN certificate with Exchange Management Console I got the following error: The certificate is invalid for Exchange Server usage

Get-ExchangeCertificate:
Status: Invalid
RootCAType: Unknown

In this particular case the cause was the ISP who delivered the wrong Intermediate CA.