Topic Last Modified: 2012-10-29

You can use Setup or Lync Server Management Shell cmdlets to prepare the Active Directory schema. The cmdlet that extends the Active Directory schema is Install-CsAdServerSchema.

Note:
The schema preparation cmdlet (Install-CsAdServerSchema) must access the schema master, which requires that the remote registry service is running and that the remote registry key is enabled. If the remote registry service cannot be enabled on the schema master, you can run the cmdlet locally on the schema master. For details about registry remote access, see Microsoft Knowledge Base article 314837, "How to Manage Remote Access to the Registry," at http://go.microsoft.com/fwlink/p/?linkId=125769.

After you complete schema preparation, manually verify that the schema partition has been replicated before proceeding to forest preparation. For details, see Verifying Schema Replication.

To use Setup to prepare the schema of the current forest

  1. Log on to a server in your forest as a member of the Schema Admins group and with administrator rights on the schema master.

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

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

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

  5. On the License Agreement page, check I accept the terms in the license agreement, and then click OK.

  6. The installer installs the Lync Server Core Components.

  7. When the Deployment Wizard is ready, click Prepare Active Directory, and then wait for the deployment state to be determined.

  8. At Step 1: Prepare Schema, click Run.

  9. On the Prepare Schema page, click Next.

  10. On the Executing Commands page, look for Task status: Completed, and then click View Log.

  11. Under the Action column, expand Schema Prep, look for the <Success> Execution Result at the end of each task to verify that schema preparation completed successfully, close the log, and then click Finish.

  12. Wait for Active Directory replication to complete or force replication.

  13. Manually verify that the schema changes replicated to all other domain controllers. For details, see Verifying Schema Replication.

To use cmdlets to prepare the schema of the current forest

  1. Log on to a computer in the forest as a member of the Schema Admins group and with administrator rights on the schema master.

  2. Install Lync Server Core components as follows:

    1. From the Lync Server 2013 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 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.

    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 2013 Core Components.

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

  4. Run:

    Copy Code 
    Install-CsAdServerSchema [-Ldf <directory where the .ldf file is located>]

    If you do not specify the Ldf parameter, the default value is the Lync Server 2013 installation path that is read from the registry.

    For example:

    Copy Code 
    Install-CsAdServerSchema -Ldf "C:\Program Files\Microsoft Lync Server 2013\Deployment\Setup"

  5. Use the following cmdlet to verify that schema preparation ran to completion.

    Copy Code 
    Get-CsAdServerSchema

    This cmdlet returns a value of SCHEMA_VERSION_STATE_CURRENT if schema preparation was successful.

  6. Wait for Active Directory replication to complete or force replication.

  7. Manually verify that the schema changes replicated to all other domain controllers. For details, see Verifying Schema Replication.

See Also