none
Group Policy Infrastructure failed due to the error listed below

    Question

  • Hi All

    I am having problem with the group policy on windows 2003 DC . when I go to windows XP sp3 and execute rsop.msc I am seeing red mark againest computer configuration and in error information getting the followin error. Any suggesition please

    Group policy infrastructure   failed.

    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.

    Thursday, February 09, 2012 9:47 AM

Answers

  •  

    Hi,

    I would like to confirm that have you tried the troubleshooting suggestions “Nav_007” provided? If not, please try all of them.

    It looks like a network connectivity issue. Based on the current situation, I would like to suggest you refer to the following Microsoft KB article and use the built-in tools to troubleshoot the network connectivity issue:

    Troubleshooting RPC Endpoint Mapper errors using the Windows Server 2003 Support Tools from the product CD

    http://support.microsoft.com/kb/839880

    Regards,

    Arthur Li

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Arthur Li

    TechNet Community Support

    Wednesday, February 22, 2012 6:30 AM
    Moderator
  • For one thing, I can see in your GPResults, there is a Computer Startup Script modifying the DNS (WembleyDNS.bat).

    So, as suggested you must try the troubleshooting steps and try adding DNS manually to see if that works.

    Wednesday, February 22, 2012 1:08 PM

All replies

  • If you open up an elevated command prompt and run: gpupdate /force /target:computer, does it succeed?

    My guess is it does, in which case it's likely one of two issues:

    1. The network has not initialised prior to the GP engine
    2. There's a network adapter driver issue (though I haven't seen this one since 2002 with some Broadcom models)

    What you ought to be enabling is this setting in one of your baseline computer policies:

    • Computer Configuration\Administrative Templates\System\Always wait for the network at computer startup and logon = Enabled

    For this setting to take effect, you'll likely have to reboot twice: once to pick up the change and once to honour it. Either that or you can use the same: gpupdate /force command to force its application and then reboot to test it.

    If on the other hand you ran the above gpupdate and it didn't work, then you have a different issue and you ought to check the following event log for more information:

    • Applications and Service Logs\Microsoft\Windows\GroupPolicy\Operational

    Cheers,
    Lain

    • Edited by Lain Robertson Thursday, February 09, 2012 10:05 AM Removed duplicate text.
    Thursday, February 09, 2012 10:04 AM
  • Lain Thanks for quick suggestion.

    I have tried from elevated command prompt and run: gpupdate /force /target:computer but did not work .

    Is this a replication issue ?

    Thursday, February 09, 2012 10:45 AM
  • Hi,

    It's a bit early to say but I wouldn't think so, since that doesn't typically cause a complete client-side failure.

    Did you get a chance to check the client side group policy log I mentioned above? That might bring a little more light to the situation.

    Cheers,
    Lain

    Thursday, February 09, 2012 10:59 AM
  • Hi you suggested that I should check the following event for further clues

    Applications and Service Logs\Microsoft\Windows\GroupPolicy\Operational

    as i am using windows xp sp3 can you please tell me how to get to this log.

    Thanks

    taj

    Thursday, February 09, 2012 12:03 PM
  • Hi Taj,

    My apologies. I didn't even notice the original Windows XP reference. That being the case, here are your logging options (they apply to XP despite the 2003 references):

    Cheers,
    Lain

    Thursday, February 09, 2012 12:35 PM
  • Are you logged in as a standard user or an admin? You will need local computer admin rights to update or see computer policy settings.

    If you are an admin, running gpresult /r on an elevated command prompt should give you computer policy results without a specifying a switch.

    Or, you could also try running gpresult /r /s <ComputerName> from your server. Will prove if the network connectivity is in place?

    Replace <ComputerName> with the name of your target computer.

    As Lain has mentioned already, having Application Logs related to Group Policy will help. You can just open EventLogs and filter them to show only 'error' and 'warnings' for  a start. This should highlight the logs which could be problematic.

    Few more things you could try:

    • Check Network, whether you can ping server?
    • Check DNS, can you ping Server by name from XP  machine?
    • Login as a different user, as well as an admin account?
    • Succesfully Rejoin the machine to the domain?

    Hope this helps,

    Thursday, February 09, 2012 1:55 PM
  • Hi Thanks for reply

    After some tweak we are getting the following error on the pc when execute rsop.msc . I can get to the share and execute the package manually form this pc without any problem. 

    Software Installation failed due to the error listed below.
    The installation source for this product is not available.  Verify that the source exists and that you can access it.

    Additional Information:
    The install of application Snow Inventory Client from policy Install Snow failed.  The error was : The installation source for this product is not available.  Verify that the source exists and that you can access it.

    Failed to apply changes to software installation settings.  Software changes could not be applied.  A previous log entry with details should exist.  The error was : The installation source for this product is not available.  Verify that the source exists and that you can access it.

    Friday, February 10, 2012 10:25 AM
  • I have attached the gpresult /v /s as you suggested

     

     

    Microsoft (R) Windows (R) Operating System Group Policy Result tool v2.0
    Copyright (C) Microsoft Corp. 1981-2001

    Created On 10/02/2012 at 08:59:22

     

    RSOP data for Bris\jon on W5127234 : Logging Mode
    ------------------------------------------------------------

    OS Type:                     Microsoft Windows XP Professional
    OS Configuration:            Member Workstation
    OS Version:                  5.1.2600
    Terminal Server Mode:        Remote Administration
    Site Name:                   Alpha
    Roaming Profile:            
    Local Profile:               C:\Documents and Settings\jon
    Connected over a slow link?: No


    COMPUTER SETTINGS
    ------------------
        CN=W5127234,OU=031 Alpha Branch,OU=Computers,OU=MYcompany Transport,DC=chsuk,DC=com
        Last time Group Policy was applied: 10/02/2012 at 08:57:12
        Group Policy was applied from:      tralpe31a.chsuk.com
        Group Policy slow link threshold:   500 kbps
        Domain Name:                        Bris
        Domain Type:                        Windows 2000

        Applied Group Policy Objects
        -----------------------------
            Default Domain Policy
            Alpha-Wsus
            firewall2
            Install Snow
            USB-disable
            Wembley DNS

        The following GPOs were not applied because they were filtered out
        -------------------------------------------------------------------
            Local Group Policy
                Filtering:  Not Applied (Empty)

        The computer is a part of the following security groups
        -------------------------------------------------------
            BUILTIN\Administrators
            Everyone
            BUILTIN\Users
            NT AUTHORITY\NETWORK
            NT AUTHORITY\Authenticated Users
            W5127234$
            Domain Computers
           
        Resultant Set Of Policies for Computer
        ---------------------------------------

            Software Installations
            ----------------------
                GPO: Install Snow
                    Name:             Snow Inventory Client
                    Version:          3.2
                    Deployment State: Assigned
                    Source:           \\10.194.1.1\testone\snow\MYcompany_dl_client.msi
                    AutoInstall:      True
                    Origin:           Applied Application

            Startup Scripts
            ---------------
                GPO: Wembley DNS
                    Name:         WembleyDNS.bat
                    Parameters:  
                    LastExecuted: 08:50:03

            Shutdown Scripts
            ----------------
                N/A

            Account Policies
            ----------------
                GPO: Default Domain Policy
                    Policy:            MinimumPasswordAge
                    Computer Setting:  N/A

                GPO: Default Domain Policy
                    Policy:            PasswordHistorySize
                    Computer Setting:  5

                GPO: Default Domain Policy
                    Policy:            LockoutDuration
                    Computer Setting:  30

                GPO: Default Domain Policy
                    Policy:            ResetLockoutCount
                    Computer Setting:  30

                GPO: Default Domain Policy
                    Policy:            MinimumPasswordLength
                    Computer Setting:  6

                GPO: Default Domain Policy
                    Policy:            LockoutBadCount
                    Computer Setting:  5

                GPO: Default Domain Policy
                    Policy:            MaximumPasswordAge
                    Computer Setting:  42

            Audit Policy
            ------------
                GPO: Default Domain Policy
                    Policy:            AuditPolicyChange
                    Computer Setting:  Success, Failure

                GPO: Default Domain Policy
                    Policy:            AuditPrivilegeUse
                    Computer Setting:  Success, Failure

                GPO: Default Domain Policy
                    Policy:            AuditDSAccess
                    Computer Setting:  Success, Failure

                GPO: Default Domain Policy
                    Policy:            AuditAccountLogon
                    Computer Setting:  Success, Failure

                GPO: Default Domain Policy
                    Policy:            AuditProcessTracking
                    Computer Setting:  Failure

            User Rights
            -----------
                GPO: Default Domain Policy
                    Policy:            MachineAccountPrivilege
                    Computer Setting:  Bris\Domain Admins
                                       Bris\Enterprise Admins
                                      
                GPO: Default Domain Policy
                    Policy:            TcbPrivilege
                    Computer Setting:  Bris\Domain Admins
                                       Administrators
                                      
                GPO: Default Domain Policy
                    Policy:            TakeOwnershipPrivilege
                    Computer Setting:  Administrators
                                      
                GPO: Default Domain Policy
                    Policy:            EnableDelegationPrivilege
                    Computer Setting:  Bris\Domain Admins
                                       Bris\Enterprise Admins
                                       Bris\jon
                                       Bris\pete
                                      
                GPO: Default Domain Policy
                    Policy:            DebugPrivilege
                    Computer Setting:  Administrators
                                      
                GPO: Default Domain Policy
                    Policy:            LoadDriverPrivilege
                    Computer Setting:  Administrators
                                      
            Security Options
            ----------------
                GPO: Default Domain Policy
                    Policy:            RequireLogonToChangePassword
                    Computer Setting:  Not Enabled

                GPO: Default Domain Policy
                    Policy:            PasswordComplexity
                    Computer Setting:  Not Enabled

                GPO: Default Domain Policy
                    Policy:            ForceLogoffWhenHourExpire
                    Computer Setting:  Not Enabled

                GPO: Default Domain Policy
                    Policy:            LSAAnonymousNameLookup
                    Computer Setting:  Enabled

                GPO: Default Domain Policy
                    Policy:            ClearTextPassword
                    Computer Setting:  Not Enabled

                GPO: Default Domain Policy
                    Policy:            Microsoft network server: Digitally sign communications (if client agrees)
                    ValueName:         MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\EnableSecuritySignature
                    Computer Setting:  1

                GPO: Default Domain Policy
                    Policy:            Network access: Restrict anonymous access to Named Pipes and Shares
                    ValueName:         MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\RestrictNullSessAccess
                    Computer Setting:  0

                GPO: Default Domain Policy
                    Policy:            Network access: Let Everyone permissions apply to anonymous users
                    ValueName:         MACHINE\System\CurrentControlSet\Control\Lsa\EveryoneIncludesAnonymous
                    Computer Setting:  1

                GPO: Default Domain Policy
                    Policy:            Network access: Named Pipes that can be accessed anonymously
                    ValueName:         MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\NullSessionPipes
                    Computer Setting:  COMNAP,COMNODE,SQL\QUERY,SPOOLSS,LLSRPC,BROWSER,netlogon,lsarpc,samr

                GPO: Default Domain Policy
                    Policy:            Network access: Do not allow anonymous enumeration of SAM accounts and shares
                    ValueName:         MACHINE\System\CurrentControlSet\Control\Lsa\RestrictAnonymous
                    Computer Setting:  0

                GPO: Default Domain Policy
                    Policy:            Microsoft network client: Digitally sign communications (if server agrees)
                    ValueName:         MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\EnableSecuritySignature
                    Computer Setting:  1

                GPO: Default Domain Policy
                    Policy:            Microsoft network client: Digitally sign communications (always)
                    ValueName:         MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\Parameters\RequireSecuritySignature
                    Computer Setting:  0

                GPO: Default Domain Policy
                    Policy:            Network access: Do not allow anonymous enumeration of SAM accounts
                    ValueName:         MACHINE\System\CurrentControlSet\Control\Lsa\RestrictAnonymousSAM
                    Computer Setting:  0

                GPO: Default Domain Policy
                    Policy:            Microsoft network server: Digitally sign communications (always)
                    ValueName:         MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters\RequireSecuritySignature
                    Computer Setting:  0

            Event Log Settings
            ------------------
                GPO: Default Domain Policy
                    Policy:            MaximumLogSize
                    Computer Setting:  16384
                    Log Name:          Security

                GPO: Default Domain Policy
                    Policy:            MaximumLogSize
                    Computer Setting:  16384
                    Log Name:          System

                GPO: Default Domain Policy
                    Policy:            RetentionDays
                    Computer Setting:  0
                    Log Name:          Application

                GPO: Default Domain Policy
                    Policy:            MaximumLogSize
                    Computer Setting:  16384
                    Log Name:          Application

                GPO: Default Domain Policy
                    Policy:            RetentionDays
                    Computer Setting:  0
                    Log Name:          System

                GPO: Default Domain Policy
                    Policy:            RetentionDays
                    Computer Setting:  0
                    Log Name:          Security

                GPO: Default Domain Policy
                    Policy:            RestrictGuestAccess
                    Computer Setting:  Enabled
                    Log Name:          Security

           

    Friday, February 10, 2012 10:27 AM
  • Any one there who can help on this matter
    Friday, February 10, 2012 4:23 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.

    Monday, February 13, 2012 9:47 AM
  •  

    Hi,

    I would like to confirm that have you tried the troubleshooting suggestions “Nav_007” provided? If not, please try all of them.

    It looks like a network connectivity issue. Based on the current situation, I would like to suggest you refer to the following Microsoft KB article and use the built-in tools to troubleshoot the network connectivity issue:

    Troubleshooting RPC Endpoint Mapper errors using the Windows Server 2003 Support Tools from the product CD

    http://support.microsoft.com/kb/839880

    Regards,

    Arthur Li

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Arthur Li

    TechNet Community Support

    Wednesday, February 22, 2012 6:30 AM
    Moderator
  • For one thing, I can see in your GPResults, there is a Computer Startup Script modifying the DNS (WembleyDNS.bat).

    So, as suggested you must try the troubleshooting steps and try adding DNS manually to see if that works.

    Wednesday, February 22, 2012 1:08 PM
  •  

    Hi,

     

    I would like to confirm what is the current situation? If there is anything that I can do for you, please do not hesitate to let me know, and I will be happy to help.

    Regards,

    Arthur Li

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Arthur Li

    TechNet Community Support

    Monday, February 27, 2012 2:43 AM
    Moderator
  • Hi Taiuk, I am having the same issue...can you share how you resolved this:

    Group Policy Infrastructure failed due to the error listed below.
    The specified domain either does not exist or could not be contacted.

    I am migrating from Windows 2003 sp2 Standard to Windows 2008 r2 Standard and I am only able to see the Domain Controlers through the Group Policy Console?

    Thanks,

    Mark


    Mark D. Albin IT Master Services www.itmasterservice.com (775) 229-4254

    Sunday, August 26, 2012 2:58 AM
  • I had this issue on Windows 7 SP1 not XP SP3 as above, particularly noticeable by printers assigned to computers via GPO not being added. User GPO's were working fine. The issue was intermittent.

    I eventually uncovered Article ID: 2459530: Event ID 5719 and event ID 1129 may be logged when a non-Microsoft DHCP Relay Agent is used http://support.microsoft.com/kb/2459530.

    As nothing at all seemed to be setup wrong, this had me banging my head against a wall I thought I'd share this, as this post was the top hit on Google on my first search and wish I'd read this here..!

    Wednesday, February 06, 2013 11:23 AM
  • Hi All

    I am having problem with the group policy on windows 2003 DC . when I go to windows XP sp3 and execute rsop.msc I am seeing red mark againest computer configuration and in error information getting the followin error. Any suggesition please

    Group policy infrastructure   failed.

    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.

    Hi,

    I had the exact same error on a windows 7 SP1 laptop in a windows server 2008R2 domain for a particular user.

    I deleted the profile of the affected user on the laptop, rebooted, logged in again as the affected user to recreate the local profile

    and now it's all working !


    • Edited by EdTech2012 Wednesday, July 10, 2013 8:38 AM edits
    Wednesday, July 10, 2013 8:36 AM
  • Hi,

    This problem may occure due to DNS resolution problem or misconfiguration, i had a same problem some day back than i follwed below steps to resolve this issue...

    1) Open CMD

    2) ping <Domain name> for ex: ping xyz.local

    3) if sucessfully resolve host name than browse \\<domain name>\sysvol\<domain name>

    4) if not resolve <domain name> than set dns configuration in client or check on DNS

    5) still problem presist than Add NS reacord in DNS <domain Name >

    6) run ipconfig /registerdns and ipconfig /flushdns command on client computer.

    7) now run rsop.msc

    That's it...

    hope this may work!!!!

    Wednesday, September 18, 2013 10:13 AM
  • Dear All,

    I have faced the same issue today. Yesterday I have enabled Default Domain Control policy and for some reasons and removed. But the policy applied to all the systems in the network. I got it resolved by enabling again DDCP and restore the earlier settings of Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > User Rights Assignment.

    Tuesday, October 29, 2013 6:50 AM