Topic Last Modified: 2013-04-16
You can use Setup or Lync Server Management Shell cmdlets to prepare domains. The cmdlet that prepares a domain is Enable-CsAdDomain.
Domain preparation is the final step in preparing Active Directory Domain Services for Lync Server 2013.
To use Setup to prepare domains
-
Log on to any server in the domain as a member of the Domain Admins group.
-
From the Lync Server 2013 installation folder or media, run Setup.exe to start the Lync Server Deployment Wizard.
-
Click Prepare Active Directory, and then wait for the deployment state to be determined.
-
At Step 5: Prepare Current Domain, click Run.
-
On the Prepare Domain page, click Next.
-
On the Executing Commands page, look for Task status: Completed, and then click View Log.
-
Under the Action column, expand Domain Prep, look for a <Success> Execution Result at the end of each task to verify that domain preparation completed successfully, close the log, and then click Finish.
-
Wait for Active Directory replication to complete or force replication to all the domain controllers listed in the Active Directory Sites and Services snap-in for the forest root domain controller.
To use cmdlets to prepare the domain
-
Log on to any server in the domain as a member of the Domain Admins group.
-
Install Lync Server Core components as follows:
-
From the Lync Server 2013 installation folder or media, run Setup.exe to start the Lync Server Deployment Wizard.
-
If you are prompted to install the Microsoft Visual C++ Redistributable, click Yes.
-
The Lync Server 2013 Setup dialog box prompts you for a location to install the Lync Server files. Choose the default location or Browse to a location of your choice, and then click Install.
-
On the License Agreement page, check I accept the terms in the license agreement, and then click OK. The installer installs the Lync Server 2013 Core Components.
-
-
Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2013, and then click Lync Server Management Shell.
-
Run:
Copy Code Enable-CsAdDomain [-Domain <DomainFQDN>]
For example:
Copy Code Enable-CsAdDomain -Domain domain1.contoso.net
If you do not specify the Domain parameter, the default is the local domain.
-
Verify that domain preparation was successful. Run:
Copy Code Get-CsAdDomain [-Domain <Domain FQDN>] [-DomainController <Domain controller FQDN>] [-GlobalCatalog <Global catalog server FQDN>] [-GlobalSettingsDomainController <Domain controller FQDN where global settings are stored>]
For example:
Copy Code Get-CsAdDomain -Domain domain1.contoso.net -GlobalSettingsDomainController dc01.domain1.contoso.com
Note: The parameter GlobalSettingsDomainController allows you to indicate where global settings are stored. If your settings are stored in the System container (which is typical with upgrade deployments that have not had the global settings migrated to the Configuration container), you define a domain controller in the root of your Active Directory forest. If the global settings are in the Configuration container (which is typical with new deployments or upgrade deployments where the settings have been migrated to the Configuration container), you define any domain controller in the forest. If you do not specify this parameter, the cmdlet assumes that the settings are stored in the Configuration container and refers to any domain controller in AD DS. If you do not specify the Domain parameter, the default is the local domain.
This cmdlet returns a value of LC_DOMAINSETTINGS_STATE_READY if domain preparation was successful.