What if the group policy cannot be accessed?

Group PolicyIt is critical for the system administrator to modify the Registry configuration by using the Group Policy. But what if the group policy cannot be opened? Detailed answers are provided below.

1) check that your machine has the gpedit. msc file by searching for it. If the group policy exists, perform the following operations. If not, it must have been deleted for some reason. You can copy one from another machine.

2) If the group policy exists, refer to the following method:

A netizen in Microsoft's Chinese news group asked the following question: in the policy item "Group Policy> User Configuration> management template> System" run only licensed Windows programs ", specify the applications that the current system can run. Considering that the operation of group policies should be allowed, therefore. msc is added to this policy item, but the Group Policy window cannot be opened again.

The essence of opening the Group Policy was to start the MMC process and then load the gpedit. msc snap-in. Therefore, you should add the mmc program instead of gpedit. msc here. If gpedit. msc is added instead of mmc, the system cannot start the mmc process, and the Group Policy window cannot be opened.

In this case, it is easy to think of a way to enable the Group Policy Management Unit of the faulty system by using the LAN computer, and then modify the policy item back to the original configuration.

To use this restoration method, the following conditions must be met:

(1) the faulty computer must be in the LAN environment.

(2) The firewall on the faulty computer must be properly configured to allow remote access to the group policy tool.

(3) the faulty computer must have no right to prohibit the Administrator account from logging on to the network.

(4) "simple file sharing" must be disabled on the faulty computer ".

(5) the faulty computer must be WindowsXPPro or Windows2000.

Recovery Process

Assume that the computer name of the faulty computer is NoGpedit, which is located in the working group environment. The Administrator account name and password of the faulty computer are Admin and Passwd. Assume that another normal computer on the LAN is named Test.

(1) Open the run dialog box on the LAN computer Test and run the following command:

Controluserpasswords2

(2) switch to the "advanced" tab in the displayed dialog box, and click "manage password" on it.

(3) In the displayed "Storage user name and password" dialog box, click the "add" button. In the displayed dialog box, enter the NoGpedit computer name and account name and password, and save the settings.

You can obtain the Administrator account Admin creden。 of the NoGpedit computer on the Test computer.

(4) In the "run" dialog box on the LAN computer Test, enter the following command and press Enter:

Gpedit. msc/gpcomputer: "NoGpedit"

(5) Open the Group Policy Edit window on the NoGpedit computer on the Test computer and modify the corresponding policy item to return to the default value.

(6) log out of the NoGpedit computer and log on again. The result will take effect.

Similarly, if the security policy prohibits all administrator accounts from logging on locally, You can remotely grant the Administrator group accounts the right to log on locally by using the Ntrights command on the LAN computer.

No HomeEdition version. Copy it to the expert edition to see if it can be used. It is best to reinstall an expert version of XP, with a lot of features of the Family version have restrictions ......

It is hoped that the solution that the Group Policy described in this article will be helpful to the readers. more knowledge about the Group Policy remains to be actively explored and learned by the readers.