You can deploy the Office Live Meeting client on desktop computers that are managed by IT professionals (that is, managed desktops). Managed desktops are desktops in an environment where security settings are enforced and managed by IT personnel. A managed desktop environment reduces the potential for users to make damaging changes to their systems and therefore may help to lower overall administrative costs.
In a managed desktop environment, the Office Live Meeting client must be installed by IT professionals before Office Live Meeting client users can join their first meeting. Organizations that use managed environments can update the meeting client on a schedule that they choose.
The LMSetup.exe application that installs the Office Live Meeting client is included in the Office Communications Server 2007 R2 product download. If required, administrators can extract the Windows Installer package (.msi file) named LMConsole.msi from the LMSetup.exe application. The ConfAddins_Setup.exe application installs the Conferencing Add-in. Also, if required administrators can extract a Windows Installer package named LMAddinPack.msi from the ConfAddins_Setup.exe application. For details, see Deploying Office Live Meeting Clients. You can deploy the meeting client using the preferred deployment method of your organization. For example, System Management Server (SMS), Active Directory Domain Services Group Policy, scripted deployment, or any other third-party software that supports .msi-based deployment.
 Note: |
|---|
| To help protect the files in the installation package from being tampered with, digital signatures are used. |
In managed environments, administrators can use the .msi installer along with the lockdown registry key and the per-user installation registry key to further control the installation of the meeting client.
Lockdown Registry Key
IT departments can better control the meeting client versions that are installed on users computers by using a lockdown registry key. This registry key disables upgrade notifications, which prevents users from installing newer versions of the meeting client that are not managed by the IT department. When a new version of the meeting client is available, the upgrade notification does not appear. This enables administrators to control the versions of the console running on the users' computers.
The following registry key disables upgrade notifications:
|
Location |
HKEY_LOCAL_MACHINE\Software\Microsoft\Live Meeting\8.0 |
|
Name |
Lockdown |
|
Data Type |
REG_DWORD |
|
Value |
1 |
Per-User Installation Registry
Key
In a typical managed environment, the IT department prevents users from installing programs on their computers by not giving Administrator permissions to users. However, there are ways that a user can attempt to install a client on their own. For example, users can click a meeting link for an Office Live Meeting service meeting or they can try to obtain the client on their own. These per-user installations will be successful unless the IT department prevents this by setting the per-user installation registry key. This registry key enables IT departments to restrict meeting client versions to only those versions that are installed by the IT department.
The following registry key disables per-user installations.
|
Location |
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer |
|
Name |
DisableUserInstalls |
|
Data Type |
REG_DWORD |
|
Value |
1 |
IT departments can use a system policy to set this registry key on all computers.
|
Note: |
|---|
| This registry key is a Windows 2.0 Installer standard that applies to all Windows 2.0 Installer programs, not only the Office Live Meeting client installer. |