Posted by: csaborio | April 4, 2008

How to Install Integration Services on a Virtual Machine without Windows XP SP3

200804032345.jpg

I love chicken and the egg problems. I ran into one of these recently while playing with the RC0 release of Windows Hyper-V (try it out, I am very very impressed).

The problem happened when importing a Virtual hard disk that I had that had Windows XP SP2. See, in order for a VM to take full advantage of Hyper-V, you need to have the Integration Services installed (these are the new Virtual Machine Additions, in Virtual Server lingo). In order to install the Integration Services, I needed to have Windows XP SP3 – which I could easily download; but the VM did not had network support. Why? Because it needed Integration Services…see where I am getting at here? ;)

I downloaded SP3 on my host machine and used ISO Recorder (as suggested by Brad in a previous post). With ISO Recorder, I packed SP3 into an ISO and mounted it in my guest machine. After a short install and removing the Virtual Machine Additions from the guest, I am running my VM with integration services without a hitch! :)

Blogged with the Flock Browser

Tags:


Responses

  1. I have installed XP SP3 in virtual machine of windows server 2008 but im unable to find the network adapters in that machine

  2. uma:

    Have you looked in the device manager to see if the network adapters are missing?

    You also need to install Integration Services in order to be able to have native network support.

    Please let me know if this helps.

  3. Windows XP Service Pack 3

    We have been getting mixed feedback from users that have installed the Windows XP SP3. One of the biggest complaints is Microsoft did not include Direct X 10. The service pack employs many features of Vista and seems to turn your current version of XP into a steppingstone for purchasing a full copy of Vista. Please be sure your current computer programs will be able to handle the transition to SP3 or you may not be able to use them anymore.

  4. Thanks for the post Vinny, I had no idea there were problems with SP3. I guess using VMs to test out if SP3 does not break anything is a sample key scenario on how virtualization can assist anyone facing these questions. Install SP3, if something does not work, go back using a restore point or simply delete the undo disk.

  5. [...] The problem with installing XP SP2 on Hyper-V is that you can not install Integration Services (also called VM Additions or VMtools by other vendors), and without Integration Services you do not have network adapters in the VM. Christian SaborĂ­o sums up the problem in his post titled How to Install Integration Services on a Virtual Machine without Windows XP SP3. [...]

  6. You may have network access in your guest OS without Integration Services:
    Settings -> Add Hardware -> Legacy Network Adapter

    By the way, creating a ISO file contains SP3 and then mount it in virtual dvd drive is a solution.

  7. In order to use virtual images which were created using Microsoft Virtual PC and Virtual Server 2005 under Server 2008 Hyper-V, first you have to uninstall VM additions from Add/Remove programs and install Hyper-V integration Components

  8. [...] I used Remote Desktop to the Hyper-V host, and started a Windows Server 2003 R2 installation, things went smooth. When Windows Server 2003 started, I tried installing Integration Services, but alas, it requires Windows Server 2003 R2 SP2. So I went and clicked and my mouse does not worked since I am using Terminal Services on the host…I press the “command” key (aka Windows Key) and it did not work, so I could not do anything besides following wizards (BTW, I blogged about this issue a while back but with Windows XP). [...]

  9. OR just add a legacy network card through the Hyper-V console. Download the drivers you desire. Then remove it after you’re finished. wam. bam done.

  10. @Nick: Thanks, don’t know why I did not do that back in the day :)

  11. It is easier to download the ISO of the service pack and install SP3 for XP or SP2 for 2003 that way.

  12. @Tholman: Yup, you are absolutely right. Don’t know if the ISO was available at the time of this post, but thanks for the comment anyways! :)


Leave a response

Your response:

Categories