+ Post New Thread
Results 1 to 6 of 6
Windows Server 2012 Thread, 2012 causing GPO's to fail in Technical; I added a server 2012 member server to my Server 2008 domain this morning. Since then group policy is failing ...
  1. #1

    Join Date
    Nov 2008
    Posts
    137
    Thank Post
    6
    Thanked 3 Times in 2 Posts
    Rep Power
    13

    2012 causing GPO's to fail

    I added a server 2012 member server to my Server 2008 domain this morning. Since then group policy is failing to apply top machines. Simply pulling the network cable from the 2012 server causes everything to start working again.

    Has anyone come across anything similar, and if so what was the cause?

  2. #2

    Join Date
    Apr 2007
    Location
    Croydon
    Posts
    501
    Thank Post
    18
    Thanked 31 Times in 30 Posts
    Rep Power
    22
    Anything from the event logs to help troubleshoot this?

  3. #3

    Join Date
    Nov 2008
    Posts
    137
    Thank Post
    6
    Thanked 3 Times in 2 Posts
    Rep Power
    13
    The report on screen reads

    User policy could not be updated successfully. The following errors were encount
    ered:

    The processing of Group Policy failed. Windows attempted to read the file \\curr
    iculum.local\sysvol\curriculum.local\Policies\{31B 2F340-016D-11D2-945F-00C04FB98
    4F9}\gpt.ini from a domain controller and was not successful. Group Policy setti
    ngs may not be applied until this event is resolved. This issue may be transient
    and could be caused by one or more of the following:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller
    has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.
    Computer policy could not be updated successfully. The following errors were enc
    ountered:

    Code:
    The processing of Group Policy failed. Windows attempted to read the file \\curriculum.local\sysvol\curriculum.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:
    a) Name Resolution/Network Connectivity to the current domain controller.
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).
    c) The Distributed File System (DFS) client has been disabled.
    
    To diagnose the failure, review the event log or run GPRESULT /H GPReport.html from the command line to access information about Group Policy results.
    GPresult shows:-

    Code:
    outlk14.adm
    Location - "\\curriculum.local\SysVol\curriculum.local\Policies\{4929AE2E-BDAB-43EC-B7A3-89F387AD96E4}\Adm\outlk14.adm"
    Error - Logon Failure: The target account name is incorrect.
    pub14.adm
    Location - "\\curriculum.local\SysVol\curriculum.local\Policies\{4929AE2E-BDAB-43EC-B7A3-89F387AD96E4}\Adm\pub14.adm"
    Error - Logon Failure: The target account name is incorrect.
    word14.adm
    Location - "\\curriculum.local\SysVol\curriculum.local\Policies\{4929AE2E-BDAB-43EC-B7A3-89F387AD96E4}\Adm\word14.adm"
    Error - Logon Failure: The target account name is incorrect.
    access14.adm
    Location - "\\curriculum.local\SysVol\curriculum.local\Policies\{4929AE2E-BDAB-43EC-B7A3-89F387AD96E4}\Adm\access14.adm"
    Error - Logon Failure: The target account name is incorrect.
    proj14.adm
    Location - "\\curriculum.local\SysVol\curriculum.local\Policies\{4929AE2E-BDAB-43EC-B7A3-89F387AD96E4}\Adm\proj14.adm"
    Error - Logon Failure: The target account name is incorrect.
    spd14.adm
    Location - "\\curriculum.local\SysVol\curriculum.local\Policies\{4929AE2E-BDAB-43EC-B7A3-89F387AD96E4}\Adm\spd14.adm"
    Error - Logon Failure: The target account name is incorrect.
    ppt14.adm
    Location - "\\curriculum.local\SysVol\curriculum.local\Policies\{4929AE2E-BDAB-43EC-B7A3-89F387AD96E4}\Adm\ppt14.adm"
    Error - Logon Failure: The target account name is incorrect.
    excel14.adm
    Location - "\\curriculum.local\SysVol\curriculum.local\Policies\{4929AE2E-BDAB-43EC-B7A3-89F387AD96E4}\Adm\excel14.adm"
    Error - Logon Failure: The target account name is incorrect.
    onent14.adm
    Location - "\\curriculum.local\SysVol\curriculum.local\Policies\{4929AE2E-BDAB-43EC-B7A3-89F387AD96E4}\Adm\onent14.adm"
    Error - Logon Failure: The target account name is incorrect.
    office14.adm
    Location - "\\curriculum.local\SysVol\curriculum.local\Policies\{4929AE2E-BDAB-43EC-B7A3-89F387AD96E4}\Adm\office14.adm"
    Error - Logon Failure: The target account name is incorrect.
    inf14.adm
    Location - "\\curriculum.local\SysVol\curriculum.local\Policies\{4929AE2E-BDAB-43EC-B7A3-89F387AD96E4}\Adm\inf14.adm"
    Error - Logon Failure: The target account name is incorrect.
    spw14.adm
    Location - "\\curriculum.local\SysVol\curriculum.local\Policies\{4929AE2E-BDAB-43EC-B7A3-89F387AD96E4}\Adm\spw14.adm"
    Error - Logon Failure: The target account name is incorrect.
    visio14.adm
    Location - "\\curriculum.local\SysVol\curriculum.local\Policies\{4929AE2E-BDAB-43EC-B7A3-89F387AD96E4}\Adm\visio14.adm"
    Error - Logon Failure: The target account name is incorrect.
    and the system event log shows:-
    Code:
    The processing of Group Policy failed. Windows attempted to read the file \\curriculum.local\sysvol\curriculum.local\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: 
    a) Name Resolution/Network Connectivity to the current domain controller. 
    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). 
    c) The Distributed File System (DFS) client has been disabled.
    Simply unplugging the network cable fromt he 2012 server and re-runnign the gpupdate command, and it runs fine.

    The 2012 server is just a member server, and is set up for :-

    • File and storage services
    • Hyper-V
    • IIS
    • Print services


    I'm tearing my hair out already with this one

  4. #4
    ful56_uk's Avatar
    Join Date
    Mar 2008
    Location
    Essex
    Posts
    569
    Thank Post
    106
    Thanked 25 Times in 22 Posts
    Rep Power
    19
    Check sysvol replication (dfs) and event logs on your domain controllers for errors

  5. #5

    Join Date
    Apr 2007
    Location
    Croydon
    Posts
    501
    Thank Post
    18
    Thanked 31 Times in 30 Posts
    Rep Power
    22
    How have you got the IP addresses configured for DC/DNS and the member servers. Can you post and ipconfig from each?

  6. #6

    Join Date
    Nov 2008
    Posts
    137
    Thank Post
    6
    Thanked 3 Times in 2 Posts
    Rep Power
    13
    I've finally managed to crack the problem.

    Some time ago, we had a problem with a failing DC, so whilst we rebuilt it we added in an extra DC.n Once everything was back up we demoted the extra DC andf took it offline. It just happens that the new 2012 member server was allocated the same IP as the former temp DC.

    Changing the IP address has solved the problem

    Thanks for the suggestion!

SHARE:
+ Post New Thread

Similar Threads

  1. Windows Update causing DHCP to fail?
    By Dunney in forum Windows Server 2000/2003
    Replies: 7
    Last Post: 26th January 2012, 02:02 PM
  2. Start menu redirection causes Flash player to fail
    By chriscubed in forum Windows 7
    Replies: 0
    Last Post: 22nd September 2010, 09:47 AM
  3. Replies: 13
    Last Post: 27th May 2010, 11:04 AM
  4. Replies: 0
    Last Post: 13th December 2007, 07:46 PM
  5. Replies: 18
    Last Post: 14th October 2005, 09:28 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •