Exchange Server 2007 / 2010 Transport: 452 4.3.1 Insufficient system resources

 

In my hotel room in Orlando, getting ready for an Exchange 2007 transport presentation tomorrow morning at TechMentor. When trying to telnet to the SMTP port of an Exchange 2007 Hub Transport server, I got the following error:

452 4.3.1 Insufficient system resources

Not a good thing the night before a presentation – Murphy’s law at work again!
The Application Event Log has Event ID 15002 from MSExchangeTransport saying “The resource pressure is constant at High. Statistics… “. The event goes on to tell you that inbound mail submission has stopped, and it’s due to disk space being low on the volume where the queue database is located.

Figure 1: Event ID 15002 logged by MSExchangeTransport
Exchange Server 2007 transport queues are not the familiar .eml files you see in Exchange Server 2003/2000, which reside in the \mailroot\vsi <1>\queue folder (<1> is the instance number of the SMTP virtual server) on the file system. Yes, transport queues have been moved to a JET database of its own.

What’s Back Pressure?

In Exchange Server 2007, the Transport service monitors system resources such as disk space and memory on Transport servers (the Hub Transport and the Edge Transport servers), and stops message submission if it’s running low on these resources. It continues to deliver existing messages in the queue. When resource utilization returns to normal, it resumes message submission. The feature is called Back Pressure.
In this case, Exchange required 4 Gigs of free disk space on the volume where the Queue database was located – I had about 3.95 Gigs. :)

Changes to Back Pressure settings in Exchange Server 2007 SP1

The Back Pressure settings in Exchange Server 2007 RTM stop inbound mailflow if free disk space is below 4 Gigs. This static threshold has been lowered in SP1 to a more realistic 500 MB.

The Resolution

Many configuration options for transport servers are saved in an XML file named EdgeTransport.exe.config (it’s the same file name on both server roles— Edge Transport and Hub Transport) located in \Exchange Server\Bin\.
To get transport to resume submissions, you can use any of the following methods. All of the following require you to edit the EdgeTransport.exe.config file.

1. Disable BackPressure: Although Microsoft doesn’t recommend it, it does provide a way to Disable Back Pressure
2. Tweak BackPressure thresholds: Modify BackPressure parameters to more accurately define what’s high utilization for your deployment or server configurations, as explained in the above docs.
3. Move the queue database to another volume: Another resolution, and the one I used in this case, was to move the queue database to another volume with ample of free space, using the following procedure:
   1. Add the following key in the <AppSettings> section in EdgeTransport.exe.config, as documented in “How to Change the Location of the Queue Database“:
      
      <add key=“QueueDatabasePath” value=”D:\Queue\QueueDB” />
   2. Save the file and restart the Microsoft Exchange Transport service from the Services console or by using the Restart-Service cmdlet (Restart-Service MSExchangeTransport).

Message submission resumes.

Error while installing Exchange 2013

Installation Fail of Exchange 2013 in PrepareAD and Setup.exe

[ERROR] Setup encountered a problem while validating the state of Active Directory: Couldn’t find the Enterprise Organization container.
[08/23/2012 16:50:04.0804] [0] The Exchange Server setup operation didn’t complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[08/23/2012 16:50:04.0804] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, was not found.
[08/23/2012 16:50:04.0804] [0] End of Setup

 More Error details from ExchageSetupLog

[08/23/2012 18:53:19.0615] [0] Setup is choosing a local domain controller…
[08/23/2012 18:53:28.0981] [0] Setup has chosen the local domain controller SRVR2012.WIN12.COM for initial queries
[08/23/2012 18:53:29.0614] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Couldn’t find the Enterprise Organization container.
[08/23/2012 18:53:29.0614] [0] [ERROR] Couldn’t find the Enterprise Organization container.
[08/23/2012 18:53:29.0614] [0] Setup will use the domain controller ”.
[08/23/2012 18:53:29.0614] [0] Setup will use the global catalog ”.
[08/23/2012 18:53:29.0614] [0] Exchange configuration container for the organization is ‘CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=WIN12,DC=COM’.
[08/23/2012 18:53:29.0614] [0] No Exchange organization container was found for the organization. Message: ‘Couldn’t find the Enterprise Organization container.’.
[08/23/2012 18:53:29.0614] [0] Setup will search for an Exchange Server object for the local machine with name ‘SRVR2012′.
[08/23/2012 18:53:29.0723] [0] No Exchange Server with identity ‘SRVR2012′ was found.


