If you used
a single-user install, scripting, or third-party tools, you will want to apply the
template at the OU level rather than at the domain policy level. This gives
you the ability to customize MOC logically, by department, hierarchy, or
geographical location.
128 Chapter 4 ??? Microsoft Offi ce Communicator 2007
Next, right-click and choose Edit; the Group Policy Object Editor will open. Choose
whether to apply the template to the user or the computer, and then choose Administrative
templates under that object (we will apply the templates to the user object in our example).
From the Action menu choose Add/remove templates. The Current Policy Templates
dialog box will appear. Click Add, choose the communicator.adm fi le, and click Open;
you will now see MOC in the current policy templates. Choose Close on the dialog box and
you will see a folder named Microsoft Offi ce Communicator Policy Settings (see Figure 4.14).
Figure 4.14 The MOC Administrative Policy Settings in the Group Policy
Object Editor
The template controls more than 60 different items (Appendix B lists all the available
settings). Here is a broad overview of some of them:
?– Security We can confi gure the SIP security level, storage of passwords, and the need
for logon credentials. We can also confi gure whether users can even run MOC. For
instance, interns or temporary employees in an offi ce may not require MOC. It is easier
to disable usage than to uninstall the client or to allow usage to a transient employee.
Pages:
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188