Jump to content

Recommended Posts

Posted

Am I right in thinking it's still best to use vmware converter to convert a server even if the virtual system will end up being hyper-v.

 

Not sure if any of the converters for hyper-v have moved on since last year when I checked. Back then I was advised to use vmware converter to get the vm and then convert that to hyper-v.

 

Is this still the recommended method?

Posted

No, it uses a VSS writer and snapshot process obviously there is an overhead and a tax to be paid whilst the vhd copy is made so if you are doing it on a live production server.

 

That why the SCVMM version is better as it was designed to be used on live running boxes and also supports 2000 Server SP4

 

We have used Disk2VHD on Exchange Servers with no problem on the host.

 

Obviously if your copying the system volumes from a production SCSI Raid server your going to have a few things to sort out when to try to emulate it on a VM as a VHD but with a bit of practise and google on hand you will get the hang of it.

Posted

Basically I am updating a server from 2003 to 2008r2 and have managed to get hold of a hp micro server to aid me in the update.

My plan is to install 2008r2 on to the micro server, then dcpromo and move the roles. At that point I was going to virtualize the old 2003 server and move that on to hyper-v on the 2008 server. At that point I can wipe the old 2003 server and install 2008, move everything back.

 

does that sound about right?

 

Looks like SCVMM needs a server to run from while it does its thing. As this is a one off h2v and its a small primary with no spare servers would I be best using the disk2vhd?

 

Thanks

Posted

A few questions about SCVMM.

 

If I install SCVMM onto a 2008r2 box will it create a vm of my 2003 AD server and will I then be able to fire up this vm on the 2008r2 box that is running SCVMM. I dont have access to lots of servers so will need to run the vm from the machine that has captured it.

Posted

Yes you can take a physical 2003 Server, use the offline physical to virtual converter (I would), then you will end up with a virtual server you can run on any server with HyperV installed.

 

I have done it before.

Posted

One last question.

 

Would I be best moving the DC roles to my 2008r2 box before conversion? So I end up with a 2008r2 server with the roles and running a hyper-v with my 2003 server. or is it ok to just grab the lot and fire the 2003 vm with all DC roles up and run it like that.

Posted

Personally if you are intending to move to a 2008R2 DC then I would move the roles across because I converted. Do you only have 1 DC, if so i'm not sure if promoting the host to a DC is a good idea, as you want the hsot to do one thing.

 

Have you considered making a new DC on the host, and having 2 DCs one new virtaul one and the older 2003 one, then move the roles etc and convert.

Posted

Yes one server in the school that does everything. And I have my own micro server that I will need to remove from the school at some point.

 

So do you mean -

 

setup 2008r2 on my micro server

add 2008r2 to domain

dcpromo microserver

 

At this point would I make the 2008r2 master dc or not?

 

then vm convert the 2003 server

 

move the 2003 vm onto my 2008r2 microserver

 

wipe the old server and setup os

Posted

Think I might bottle out on this.

 

Going to take a vm of the server as a backup, but will do a standard migrate. Move all the files and roles onto the microserver, check all is ok and then move them back. Its long winded but is something I have done many times. The virtual element is adding in some confusion for me.

Posted

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!

  • Thanks 1
Posted
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.

Posted

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.

Posted

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.

Posted

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.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...