CAUSE : 

Generally this problem occurs when unsuccessful installation of Exchange server 2013 found in Active directory Forest.

SOLUTION :

First of all  Delete the Exchange Server Folder – "C:\Program Files\Microsoft\Exchange Server."

1. Log on to the domain controller with administrative credentials.
2. Click Start, click Programs, click Administrative Tools and then click Active Directory Users and Computers.
3. In the Active Directory Users and Computers management console pane, click View from the toolbar menu and select Advanced Features.
4. In the Active Directory Users and Computers management console pane, locate the incorrect, duplicate Microsoft Exchange System Objects container or organizational unit (OU).
5. Verify the incorrect, duplicate Microsoft Exchange System Objects container or OU does not contain valid Active Directory objects.
6. Right-click the incorrect, duplicate Microsoft Exchange System Objects container or OU and then click Delete.
7. Confirm the deletion by clicking Yes in the Active Directory dialog box.
   
   
   For More information Please visit microsoft Technet website :
   http://technet.microsoft.com/en-us/library/aa998138%28v=exchg.80%29.aspx
   
   

   Now Run the setup again. :) :)

   
    

Microsoft Exchange 2010 OWA not able to Open.

Hello Friends,

Today i will show you how to resolve Outlook Web Access isses in Microsoft Exchange 2010 after installing Updates / SP upgrade.

After Installing Service Pack of Update OWA stops working with below error.

Error :

Microsoft.Exchange.Clients.Owa.Core.OwaThemeManagerInitializationException
Exception message: Couldn’t find a base theme (folder name=base)

Solution :

1) Open Microsoft Exchange Power Shell
2) Go to "C:\Program Files\Microsoft\Exchange Server\V14\Bin"
3) run CAS Powershell Script by using this command "./UpdateCas.ps1"
4) Restart IIS

And it's Done!!!!

hope this solution helps you..please write any suggetions or correct me if any correction needed.

Have a Good Day!!!!


 

how to change Default SMTP port 25 to custom port in Exchange 2010

Problem:

How do I change the port on MS Exchange 2010 SMTP Send Connector?

Solution:

By default the SMTP Send Connector is set to use port 25 with a Smart Host. However if you need to change the port from port 25 to port 587 then follow the below instructions.
Launch the Exchange Management Shell (EMS).
Use the following command in the Exchange Management Shell to get the current Connector information.

Get-SendConnector

To change the port to 587 use the following command

Set-SendConnector "Your SMTP Send Connector" -Port 587

Greetings,,
free spam filter

The Exchange Management Shell is missing and how to recover

Hello Friends,

Recently i have installed Microsoft Exchange 2010 on Server 2008 R2 with fully updated OS, All configuration went well and tested all services,OWA, Microsoft Console, etc...

After all necessary Testing i have decided to Upgrade Exchange 2010 with Service pack 2, then suddenly Outlook Web Access Was not working properly with below error.

Error : 

Outlook Web App didn’t initialize. If the problem continues, please contact your helpdesk.
Couldn’t find a base theme (folder name=base)

Problem: After installing Service Pack 2 for Exchange Server 2010, the Exchange Management Shell is missing.

Cause: Missing certain .ps1 scripts from the bin directory, removed during SP2 setup.

Resolution: There is no resolution at this time.

Workaround:

