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
DT1640759System Engineer - ITAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MaheshArchitectCommented:
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
MaheshArchitectCommented:
Also remove ns records and host a record for other dcs
Metadata for other dcs must be cleared
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
10 Holiday Gifts Perfect for Your Favorite Geeks

Still have some holiday shopping to do for the geeks in your life? While toys, clothing, games, and gift cards are still viable options for your friends and family, there’s more reason than ever to consider gadgets and software.

DT1640759System Engineer - ITAuthor 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.
MaheshArchitectCommented:
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/StorageCommented:
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's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Virtualization

From novice to tech pro — start learning today.