Privacy supplement for Microsoft Office Conferencing Add-in

Last updated: November 2008

This page is a supplement to the Privacy Statement for Microsoft Office Communications Products. In order to understand the data collection and use practices relevant for a particular Office Communications product or service, you should read both the Privacy Statement for Microsoft Office Communications Products and this supplement.

Microsoft Live Meeting and Microsoft Office Communicator Integration

What This Feature Does: The Conferencing Add-in enables you to schedule Microsoft Live Meeting or Microsoft Office Communicator conferences within Microsoft Outlook without entering your login information each time.

Info rmation Collected, Processed, or Transmitted: When you schedule a conference using the Conferencing Add-in, your Office Communications Server username (SIP address), attendee SIP addresses, and audio leader code are transmitted to your enterprise’s Office Communications Server. No information is sent to Microsoft.

Use of Information: The information transmitted is used to schedule your conference.

Choice/Control: You can input login information manually or have it filled in automatically by your network administrator. Your account information is only sent when conferences are scheduled.

Client-Side Logging

What This Feature Does: Client-Side Logging stores error information about the Conferencing Add-in in your User Profile. The information is intended to be used for troubleshooting Conferencing Add-in issues you may have.

Information Collected, Processed, or Transmitted: There are two types of logging: basic logging and verbose logging. Basic logging stores on your computer meeting information such as your unique Live Meeting identifier, meeting attendee SIP addresses, the URLs for meeting content, and meeting expiration time. Verbose logging stores on your computer your IP address, and personal information such as e-mail address and detailed account information as well as the information stored by basic logging.

Use of Information: Logs can be used for troubleshooting Conferencing Add-in issues you may have. They are not automatically sent to Microsoft, but you can choose to send them manually.

Choice/Control : Basic logging is on by default, and cannot be disabled. Verbose logging is off by default, and can be enabled by setting the Logging REG_DWORD registry key to a value of 1000(Hex). Verbose logging can be disabled by setting the Logging registry key to a value of 0(Hex). The Logging registry key is configured in the following registry path: HKEY_CURRENT_USER\Software\Microsoft\Live Meeting\Addins.

Client-side logs are stored on your computer in the following directory:

  • For Windows XP: <System Drive>\Documents and Settings\<User>\Local Settings\Application Data\Microsoft\LiveMeeting\

  • For Windows Vista: <System Drive>\Users\<User>\AppData\Local\Microsoft\LiveMeeting\

Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer. You can also use the Last Known Good Configuration startup option if you encounter problems after manual changes have been applied.

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!