Microsoft introduced the idea of group policies way back in NT 4.0,
moreover, each successive generation has added more settings so that in Windows 7
we have over 2,500 policies. As with previous operating systems you can inspect and control the settings with a snap-in called
gpedit.msc.
Troubleshooting gpedit.msc in Windows 7 Home Premium.
If you have Active Directory then you will probably control group policy
strategy via GPMC on the domain controller. However, if you are responsible
for Windows 7 in a Workgroup or HomeGroup then you will choose
the local group policy editor - gpedit.msc.
Types of Group Policy Settings There are broadly three reasons for changing group policy settings,
firstly, adding features present in Vista and XP, but absent in Window 7.
Secondly, using group policy to remove stuff that is inappropriate for that
machine, for example, if you have no speakers: 'Remove volume control icon'.
Thirdly, employing the traditional group policy role of restricting users,
for example, 'Prevent users from changing the taskbar'.
When you want change a setting this is how you launch the Local Group
Policy Editor.
Click on the Start orb, and in the search dialog box type:
gpedit.msc Note: Most people forget to type the .msc file
extension, consequently nothing happens.
When gpedit.msc appears in the search results, consider creating a shortcut by
right-clicking and choosing either 'Pin to Taskbar', or 'Pin to Start
Menu'.
Navigating through the Local Computer Policy is as easy as finding
files and folders with Windows Explorer.
A good place to start your exploration is in the User Configuration, Administrative Templates.
Alternatively, you could trawl the 'All Settings' folder.
A common problem is that even though you type precisely gpedit.msc, Windows 7
cannot find gpedit.msc. The most likely cause is that you have the
Home Premium edition. It's most disappointing that you only get
gpedit.msc in the Ultimate, Professional (old Business) and Enterprise editions, and not in the
Windows 7
Home Premium or Basic editions.
Another common problem is that you forget to type the .msc file extension.
Windows 7 cannot find gpedit unless you append the .msc file extension.
Other your problem launching the group policy editor could be a plain typo,
you type gdedit.mcs or some other anagram of gpedit.msc.
Guy
Recommends: The Free Config Generator
Solarwinds' Config Generator is a free tool, which puts you in charge of
controlling changes to network routers and other SNMP devices.
Boost your network performance by activating network device features
you've already paid for.
Guy says that for newbies the biggest benefit of this free tool is that
it will provide the impetus for you to learn more about configuring the SNMP
service with its 'Traps' and 'Communities'.
Thus utility makes it easy to check the health of a router or
firewall. Check the real-time performance, and availability statistics, for any device
on your network. Get started with an extensive collection of "out-of-the-box"
monitors for popular network devices.
Windows 7 Group Policies, created by gpedit.msc are stored in a special
hidden folder %SystemRoot%\System32\GroupPolicy\
Actually there are two sub-folders where you will find the registry.pol
files: ..\GroupPolicy\Machine and ...\GroupPolicy\User. This name
of these files remind us that virtually all group policy settings affect
settings in the registry.
Incidentally, the environment variable %SystemRoot% usually translates to
C:\Windows.
»
Summary of Windows 7 Gpedit.msc - Local Group Policy Editor
Microsoft has continued the good work of creating a Local Group Policy
Editor so that you can change settings without using regedit. As with
previous operating systems you can inspect and control the settings with a
snap-in called gpedit.msc, and see that in Windows 7 we have over 2,500
policies.
If you are troubleshooting gpedit.msc in Windows 7 Home Premium, it
does not exist; you need to upgrade to the Ultimate edition.
If you like this page then please share it with your friends
