none
Group policy not refresh

    Question

  • Dear Team,

    Please check below we facing one issue in Domain controller

    when we run Gpupdate/force received below error please suggest about this 

    Tuesday, January 19, 2016 5:26 AM

Answers

  • Hi,

    Regarding the error, you could refer to the following steps to narrow down the issue:

    1. First we should make sure DFS and FRS both run properly.

    a. Initiate the force replication of the DC by restarting the FRS services to have a test.

    b. Run DCDIAG and REPADMIN to check the status.

    If something is wrong with the FRS and DFS, you could go through the following article to perform troubleshooting:

    How to Troubleshoot the File Replication Service and the Distributed File System

    https://support.microsoft.com/en-us/kb/272279

    2. Troubleshoot Name Resolution/Network Connectivity:

    a. Please try to browse the sysvol directory (\\domainname\sysvol\) from start\run.

    b. If you receive the error like “Network Error-Windows cannot access \\domainname\sysvol\”, then try to browse the Sysvol directory by Domain Controller name or FQDN (\\DC1\Sysvol\) instead of domain name from Start\Run.

    c. If you can access the sysvol without any problem, so the ultimate cause for this issue is Name Resolution/Network Connectivity problem.

    More article for your reference:

    Error results when you run the "gpupdate /force" command on a computer that is running Windows Vista: "User policy could not be updated successfully"

    https://support.microsoft.com/en-us/kb/934907

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, January 19, 2016 9:50 AM
    Moderator

All replies

  • Tuesday, January 19, 2016 6:16 AM
  • Please suggest about this
    Tuesday, January 19, 2016 8:13 AM
  • Hi,

    Regarding the error, you could refer to the following steps to narrow down the issue:

    1. First we should make sure DFS and FRS both run properly.

    a. Initiate the force replication of the DC by restarting the FRS services to have a test.

    b. Run DCDIAG and REPADMIN to check the status.

    If something is wrong with the FRS and DFS, you could go through the following article to perform troubleshooting:

    How to Troubleshoot the File Replication Service and the Distributed File System

    https://support.microsoft.com/en-us/kb/272279

    2. Troubleshoot Name Resolution/Network Connectivity:

    a. Please try to browse the sysvol directory (\\domainname\sysvol\) from start\run.

    b. If you receive the error like “Network Error-Windows cannot access \\domainname\sysvol\”, then try to browse the Sysvol directory by Domain Controller name or FQDN (\\DC1\Sysvol\) instead of domain name from Start\Run.

    c. If you can access the sysvol without any problem, so the ultimate cause for this issue is Name Resolution/Network Connectivity problem.

    More article for your reference:

    Error results when you run the "gpupdate /force" command on a computer that is running Windows Vista: "User policy could not be updated successfully"

    https://support.microsoft.com/en-us/kb/934907

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, January 19, 2016 9:50 AM
    Moderator