activateahsd
asked on
Manually copy SYSVOL and NETLOGON?
I have a new Server 2016 machine on the same domain as an old SBS2008 machine. I have joined the 2016 box to the domain and promoted it to a DC. It has replicated AD, DNS and Group Policy but it wont create the SYSVOL or NETLOGON shares on the new machine. I have tried all the fixes on google i could find that seemed relevant but it wont replicate FRS. As it seems to have replicated everything else i was wondering if i could simply manually copy over the SYSVOL and NETLOGON shares to the new machine? I know its probably not recommended but the old machine will be demoted so in theory i would have thought that at that point it wouldnt matter that it couldnt replicate?
Anyway if anyone has any idea if this approach is workable please let me know?
Thanks in advance.
Andrew
Anyway if anyone has any idea if this approach is workable please let me know?
Thanks in advance.
Andrew
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi,
The event logs don't really tell me much, just that frs cant replicate, dcdiag does show some frs issues but googling these hasn't helped.
One thing i didn't look at which i should have done at the start was the output of ipconfig/all on the 2008 machine, for dns it shows its ip and the ip of the new server but also above them in the list is a ipv6 address, nslookup on the server shows that same ipv6 address and unknown for the default server so i am thinking that this might be something to do with it.
Can anyone tell me what to try next?
Thanks
Andrew
The event logs don't really tell me much, just that frs cant replicate, dcdiag does show some frs issues but googling these hasn't helped.
One thing i didn't look at which i should have done at the start was the output of ipconfig/all on the 2008 machine, for dns it shows its ip and the ip of the new server but also above them in the list is a ipv6 address, nslookup on the server shows that same ipv6 address and unknown for the default server so i am thinking that this might be something to do with it.
Can anyone tell me what to try next?
Thanks
Andrew
ASKER
Also i found on the new server that the 1st dns address in the list was ::1 which i know has caused issues with replication in the past on other machines, i have removed that entry now.
I have done dcdiag /test:dns and on the new server it passes all ok, on the old server i get some missing AAAA records for both DC's which i think is IPv6 related. I am thinking about turning off IPv6 on the SBS2008 machine in case it is this that is causing the replication problem?
I have done dcdiag /test:dns and on the new server it passes all ok, on the old server i get some missing AAAA records for both DC's which i think is IPv6 related. I am thinking about turning off IPv6 on the SBS2008 machine in case it is this that is causing the replication problem?
Don't turn off IPv6. Since vista/2008, WI does runs a concurrent dual stack. IPv6 isn't your problem.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Agreed. My original commend definitely put mentioning DFS-R in the last paragraph and was "as an aside" for a reason. While DFS-R improves on FRS in may ways, it won't fix existing corruption or issues already present in replication.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Asker solved the problem with help from experts.
http://www.rebeladmin.com/2015/04/step-by-step-guide-for-upgrading-sysvol-replication-to-dfsr-distributed-file-system-replication/