How can I unlock the Group Policy Manager if it is disabled?

Group PolicyThe Group Policy can ensure the network security of the system and modify the registry information by using the Group Policy. However, if the Group Policy Manager is disabled, the convenience of all this will become inconvenient. How can this problem be solved?Group Policy ManagerHow about unlocking? Detailed solutions are provided below.

The Group Policy Manager has disabled the unlock method.

Run the Group Policy Editor to enable the Group Policy item "only allow running Windows Applications", whether or not you have added gpedit in "only allow running programs list. msc Command, as long as the Group Policy item "only allow Windows applications to run" takes effect, the system's group policy will automatically "self-lock", even if you use "gpedit. msc command, you cannot open the system group policy edit window

How to unlock the Group Policy Manager:

1. Restart the server system. During the startup process, press F8 until the System Startup menu appears.

2. Run the "security mode with command line prompts" command to switch the server system to the command line prompt status.

3.directly execute the mmc.exe string command at the command prompt

4. In the pop-up System Console interface, click the "file" menu item, and click the "Add/delete Management Unit" option from the pop-up drop-down menu

5. Click the "independent" tab in the subsequent window, and then click "add ".

6. Click Group Policy, add, finish, close, and OK.

In this way, you can successfully Add a new Group Policy console. Later, you can re-open the Group Policy editing window.

How to unlock the Group Policy Manager: B

In addition to the policy to restrict the application to run, many operations can enable the Group Policy to be "self-locked" inadvertently. If the Group Policy is "self-locked" due to other factors, how can we easily remove it?

In fact, all group policy settings are based on the system registry. Therefore, the settings of any branch of the Group Policy are reflected in the corresponding branch of the Registry; therefore, we can easily crack the "self-locking" Phenomenon in the Group Policy Editor by modifying the registry:

1. click Start or run. In the displayed system running dialog box, enter the string command regedit and click OK to open the registry editing window;

2. In this window, expand the Registry branch HKEY_CURRENT_USER \ Software \ Policies \ Microsoft \ MMC,

3. Modify RestrictToPermittedSnapins to 0 to use the "gpedit. msc" command.

4. Modify RestrictToPermittedSnapins to 1 to disable the "gpedit. msc" command.

5. Expand the Registry branch HKEY_CURRENT_USER \ Software \ Policies \ Microsoft \ MMC \ {8fc0b734-a0e1-11d1-a7d3-109f87571e3 },

6. Modify the value of RestrictToPermittedSnapins to 0 to use the "gpedit. msc" command.

7. Modify RestrictToPermittedSnapins to 1 to disable the "gpedit. msc" command.

Both methods are supported!

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