Thin Client and Virtual Machines Thread, Hyper V going head to head with Virtual Server in Technical; Morning all,
As with all things IT there is an impossible deadline to meet and little time to implement the ...
15th November 2009, 11:50 AM #1
- Rep Power
15th November 2009, 12:08 PM #2
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?
15th November 2009, 01:57 PM #3
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.
15th November 2009, 03:05 PM #4
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.
16th November 2009, 11:33 AM #5
- Rep Power
Just to confirm,
- 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.
20th November 2009, 03:30 PM #6
- Rep Power
I don't know how i've done it but I have managed to connect the servers to the network.
20th November 2009, 04:27 PM #7
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.
By tech_guy in forum General Chat
Last Post: 17th November 2008, 09:34 AM
By Dos_Box in forum General Chat
Last Post: 4th April 2007, 09:01 AM
By Ric_ in forum General EduGeek News/Announcements
Last Post: 20th June 2005, 09:33 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)