1.	Verify that the ConnectFunctions.ps1 , RemoteExchange.ps1 and CommonConnectFunctions.ps1 files are present in the %ExchangeInstallPath%\bin directory. NOTE : If these files are missing, you can copy the files from the Exchange Server 2010 Service Pack 1 installation media to the %ExchangeInstallPath%\bin directory. These files are present in the \setup\serverroles\common folder.
2.	Right click an open area on the Desktop, click New , click Shortcut .
3.	In the Type the location of the item , type in the text below: %SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -command ". '%ExchangeInstallPath%\bin\RemoteExchange.ps1'; Connect-ExchangeServer -auto"
4.	Name the shortcut Exchange Management Shell and click Finish .
5.	Right click the Exchange Management Shell shortcut, click Properties and remove the text from Start In field on the Shortcut tab.
6.	On the Shortcut tab, click Change Icon , click Browse and type in the text below: %SystemRoot%\Installer\{4934D1EA-BE46-48B1-8847-F1AF20E892C1}\PowerShell.exe
7.	Select the Exchange icon and click OK .
8.	Click Apply and click OK .
9.	Copy the new Exchange Management Shell shortcut to this location: %systemdrive%\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft Exchange Server 2010 Run this Command to fix Outlook Web Access Problem : 1) Open Exchange Management Shell and run Power shell script which is located on below path.. C:\Program Files\Microsoft\Exchange Server\V14\Bin\UpdateCas.ps1  Good Luck...

HOWTO Install Exchange 2010 - Step by Step

Install the Windows Server 2008 R2 operating system prerequisites

http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx#WS08R2

On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack

  

http://www.microsoft.com/downloads/details.aspx?FamilyId=60C92A37-719C-4077-B5C6-CAC34F4227CC&displaylang=en

1. On the Start Menu, navigate to All Programs, then Accessories, then Windows PowerShell. Open an elevated Windows PowerShell console, and run the following command:

Import-Module ServerManager

2. Use the Add-WindowsFeature cmdlet to install the necessary operating system components:

For a server that will have the typical installation of Client Access, Hub Transport, and the Mailbox role:

Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart

Restart

3. After the system has restarted, log on as an administrator, open an elevated Windows PowerShell console, and configure the Net.Tcp Port Sharing Service for Automatic startup by running the following command:

Set-Service NetTcpPortSharing -StartupType Automatic

Prepare Active Directory

http://technet.microsoft.com/en-us/library/bb125224(EXCHG.140).aspx

Prerequisites

• Your domains and the domain controllers must meet the system requirements in the "Network and Directory Servers" section of Exchange 2010 System Requirements.
• In each domain in which you will install Exchange 2010, you must have at least one domain controller running Windows Server 2003 Service Pack 1 (SP1).
• If you are running the release to manufacturing (RTM) version of Exchange 2010 Setup.com, in each domain (including child domains) where you have the Exchange Enterprise Servers and Exchange Domains Servers security groups and therefore must run Setup /PrepareLegacyExchangePermissions, you must have at least one domain controller running Windows Server 2003 SP1 or a later version.
• If you are deploying a new Exchange organization, and you are preparing your Active Directory schema and domains by using a computer running Windows Server 2008, you must first install the Active Directory management tools on the Windows Server 2008 computer prior to preparing the schema or domains. To do this, run the following command.

ServerManagerCmd -i RSAT-ADDS

• The computers on which you will install Exchange 2010 must meet the system requirements. For details, see Exchange 2010 System Requirements.

Prepare Active Directory and domains

1.        If you have any computers in your organization running Exchange 2003, open a Command Prompt window, and then run one of the following commands:

o    To prepare legacy Exchange permissions in every domain in the forest that contains the Exchange Enterprise Servers and Exchange Domain Servers groups, run the following command.
setup /PrepareLegacyExchangePermissions.or setup /pl

o    To prepare legacy Exchange permissions in a specific domain, run the following command.
setup /PrepareLegacyExchangePermissions: < FQDN of domain you want to prepare > or setup /pl:<FQDN of domain you want to prepare>

