Single Domain Controller to Virtual Environment

Hello Everybody,

I have a question for VMware.
We have a domain and got only one domain controller in the network and we converted the Domain Controller to Virtual Environment to run in EXSi 4.0.
After conversion it did not take the IP address and we assign the same IP address manually, before in the physical server the network was teamed. We are able to ping the server with IP address but not with name and when we give nslookup command it returns bad server. Another  thing when the client tries to login its taking more time to get the profile to be loaded and always the popup comes asking the user name and password for connecting to the file server in which the user profile synchronized.
Kindly suggest us is it advisable to convert a single Domain controller to virtual environment. If it is advisable to do kindly suggest us a work around.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

It is absolutely doable/advisable to convert a DC to a VM...all my DCs are VMs. Did you P2V your physical DC to a virtual one? Sometimes doing a P2V causes issues. I P2V'd all my DCs without any issues (thankfully), but I have seen some posts on here where there has been. That being said, with the issues you're having, I recommend building up a clean VM from scratch (that is also VMware's official stance, not just with DCs, but any VM); add whatever server roles you want (DNS, DHCP, etc.); promote it to a DC; transfer FSMO roles to it from your other DC VM; demote your 1st DC VM; change the IP of your 1st VM to DHCP; change the IP of your new DC VM to the IP of your old DC. You should then be good to go.

vmwarun - ArunCommented:
I do not recommend a P2V of a Domain Controller for 2 reasons, USN Problems and DC reachability problems.
The recommended way is to dcpromo a new 2008 or 2003 VM, transfer the roles to the VM and then wait for replication to get completed.
After checking with dcdiag and other tools for any issues, create a second VM and promote it as a DC for redundancy.
Once both VMs are up and running, demote the physical DC.

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
As per  my knowledge this seems to be the issue with the P2V process which you have done... Better do it agiain and make sure that the NIC showing in the Virtual Machine is using the Vmware nic driver rather than the Physical Nic..... check the Nic information is changed or not in the device manager.
Was DNS AD integrated?

 When pinging the IP is the -a switch used for both IP and host name, is the FQDN returned?

I would prefer two DC's one physical (if using MS DNS) and any number virtual.
That way DNS would be available no matter what state the host was in.
gogimathewAuthor Commented:
The solution was partially correct.
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

From novice to tech pro — start learning today.