Hyper V going head to head with Virtual Server

[Geek_of_HeathMount]

Morning all,
As with all things IT there is an impossible deadline to meet and little time to implement the desired solution!! With that in mind here is my situation

I have a brand new 64bit server with 2008 Enterprise R2 installed on it and I can not decide if i should use the Hyper V role or just install MS Virtual Server 2005

I know that Hyper V is the way to go but I just can't get a virtual server to connect to the network. there always seems to be a missing device However, if I use virtual server or virtual pc instant connection and all my problems disappear.

Do i take the easy route or do i keep trawling the web looking for a solution to my Hyper V problem ??


Any help greatly appreciated

[mb2k01]

The technologies aren't too far apart. I'd say use what you know works if your deadline is fast approaching. If you have a bit of extra time Hyper-V would be the preferred option. Make sure that BIOS is set up correctly to use it and then install the role - i've done it on a few servers now and i've not come accross a problem.

At a rough guess I'd say check bios and then check nic drivers?

[steve]

It sounds like you're using pre-existing Virtual PC servers on Hyper-V.

What I believe is happening is the NIC within these VMs isn't functioning when connected to a Hyper-V system.

To rectify this you need to un-install the Virtual PC add-ons from the VM (you can do this under Hyper-V). Make a note of the network config first.

After a reboot of the VM, install the Hyper-V add-ons. This will setup the relevant NIC drivers. You should then be able to configure the network settings as required.

[tmcd35]

I take it you don't have both Hyper-V and Virtual Server 2005 installed on the same server? This would likely cause network issues, amongst others.

[Geek_of_HeathMount]

Morning all,
Just to confirm,[LIST]

• The server has a clean install of Hyper V

• The BIOs has been checked and set.

• The virtual machines are being created using the default settings from Hyper V.

• MS Virtual server/pc have not been used on this server

• The use of MS Virtual server/pc is a last resort as I know I can get them working

I hope this clears the confusion.

[Geek_of_HeathMount]

I don't know how i've done it but I have managed to connect the servers to the network.

Thanks guys

[theriver]

Perhaps a little after the fact, but it's nice to know why these things happened . . . .

Had you defined a network in Hyper-V (Action > Virtual Network Manager)? After you've done this, the network card on the virtual server will be available for selection during the machine configuration wizard.