(h2v) convert 2003 server hardware to hyper-v

[Achandler]

Sorry been busy.

Install 2008R2 to your micro server. Create a VM on your microserver, Server 2008R2.

You now have 3 servers, a VM host, the old server and a new clean VM.

Make the new VM a DC, using dcpromo, have this server takeover the FSMO roles, DNS and DHCP fro your 2003R2 server.

We still have 3 servers, but now the main DC (along with DNS and DHCP) is virtual and is 2008R2.

Now we do a physical to virtual convert on the 2003R2 server onto the host (microserver). So we end up with 3 Server still. The Mmcro server as a host, then 2 virtuals the a New main DC and the older 2003R2 server. You also have a spare phsyical box (the old 2003R2 server).

I would now assume you are going to move the virtual server back from the micro server to the old physical box, once you ahve wiped it and installed HyperV etc on. We we end up with 3 servers still, 1 physical 2 virtual and you take your microserver home.

Its liek that crossing the river with the corn, a chicken a hen and a fox!

[edutech4schools]

Ahh that looks good. Cheers.

How does SCVMM work. Do I install it onto my micro server and it grabls an image from a remote machine or does it need installing on to the machine its going to image?

[Achandler]

Install it on the host, then when it converts it installs an agent on the 2003R2 server to capture it.

[edutech4schools]

Just downloading as I type. Going to take a few hours.

Does the server need sql installed to run SCVMM or does it install its own database?

[edutech4schools]

Just found out it does install sql express.

[edutech4schools]

Make the new VM a DC, using dcpromo, have this server takeover the FSMO roles, DNS and DHCP fro your 2003R2 server.

Why would you do this in a vm and not on the host machine? Both are not recommended by MS.


EDIT: by both I mean. running a DC in a vm or running hyper-v on a host that also is the DC.

[Achandler]

If you are using 1 server for everything which you are (not recommended) then running your DC as a VM or DC as a physical HyperV is neither here nor there.

Microsoft recommend keeping 1 physical DC if you virtualise because shoudl your Hosts all go down then you still have DC and can login, also your hosts would fail without DNS if you were using Failover Cluster Manager.

The main reason I would do it to the VM (not recommended) and not the host (also not recommended) would be I would have 2 DCS in the end, and I can backup the whole Virtual Machine easier then backing up a physical machine. It would also be easier in the future to delete this new DC should it be necessary, as you can demote it and remove it without effecting the physical host.

[edutech4schools]

Sorry to drag this on.

I would have 2 DCS in the end

But with my set up I would end up with only one would I not. (one vm dc and one vm server) is that correct or have I got it wrong, or am i still leaving the roles on the old server which has now been virtualzed.

Sorry I am really keen to go down this road but need double check everything before I start.

[Achandler]

Its not a problem.

Your Main DC would be the new one, but I wouldn't demote your 2003R2 server yet. I would keep it running as a DC (once virtualised) but not the main DC; at least until you are sure everything is working and you are happy with it.

[edutech4schools]

Cheers