Shulou(Shulou.com)06/01 Report--

This article mainly introduces how to unlock the Group Policy Manager when it is disabled, which has a certain reference value. Interested friends can refer to it. I hope you will gain a lot after reading this article. Let the editor take you to know it.

Group policy is very important for system administrators. Group policy can ensure the network security of the system, and the information in the registry can be modified by using group policy. But if the Group Policy Manager is disabled, then all this convenience will become inconvenient, how to unlock the Group Policy Manager? The detailed solution is given below.

Unlock method disabled by Group Policy Manager

Run the group policy editor to enable the group policy project that "only Windows applications are allowed to run". Whether or not you add the gpedit.msc command in the "only running programs list", as long as the group policy project that "only Windows applications are allowed to run" takes effect, the system's group policy will automatically "self-lock", even if you use the "gpedit.msc" command under the Super Admin account. Nor can you open the system's group policy editing window

Method for unlocking Group Policy Manager: a

1. Restart the server system and keep pressing the F8 function key during startup until the system startup menu appears

two。 Then execute the "safe mode with command prompt" command to switch the server system to the command line prompt state

3. Next, execute the mmc.exe string command directly from the command prompt

4. In the pop-up system console interface, click the File menu item and click the add / remove snap-in option from the pop-up drop-down menu

5. Then click the stand-alone tab in the subsequent window, and then click the add button

6. Then click the Group Policy, add, finish, close, OK buttons

In this way, you can successfully add a new Group Policy console; later, you can reopen the Group Policy editing window.

How to unlock Group Policy Manager: B

In addition to policies that restrict the running of applications, there are many actions that can cause group policies to "lock" inadvertently. If other factors cause the "self-locking" phenomenon of group policy, how can we easily release it?

In fact, all the settings for Group Policy are based on the system registry, so the settings for any branch of Group Policy will be reflected in the corresponding branch of the registry. For this reason, we just need to modify the registry. You can easily crack the "self-locking" phenomenon of the Group Policy Editor:

1. Click the start / run command, enter the string command "regedit" in the pop-up system operation dialog box, and click the "OK" button to open the registry editing window of the system.

two。 In this window, expand the registry branch HKEY_CURRENT_USER\ Software\ Policies\ Microsoft\ MMC

3. Modify the restrict ToPermittedSnapins value to 0 to use the "gpedit.msc" command.

4. Change the restriction to PermittedSnapins value to 1 to disable the "gpedit.msc" command.

5. Or expand the registry branch HKEY_CURRENT_USER\ Software\ Policies\ Microsoft\ MMC\ {8FC0B734-A0E1-11D1-A7D3-0000F87571E3}

6. Modify the restrict ToPermittedSnapins value to 0 to use the "gpedit.msc" command.

7. Change the restriction to PermittedSnapins value to 1 to disable the "gpedit.msc" command.

Both methods are fine!

Thank you for reading this article carefully. I hope the article "how to unlock when the Group Policy Manager is disabled" shared by the editor will be helpful to everyone. At the same time, I also hope that you will support and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.