Note:

You can skip this step and prepare the legacy Exchange permissions as part of Step 2 or Step 3. The advantages of running each step separately are that you can run each step with an account that has the minimum permissions required for that step, and you can verify completion, success, and replication before continuing to the next step.

1.        Note the following:

o    To run this command to prepare every domain in the forest, you must be a member of the Enterprise Admins group. To run this command to prepare a specific domain, or if the forest has only one domain, you must be delegated the Exchange Organization Management role, and you must be a member of the Domain Admins group in the domain that you will prepare.

o    If you don't specify a domain, the domain in which you run this command must be able to contact all domains in the forest. If the server can't contact a domain that must have legacy Exchange permissions prepared, it prepares the domains that it can contact, and then returns an error message that it was unable to contact some domains.

o    You can run this command from any 64-bit Windows Server 2003 SP1 server in the forest.

o    You must run this command on a computer in the same domain and in the same Active Directory site as the schema master. Setup will make all configuration changes to the schema master to avoid conflicts because of replication latency. For information on how to identify the schema master, see Identify the schema master. To change site membership for the schema master:

5. For information on how to transfer

o After you run this command, you must wait for the permissions to replicate across your Exchange organization before continuing to the next step. If the permissions haven't replicated, the Recipient Update Service on your Exchange Server 2003 computers could fail. The amount of time that replication takes depends on your Active Directory site topology.

Note:

To track the progress of Active Directory replication, you can use the Active Directory Replication Monitor tool (replmon.exe), which is installed as part of the Microsoft Windows Server 2003 Support Tools Setup. By default, it's located at "%programfiles%\support tools\." Add your domain controllers as monitored servers so that you can track the progress of replication throughout the domain.

1.        For detailed information about the permissions set by this command, see Preparing Legacy Exchange Permissions.

From a Command Prompt window, run the following command.
setup /PrepareSchema or setup /ps

Note:

You can skip this step and prepare the schema as part of Step 3.

Important:

You must not run this command in a forest in which you don't plan to run setup /PrepareAD. If you do, the forest will be configured incorrectly, and you won't be able to read some attributes on user objects.

Note:

It isn't supported to use the LDIF Directory Exchange tool (LDIFDE) to manually import the Exchange 2010 schema changes. You must use Setup to update the schema.

This command performs the following tasks:

o Connects to the schema master and imports LDAP Data Interchange Format (LDIF) files to update the schema with Exchange 2010 specific attributes. The LDIF files are copied to the Temp directory, and then deleted after they are imported into the schema.

o If you haven't completed Step 1, setup /PrepareSchema will automatically perform the PrepareLegacyExchangePermissions step.

Note the following:

o If you want to verify the updates to the schema before the changes are replicated to other servers in the domain, you must disable outbound replication on the computer on which you run the command before you run it, and then enable outbound replication after you have verified that the import completed successfully.

o To run this command, you must be a member of the Schema Admins group and the Enterprise Admins group.

o You must run this command on a 64-bit computer in the same domain and in the same Active Directory site as the schema master.

o If you haven't completed Step 1, setup /PrepareSchema will automatically perform the PrepareLegacyExchangePermissions step. To complete the PrepareLegacyExchangePermissions step, the domain in which you run this command must be able to contact all domains in the forest. The advantages of running each step separately are that you can run each step with an account that has the minimum permissions required for that step, and you can verify completion, success, and replication before continuing to the next step.

o If you use the /DomainController parameter with this command, you must specify the domain controller that is the schema master.

o After you run this command, you should wait for the changes to replicate across your Exchange organization before continuing to the next step. The amount of time this takes is dependent upon your Active Directory site topology.

Note:

