• Article

Appendix A: Attribute Synchronization in Cross Forests

Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

If your organization deployed Microsoft Exchange Server 2007 in a cross-forest topology, you must implement synchronization of the following attributes for Office Communications Server 2007 when deployed in a central forest.

You must synchronize the contact object in the central forest and the mailbox in the Exchange Server forest.

Attributes Requiring Synchronization

The following attributes must be synchronized from the user object to the contact object.

  • ObjectSid

  • telephoneNumber

  • displayName

  • givenName

  • sn (surname)

  • physicalDeliveryOfficeName

  • l (city)

  • st (state)

  • Country

  • Title

  • Mail

  • Company

  • Cn

Important

The primary user address (msRTCSIP-PrimaryUserAddress) of the contact must be added to the list of proxy addresses in the ProxyAddresses attribute of the mailbox object. This is required for integration with Outlook and other Microsoft Office products.

Table 5 shows how attributes are mapped from a user object to a contact object using the example user, User A.

Table 5 The attributes on the User and Contact objects

Attribute User A Contact for User A

Cn

UserA

UserA

ObjectSID

sidA

 

ms-RTC-SIP-OriginatorSID

 

sidA

telephoneNumber

555-1234

555-1234

displayName

User A

User A

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

Mail

userA@contoso.com

userA@contoso.com

Company

Contoso

Contoso

ProxyAddresses

<proxy addresses>

<proxy addresses>

Group Attributes

The following attributes must be synchronized across forests for distribution group expansion to work in a cross-forest scenario:

  • ObjectSid

  • Mail

  • displayName

  • groupType

Table 6 shows how attributes are mapped from a user object to a contact object using the example group, Group A.

Table 6 The attributes on the Group and Contact objects

Attribute Group A Contact for Group A

Cn

GroupA

GroupA

ObjectSID

sidA

 

ms-RTC-SIP-OriginatorSID

 

sidA

displayName

GroupA

GroupA

groupType

Distribution Group - Universal

 

ms-RTC-SIP-SourceObjectType

 

Distribution Group - Universal

Mail

GroupA@contoso.com

GroupA@contoso.com

Distinguished name (DN)

<distinguished name of group A>

 

msRTCSIP-SourceObjectDN

 

<Distinguished name of group A>

For group to contact synchronization, the attribute msRTCSIP-SourceObjectDN on the contact should be populated with the DN (distinguished name) of the group that is used in the forest where the group is managed.