Windows Server 2008 DC Fsmo problem
Hi,
I copied a Windows Server 2008 domain controller (Hyper-V VM) from company to my home for testing. I impoted the VM and seized all FSMO roles to this dc. DNS server and all AD tools cannot locate the AD information after I restart the dc everytime. Please refer to the following screenshot.
After I used the tool NTDSUTIL and submited roles -> connections, All DNS and AD services decame normally.
I want to know that why happpen this issue and how to fix it.
Note this domain contain 6 DCs, however, I only copied one dc to my home network and I will delete the other five dc later.
Thomas
I copied a Windows Server 2008 domain controller (Hyper-V VM) from company to my home for testing. I impoted the VM and seized all FSMO roles to this dc. DNS server and all AD tools cannot locate the AD information after I restart the dc everytime. Please refer to the following screenshot.
After I used the tool NTDSUTIL and submited roles -> connections, All DNS and AD services decame normally.
I want to know that why happpen this issue and how to fix it.
Note this domain contain 6 DCs, however, I only copied one dc to my home network and I will delete the other five dc later.
Thomas
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You might have missed step initially to set dc own ip as static ip and primary dns as well followed by loopback as secondary dns
You are using vmware workstations at home if i am not wrong and it actually hand out ips automatically with built-in dhcp and there's you got in issues i believe
You are using vmware workstations at home if i am not wrong and it actually hand out ips automatically with built-in dhcp and there's you got in issues i believe
When there are other DCs, especially one that has the FSMO Roles on it that is not the one being worked with, AD will sometimes not start.
It can take a bit of a step-by-step process to get AD started to the point where the FSMO Roles can be seized. Once that is done though things are pretty much golden after cleaning up as above.
It can take a bit of a step-by-step process to get AD started to the point where the FSMO Roles can be seized. Once that is done though things are pretty much golden after cleaning up as above.
ASKER
Your suggestions work for me. I removed the other DCs in Active Directory Sites and Services, the other DCs and references to them from DNS. Restart the DC and problem is solved.
Actually, I want to know why happen this issue. I have seized all FSMO roles to this dc.
Thanks for your help.