Exchange Server setup encountered an error.

Welcome to Microsoft Exchange Server 2007 Unattended Setup

Preparing Exchange Setup

Exchange Server setup encountered an error.

This error can be caused by a halted command line install. To fix it, remove the following keys from the registry and re-run the setup

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange ADAccess

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange Anti-spam Update

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange Autodiscover

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange Common

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange EdgeSync

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange IMAP4

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange Management Application

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange POP3

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange Process Manager

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange System Attendant Mailbox

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchange Topology

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeFDS

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeMailboxAssistants

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeServiceHost

Adding more addresses to a mail contact. Works for users too.

$Temp = Get-MailContact 'Test User'
$Temp.EmailAddresses.Add("test.user@test.com")
$Temp.EmailAddresses += ("X400:c=AT;a=ada;p=domain;s=user;g=test;")
Set-MailContact -Instance $Temp

PowerShell Remove Email Addresses

To remove an email address from many users is a time consuming task. This PowerShell command will automate the process.

$mailbox = Get-Mailbox mail.alias ; $mailbox.EmailAddresses -="email.alias@mydomain.com" ; $mailbox set-mailbox

Store.exe using excessive memory

There are many reasons why store.exe would use lots of memory. The strangest one i have found recently was failed backups.
After performing a backup of the mailbox databases the memory utilisation of store.exe dropped from 15.6Gb to 2.9Gb.

The drop in the above screen capture was 1 of 3 drops that occurred during the backup process. So if your store.exe is using heaps of memory and you cannot explain it. Check when your last backup was successful.

Unified Messaging Language Packs

If you are from South Africa or the UK, you'd probably say "what the hell is the pound key?" when the auto assistant on Exchange 2007 asks you to press it.

The default installation of the Unified Messaging role installs the US English Language Pack. If you would like to speak to the auto assistant's sexy and sultry british alter-ego, you need to install the British English Language Pack. She will then prompt you to press the "Hash" key.

To make a date with this British beauty you will need the Exchange 2007 Server media or installation files. The language pack can only be installed from the command prompt.

Exsetup /AddUmLanguagePack:en-GB /sourcedir:d:\Downloads\UmLanguagePacks

Once this has installed the pack, simple open exchange management console. Expand Organization Configuration and then Unified Messaging. Right-Click the UM Dial Plan you would like to change the language for, and select properties. Select the Settings Tab and change the language pack from English(United States) to English(British)

That's it, instant results.

Anonymous relay

To enable anonymous relay on exchange 2007 you need to create a new connector, assign an inbound range of ip addresses to it and then enable relay to the anonymous account.

1) Create the connector
In exchange management console. expand Server Configuration, click Hub Transport. On the right, select the hub transport server that will relay. In the Action pain, click "New Receive Connector". Give it a name, something intuitive preferable. "Anonymous Relay" is good one :) Click Next.
You can leave the next screen alone, unless you plan to use a different IP address for this relay.

Next you need to specify what IP addresses will be allowed to relay through this connector.
Select the default range listed and click Edit. If you are using a single IP address, enter the same address in the start address and end address.
Click OK and then Next. Click New and then Finish to complete this process.

2) The next step actually enables the anonymous relay.
Right-click the new receieve connector, and select properties. One the Authentication Tab remove all the existing ticks and place a tick in the "Externally Secured (for example IPsec)" box. On the Permission group Tab, select Anonymous and Exchange Servers only. Click OK.
Close the exchange management console and open the exchange management shell.
type in the following :

Get-ReceiveConnector "Receive Connector Name" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"

That's it. The ip addresses you specified in the receive connector will be able to relay to any domain.

Exchange 2003 and 2007 cannot exchange mail

If you have created the routing group connector using the Management Shell and you are still unable to route mail between exchange 2003 and exchange 2007, you may find the permission inheritance on the exchange 2003 servers has been disabled.

To correct this, you will first of all need to enable the security tab in exchange 2003 system manager.

http://support.microsoft.com/default.aspx/kb/264733


1. Start Registry Editor (Regedt32.exe).
2. Locate the following key in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Exchange\EXAdmin
3. On the Edit menu, click Add Value, and then add the following registry value:
Value Name: ShowSecurityPageData Type: REG_DWORDRadix: BinaryValue: 1

Once this is done, open Exchange System Manager, navigate to each server in turn and edit the properties. On the security tab, click advanced. Tick the "Allow inheritable permission from the parent ... " check box. Click OK twice.

Incidently, if you run the Best Practices Analyser that come with exchange 2007, and choose the 2007 readiness check, it will report this as a problem area if permission inheritance is not enabled.