Comment install gpedit.msc on Windows Starter Edition, Home and Home Premium?
J'ai utilisé the following procedure to successfully install gpedit.msc on Windows 7 64 bit Home Premium.
Notes:
-
Confirmed as working on Windows 10 by Moab
-
It apparently works on Windows 8, Windows 8.1 and Windows 10 aussi. J'ai not personally tested this.
MISE À JOUR : According to our readers, this tool also works fine in Windows 8, Windows 8.1 and Windows 10.
Today we are going to share a simple installer which installs the required system files in Windows so that vous pouvez enjoy Stratégie de groupe Editor in all Windows 7 editions.
-
First download the setup file using following link:
Download Stratégie de groupe Editor Installer
Vous trouverez the download link in right-side section of the above
mentioned page:
-
After downloading the ZIP file, extract it using WinRAR or 7-Zip.
-
Run the extracted setup.exe file.
It will install the files and you'll be able to access gpedit.msc
command via RUN or menu Démarrer search box.
Remarque :
- For Windows 7 64-bit (x64) users! You'll also need to allez dans "SysWOW64" folder present in "C:\Windows" folder and copy
"GroupPolicy", "GroupPolicyUsers" folders and gpedit.msc file from
there and paste them in "C:\Windows\System32" folder.
Si vous êtes getting "MMC could not create the snap-in" error message
while running gpedit.msc, check out following steps to fix the
problem. Basically it happens when your username in Windows contains
more than one word.
-
Run the installer and leave it at the last step (do not cliquez sur the "Finish" button).
-
Now allez dans C:\Windows\Temp\gpedit\ folder.
-
Si vous êtes running 32-bit (x86) edition of Windows 7, faites un clic droit sur x86.bat file et choisissez "Open With -> Notepad" option. If you are
running 64-bit (x64) edition of Windows 7, faites un clic droit sur x64.bat file
et choisissez "Open With -> Notepad" option.
-
Vous trouverez a total of 6 lines containing the following string in the file:
%username%:f
-
Edit those lines and replace %username%:f with "%username%":f
Original: icacls %WinDir%\SysWOW64\gpedit.dll /grant:r %username%:f
New: icacls %WinDir%\SysWOW64\gpedit.dll /grant:r "%username%":f
-
Save and run the file (faites un clic droit sur -> Run as Administrator).
-
That's it. You'll have working gpedit.msc.
Source Comment Enable "Stratégie de groupe Editor" (gpedit.msc) in Windows 7 Home Premium, Home Basic and Starter Editions?
Stratégie de groupe Settings Reference Guide
Microsoft has updated and made available as a download, the complete Stratégie de groupe Settings Reference Guide for Windows 10, Windows 8.1, Windows 8, Windows 7, Windows Vista, Windows Server 2003 SP2, Windows Server 2008 R2 and Windows Server 2012 R2.
The download is available in the form of spreadsheets for different operating systems. So vous pouvez download the spreadsheet only for those operating system/s which you may be interested in.
Spreadsheet Download Link
...
Qu'est-ce que also very useful in these spreadsheets, is that it also lists le registre keys which are affected when the settings are changed. Of course, vous pouvez always use the Stratégie de groupe Settings Search, to know le registre key and value name that backs a particular policy setting, but these spreadsheets put them all in one place.
The Administrative Template spreadsheet contains three columns that provide more information about each policy setting’s behavior related to reboots, logoffs, and schema extensions. These columns are the following:
Logoff Required: A “Yes” in this column means that the Windows operating system requires the user to log off and log on again before
it applies the described policy setting.
Reboot Required: A “Yes” in this column means that the Windows operating systems requires a restart before it applies the described
policy setting.
Active Directory Schema or Domain Requirements: A “Yes” in this column means that you must extend the Active Directory schema before
vous pouvez deploy this policy setting.
Status: A “New” in this column means that the setting did not exist prior to Windows Server 2012 and Windows 8. It does not mean
that the setting applies only to Windows Server 2012 and Windows 8.
Refer to the column entitled “supported on” to determine to which
operating system the policy setting applies.
Source Stratégie de groupe Settings Reference Guide for Windows 10/8.1/7/Server
