Convert a W2K3 DC to a VM

Posted on 2011-10-20
Medium Priority
Last Modified: 2012-06-21
We have an old Windows 2003 Server DC that is starting to show hardware problems, and would like to move this server to a Vmware Esxi 4.1 and run it as a VM. This old server presently acts as a DC and also the DNS, DHCP and WINS server for the network. We have another DC (Windows 2008) running on the network, acting also as a 2nd DNS server.

We were planning on using the VMware vCenter Converter to do a P2V conversion. Will this cause issues since it is a DC ?  Or should we demote it to a member server, remove DNS server, dhcp, wins before doing the conversion, and then promote it back to a DC and assign DNS, Dhcp, Wins server roles after it is running as a VM ?


Question by:ndidomenico
  • 4
  • 4
  • 2
  • +2

Accepted Solution

bill_lynch earned 800 total points
ID: 37000955
Why not just build a new 2003 domain controller as a VM and demote the other after AD has replicated.  Also remember to move FSMO roles if you choose this route.

Author Comment

ID: 37000980
This server is running a custom application and we don't want to go through the re-installation and configuration.

Expert Comment

ID: 37001008

It appeears that VMware recommends staying away from P2V Domain Controllers, so it looks like a demotion and then a re-promotion would be the better choice.
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.


Assisted Solution

bart1975 earned 400 total points
ID: 37001024
It is not recomennded to P2V a DC, it can cause kerberos & replication issues etc.
Maybe you could build another DC and Demote this one and then P2V it to get it within the VM environment
LVL 124
ID: 37001039
Do you have a single DC - if so it's recommended to use VMware Converter COLD, e.g. with Server powered-off!

otherwise you would have to shutdown ALL the services if doing the conversion HOT.

It may be quicker to build a new DC, and transfer the roles (and safer).
LVL 124

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE^2)
Andrew Hancock (VMware vExpert / EE MVE^2) earned 800 total points
ID: 37001055
Build a new DC, and Transfer the roles, and then migrate DHCP, DNS, WINS

Author Comment

ID: 37001327
Ok, so no P2V of a DC.

But it would save us a lot of work if we could P2V the server without the DC, DNS, DHCP, WINS server roles, because of the custom server application running on it for all of our users, and also the shares used by all of our users. And we need to keep the same server name, IP address, etc.

Would this be a viable plan:
1) Demote server as a DC
2) Remove DNS, DHCP, WINS server roles
3) Shutdown server
4) Do a cold P2V of server and create new VM from the P2V file, keeping same Name and IP address
5) Promote VM as a DC
6) Install DNS, DHCP, WINS

LVL 124
ID: 37001527
The issue you will have if the server is having hardware difficulties, whether P2V will work correctly, and get an image 100% of the disk.

If you are going to do a COLDCLONE P2V, no need to shutdown any of the services. Shutdown the server for the last time. (NEVER TURN ON THE PHYSICAL AGAIN connected to the LAN!)

Boot COLDCLONE P2V, convert to VM, do not connect to the network, at first reboot, follow Best Practice, and remove drivers, and hidden devices.

Read fellow Expert Bestway's article.

Best Practice Video Guide here

Check the video here I created earlier, and you can see the process.

TURN on VM and connect to LAN, check for replication errors, but there should not be any, and after 15-30 minutes all errors should have cleared!

Not recommended, but if done carefully can be done!

Author Comment

ID: 37001723
hanccocka: your last comment is for a P2V of a regular member server, not a DC, right ? Your last statement about checking replications errors seems to refer to a P2V of a DC. Everybody else seems to strongly discourage a P2V of a DC (as you also seem to: "... Not recommended, but if done carefully can be done!).

Note: the hardware is presently working ok on the old server. We had a bad memory chip issue recently and had to change some memory chips. The server is 7-8 years old, so we thought we should think about moving it elsewhere before we start having real hardware problems (disk, motherboard, etc).
LVL 24

Expert Comment

by:Luciano Patrão
ID: 37001782

@hanccocka in my opinion for this type of servers DC, Exchange etc., you should always disable non Windows services(and in DC case, all services related).

Not for the conversion itself, but when you power up that VM for the first time.

Until you clean, remove any phantom hardware, build new Network adapters(all this in safe mode), you should have that services down.

Then when the VM is clean and ready, you should run Windows on normal mode and start all services.

With this, we will bypass any issue that may encounter after the P2V. Is safer this way.

But like above answers, the best choice is too build a new DC and move all the roles into the new DC. But if you have legacy software that you need to move and you cannot install again, then do this conversion in the right way, to bypass any issues on your DC and domain.

Hope this can help.

LVL 124
ID: 37001841
Yes, I know it is!

It depends on your circumstances, if you have time to setup again, build a new DC, transfer roles, MIgrate Services. That should be the prefered route, BUT, we ALL live in the real world, where time is money, and sometimes, that takes time, and your Server is failing........(it could be dead in the water in an hour!)

or P2V, it's not recommended, but many, many P2Vers do it! Many create P2V copies for Backup, and also to provide DR and Test facilities, and some do it, WARM *WITHOUT* shutting down!

It's also like asking the question, "whether a Domain Controller should be virtual?".

If the machine is OFF, and COLDCLONED, AD does not know anything has changed, other than the DC has been OFF for x hours!

After which, it will start replicating again.

Once you understand the possible issues, you must eventually make the decision, and if it's not that large a DC, you'll be done in 30 mins! (image will be done, 30 mins to tidy drivers and hidden devices etc)

Test it and try it, it will not hurt!
LVL 24

Expert Comment

by:Luciano Patrão
ID: 37001903

And since he have another DC in the domain, he should have double careful.

I have done P2V in domain with one or more DCs. Also I have restored DCs in some failovers of all the infrastructure. The focus must be on how to do the job and do the right plan(to perform a P2V or to perform a restore)

Example on restoring DCs:

If you have backup 2 or more DCs with lets say Veeam, if you plan to restore all the DCs, you should always start with the last DC that you have backup. Because this last DC is the most actualized in the domain.


Author Comment

ID: 37119997
Finally, as it was recommended, we did a fresh install and migration of services instead of doing a P2V.


Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If we need to check who deleted a Virtual Machine from our vCenter. Looking this task in logs can be painful and spend lot of time, so the best way to check this is in the vCenter DB. Just connect to vCenter DB(default DB should be VCDB and using…
While rebooting windows server 2003 server , it's showing "active directory rebuilding indices please wait" at startup. It took a little while for this process to complete and once we logged on not all the services were started so another reboot is …
Teach the user how to delpoy the vCenter Server Appliance and how to configure its network settings Deploy OVF: Open VM console and configure networking:
Teach the user how to use configure the vCenter Server storage filters Open vSphere Web Client:  Navigate to vCenter Server Advanced Settings: Add the four vCenter Server storage filters: Review the advanced settings: Modify the values of the four v…
Suggested Courses

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question