Schema Extensions
,To provide the necessary attributes used by Lync Server, it is necessary to extend the schema with the provided extensions. This process is easiest to run on a system destined to be a Lync Server, and by someone who is currently a member of the Schema Administrators group must perform it. If you add your account to Schema Administrators for installing Lync Server, be sure to log off and on to ensure you have a Kerberos ticket that reflects the recent group membership change. Prior to extending the schema, first install the following components:
• .NET 3.5 SP1
• Active Directory Domain Services (does not need to be promoted)
From the Lync Server installation media, follow these steps:
1. Launch Setup.exe.
2. When the wizard displays, browse to your intended installation location. Choose whether to check for updates, and then click OK.
3. When prompted, carefully read the software license terms, and then click the I accept the terms in the license agreement option if you agree to the terms. Then click OK.
4. When the Deployment Wizard launches, it determines the current state of the environment and prompts you for installations as needed. In the case of a fresh installation, you are offered the opportunity to prepare Active Directory. Click Prepare Active Directory, as shown in Figure 10.1.
Figure 10.1 Running the Deployment Wizard
5. Assuming the prerequisites are met, click Run on Step 1: Prep Schema, which will launch the wizard shown in Figure 10.2.
Figure 10.2 Preparing the Schema
6. Click Next.
7. When the commands are executed, click Finish.
8. Using tools such as Repadmin or ADSIEDIT, spot check DCs to ensure that the updated schema partition has replicated.
New Active Directory classes created include
• msRTCSIP-GlobalTopologySettings—This class is a container that holds global topology setting objects.
• msRTCSIP-GlobalTopologySetting—The local global topology setting object.
• msRTCSIP-ConnectionPoint-Generic—SCP to specify computer as a Live Lync Server.
New Active Directory attributes include
• msRTCSIP-TenantId—This attribute is a unique identifier of the tenant. This identifier should be unique across all tenants.
• msRTCSIP-UserPolicies—This attribute is used to store name-value pairs.
• msRTCSIP-OwnerUrn—This attribute is the Uniform Resource Name (URN) of the owner for the application contact.
• msRTCSIP-TargetUserPolicies—This attribute is used to store name-value pairs for target policies on a Lync Server user.
• msRTCSIP-DeploymentLocator—This attribute is used in a split-domain topology and contains a fully qualified domain name (FQDN).
• msRTCSIP-PrivateLine—This attribute contains the device ID of a private line device.
• msRTCSIP-AcpInfo—This attribute is used to store user audio conferencing provider information.
• msRTCSIP-GroupingID—This attribute is a unique identifier of a group, used to group address book entries.
• ms-Exch-UC-Voice-Mail-Settings—This multivalued attribute holds voice mail settings. This attribute is shared with Exchange Unified Messaging (UM).
The following Active Directory classes are modified to add a mayContain:
• Organizational-Unit
• add mayContain msRTCSIP-TenantId
• User
• add mayContain msRTCSIP-AcpInfo
• add mayContain msRTCSIP-GroupingID
• add mayContain msRTCSIP-ApplicationOptions
• add mayContain msRTCSIP-OwnerUrn
• add mayContain msRTCSIP-UserPolicies
• add mayContain msRTCSIP-TargetUserPolicies
• add mayContain msRTCSIP-TenantId
• Contact
• add mayContain msRTCSIP-AcpInfo
• add mayContain msRTCSIP-OwnerUrn
• add mayContain msRTCSIP-GroupingID
• add mayContain msRTCSIP-UserPolicies
• add: mayContain msRTCSIP-TargetUserPolicies
• add mayContain msRTCSIP-TenantId
• add mayContain msRTCSIP-GroupingID
• add mayContain msRTCSIP-TenantId
• msRTCSIP-GlobalTopologySetting
• add mayContain msRTCSIP-BackEndServer
• add mayContain msRTCSIP-ServerVersion
• add mayContai-msRTCSIP-ExtensionData
• Mail-Recipient
• add mayContain ms-Exch-UC-Voice-Mail-Settings