Then the next step may be to try and do a network trace between the client and its DC. If you are still getting directory server errors, I don't see any other obvious path at the moment, other than to check the event logs on the DC in question to ensure that nothing is amiss. Darren From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of minesh pandya Sent: Wednesday, June 11, 2008 4:48 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: GP Core Failure After running GPOTool these are the results I got on the DC: Validating DCs... Available DCs: PACIFIC.SH.DOMAIN.ROOT.local baltic.SH.DOMAIN.ROOT.local bering.SH.DOMAIN.ROOT.local Searching for policies... Found 15 policies ============================================================ Policy {10F31E9B-DDB1-4278-89D4-5D4F5254E225} Friendly name: Components Install Policy OK ============================================================ Policy {31B2F340-016D-11D2-945F-00C04FB984F9} Friendly name: Default Domain Policy Policy OK ============================================================ Policy {3C06A03F-39A8-452D-BC19-B34EA6D02A7B} Friendly name: WSP Install Policy OK ============================================================ Policy {4F63D2B0-9B4D-46DB-ADDD-4089EF16114C} Friendly name: security install Policy OK ============================================================ Policy {6AC1786C-016F-11D2-945F-00C04FB984F9} Friendly name: Default Domain Controllers Policy Policy OK ============================================================ Policy {72CB9E16-233F-4B95-A8BF-4096DB9E8BB1} Friendly name: SH server policy Policy OK ============================================================ Policy {9155632C-4332-421D-8C42-C92CE6264950} Friendly name: Office XP Install Policy OK ============================================================ Policy {B9BA8457-23AB-4ECA-828B-6749B26E4492} Friendly name: SH Citrix Server Lockdown Policy Policy OK ============================================================ Policy {D78C2C3A-6327-42FF-81D2-0217447478D0} Friendly name: Office xp policy Policy OK ============================================================ Policy {E5C27437-C966-4E47-9DE7-786758FEDF7F} Friendly name: ProLaw 11 Install Policy OK ============================================================ Policy {EDF1F2FF-C6C6-431B-870E-2FCF977E61AE} Friendly name: wallpaper Policy OK ============================================================ Policy {EF5A82D7-43BF-4FDF-8237-3100C2953090} Friendly name: Workstation Policy Policy OK ============================================================ Policy {EFD124FA-FC58-4556-9E96-361E5EB00017} Friendly name: Core Applications Install Policy OK ============================================================ Policy {F143210C-4AF2-4FB4-B171-9A821D874BFD} Friendly name: Outlook 2003 Install Policy OK ============================================================ Policy {FB8C8CD6-E698-4C38-A291-B5B73783B98C} Friendly name: SH Password Policy Policy OK ============================================================ Policies OK On Tue, Jun 10, 2008 at 4:08 PM, minesh pandya <minesh.pandya@xxxxxxxxx> wrote: Im quite sure the Sysvol is ok now as the software installations are working on another pc... I will run the GPOTool and see what happens... the DNS is configured correctly... Il have an update tomorrow as its a server in Shanghai im working on... Thanks On Tue, Jun 10, 2008 at 3:27 PM, Darren Mar-Elia <darren@xxxxxxxxxx> wrote: Minseh- Are you sure that SYSVOL on that DC that the client is using is ok? I mean, can you compare it to the PDC emulator to make sure? It sounds like that DC is still having some kind of problem, either with SYSVOL or something in AD. You might want to run GPOTool against that DC and see what it says. Also make sure that the client's DNS config. is correct. A "directory service error" sounds fairly fatal. Darren From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On Behalf Of minesh pandya Sent: Tuesday, June 10, 2008 7:15 AM To: gptalk@xxxxxxxxxxxxx Subject: [gptalk] Re: GP Core Failure In an attempt to resolve this I have implemented the following article: http://support.microsoft.com/default.aspx?scid=kb;en-us;840669 The following error now appears in RSOP: Group Policy Infrastructure failed due to the error listed below. A directory service error has occurred. Note: Due to the GP Core failure, none of the other Group Policy components processed their policy. Consequently, status information for the other components is not available Thanks Minesh On Tue, Jun 10, 2008 at 3:09 PM, minesh pandya <minesh.pandya@xxxxxxxxx> wrote: Recently on one of my sites the Sysvol was overwritten with a empty folder. The Sysvol was restored from a backup. Those GPO's that were applying software and policy are failing on a new build machine. A RSOP on a new build displays the following error: 10 June 2008 9:00:47 pm Group Policy Infrastructure failed due to the error listed below. The specified domain either does not exist or could not be contacted. Note: Due to the GP Core failure, none of the other Group Policy components processed their policy. Consequently, status information for the other components is not available. I ran a DCDiag and everything passed... Software installation via GP on the old build prior to the Sysvol loss works fine. Sysvol permissions have been checked against another DC in another domain and are exactly the same. I can navigate to the Sysvol from the client machine and open scripts, and I can navigate to the software share from the client machine and manually run the MSI's sucessfully. Does anyone have any ideas on what the problem is? -- Regards Minesh Pandya -- Regards Minesh Pandya -- Regards Minesh Pandya -- Regards Minesh Pandya