The Colleagues Container has a container ID value of 200. The default access control list contains a single entry for enterprise network users. Non-private category instances published to this container are visible to all the users of the same enterprise network by default.
The following category instances are published to this container.
Category Instances Published by Microsoft Lync Server 2010
Contains the local user’s identity consisting of the display name and e-mail address as provisioned from the Active Directory. The following is an example of this category instance.
Contains the availability number of the local user’s current state[@type='aggregateState'] making the local user’s presence status available to the container members using legacy clients. The following is an example of this category instance.
This category instance is meant to contain the local user’s contact information as constructed from the user-configurable options, such as the local user’s home phone number. This effectively blocks members of this container from accessing such information.
Contains the local user’s company description and job title, which are obtained from the underlying Lync Server 2010 Address Book Server. This is shown in the following example.
Contains the server-provisioned voice mail URL of the local user when the user has unified communications (UC) enabled. This is shown in the following example.
Contains the local user’s job title and display photo. This causes the local user’s photo displayed to members of this container. This is shown in the following example.
Notice that the local user’s free-busy information is visible to the Colleagues, Workgroup, and Friends and Family container members, while it is not visible to the External Contacts container members.
Contains an empty value when the local user is not in the Do not disturb availability mode and contains an availability number of 9500 when the user is in the Do not disturb mode. This is shown in the following example.
A hash dependent of the local user’s email address
Published during an OOF period, this instance contains an out-of-facility (OOF) note the local user set in Microsoft Outlook as shown in the following example.
<note xmlns="https://schemas.microsoft.com/2006/09/sip/note">
<body type="OOF"
uri="johnd@exchange.contoso.com"
startTime="2010-06-22T19:00:00Z"
endTime="2010-06-23T19:00:00Z">A OOF message set in Outlook</body>
</note>
Note
Notice that OOF note is visible to the Workgroup container members, while it is not visible to the External Contacts container members.
Contains a local user’s previously published personal note, as shown in the following example.
<noteHistory xmlns="https://schemas.microsoft.com/2006/09/sip/note">
<body type="personal" uri="">Out to lunch</body>
</noteHistory>
Notice that noteHistory is published to Colleagues container, but not to the External Contacts container. By default, there can be up to three noteHistory category instances and they correspond to the three most recent note instances published before the current one.
One or more routing category instances containing the user-configurable routing rules to handle incoming calls from a member of this container. The following is an example of such an instance.