Windows System Group Policy application full Raiders (top) 1th/2 page _windowsxp

One, what IS Group Policy

(i) What is the use of Group Policy?

When it comes to Group Policy, you have to mention the registry. The registry is a database of system and application software configuration in Windows System, and with more and more features of Windows, there are more and more configuration items in the registration table. Many configurations are customizable, but these configurations are published in every corner of the registry and, if it is manually configured, how difficult and tumultuous it is to be. Group Policy, however, integrates the important configuration functions of the system into various configuration modules for direct use by managers so as to facilitate the management of computers.

To put it simply, Group Policy is to modify the configuration in the registry. Of course, Group Policy uses its own more perfect management organization method, can manage and configure the settings of various objects, far more convenient, flexible and powerful than manual modification of registry.

(ii) version of Group Policy

Most Windows 9X/NT users may have heard the concept of "system policy," and most of us now hear the name "Group Policy." In fact, Group Policy is a more advanced extension of system Policy, which is developed by Windows 9x/nt's "System Policy", with more administrative templates and more flexible settings objects and more features that are currently used primarily in Windows 2000/xp/2003 systems.

The mechanism of early system policy is to define specific, through policy management templates. POL (usually Config.pol) file. When a user logs on, it overrides the setting value in the registry. Of course, the System Policy Editor also supports modifications to the current registry, and it also supports connecting network computers and setting up their registry. Group Policy and its tools, however, make direct modifications to the current registry. Obviously, the network function of the Windows 2000/xp/2003 system is its biggest characteristic, its network function is naturally essential, so the Group Policy tool can also open the computer on the network to configure, can even open an active Directory object (that is, the site, Domain or organizational unit) and set it. This is not possible in the previous System Policy Editor tool.

Whether they are system policy or Group Policy, their rationale is to modify the corresponding configuration items in the registry to achieve the purpose of configuring computers, but some of their operating mechanisms have changed and expanded.

Ii. Administrative Templates in Group Policy

Several. adm files are included in the Windows 2000/xp/2003 directory. These files are text files, called Administrative Templates, that provide policy information for Group Policy Management template projects.

In a Windows 9X system, the default Admin.adm administrative template is saved in the same folder as the Policy Editor. The INF folder for the Windows 2000/xp/2003 System folder contains the 4 template files that are installed by default, respectively:

1) System.adm: Installed by default in Group Policy, for system settings.

2) Inetres.adm: Installed by default in Group Policy, for Internet Explorer policy settings.

3) Wmplayer.adm: For Windows Media Player settings.

4) Conf.adm: for NetMeeting settings.

In the Windows 2000/XP/2003 Group Policy console, you can add policy templates multiple times, and under Windows 9X, only one policy template is currently open. The following methods are used to use policy templates. First, use the following in the Windows 2000/XP/2003 Group Policy console:

The dialog box shown in Figure 1 pops up by running the Group Policy program and then selecting Administrative Templates under Computer Configuration or User configuration, pressing the right mouse button, and choosing Add/Remove Templates from the pop-up menu.

Figure 1

Then click the Add button and select the appropriate. adm file in the dialog box that pops up. Click the Open button to open the selected script file in the System Policy Editor and wait for the user to execute it.

After you return to the Group Policy Editor main interface, open the directory "local Computer policy → user Configuration → Administrative Templates", then click on the appropriate directory tree, you will see our newly added management template generated by the configuration items (for the purposes of this article later on, we can work together, It is recommended that you add additional template files in addition to the default template files.

Then look at the Group Policy Editor under Windows 9X. First, select Close on the File menu in Group Policy Editor to close the current script and then select Templates from the Options menu to eject the dialog box shown in Figure 2.

Figure 2

Then click the Open Template button, select the appropriate. adm file in the pop-up dialog box, and click the Open button to open the selected script file in the editor and wait for the user to execute it.

Third, run Group Policy

(i) Windows 9X Policy Editor

Depending on the operating system, the policy editing tool is divided into two types: the Windows 2000/XP/2003 Group Policy Management Console, which was installed by default when the system was installed, and the Windows 9X System Policy Editor, which is not installed when the system is installed. The program file is in the \tools\reskit\netadmin\poledit directory on the Windows installation disk, and it includes files such as Poledit.exe, Poledit.inf, Windows.adm, and so on.

If the Windows 9X system is in the following way, you can perform the normal installation process.

1. In Control Panel, double-click the Add/Remove Programs icon, click the Install Windows tab, and then click the Install from disk option.

2. In the Disk Installation dialog box, click the Browse button and specify the Tools\Reskit\Netadmin\Poledit directory for the Windows 9X installation CD.

3. Click the Confirm button, and then click the Confirm button in the dialog box again.

4. In the Disk Installation dialog box, select the System Policy Editor and Group Policy check boxes, and then click the Install button.

When the installation is complete, click the Run command entry, enter Poledit, and then click the OK button (the following interface is shown in Figure 3).

Figure 3

Current 1/2 page 12 Next read the full text