Containers for Local Access

Microsoft Lync 2010 uses the following containers to store category instances for local use. The category instances represent local presence information, roaming user data, server configurations and other application data. Both Lync 2010 and the Microsoft Lync Server 2010 components, such as the aggregation script, publish data to these locally-accessible containers or use the data in them.

Container Id	Friendly Name	Default ACEs	Description
1	Self	Unspecified	Lync 2010 uses this container to cache data about the local user or data used by the local client. The cached data includes the user information (userProperties and userInformation), his or her working hours (workingHours or calendarData), contact list, and any user-configured options (alerts and otherOptions) that dictate Lync 2010 how to display alerts, to operate in privacy modes, and to forward calls.
2	Aggregation 1	Unspecified	Lync 2010 publishes the endpoint-specific presence state and device information that must be aggregated to produce endpoint-independent aggregated presence state, capabilities of the user and the most current active location. The aggregation script takes the data in this container as the input and outputs the aggregated results to the Container 100, 200 and 400.
3	Aggregation 2	Unspecified	As with the first Aggregation container, the Aggregation script takes the endpoint-dependent presence state data in this aggregation container as the input to produce endpoint-independent aggregated presence states. The aggregation logic is slightly different from that applied to the input in first aggregation container: when the local user is in the Do Not Disturb (DND) state, the aggregated state will be set to busy with Urgent Interruptions Only. The aggregated results are output only to Container 300.