Container for Remote Access

Microsoft Lync 2010 uses the following containers to publish category instances for other (remote) users or entities to receive the presence data. Microsoft Lync Server 2010 can also publish presence data to these containers on behalf of the local user. The remote users or entities allowed to receive the published presence data are specified as members of the containers. The membership is specified by a list of SIP URIs for individual users or domains. The membership can also be specified by a membership type. Supported membership types include “everyone”, “sameEnterprise”, or “publicCloud”. They are defined in the ContainerManifest.XSD schema file.

Container Id	Friendly Name	Default ACEs	Description
0	Default	Unspecified	This is the default container to control access to the local user’s non-private presence publication by remote users who are not a member of any other containers. The only non-private presence information published to this container is the identity of the local user. It is represented by a contactCard category instance containing only the identity information that is comprised of the user’s display name and his or her email address. The server publishes the display name and email address on behalf of the local user regardless of whether the user is signed in or not. The publication of this information ensures that the local user can be discovered by any other user or entity even when the local user is not signed in. This container also contains private routing and dndState category instances that are used, respectively, to determine how to forward incoming calls made by anyone not assigned to any of the other containers and how to block the incoming calls when the local user is in the Do Not Disturb state.
100	External Contacts	Federated	Non-private category instances placed in this container are visible to federated users. Non-private category instances are calendarData, contactCard, legacyInterop, note, noteHistory, services and state. This container also contains private routing and dndState category instances that are used, respectively, to determine how to forward incoming calls made by anyone within the membership scope of this container and how to block the incoming calls when the local user is in the Do Not Disturb state.
200	Colleagues	sameEnterprise	Non-private category instances placed in this container are visible to the users within same enterprise network of the container owner. Non-private category instances calendarData, contactCard, legacyInterop, note, noteHistory, services and state. This container also contains private routing and dndState category instances that are used, respectively, to determine how to forward incoming calls made by anyone within the membership scope of this container and how to block the incoming calls when the local user is in the Do Not Disturb state.
300	Workgroup	Unspecified	The local user must designate specific users or domains as members of this container. Non-private category instances calendarData, contactCard, legacyInterop, note, noteHistory, services and state. This container also contains routing and dndState category instances that are used, respectively, to determine how to forward incoming calls made by anyone within the membership scope of this container and how to block the incoming calls when the local user is in the Do Not Disturb state.
400	Friends and Family	Unspecified	The local user must designate specific users or domains as members of this container. Non-private category instances calendarData, contactCard, legacyInterop, note, noteHistory, services and state. This container also contains routing and dndState category instances that are used, respectively, to determine how to forward incoming calls made by anyone within the membership scope of this container and how to block the incoming calls when the local user is in the Do Not Disturb state.
32000	Blocked Contacts	Unspecified	By default, empty category instances of calendarData, contactCard, note, noteHistory, and services are published to this container. In addition, a routing category instance a block rule, a state category instance of the aggregateState type and a legacyInterop category instance, both containing an availability number of 18500 to indicate the Offline status, and an identity-specific contactCard category instance provisioned from Active Directory by Microsoft Lync Server 2010 are also published to this container.