Friday, August 20, 2010

Configure MOC 2007 R2 Clients using GPOs

We will walk through three main steps in order to complete creating and deploying these configurations:-

• Download required administrative templates

• Create Group Policy and add the administrative templates to it

• Create a security group and filter the GPO to it

Download required administrative templates

One way to provide the appropriate registry settings for each user when you are deploying Office Communicator 2007 R2 or Microsoft office Live Meeting 2007 is to define Group Policies by using an administrative template (.adm) file.



Create Group Policy and add the administrative templates to it

In order to automatically configure and manage the Office Communicator components (MOC 2007 R2 and Live Meeting 2007) the creation and configuration of a dedicated Group Policy Object is required.

The new GPO should be linked to the OU that directly or indirectly contains all the user accounts under your administration, even if the Office Communicator components are not to be distributed over all of them: a security group must be configured and set as target of the GPO object.

In this way only the user accounts set as member of this group will be involved into the automated configuration procedures.

After creating GPO you must add the administrative Template, after adding adm files you can configure GPO settings.

The following figure describes the custom GPO containers containing setting for Communicator and Live Meeting clients.


If you don’t see settings disable filtering view.


Then configure the settings accordingly to the following figure, and you can modify it according to your requirements.



Create a security group and filter the GPO to it

In order to filter GPO scope it’s necessary to create a security group, for example MOC2007 Users security group.

Then configure a GPO containing the above settings as following:

• Scope: OU where the GPO has been linked (top level domain OU is preferred)

• Security filtering: add the previously created group and delete any other account listed in the Security Filtering panel

No comments:

Post a Comment