How to Apply Default Domain Policy in Windows Server 2012 R2

In order to remove the Folder Redirection settings from a GPO properly, you need to:

• As mentioned by other people here, remove the Documents and Settings folder under \\domain\sysvol\Policies\{GPO GUID}\User and the fdeploy.ini and fdeploy1.ini files contained within.

However, on its own, this will confuse the GPO Editor as it still thinks there's a Folder Redirection policy attached to the GPO. To solve this, you need to remove the association between the GPO and the Folder Redirection Group Policy Extensions (there are two, one which activates Folder Redirection editing in the GPO Editor, the other activates the actual Folder Redirection policy processing):

• Open AD Users and Computers. Turn on Advanced Features (View->Advanced Features). Navigate to System->Policies->{GPO GUID}. Right click on {GPO GUID}, choose Properties. In the dialog that pops up, switch to Attribute Editor. Scroll down to gPCUserExtensionNames, and double click it.

• This will pop up a dialog with a long text entry box, and a bunch of GUIDs. This attribute defines the list of GP Extensions associated with this GPO in the User context. Immediately above it you'll see the related attribute gPCMachineExtensionNames which defines the associated GP extensions in the Machine context of the GPO.

• Delete the following entry from gPCUserExtensionNames : [{25537BA6-77A8-11D2-9B6C-0000F8080861}{88E729D6-BDC1-11D1-BD2A-00C04FB9603F}]

• Note that associated GP Extensions are grouped by square brackets [].

• Do not touch any other entries in the attribute, or you will break other functionality in the GPO.

• Click OK, and you're done.

• If you're interested in what GP Extension is associated with each GUID, simply use regedit to search the registry for that GUID - e.g. try searching for 25537BA6-77A8 or 88E729D6-BDC1.

It sounds to me like your clients aren't using your DCs as their DNS servers. You should make sure that your DCs are indeed running DNS for your AD zone and that your clients are configured to use them.

If there was a change in your config, the old policies will still apply since they're cached on the clients, but they won't be able to update or check for new policy. If you're using DHCP, make sure that it's set to configure clients to use the proper DNS servers.