Table 4 shows the attributes that must be mapped from a user object in the user forest to a corresponding disabled user object in the resource forest using the example user, User A.
Table 4. Attributes on User and Contact Objects
Attribute | User A in User Forest | Disabled user account for User A in a Resource Forest |
---|---|---|
Cn |
Dylan |
Dylan |
ObjectSID Note In a deployment that includes Microsoft Exchange Server, set the ObjectSID attribute to the value from the msExchMasterAccountSID attribute. |
sidDylan |
|
msRTCSIP-OriginatorSID |
|
sidDylan |
msRTCSIP-TargetHomeServer |
|
|
telephoneNumber |
555-1234 |
555-1234 |
displayName |
Dylan Miller |
Dylan Miller |
givenName |
Dylan |
Dylan |
Surname |
Miller |
Miller |
physicalDeliveryOfficeName |
4500 |
4500 |
l (city) |
Redmond |
Redmond |
st (state) |
WA |
WA |
Country |
U.S.A |
U.S.A |
Title |
Director |
Director |
|
dylan@contoso.com |
dylan@contoso.com |
Company |
Contoso |
Contoso |
Note: |
---|
In resource forest deployments with Microsoft Exchange Server, all attributes are already populated except for the ones beginning with the ms-RTC-SIP prefix. Populate these attributes using the SID Mapping Tool, as described in Use the SID Mapping Tool to Populate Attributes in a Resource Forest. |
In resource forest deployments without Exchange Server, you must manually populate the required attributes on each disabled user account in your resource forest. This method can introduce problems that are difficult to fix. In these deployments, use the Central Forest topology instead. For more information, see Deploying Office Communications Server 2007 R2 in a Central Forest Topology.