1

I recently installed 2 new Windows 2016 server to replace my 2008 Domain controllers. Everything seemed to go fine but now I am having issue with files replication from one to the other. The biggest issue is Group Policy. If I do a \domain I only see the sysvol folder not the netlogon folder. I have been doing some research and havent been able to come up with anything that works. I have demoted the 2008 servers but still have them on the network. Its seems like a DNS issue but cant find anything wrong with DNS, but I am sure there is.

When I do go to a client and try to manually update GP I get the following error.

Updating policy…

Computer policy could not be updated successfully. The following errors were encountered: The processing of Group Policy failed. Windows attempted to read the file \DOMAIN.LOCAL\SysVol\PLENARYGROUP.LOCAL \Policies{9E559CBB-964F-4750-97E8-9BCD152371A5}\gpt.ini from a domain controller and was not successful. Group Policy s ettings 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 domai n controller).

c) The Distributed File System (DFS) client has been disabled. User Policy could not be updated successfully. The following errors were encountered: The processing of Group Policy failed. Windows attempted to read the file \DOMAIN.LOCAL\sysvol\PLENARYGROUP.LOCAL \Policies{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful.

Group Policy s ettings 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 domai n 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 informati on about Group Policy results.

4 Spice ups
2

You might have to migrate from FRS to DFSR SYVOL although it should still be working in 2016, but that’s the last supported. Good Luck.

3

Will that work even if I have already demoted the 2008 DC’s?

4

You have to have a functional FRS setup prior to the migration but, yes I did this over the summer after we upgraded to all 2016 DC’s.

Is there a scripts folder inside your sysvol share under your domain name?

5

Thanks Chris for the reply.

I have scripts folder on the old 2008 DC but not the new 2016 DC. On the new one I just have a policies folder. Also from what I have read, If you browse to \Domainname.com you should have a logon shared folder and Sysvol folder. I only have Sysvol when I do that.

6

I would try creating the missing share on your 2016 DC. Create the folder if neccessary.

Share Name: NETLOGON

Path: %SystemRoot%\SYSVOL\sysvol\your.domain.name\SCRIPTS

No user limit

Everyone Read Share Permissions

DOMAIN\Administrators Full Control Share Permissions

It may make the logon folder functional, but you need to test file replication between servers (if you have more than one) to make sure they are copying.

7

Now that I reread your OP you definitely have another issue alongside the NETLOGON folder.

\DOMAIN.LOCAL\SysVol\PLENARYGROUP.LOCAL

Is your domain a single domain forest?

You don’t necessarily have to (or should want to) answer these questions on this PUBLIC forum… but…

Is DOMAIN.LOCAL a valid domain name in your environment?

is PLENARYGROUP.LOCAL a valid domain in your environment?

Assuming this should be a single domain, you need to figure out whether the \DOMAIN.LOCAL address is reachable from the client.

If you can’t get to \DOMAIN.LOCAL\SysVol\PLENARYGROUP.LOCAL from a client, but can get to \PLENARYGROUP.LOCAL\SysVol\PLENARYGROUP.LOCAL then you need to figure out why the client is not working.

8

Thanks Chris for all the help. I was able to get this resolved. Had to do a restore on the sysvol and scripts folders. This is how I did it.

Once I did that and had frs working good, I was able to do a migration to dfrs and all is now looking good.