• 0

gpedit.msc for xp home (err well sorta working but not)


Question

so anyways im currently trying to rip the gpedit.msc so it can be used by xp home users (I was a foolish sheep that went cheapo and got the home edition and losing the old faithful policy editer (aka poledit.exe for you win9x people))

currently I have pretty much got the thing running but seem to not be able to register/open/use the templates.

im assuming this is simply a registry problem. but it may be also either something making sure that its not running on xp home or simply home handles things loads different and cant use the templates anyways.

I believe its simply registry problems as lets face the facts microsoft dont really try to hard the underlying differences between home and pro are nothing home simply has a load of missing dll's and registry entries. There is no difference in existing dll's/exe's etc.

What im posting here for is if anyone knows anything I dont. AKA is this physically impossible due to the differences in xp home and pro. Do you know what registry settings I have missed and/or any files I have missed.

to "install" simply dump the dll's in the system32 folder in your system32 folder. Dump the "adm" folder in system32grouppolicy and drop all the files directly into system32inf aswell (they appear both places in pro so why not follow suite..)

apply the reg file. and then run gpedit.msc hopefully it starts fine and just shows u a mmc console lacking policy templates.

Other things to note is now you have the option under "add snap-in" to add the "group policy" feature. yet cant click finish.

You can also open mmc then open gpedit.msc from inside mmc.exe see the group policy editer added as a snap-in in mmc, and allows u to see some of the extensions (only several and some are still ****ed due to missing registry entries.)

http://twistedddx.tripod.com/grouppol.txt (right click "save target as" and rename to .zip)

so far 2 nights work with a friend stealing his files and keys ;)

Link to comment
Share on other sites

2 answers to this question

Recommended Posts

  • 0

not all things will work with it if u rip it directly since XP Home has some missing feautres that XP Pro has..

if GPEdit messed with these it mite cuase some probs dont cha think?!

Link to comment
Share on other sites

  • 0

very true.

Thought about this already. Altho I'ld assume nearly everything would be identicle tho(if the policy format remains between home and pro, which I have clue about or if it even exists in home at all..).

Like I said. Microsoft are slack ****s. They wont code an operating system twice(and im not talking about xp home and xp pro, im talking about the entire windows code base.). Home and Pro are very alike (remember u can join home onto a domain even tho home "cant") Microsoft just remove the shortcuts, via the registry and dll's. Thats why there is so many freakin clsid's start removing them and u'll start "hiding" features, know what your doing and you'll enable them.

They code it all once and the dll's just check the registry to what it is spose to display.

Ofcourse before trying something as crazy as this you'ld re-enable system restore. make a restore point before you even start playing ;)

thats the least of the problems right now anyways. the main problem is getting the templates running. If however someone says "this is physically impossible due to differences in home and pro", its an entirely different story.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.