Description of the administrative template (.adm) file for the Windows-based Live Meeting 2007 client and the Conferencing Add-in for Outlook

This article describes an administrative template (.adm) file that provides the appropriate registry settings for deployment of the following updates on Microsoft Windows-based Live Meeting clients:

• Update for the Windows-based Live Meeting 2007 client
  
  For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  952579  (http://support.microsoft.com/kb/952579/ ) Description of the Windows-based Live Meeting 2007 client update package: June 4, 2008
• Update for Live Meeting Conferencing Add-in for Microsoft Office Outlook
  
  For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  952578  (http://support.microsoft.com/kb/952578/ ) Description of the update for the Live Meeting Conferencing Add-in for Outlook: June 4, 2008

Note To deploy the updates on a Windows-based Live Meeting client, a user must test the connection manually after the updates are installed. The .adm file enables a user to deploy the updates successfully without testing the manual connection.

Note If you already have the Live Meeting .adm file installed, and you are upgrading to the latest version of the Live Meeting .adm file, you must first set all .adm settings to not configured, and then force an update of the settings. You can then remove the current Live Meeting .adm file and apply the new Live Meeting .adm file.

To obtain this .adm file, contact Microsoft support to request hotfix 948741.

Description of the policy settings in the administrative template (.adm) file for the Windows-based Live Meeting 2007 client and the Conferencing Add-in for Outlook

Administrators can use policy settings in the .adm file to help set the client registry keys. In this scenario, administrators deploy the Windows-based Live Meeting 2007 client or the Conferencing Add-in for Outlook. Users will not have to test the connection, and they will not have to update their settings in the user interface (UI).

User Account UI

When either the "Service Configuration" setting or the "Server Configuration" setting is enabled by using this .adm file, the User Accounts dialog box will be disabled for the users of the Windows-based Live Meeting 2007 client and the Conferencing Add-in for Microsoft Office Outlook.

However, the User Accounts dialog box will not be removed. The dialog box still shows that the meeting portal and the sign-in name are detected by using the policy settings in the .adm file. The User Accounts dialog box still allows for troubleshooting for the Windows-based Live Meeting 2007 client or for the Conferencing Add-in for Outlook without modifying registry keys. Advanced settings in the User Accounts dialog box will not be available.

Policy properties

Allow AppSharing Give Control

This setting lets you prevent users from requesting control of shared applications during Live Meeting sessions.

Note To prevent users from requesting control of shared applications during a Live Meeting session, set this policy to Disabled.

Enable Basic Authentication for HTTP Proxy
This setting allows HTTP basic authentication.

Specify Transport
This setting lets you set the transport for the Windows-based Live Meeting 2007 client or the Conferencing Add-in for Outlook. Because the "Specify Transport" setting is a registry key setting that is shared with Office Communicator 2007, this setting matches the settings of the .adm file for Communicator 2007.

You can use the .adm file to define the internal Office Communications Server or the external Office Communications Server to which you want to connect. The automated test connection uses service resource records (SRV records) when there is no "Specify Transport" setting. For example, you can use the .adm file to detect the external server. You can detect the internal server by using the SRV record when the automated test connection is finished.

Prevent Initial "Test Connection" dialog box

This setting suppresses the User Accounts dialog box that usually appears when a user starts the Windows-based Live Meeting 2007 client or the Conferencing Add-in for Outlook for the first time.

Service Configuration

This setting only works together with an enterprise portal. Because a password cannot be set for this policy setting, you can use only a portal URL. If the wrong server or portal URL is pushed by a policy setting, users cannot change the setting because the User Accounts dialog box is disabled.

The Live Meeting registry settings were designed to work together with a UI. Therefore, you have to enable a similar UI in the settings dialog box. However, some settings may have only one option. This is a limitation of the Local Group Policy Editor. For example, "Single Sign" setting will always be "Automatic," and the "User needs a password" setting will always be "Off."

To create another test connection, the service configuration number must be changed. This change creates another test connection the next time that the Windows-based Live Meeting 2007 client or the Conferencing Add-in for Outlook starts.

Note Because the "Service Configuration" setting disables the User Accounts dialog box, users cannot make these changes.

This setting enables automated test connections for the server. If the test connection ever has to be reset, changing the Server Configuration number will create a new test connection when the Windows-based Live Meeting 2007 client or the Conferencing Add-in for Outlook starts.

If you do not specify a server in the "Specify Transport" setting, the test connection uses the SRV record to find the server.

Note Because the "Server Configuration" setting disables the User Accounts dialog box, users cannot make changes.

The user account information in Communicator is shared with the Live Meeting console. If the Live Meeting connection settings are automated by Group Policy settings, a potential mismatch of user credentials may occur. This mismatch may occur when users manually change their account information in Communicator, or the user’s name is changed after the initial provisioning of their account.

General notes

• If no policy is set for the Windows-based Live Meeting 2007 client or for the Conferencing Add-in for Outlook, default settings will apply.
• Computer policies are observed before user policies. Preferences are observed last. If a preference is set before policies are set, the preferences will not be overwritten. If only one policy is set for a server or for a service, the preference will be used for the unset policies. If policies are removed, the previous preference settings will be used.
• If you already have the Live Meeting .adm file installed, and you are upgrading to the latest version of the Live Meeting .adm file, you must first set all .adm settings to not configured, and then force an update of the settings. You can then remove the current Live Meeting .adm file and apply the new Live Meeting .adm file.
  
  We recommend that you remove existing preferences before you set policies.