NetMeeting 2.1 Resource Kit

This chapter describes how corporations can use the system features in Windows® 95 and Windows* NT®* to control user and computer access to Microsoft® NetMeeting™ components and features. System administrators can predefine NetMeeting options for their user communities by implementing the system policy settings discussed in this chapter. This process allows organizations to customize the NetMeeting work environment.

For additional information about creating and implementing system policies, refer to the Microsoft Windows 95 Resource Kit or the Microsoft Windows NT Workstation Resource Kit.

Overview

System policies for NetMeeting are a powerful mechanism for increasing control and manageability of computers across a network. Defined in a policy file, system policies are a method to enforce user and computer settings by overriding default registry values. Using System Policy Editor in Windows 95 or Windows NT 4.0, you can implement policies to control user and computer access privileges and to standardize configurations for your NetMeeting user community. System policy settings for users can apply to an individual user, a user group, or all users; system policy settings for computers can apply to an individual computer or all computers. For detailed lists of the system policies that can be changed, see the tables at the end of this chapter.

Benefits of Setting System Policies

Organizations can realize many benefits from implementing system policies for users and computers. The following list describes some of these benefits.

System policies can enforce a standard NetMeeting configuration. You can restrict the features that users can access within NetMeeting. For example, you can preset the NetMeeting work environment to control audio and video access, or to prevent users from sending files to or collaborating with other users during application sharing. Also, you can use system policies to customize parts of NetMeeting, including the default directory server.

System Policy Editor enables you to change registry settings. You can use System Policy Editor in Windows 95 or Windows NT to change registry settings, either by user, group, or computer. You can use these settings in a system policy file to change registry values on multiple computers.

System policies can apply to individuals or to groups of users. With System Policy Editor, you can add system policies for individual users and for user groups. You can define group policies on the basis of membership in a predefined group. Group policies facilitate computer management on a corporate network by leveraging the current administrative organization of users.

Issues to Consider Before Setting Policies

Before implementing system policies, you should consider the following issues:

• What types of restrictions and settings would you like to define and manage centrally? For example, do you want to limit access to NetMeeting file transfer, application sharing, or audio and video features? 

• Do you want to use one set of standard system policies for all users and computers, or do you want to customize settings by groups of users? Also, do you want to maintain some individual settings for specific users and computers?

• A typical way to customize settings is by groups, such as Accounting and Marketing. A small group of individuals, such as administrators, could have unique privileges set for their specific needs. 

How Do System Policies Work?

When the user logs on, Windows 95 or Windows NT checks the user's configuration information for the location of the policy (.pol) file. Then, the operating system downloads the policies and copies the information into the registry using the following process:

1. Windows 95 or Windows NT checks the policy file for a matching user name. If the user name is located, the operating system applies the user-specific policy. If a user policy file does not exist, the operating system applies the default user policy file. All user settings are copied into the User.dat section of the registry for Windows 95 or the Ntuser.dat section of the registry for Windows NT.

   Note For Windows 95, you must enable user profiles in order to define user settings. For more information about user profiles, see Chapter 15, "User Profiles and System Policies" in the Microsoft Windows 95 Resource Kit. 

2. For group policies, Windows 95 or Windows NT checks whether the user is registered as a member of any groups. If so, group policies are processed for all groups the user belongs to. The group with the highest priority is processed last so that the settings in that group's policy file supersede those in lower priority groups. Group policies are not applied if a policy file for a specific user exists. All group settings are copied into the User.dat section of the registry for Windows 95 or the Ntuser.dat section of the registry for Windows NT. 

   Note For Windows 95, you must install support for group policies and enable user profiles in order to define group settings. For more information about user profiles, see Chapter 15, "User Profiles and System Policies" in the Microsoft Windows 95 Resource Kit. 

3. Windows 95 or Windows NT checks for a computer policy file to match the computer name. If one exists, the operating system applies the computer-specific policies to the user's desktop environment. If a policy file for that computer name doesn't exist, the operating system applies the default computer policy file. All computer settings are copied into the System.dat section of the registry for Windows 95 or the Ntsystem.dat section of the registry for Windows NT. 

