Request a topic or
contact an Arke consultant
404-812-3123
All posts tagged 'virtulization'

Arke Systems Blog

Useful technical and business information straight from Arke.

About the author

Author Name is someone.
E-mail me Send mail

Recent comments

Archive

Authors

Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2017

Moving Virtual Machines to Server 2008 and Hyper-V

Now that we've upgraded our VM infrastructure to Hyper-V, I thought I'd write up some of our experiences.  Trenton has already gone over some of the more technical details, like getting Debian configured, but I thought I'd start with the biggest potential hang-up I saw.  Simply put, if you're moving some old Virtual Server 2005 VMs to Hyper-V, there's to things you need to take into account:

  1. Uninstall the VS 2005 extensions from the client VM.
  2. Be prepared to reactivate Windows on the client VM.

Really, those are the only two things I found that are really important.  Everything else is really details.  Even though it's only in Release Candidate status right now, Hyper-V is already immensely better over Virtual Server 2005.  The VMs are faster, they're easier to manage, pretty much everything works better.


Posted by Wayne Walton on Tuesday, April 15, 2008 10:30 AM
Permalink | Comments (0) | Post RSSRSS comment feed

Hyper-V Miscellaneous

So I've been working on getting 2 VMs setup in Hyper-V today, a Windows 2003 server and a Debian Server.  Below are the issues I ran into and how to solve them.

 

Windows Server 2003 Standard

The main issue I ran into here was the inability to run the full Microsoft Update web site.  Basically when I clicked on Custom update, it would process for a while then end with an 0x80072ee2 error.

To fix this you have to disable TCPIP offloading.

  1. Run->regedit
  2. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
  3. Add a REG_DWORD key/value pair:
    1. DisableTaskOffload = 1

Restart and you'll be able to access Microsoft's updates again.

 

Debian 4.0R3

The problem I ran into here, is that Debian does not detect the default Hyper-V virtual network adapter.  To fix this you'll need to go to you're VM's Settings page.

  1. Select the network adapter and delete it
  2. Select the Add Hardware option
  3. Add a new Legacy Network Adapter
  4. Modify settings on this as needed

You'll now be able to install Debian on the VM, and the installer will detect the network adapter

 

kick it on DotNetKicks.com

Posted by Trenton Adams on Friday, April 11, 2008 3:58 PM
Permalink | Comments (0) | Post RSSRSS comment feed