To track the progress of Active Directory replication, you can use the Active Directory Replication Monitor tool (replmon.exe), which is installed as part of the Windows Server 2003 Support Tools Setup. By default, it's located at "%programfiles%\support tools\." Add your domain controllers as monitored servers so that you can track the progress of replication throughout the domain.

For more information, see Exchange Server Changes to the Active Directory Schema.

From a Command Prompt window, run the following command.
setup /PrepareAD [/OrganizationName: <organization name> ] or setup /p [/on:<organization name>]
This command performs the following tasks:

o If the Microsoft Exchange container doesn't exist, this command creates it under CN=Services,CN=Configuration,DC=<root domain>.

o If no Exchange organization container exists under CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain >, you must specify an organization name by using the /OrganizationName parameter. The organization container will be created with the name that you specify.
The Exchange organization name can contain only the following characters:
A through Z
a through z
0 through 9
Space (not leading or trailing)
Hyphen or dash
The organization name can't contain more than 64 characters. The organization name can't be blank. If the organization name contains spaces, you must enclose the name in quotation marks.

o Verifies that the schema has been updated and that the organization is up to date by checking the objectVersion property in Active Directory. The objectVersion property is in the CN=<your organization>, CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain> container. The objectVersion value for the RTM version of Exchange Server 2007 is 10666.

o If they don't exist, creates the following containers and objects under CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>. These are required for Exchange 2010.
CN=Address Lists Container,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Addressing,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Administrative Groups,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Client Access,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Connections,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=ELC Folders Container,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=ELC Mailbox Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Global Settings,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Mobile Mailbox Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Recipient Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=System Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Transport Settings,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM AutoAttendant,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM DialPlan,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM IPGateway Container,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM Mailbox Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>

o If it doesn't exist, creates the default Accepted Domains entry, based on the forest root namespace, under CN=Transport Settings,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>.

o Assigns specific permissions throughout the configuration partition.

o Imports the Rights.ldf file. This adds the extended rights required for Exchange to install into Active Directory.

o Creates the Microsoft Exchange Security Groups organizational unit (OU) in the root domain of the forest and assigns specific permissions on this OU.

o Creates the following universal security groups (USGs) within the Microsoft Exchange Security Groups OU:
Exchange Organization Administrators
Exchange Recipient Administrators
Exchange Servers
Exchange View-Only Administrators
Exchange Public Folder Administrators (New in Exchange Server 2007 Service Pack 1)
ExchangeLegacyInterop

o Adds the new USGs that are within the Microsoft Exchange Security Groups OU to the otherWellKnownObjects attribute stored on the CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain> container.

o Creates the Unified Messaging Voice Originator contact in the Microsoft Exchange System Objects container of the root domain.

o Prepares the local domain for Exchange 2010. For information about what tasks are completed to prepare a domain, see Step 4.

Note the following:

o To run this command, you must be a member of the Enterprise Admins group.

o The computer where you run this command must be able to contact all domains in the forest on port 389.

o You must run this command on a computer in the same domain and in the same Active Directory site as the schema master. Setup will make all configuration changes to the schema master to avoid conflicts because of replication latency.

o If you haven't completed Step 1, setup /PrepareAD will automatically perform the PrepareLegacyExchangePermissions step. To complete the PrepareLegacyExchangePermissions step, the domain in which you run this command must be able to contact all domains in the forest. If you are also a member of the Schema Admins group, and if you haven't completed Step 2, setup /PrepareAD will automatically perform the PrepareSchema step. The advantages of running each step separately are that you can run each step with an account that has the minimum permissions required for that step, and you can verify completion, success, and replication before continuing to the next step.

o After you run this command, you should wait for the changes to replicate across your Exchange organization before continuing to the next step. The amount of time this takes is dependent upon your Active Directory site topology. 

Note:

To track the progress of Active Directory replication, you can use the Active Directory Replication Monitor tool (replmon.exe), which is installed as part of the Windows Server 2003 Support Tools Setup. By default, it is located at "%programfiles%\support tools\." Add your domain controllers as monitored servers so that you can track the progress of replication throughout the domain.

