Server 2012 R2 to 2016: SYSVOL, NETLOGON replication issue
SYSVOL and NETLOGON are not replicating.
Checked to make sure I didnt forget how to migrate DCs with this guide: http://www.rebeladmin.com/2016/10/step-step-guide-migrate-active-directory-fsmo-roles-windows-server-2012-r2-windows-server-2016/
Didnt have any issues promoting to DC. FSMO is moved to new 2016 server. Still have the AD roles on the old 2012 server.
Seems the SYSVOL share was created, but there is nothing in the folder. Server 2016 has two NICs that are teamed. Would that be causing an issue? IPv6 is turned off. Both servers are looking at each other for secondary DNS address.
Rebooted both servers a couple of times.
Checked the old "source" server and there isn't anything the NETLOGON folder. If I try to access the share, I get an access denied error.
Attached dcdiag log.dcdiag.txt
Checked to make sure I didnt forget how to migrate DCs with this guide: http://www.rebeladmin.com/2016/10/step-step-guide-migrate-active-directory-fsmo-roles-windows-server-2012-r2-windows-server-2016/
Didnt have any issues promoting to DC. FSMO is moved to new 2016 server. Still have the AD roles on the old 2012 server.
Seems the SYSVOL share was created, but there is nothing in the folder. Server 2016 has two NICs that are teamed. Would that be causing an issue? IPv6 is turned off. Both servers are looking at each other for secondary DNS address.
Rebooted both servers a couple of times.
Checked the old "source" server and there isn't anything the NETLOGON folder. If I try to access the share, I get an access denied error.
Attached dcdiag log.dcdiag.txt
Cliff Galiher
Teaming wouldn't break anything. Did you check the health of the AD *before* promoting the new DC? Why did you disable IPv6? Definitely some odd questions arise from your post.
ASKER
AD health was ok.
Disabling IPv6 was something recommended by an article that resolved the issue.
Disabling IPv6 was something recommended by an article that resolved the issue.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok...
Windows Server 2012 Std: DC/file share being migrated to a Windows Server 2016 DC/file share. Simple environment. Nothing crazy is setup. No idea if 2012 server was migrated from pre-existing server (inherited client). ADSIEdit doesnt show any other DC's hanging out, neither does AD Sites. Health check was ok. I did run on both servers.
DFS is running, not sure where you're seeing that it's disabled. I see where the log states that could be a cause, but not that it's disabled.
Other than Sysvol/netlogon not replicating to the new server, everything appears to be working as intended.
Windows Server 2012 Std: DC/file share being migrated to a Windows Server 2016 DC/file share. Simple environment. Nothing crazy is setup. No idea if 2012 server was migrated from pre-existing server (inherited client). ADSIEdit doesnt show any other DC's hanging out, neither does AD Sites. Health check was ok. I did run on both servers.
DFS is running, not sure where you're seeing that it's disabled. I see where the log states that could be a cause, but not that it's disabled.
Other than Sysvol/netlogon not replicating to the new server, everything appears to be working as intended.
ASKER
Found the issue to be a mounted backup on the backup server from another tech was left live and somehow wiped the group sysvol folder on the main server. Restored files and checked logins/gp. Everything seems ok now with the sysvol folders.
Sorry for the confusion on the original question.
Sorry for the confusion on the original question.