How System Policies Change Registry Settings

The system policy entries you set through System Policy Editor are reflected in the policy file, which overwrites default settings in the registry when the user logs on the network. NetMeeting policy entries change registry settings in the following way:

• User-specific settings modify the Hkey_Current_User key in the registry, which defines the contents of User.dat or Ntuser.dat. All policy settings affecting User.dat or Ntuser.dat are defined for a specific user, group of users, or for the default user. 

• Computer-specific settings modify the Hkey_Local_Machine key in the registry, which defines the contents of System.dat or Ntsystem.dat. All policy settings affecting System.dat or Ntsystem.dat are defined for a specific computer or for the default computer. 

Getting Started Using System Policy Editor

You must install System Policy Editor for Windows 95 or Windows NT to create system policies. For specific instructions on how to install and use System Policy Editor, see the Microsoft Windows 95 Resource Kit or the Microsoft Windows NT Workstation Resource Kit. System Policy Editor for Windows NT is included with the Windows NT Server.

Using the System Policies Template

NetMeeting system policies are set using the Conf.adm template. You can download this template from the NetMeeting Web site at https://www.microsoft.com/netmeeting/reskit/conf.adm. For Windows 95, you must install this template in the Windows\Inf directory. For Windows NT, you must install this template in the Winnt\Inf directory.

After starting System Policy Editor, you must open the Conf.adm template to set NetMeeting system policies.

To open the Conf.adm template

1. In System Policy Editor, make sure all policy files are closed. 

2. On the Options menu, click Template for Windows 95 or Policy Template for Windows NT. 

3. Click Open template for Windows 95 or Add for Windows NT, and click the Conf.adm file. Then, click Open. 

4. Click Close to return to System Policy Editor. 

Note You can use the Windows NT System Policy Editor to create and update system policies in Windows 95. The Windows NT System Policy Editor enables you to load multiple templates. For Windows NT and Windows 95, you can apply the policies of multiple templates to a single policy file.

Changing System Policy Settings

This section describes the policy options that you can use for NetMeeting. These options are determined by the Conf.adm template. You might find it helpful to start System Policy Editor while you review these options.

These policies are described in the order that they appear in System Policy Editor. For each category, you must click the option that appears in bold type to display the related policies that you can define for that category.

Note When you click on some system policies, additional settings may display at the bottom of the properties dialog box. In this case, you must click on both the system policy and one or more of the additional settings in order to implement the system policy (Clicking on the system policy alone will not enforce the option.) If you want to deselect a system policy, clearing the check box for the option will automatically cancel the additional settings as well.

Setting User-Specific System Policies

System Policy Editor enables you to view the default user policies for NetMeeting, and then create custom settings for your user community. You can apply these policies to individual users or to groups of users. For Windows 95, you must enable user profiles in order to define user settings.

When you double-click the Default User icon and expand the Microsoft NetMeeting book, the following list of system policies is displayed.

With this template, you can predefine or restrict access to settings that will apply when the user logs on to the system. These system policy settings are stored in the User.dat or Ntuser.dat section of the registry. The following table describes the system policies you can change to restrict access to user-specific settings.

Setting Computer-Specific System Policies

You can use System Policy Editor to define settings for the default computer or for specific, named computers. The default computer settings apply when a new user logs on to a computer that does not have individual policies assigned.

When you double-click the Default Computer icon and expand the Microsoft NetMeeting book in System Policy Editor, the following list of system policy options is displayed.

With this template, you can predefine or restrict access to settings that will apply when the user logs on to the system. These system policy settings are stored in the System.dat or Ntsystem.dat section of the registry. The following table describes the system policies you can change to restrict access to computer-specific settings.

Note NetMeeting 2.1 system policies for Default Computer Properties differ from the policies available with NetMeeting 2.0. Policies to enable protocols for Modem, Network (IPX), and PictureTel LiveShare are no longer available with NetMeeting 2.1.

Common Scenarios

Typically, organizations may want to implement several system policies for their user communities. The following table lists some common scenarios, and the associated policy name that organizations would set.