GPO and SYSVOL – How to Reset GPO and SYSVOL

When you talk about "moving" logon scripts and GPO's, that makes me think that you didn't let the SYSVOL replicate properly. The file-based portions of Group Policy would have replicated automatically into the new server computer's SYSVOL. You may have made a serious mess of things, depending on what did or did not replicate and what steps you took, exactly.

That having been said, I highly doubt the "Default Domain Policy" is "corrupt" or missing if you're not getting errors on all your client computers. (Errors on clients would occur much less frequently than every 5 minutes. They would be one every 90 minutes.)

It looks to me like you're having a name resolution, DFS, or file and print sharing protocol problem on the server computer itself.

Some questions:

• What does the output of DCDIAG on the server computer look like?
• Is the server using itself (and only itself) as its DNS server?
• Can you browse to the GPO's path (in the error message) from Windows Explorer on the server computer?

After a LOT of testing and waiting for user feedback, I tried the above mentioned Hardened UNC approach, but this time not via GPO itself, but via a GPP to set the appropriate registry entries (HKLM\SOFTWARE\Policies\Microsoft\Windows\NetworkProvider\HardenedPaths\\\*\NETLOGON || SYSVOL - RequireMutualAuthentication=0, RequireIntegrity=0) directly. Lo and behold! It works...I have no idea why the implemented GPO options don't, though. Maybe I did something wrong, but at this time I really don't care anymore, as long as it works. Microsoft will probably release a (new) hotfix soon anyway.

EDIT: Please remember that the hardened UNC Paths were implemented to fix a "critical" Windows security issue, which can be dated back to the year 2000. By deactivating the hardened UNC paths you actively open that hole again, if it's worth it depends on your topology and / or needed infrastructure security.