Many current machines come by default with Windows XP Home version. Although it has differences with the Professional version, the biggest that we could find is the absence of the Group Policy editor, [i] group policy editor [/i] or [i] [/i] gpedit.msc. In this document, I researched a way to add it.
The Group Policy editor is a tool that allows you to configure million system functions, restrictions, and aspects of performance, safety and aesthetic in a way that is as simple as selecting an option in a box of options, however, this tool is not included in the Home version of Windows XP system.
If you've read any of the documents of my site you'll see that few things are those that cannot be made with a bit of cunning and patience, I think adding the functionality of Group Policy editor will also be it.
First, we clearly need the disk of Windows XP Professional. The Group Policy editor corresponds to the file gpedit.msc.
In the Windows disk files are compressed and their file names are encoded. For the compiled files as folders of devices (*.inf) there are complete packages, but for individual files there are separate files, where each file extension is modified, for example Task Manager Taskmgr.exe We found it as Taskmgr.ex_ on the operating system disk.
We seek and unzip the Group Policy editor from the Windows XP Professional disc:
To work with found
We have three files, one is a library (DLL) clearly, the other is help (HLP) file and the latter is the searched file, although apparently it also depends on these two. We are now looking for the place where are stored the other MSC files in our Windows XP Home:
They are in the folder System32 the root directory of the operating system.
We descomprimamos three previous files. To unzip them I am using WinRAR, I add the extension of the program to each file:
Now unzip its contents (files compression is CAB, Winzip and other compatible compressors could also be used):
Ready, now copy files to System32 We can test the functioning of the file gpedit.msc. We have a nasty surprise:
Something is missing. That identifier is a library that must be loaded manually or in a way assisted with the utility RegSvr32.
What is missing?
Probably not only the indicated library is required. To find out, the file abrirmos gpedit.msc in a compatible editor.
To clarify more the panorama, MSC console files are executed with the MMC utility (to check this run an MSC file as e.g. write compmgmt.msc and check in the task manager that a process called appears MMC.exe) because the MSC file itself is not a binary executable, is a file with XML structure that defines the behavior of a console that although it is defined by the same file, is executed by another utility and uses many independent bookstores to the file
So, let's look at our archive gpedit.msc in Microsoft Word 2003:
Locate required files without an installation of Windows XP Professional would be almost impossible. To locate files in the Professional Edition of the operating system installation, go to the Windows registry and do the code search. Within the key, we will find a subkey "InProcServer32" that contains the name of the library and its route.
Summarizing the history, after researching many keys on the computer running Windows XP Professional, we need the following files, which I added to the previous ones:
Now unzip the files as before:
Finally copy files to System32 and run again gpedit.msc to see the result.
Again we get the same error. Why?, but bookstores are physically, Windows still not assigned a unique key identifier HKEY_CLASSES_ROOTCLSID then even there for the system.
The blessed regsvr32
To assign the ID, run the following command in the command console:
We can copy or paste the command in the console and evaluate it:
Let's try to run gpedit.msc Once again. We get a comforting display of group policy administration.
However, after reviewing the application we found missing many commands in it.
The excellent application FileMonwhich allows us to see the Windows disk activity, can help us to reveal the mystery of the absence of options. We apply the filter "mmc.exe" application to obtain only the actions carried out by the application that runs our gpedit.msc:
After reviewing the list a bit, we found something odd:
Do you see the event"NO MORE FILES“?
That means that MMC.exe He called for more files in that directory. This means that probably the archives contained in this folder define the program options.
The contents of the above-mentioned folder allocation:
"admfiles.ini" that in reference to a single file "wuau.adm"?, does that mean that other ADM files will be missing?, probably yes.
Remember that files compressed had a similar name to? FILE.EXTENSIO_ When was its extension EXTENSION?
So look for ADM files Windows XP Professional disk, looking for "*."AD_ "." As always, unzip and copy the files to the folder that we gave FileMon:
In this way we obtain a folder similar to the following:
Final attempt, victory
Now, we run again gpedit.msc to see the options appeared magically. Although unfortunately there are now plenty of options:
They are options that say they are not for this version of Windows (although out Windows 2000 error probably in those options). Then we clean our directory as shown below, is as simple as deleting above files incorrectly in gpedit.msc:
Now yes, although it took a little more than expected, we get a satisfactory result, the same functionality of Windows XP Professional with respect to configuration directives of the computer in Windows XP Home, I hope that they serve and if you have any problems or questions don't hesitate to make a comment.
Update (August 17, 2006)
According to several comments, although the Group Policy editor starts up perfectly in Windows XP Home, unfortunately does not apply changes to System.
At the request of the same people that made the comment and after several hours looking for any condition within the system that did all that I could discover the difference of behaviour in the HOME and PROFESSIONAL version is that the application of Windows login)WINLOGON.exe) is not called in the HOME version, so it does not change, however I can not find the reason why this happens.
The truth is that after focus on another target, I was able to apply changes in the policies of manually group and develop a small application that does the job. Although the application is in a phase very preliminary does its job.
My idea in the future is to integrate my small application to GPEDIT, in a way that automatic application of changes outside, the truth is that what most pushes me to achieve that GPEDIT works well in Windows XP Home is because looking for the network, all the sites in English and Spanish say that this is not possible, that this document was yet unfinished.
The source code for this application is not available for the moment.