Containers and Categories Used by Microsoft Lync

  • Article

Microsoft Lync 2010 makes a distinction between the data that can be accessed only by the local user and the data that can be accessed by other users. It does so by designating one set of containers for local user access and another set of containers for remote user access.

  • The local-access only containers are used to contain the user’s presence information, server configuration, user settings, including contact lists, and other application data. The Ids of these containers are 1, 2 and 3. They are also known as Self Container, Aggregation Container 1 and Aggregation Container 2, respectively. The data is visible only to the local user through self-subscription. Lync 2010 uses these containers to roam the user settings, including the contact list, and to initiate presence aggregation across multiple endpoints, to determine the server configuration, or to facilitate scheduling and establishing conference calls. For more information about these containers, see Containers for Local Access. For information about what data is published to the locally accessible containers, see Local-Access Only Category Instances

  • The remotely accessible containers are used to contain the user’s sharable presence information and rules to route incoming calls. The Ids of these containers are 0, 100, 200, 300, 400 and 32000. They are also referred to, respectively, as Default Container, External Contacts Container, Colleagues Container, Workgroup Container, Friends and Family Container and Blocked Contacts Container. Remote users receive the data by subscribing to specified categories published by the local user, provided that the remote users are members of one or more of these containers, except for the Blocked Container. Remote users do not specify containers when submitting a subscription. Lync 2010 uses these containers to control who can view what data. For more information, see Container for Remote Access. For information about what data is published to the remotely accessible containers, see Remotely Accessible Category Instances.

In addition to Lync 2010, Microsoft Lync Server 2010 components, including the User Replicator and Aggregation Script, also publish certain information on behalf of the local user. Examples of such information include user properties as provisioned from the underlying Active Directory and aggregated presence information performed by the Aggregation Script.

In This Section