Quite often, many users who workon computer terminals without administrator rights, they face the problem that some action is disabled by the administrator or simply prohibited. For such prohibitions, the Group Policy Editor is used. What is it and how to work with it, we now look.
What is Group Policy Editor?
The editor in itself is enougha complex and powerful tool that allows you to fine-tune the system, enable or disable its individual components, set permissions and prohibitions for users to use individual Windows components, install or run applications, and so on.
It should also be taken into account that there are twosuch as the local group policy editor (for this terminal) and the tool for the group policy of the directory service (Active Directory is used by sites, domains, network terminals, etc.).
In addition, it is necessary to know that suchfunctions are provided in the same Windows 7 or 8 systems exclusively versions of Ultimate, Professional and Enterprise. In home versions such as Home or Starter, this element is not installed from the beginning, so to search for it there is nothing to try. A little later, we'll look at how to enable the Group Policy Editor in Windows home builds. In the meantime, let's look at the basic functions of this tool.
Running the editor
To begin, let us consider the question of how to enterlocal group policy editor. The simplest way is to use the command line or the "Run" menu (Win + R). The Group Policy Editor (Windows 8 or 7) is invoked by the gpedit.msc command.
Now let's look at the basic settings and figure out what they are intended for.
Basic Settings and Settings
In the left window of the editor you can immediately see twomain sections. The first concerns the computer system as a whole. Here you can edit all the parameters that apply to the system, regardless of which user is currently working on the terminal. The second section contains settings, so to speak, tied to each specific user.
In this case (of course, if you log in as an administrator), you can set bans and permissions to other users to perform certain actions.
Так, например, необходимо отключить, допустим, editing the registry so that an inexperienced user, God forbid, didn’t go there and didn’t delete an important key or entry that may affect the performance of the entire OS. To do this, use the Administrative Templates section of the user configuration, where the appropriate point for denying access to registry editing tools is selected. When you enter the subsection menu, just put a check mark in front of the "Enabled" parameter.
Now the user when entering the regedit command will receivemessage that editing the registry is prohibited by the administrator. However, this applies to any user actions and current restrictions or permissions.
Computer settings look interesting too.configurations. So, for example, you can easily change, omit, the action performed by pressing the Ctrl + Alt + Del key combination, or something else. In other words, using the parameters of the editor, you can customize the system, which is called, by itself. For this there is a lot of powerful tools.
Installing and enabling the Group Policy Editor in Windows Home versions (7, 8)
Now a few words about how you canuse Group Policy Editor in Windows Home and Starter versions. To do this, just download the installation distribution from the Internet and install this component. Installation does not cause problems, since it is a standard process. Upon completion, you will need to restart the computer system. But that is not all.
Where is the local group policy editor
Here we come to the issue of whereaboutsthe file responsible for launching the editor. In the standard version for systems with a 32-bit architecture, the startup file is located in the System32 system folder in the Windows root directory.
In 64-bit versions of the same "seven" or“Eights” after installing the file using the above utility, its location will be changed to the SysWOW64 folder (this is where all the command files called via the “Run” menu are located).
So if immediately after installation andreboot the system enter the command to call the editor, it may not work. The system will simply display a message that the gpedit.msc file was not found. Nothing wrong. The way out of this situation is quite simple. You just need to copy the desired file to the System32 folder, that's all.
Conclusion
In conclusion, it remains to add that the editorGroup Policy is a powerful and serious tool. Therefore, at least without any initial knowledge, it is not recommended to change the parameters that are there, but something else that is good, the whole system will “fly out”. Well, an experienced user, using the system registry and Group Policy settings, can do a lot, especially since the editor and the registry are interconnected, up to a complete duplication of some settings and parameters.
