Server 2003 replacement domain controller issue
Posted on 2011-05-11
I have a client that had a 2003 domain server crash. I had installed a secondary domain controller and promoted it to secondary DC status before the crash, however failover did not happen and it took the network down. I seized the fsmo roles from the crashed server to the new server and everything was working that day. I was remoted in when I seized the roles and told the client that the old server MUST be disconnected so that it could not miraculously comeback online and cause problems since the roles were seized and not transferred. The client did not disconnect the old server and it came online and now I have issues with the new replacement server.
Now on the new replacement server the "sysvol" and "netlogon" folders are empty and unshared. The workstations keep connecting back to the old server instead of the new one.
My question is there a way to resolve this without reloading the new server and rebuilding the domain from scratch and rejoining all the workstations. I really don't want to have to go this route as they have 100+ workstations.