This page is a supplement to the Privacy statement for Microsoft Lync products. In order to understand the data collection and use practices relevant for a particular Microsoft Lync product or service, you should read both the Privacy statement for Microsoft Lync products and this supplement.
What This Feature Does: Audio Extractor helps retrieve an audio sample from the data collected by using the Collect Logs feature. Collect Logs allows enterprise administrators to collect Microsoft Lync 2010 logs so that Microsoft can investigate audio, video, or connectivity issues that you might encounter.
Information Collected, Processed, or Transmitted: If an end user clicks the Collect Logs button in a conversation window, the following information is collected:
Lync 2010 logs, containing the user’s Contacts list and information about his or her previous conversations. (Lync logs do not include the content of instant-messaging (IM) conversations.)
Audio parameters, such as speech signal level and noise level
Network conditions
Device setup
Operating system version and information
Programs running on the user’s computer, such as Microsoft Outlook and Windows Internet Explorer
The end user can choose to collect the following information as well:
A 30 second recording of the user’s latest call
A screenshot of his or her desktop
Use of Information: The information collected from the end user’s computer will be used to help troubleshoot the problem that he or she encountered and to help improve Lync.
Choice/Control: Lync does not collect logs from end users’ computers by default. Rather, it collects logs only when a user clicks the Collect Logs button. The logs are collected locally on the user’s computer (under %USERPROFILE%\tracing\). The user needs to manually upload the logs by following their enterprise administrator's instructions. The enterprise administrator then sends the logs to Microsoft for troubleshooting purposes.
What this Feature Does: Call Parkometer can track currently parked calls. It also collects statistics about orbits and the Microsoft Lync Server 2010 Call Park application usage.
Information Collected, Processed, or Transmitted: The Call Parkometer can display the following information:
All orbit ranges that are configured for this pool
Currently parked calls
Number of free (available) orbits
Recently parked calls
Reserved orbits, for testing uniform and random orbit values
Use of Information: Enterprise administrators can use this information to view the Call Park service usage and to determine the number of orbits assigned to a pool.
Choice/Control: This information is available only to enterprise administrators and can be found for a specific user only if the user’s SIP Uniform Resource Identifier (URI) is already known.
What this feature does: For organizations that are subject to compliance regulations, ErrorLogReplayer helps ensure that archiving and call details recording (CDR) messages that failed to insert into the archiving database and CDR database, respectively, are inserted into these databases. If an error happens during the data insertion process, the Archiving and CDR services write the failed messages into error log files in the local file system. The error log file contains complete information about the failed messages. This information can be used to attempt to re-insert the data into the relevant database.
ErrorLogReplayer is the tool that reads the error log file and inserts the failed messages into the archiving or CDR database.
Information Collected, Processed, or Transmitted: ErrorLogReplayer reads the errors encountered when trying to write to archiving or CDR databases.
If the CDR archiving feature is enabled, the data from all peer-to-peer communications and meetings is recorded in the CDR database. (The content is not recorded.) The CDR data is stored in the Monitoring Server database that is deployed in the enterprise and reported in a set of standard Monitoring Server reports. No information is sent to Microsoft.
Archiving Server stores the content of IM conversations, information about the end user’s IM usage, meeting content, and meeting information. This data is stored on a server that the enterprise administrator configures. No information is sent to Microsoft.
Choice/Control: Archiving is turned off by default and can be turned on by an enterprise administrator by going to the Lync Server 2010 Control Panel Monitoring and Archiving Settings page and updating the Archiving Policy and Archiving Configuration.
CDR archiving is turned on by default, but the enterprise administrator must install a Monitoring Server, connected to a Monitoring Server backend database, to collect the CDR data. The enterprise administrator can deploy the standard Monitoring Server reports or create custom reports by querying the Monitoring Server database.
What This Feature Does: Microsoft Error Reporting Service for Microsoft Lync 2010 Phone Edition allows participating end users to report problems they might be having to Microsoft and to receive information that might help them solve the problems or avoid them in the future.
Information Collected, Processed, or Transmitted: For information about the information collected, processed, or transmitted by Microsoft Error Reporting, see the Microsoft Error Reporting privacy statement at Privacy Statement for the Microsoft Error Reporting Service.
Use of Information: The error reporting data that the end user submits might be used to solve customer problems and to improve Microsoft software and services.
Choice/Control: End users can participate in Microsoft Error Reporting by installing the Microsoft Lync Server 2010, Resource Kit Tools and then running the Watson Support Tool for Lync 2010 Phone Edition.
In rare cases, such as problems that are especially difficult to solve, Microsoft might request additional data, including sections of memory (which might include memory shared by any or all programs running at the time the problem occurred), some registry settings, and one or more files from the user’s computer. The user’s current documents might also be included. When additional data is requested, the user will have an opportunity to view the information contained in the error report before choosing whether to send the report to Microsoft.
What this feature does: The Response Group application queues incoming calls and then routes them to agent groups. To make informed decisions about which calls to service, response group agents can access real-time information about their agent groups, such as what other agents are available and how many calls are waiting in each queue. This information, initially accessible only through the Response Group service, is made available in a simple and graphical way by Response Group Agent Live.
Information Collected, Processed, or Transmitted: After an agent signs in by using Response Group Agent Live, the following information displays:
Group membership. When an agent group is selected, Response Group Agent Live displays the list of the agents in this group, in the right pane. If Lync is running on the same computer as Response Group Agent Live, the caller’s presence information and contact card are displayed in Response Group Agent Live. Agents can send an instant message or call other agents directly from Response Group Agent Live.
Real-time statistics. Response Group Agent Live provides real-time statistics for all agent groups. Statistics are updated every minute. When a call is answered by a response group, a visual indicator is added next to the group name with the current number of queued calls. Pointing to the group also displays the longest waiting time. The data about pending calls is anonymous.
None of this data is transmitted to Microsoft.
What this feature does: Secondary extension feature activation (SEFAUtil) enables Lync Server administrators and helpdesk agents to configure delegate-ringing and call-forwarding settings on behalf of an end user. This tool also allows enterprise administrators to query the call-routing settings that are published for a particular user.
Information Collected, Processed, or Transmitted: SEFAUtil can display the following information about a user’s call-forwarding settings:
The user’s address of record
The user’s display name
Whether the user is enabled for Microsoft Exchange Unified Messaging (UM)
Whether Simul-ring is turned on
The ring time for a user
How calls are forwarded when they are not answered
Enterprise administrator can use this information to troubleshoot a user’s call-forwarding settings. This information is not transmitted to Microsoft.
Choice/Control: This information is available only to enterprise administrators running this tool.
What this feature does: Snooper is a multi-purpose debugging tool for Lync Server. It parses server and client trace log files and makes protocol (for example, SIP and HTTP) messages and traces easier to read. It can also read call details and stored procedure execution reports for errors. In addition, Snooper can display reports about users, meetings, and conferencing servers (also known as multipoint control units or MCUs).
Information Collected, Processed, or Transmitted: Snooper displays its data by reading the following information:
Client logs, including tracing and protocol logging. Client-Side Logging stores the following information about end users on client computers:
Meeting subjects and locations
SIP messages
Responses to online meeting requests
Information about the sender and receiver of each Lync instant message and the route that the instant message took
The Contacts list
Presence information
Names of any shared programs, attachments, Microsoft PowerPoint files, whiteboards, and polls, as well as poll questions and responses
The contents of Lync conversations are not stored. No information is automatically sent to Microsoft, but users can choose to manually send information.
Server logs, including tracing and protocol logging. Server-Side Logging stores the same information as Client-Side Logging (see above) and IM conversation content in the server logs. No information is automatically sent to Microsoft, but the administrator can choose to manually send information.
Call Detail Records (CDR) from the Monitoring Server database. If CDR logging is enabled, the data from all peer-to-peer communications and meetings is recorded in the CDR database. (The content is not recorded.) The CDR data is stored in the Monitoring Server database that is deployed in the enterprise and reported in a set of standard Monitoring Server reports. No information is sent to Microsoft.
Conference details from the conferencing database. The meeting organizer, subject, location, and who was invited is stored in the conferencing database. No information is sent to Microsoft.
Health of A/V Conferencing Server, Web Conferencing Server, Applications Sharing Server and IM Conferencing Server. The health of conferencing servers displays no user data and shows only how healthy the conferencing servers are. No information is sent to Microsoft.
Choice/Control:
Client Side Logging: Client-Side Logging is turned off by default and must be turned on by an enterprise administrator. If the enterprise administrator has not disabled the end users’ ability to control logging, users can change the settings as follows:
In the Lync main window, on the Tools menu, click Options. Or, click the Options button.
Click General, and then select the Turn on logging in Lync and Turn on Windows Event logging for Lync check boxes.
Click OK.
Server Side Logging: Server-Side Logging is turned off by default and must be turned on by an enterprise administrator. The administrator can use the following Windows PowerShell cmdlets to turn on or off this feature at the site, service, or server levels:
New-CsDiagnosticsFilterConfiguration
Set-CsDiagnosticsFilterConfiguration
Get-CsDiagnosticsFilterConfiguration
Additionally, the content of IM conversations is logged if a certain registry value is set on each Front End Server.
CDR: CDR is turned on by default, but the enterprise administrator must install a Monitoring Server, connected to a Monitoring Server backend database, to collect the CDR data. The enterprise administrator can deploy the standard Monitoring Server reports or create custom reports by querying the Monitoring Server database