Topic Last Modified: 2011-01-31

Use the Enable-CsAdDomain cmdlet to prepare the domains for Lync Server 2010.

To use cmdlets to prepare the domain

  1. Log on to any server in the domain as a member of the Domain Admins group.

  2. Install Lync Server Core components as follows:

    1. From the Lync Server 2010 installation folder or media, run Setup.exe to start the Lync Server Deployment Wizard.

    2. If you are prompted to install the Microsoft Visual C++ Redistributable, click Yes.

    3. The Microsoft Lync Server 2010 Setup dialog box prompts you for a location to install the Lync Server 2010 files. Choose the default location or Browse to a location of your choice, and then click Install.

    4. On the License Agreement page, check I accept the terms in the license agreement, and then click OK. The installer installs the Lync Server 2010 Core Components.

  3. Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.

  4. 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.

To verify that domain preparation was successful

  1. Log on to a computer that is joined to a domain and on which you have the appropriate administrator rights and permissions.

  2. Open the Lync Server Management Shell console, and then run:

    Copy Code
    Get-CsAdDomain [-Domain <Fqdn>] [-DomainController <Fqdn>] [-GlobalCatalog <Fqdn>] [-GlobalSettingsDomainController <Fqdn>] 
    

    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 setting 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 Active Directory Domain Services (AD DS).

    If you do not specify the Domain parameter, the default is the local domain.

    This cmdlet returns a value of LC_DOMAIN_SETTINGS_STATE_READY if domain preparation was successful.

See Also

Other Resources

Running Domain Preparation