o To verify that this step completed successfully, make sure that there is a new OU in the root domain called Microsoft Exchange Security Groups. This OU should contain the following new Exchange USGs:
Exchange Organization Administrators
Exchange Recipient Administrators
Exchange View-Only Administrators
Exchange Servers
Exchange Public Folder Administrators (new in Exchange 2007 SP 1)
ExchangeLegacyInterop

From a Command Prompt window, run one of the following commands:

o Run setup /PrepareDomain or setup /pd to prepare the local domain. Note that you don't need to run this in the domain where you ran Step 3. Running setup /PrepareAD prepares the local domain.

o Run setup /PrepareDomain:<FQDN of domain you want to prepare> to prepare a specific domain.

o Run setup /PrepareAllDomains or setup /pad to prepare all domains in your organization.

These commands perform the following tasks:

o Sets permissions on the domain container for the Exchange Servers, Exchange Organization Administrators, Authenticated Users, and Exchange Mailbox Administrators.

o If this is a new organization, creates the Microsoft Exchange System Objects container in the root domain partition in Active Directory and sets permissions on this container for the Exchange Servers, Exchange Organization Administrators, and Authenticated Users. This container is used to store public folder proxy objects and Exchange-related system objects, such as the mailbox database's mailbox.

o Sets the objectVersion property in the Microsoft Exchange System Objects container under DC=<root domain>. This objectVersion property contains the version of domain preparation. The version for Exchange 2007 RTM is 10628.

o Creates a new domain global group in the current domain called Exchange Install Domain Servers. The command places this group in the Microsoft Exchange System Objects container. It also adds the Exchange Install Domain Servers group to the Exchange Servers USG in the root domain.

Note:

The Exchange Install Domain Servers group is used if you install Exchange 2010 in a child domain that is an Active Directory site other than the root domain. The creation of this group allows you to avoid installation errors if group memberships haven't replicated to the child domain.

o Assigns permissions at the domain level for the Exchange Servers USG and the Exchange Recipient Administrators USG.

Note the following:

o For domains that are in an Active Directory site other than the root domain, /PrepareDomain might fail with the following messages:
"PrepareDomain for domain <YourDomain> has partially completed. Because of the Active Directory site configuration, you must wait at least 15 minutes for replication to occur, and run PrepareDomain for <YourDomain> again."
"Active Directory operation failed on <YourServer>. This error is not retriable. Additional information: The specified group type is invalid.
Active Directory response: 00002141: SvcErr: DSID-031A0FC0, problem 5003 (WILL_NOT_PERFORM), data 0
The server cannot handle directory requests."
If you see these messages, wait for or force Active Directory replication between this domain and the root domain, and then run /PrepareDomain again.

o To run setup /PrepareAllDomains, you must be a member of the Enterprise Admins group.

o To run setup /PrepareDomain, if the domain that you are preparing existed before you ran setup /PrepareAD, you must be a member of the Domain Admins group in the domain. If the domain that you are preparing was created after you ran setup /PrepareAD, you must be a member of the Exchange Organization Administrators group, and you must be a member of the Domain Admins group in the domain.

o You must run this command in every domain in which you will install Exchange 2007. You must also run this command in every domain that will contain mail-enabled users, even if the domain doesn't have Exchange 2007 installed.

To verify that this step completed successfully, confirm the following:

o You have a new global group in the Microsoft Exchange System Objects container called Exchange Install Domain Servers.

Note:

To view the Microsoft Exchange System Objects container in Active Directory Users and Computers, on the View menu, click Advanced Features.

o The Exchange Install Domain Servers group is a member of the Exchange Servers USG in the root domain.

o On each domain controller in a domain in which you will install Exchange 2010, the Exchange Servers USG has permissions on the Domain Controller Security Policy\Local Policies\User Rights Assignment\Manage Auditing and Security Log policy.

Install Exchange Server 2010