Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We have a 2003 DC that I want to virtualize as the lease on the hardware is expiring.

It's a DC, GC, FSMO master, DNS, DHCP and TS License Server.

I want/need to keep the same name and IP on the new box, and my plan right now is:

Build the new box and add to the domain with temp name/IP, patch etc. then dcpromo and make it a DC.

Sit back and wait for things to replicate.

Transfer FSMO roles, install DHCP and migrate/configure scopes, authorize new server, de-authorize existing server so now this one is our DHCP server.

De-Activate TS Licensing on current DC.

DCPromo current DC and demote, change name and IP and force replication amongst remaining DC's.

Rename new DC to name of existing DC, reboot, force sync etc.

Change IP of newly renamed DC to required IP, force replication.

Install TS Licensing role and install/activate TS CALs.

Hopefully sit back and admire my new DC with the same name and IP of the old hardware.

share|improve this question
    
What's the question? –  Nick Kavadias Jul 23 '10 at 5:56
    
why does it need to have the same name/ip? is adding an additional IP on the box & using a cname good enough? –  Nick Kavadias Jul 23 '10 at 5:58

3 Answers 3

Why not just do a P2V using vSphere Converter?

share|improve this answer
    
This works very good in almost all cases, I virtualized our old DC's this way to retain any old legacy setup within our domain. –  pauska Oct 11 '10 at 1:08

If you are planning to virtualize the box, use Disk2VHD

Oh, and once you've made a server a DC, you cannot rename. (well you can, but enjoy hell)

share|improve this answer
2  
We use ESX rather than Hyper-V and I'm not interested in doing any kind of P2V as it's more trouble than it's worth trying to remove all the HP agents and stuff. Can you expand on "enjoy hell" as I've renamed DC's before with no issue, I just don't do it often hence the sanity check. technet.microsoft.com/en-us/library/cc757349(WS.10).aspx suggests what I thought, which is that there's little more it than renaming it and replicating. –  Hutch Jul 22 '10 at 17:39
    
I would think that removing agents is less trouble than renaming a DC. –  DanBig Jul 22 '10 at 18:04

Why aren't you running two DC's?

Setup the first Virtual Machine as a new secondary with a different name, promote etc, decomission the old physical, rebuild the old physical as virtual with the same name, promote.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.