Adding the Group Policy Editor to 64bit Windows 7 Home Premium
673 views
Skip to first unread message
DES
Jan 3, 2012, 10:38:16 AM1/3/12
to The Xxclone Forum
Nothing to do with xxclone, but something useful I just figured out.
Don't see how to upload any files here like on the xxcopy forum? Since
the volume here is quite low, interested parties can just ask directly
for a 460KB zip containing all the goodies.
There is an installer available online for this... with a few
problems. First it's for 32bit Windows 7. Second it uses older pre
Windows 7 files (it does backup the 32bit originals first time
around). Third it doesn't usually totally work the first time around
for various security reasons. And forth what it's actually doing can
only be found out elsewhere. Making success about a 50% possibility at
best.
What it does. It takes ownership of fde.dll, fdeploy.dll, gpedit.dll,
and gptext.dll to allow overwriting them. And adds appmgr.dll and
gpedit.msc. The first 4 files are already present but are replaced, I
assume because the older versions go with the last 2. If the correct
last 2 were used to start with you don't need to replace the first 4.
But whatever. It also adds the folder adm to \GroupPolicy\ containing
inetres.adm, system.adm, conf.adm, wuau.adm, wmplayer.adm, and
adminfile.ini. If the installer is run on a 64bit system it does all
this to \SysWOW64\ instead of \System32\. However if what it's
supposed to do is actually correctly accomplished, the older 32bit
version of gpedit.msc will actually run from \SysWOW64\. I would
suggest acquiring the correct 32bit versions of appmgr.dll and
gpedit.msc and saving yourself some trouble. If you have access to
those 2 files then you most probably have access to the associated adm
folder and it's contents as well.
If the correct 64bit versions of appmgr.dll and gpedit.msc and the adm
folder with it's contents above are added to \System32\ you're done.
And the 64bit version of gpedit.msc is quite sportier.
Further, I researched registering gpedit as a snapin for MMC and
managed that by borrowing some registry contents from Windows XP Pro.
One optional key, the StringNameIndirect referencing other languages
and pointing to a specific XP file not present on WIndows 7, was
deleted. But my Microsoft Manament Console offers the Group Policy
Object Editor too now thank you.
All this is included in that zip file if anyone is interested. You
don't normally need these advanced tools. But adding this one
convinced me that the higher versions of Windows are a must for me. I
just wound up with Home Premium by default as that was all that was
available on a laptop at the time. I should have gone the Anytime
Upgrade route. Just one exercise in trying to diagnose why another
Windows 7 machine couldn't network on a Workgroup brought it all home
(pun intended). Sure the Homegroup works better, it's supposed too,
that helps foster more upgrades!
DES
Don't see how to upload any files here like on the xxcopy forum? Since
the volume here is quite low, interested parties can just ask directly
for a 460KB zip containing all the goodies.
There is an installer available online for this... with a few
problems. First it's for 32bit Windows 7. Second it uses older pre
Windows 7 files (it does backup the 32bit originals first time
around). Third it doesn't usually totally work the first time around
for various security reasons. And forth what it's actually doing can
only be found out elsewhere. Making success about a 50% possibility at
best.
What it does. It takes ownership of fde.dll, fdeploy.dll, gpedit.dll,
and gptext.dll to allow overwriting them. And adds appmgr.dll and
gpedit.msc. The first 4 files are already present but are replaced, I
assume because the older versions go with the last 2. If the correct
last 2 were used to start with you don't need to replace the first 4.
But whatever. It also adds the folder adm to \GroupPolicy\ containing
inetres.adm, system.adm, conf.adm, wuau.adm, wmplayer.adm, and
adminfile.ini. If the installer is run on a 64bit system it does all
this to \SysWOW64\ instead of \System32\. However if what it's
supposed to do is actually correctly accomplished, the older 32bit
version of gpedit.msc will actually run from \SysWOW64\. I would
suggest acquiring the correct 32bit versions of appmgr.dll and
gpedit.msc and saving yourself some trouble. If you have access to
those 2 files then you most probably have access to the associated adm
folder and it's contents as well.
If the correct 64bit versions of appmgr.dll and gpedit.msc and the adm
folder with it's contents above are added to \System32\ you're done.
And the 64bit version of gpedit.msc is quite sportier.
Further, I researched registering gpedit as a snapin for MMC and
managed that by borrowing some registry contents from Windows XP Pro.
One optional key, the StringNameIndirect referencing other languages
and pointing to a specific XP file not present on WIndows 7, was
deleted. But my Microsoft Manament Console offers the Group Policy
Object Editor too now thank you.
All this is included in that zip file if anyone is interested. You
don't normally need these advanced tools. But adding this one
convinced me that the higher versions of Windows are a must for me. I
just wound up with Home Premium by default as that was all that was
available on a laptop at the time. I should have gone the Anytime
Upgrade route. Just one exercise in trying to diagnose why another
Windows 7 machine couldn't network on a Workgroup brought it all home
(pun intended). Sure the Homegroup works better, it's supposed too,
that helps foster more upgrades!
DES
Joel Hedding
Dec 28, 2012, 4:52:40 PM12/28/12
to xxc...@googlegroups.com
Is this file still available? I've been going nuts trying to find the correct version of gpedit.msc for Windows 7 HP, like you said the old version included in the installer that everyone links to works but it is missing a ton of options. Thanks for your help, sorry for digging up an old post.
Reply all
Reply to author
Forward
0 new messages