Windows Server 2008 DC Fsmo problem

DT1640759
DT1640759 used Ask the Experts™
on
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
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
MaheshArchitect
Distinguished Expert 2018
Commented:
Did you get success in seizing fsmo?
If yes, what is ipaddress and preferred dns on network card of dc
Make sure it is same and remove any other entry from dns and add loopback address as alternate dns entry
Then from aduc, remove all unwanted dcs and reboot the dc
It should work
MaheshArchitect
Distinguished Expert 2018
Commented:
Also remove ns records and host a record for other dcs
Metadata for other dcs must be cleared
Technical Architect - HA/Compute/Storage
Commented:
Make sure DNS0 on the vNIC is pointing to itself and no others.

Remove the other DCs from Sites & Services
Remove the other DCs and references to them from DNS
Use NTDSUtil to verify.

Restart and verify the DC has FSMO ownership. You may need to run this process again.
OWASP Proactive Controls

Learn the most important control and control categories that every architect and developer should include in their projects.

DT1640759System Engineer - IT

Author

Commented:
Hi Mahesh and Philip,

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.
MaheshArchitect
Distinguished Expert 2018

Commented:
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
Philip ElderTechnical Architect - HA/Compute/Storage

Commented:
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.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial