Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations sizbut on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Group Policy Diagnostic Best Practice Analyzer results?

Status
Not open for further replies.

ADB100

Technical User
Mar 25, 2003
2,399
GB
I have install the 'Group Policy Diagnostic Best Practice Analyzer (KB940122)' application and was hoping someone can explain the results that it considers are errors?

For two policies that exist - some GUID names that map to the 'Default Domain Policy' and a separate policy for the main site - the same error is reported:
For GPO Default Domain Policy File not Found while trying to access \\dc.domain.com\SYSVOL\domain.com\Policies\{GUID}\users\MICROSOFT\IEAK\Install.ins. Please troubleshoot the file replication service.

I have checked and the file 'Install.ins' doesn't exist in the two policies, however it exists in another policy (I think the Default Domain Controller policy?). I am a bit stuck as to whether this is a real issue or whether it can be ignored. It wories me a bit as it is flagged as 'critical'?

Andy
 
I thought I would put a sniffer on and watch what happens when I run the GPO diagnostic tool and it looks like the file it is looking for isn't there. For some reason it is looking for 'Instal.ins' as opposed to 'Install.ins'. Is this a bug in the GPO diagnostic tool or is there a pointer to the wrong file somewhere?

Andy
 
Answering my own questions.....

OK, it looks like there is a typo in one of the .xml files that get installed with the GPO Diagnostic tool. In the \Program Files\GPDBPA\en folder is a file called 'gpbpa.ManagedNode.xml' and in here is a reference to the 'Instal.ins' file which I assume is a typo (just open the file in notepad and search for Instal.ins). I edited this and changed the line from
<Substitution Name="PATH">user\MICROSOFT\IEAK\Instal.ins</Substitution>
to
<Substitution Name="PATH">user\MICROSOFT\IEAK\Install.ins</Substitution>
and it now doesn't report the error.

I can only assume this is a 'bug'?

Andy
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top