MS UC 2013-2-Deploy Microsoft Exchange Server 2013-2-Prepare

Prepare Active Directory and Domains

• Estimated time to complete: 10-15 minutes (not including Active Directory replication) or more, depending on organization size and number of child domains
• The computers on which you plan to install Exchange 2013 Preview must meet the system requirements. For details, see Exchange 2013 System Requirements.
• Your domains and the domain controllers must meet the system requirements in “Network and directory servers” in Exchange 2013 System Requirements.
• In each domain in which you install Exchange 2013 Preview, you must have at least one domain controller running any of the following:
  • Windows Server 2012
  • Windows Server 2008 Standard or Enterprise (32-bit or 64-bit)
  • Windows Server 2008 R2 Standard or Enterprise
• For multiple domain organizations running the following /Prepare* commands, we recommend the following:
  • Run the /Prepare* commands from an Active Directory site with an Active Directory server from every domain.
  • Run the first server role installation from an Active Directory site with a writeable global catalog server from every domain.
  • Verify that replication of objects from the preceding actions is completed on the global catalog server in the Active Directory site before installing the first Exchange 2013 Preview server to that site.
• If you run the Exchange 2013 Preview Setup wizard with an account that has the permissions required (Schema Admins, Domain Admins, and Enterprise Admins) to prepare Active Directory and the domain, the wizard automatically prepares Active Directory and the domain. For more information, see Install Exchange 2013 Using the Setup Wizard. However, you must first install the Active Directory management tools on the computer prior to preparing the schema or domains. To do this, run one of the following commands.
  • On Windows Server 2008 R2 SP1 computers, run the following command in a Windows PowerShell session:

• • On Windows Server 2012 computers, run the following command in a Windows PowerShell session:

• You must specify the /IAcceptExchangeServerLicenseTerms parameter when you run setup.exe to accept the Exchange 2013 Preview license terms.
• For information about keyboard shortcuts that may apply to the procedures in this topic, see Keyboard Shortcuts in Exchange 2013.

Note:

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

Important:

If you have multiple forests in your organization, make sure that you run your forest preparation from the correct Exchange forest. Setup preparation makes configuration changes to your forest, and it could configure a non-Exchange forest incorrectly.

2.

Note:

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

This command performs the following tasks:

o Creates a 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 2013 Preview 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.

• In the Schema naming context, verify that the rangeUpper property on ms-Exch-Schema-Verision-Pt is set to 15132.
• In the Configuration naming context, verify that the objectVersion property in the CN=<your organization>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain> container is set to 15448.
• In the Default naming context, verify that the objectVersion property in the Microsoft Exchange System Objects container under DC=<root domain is set to 13236.

You can also check the Exchange setup log to verify that Active Directory preparation has completed successfully. For more information, see
Verify an Exchange 2013 Installation
.

Note:

You won’t be able to use the Get-ExchangeServer cmdlet mentioned in the Verify an Exchange 2013 Installation topic until you’ve completed the installation of at least one Mailbox server role and one Client Access server role in an Active Directory site.