I’ve decided to make the leap into Ubuntu; well sorta. I’m going to run it in a Virtual Machine for now. I’ll set it up in a multi boot on my main pc once I’m more familiar with Linux and related stuff, but then again I may keep it running in a virtual machine if virtualization works out well enough.
Below are the steps I took to get things setup.
Step 1: Install Virtual Server 2005 R2
Since I have Vista x64 installed on my pc; I am forced to use Virtual Server 2005 R2 instead of Virtual PC 2004 because VPC’04 wont install on it. Before installing Virtual Server 2005 you need to install/enable IIS on Vista first. Oh yeah, and don’t forget to install all the IIS6 Compatibility stuff. This post helped me with this; Installing Virtual Server on Windows Vista Beta 2
Yes, I know I could use Virtual PC 2007, but I want to try not to put Beta software on my primary box if I can help it. But, once Virtual PC 2007 RTM’s I’ll be installing it and using that instead. But, for now we’ll just continue along…
Step 2: Make sure the Virtual Server Adminstration website has the appropriate access rights.
You’ll find out if it’s not setup correctly if you cannot create a new Virtual Machine as described in the next step.
If the access rights aren’t setup correctly; heres what I did to get it to work:
1) Goto the IIS Manager
2) Open up the “Advanced Settings” dialog for the “Virtaul Server” virtual folder within the Default Web Site.
3) Change the Physical Path Credentials from “Application user” to “Specific user” and enter the username and password for a user that has Admin rights on the box. Ok, I know this isn’t the most secure way (and I don’t recommend it if you don’t want everyone that accesses the VS Admin Site to run as Admin), but I am installing this on my Home PC and I don’t have those Security concerns on this box.
Step 3: Setup a Virtual Machine that will be used to install Ubuntu on
Look at “Chapter3: Setting Up a virtual Machine” withing the Getting Started Guide that is install when you install Virtual Server. This document can be found in: Start Menu - All Programs - Virtual Server - Getting Started Guide
Here are the steps I followed:
1) Open the Virtual Server Administration web site within IE
2) Click on “Create” under the “Virtual Machines” section in the navigation bar on the left side.
3) Fill out the required/desired fields:
Virtual Machine Name: UBUNTU
Virtual hard disk: Select “Create a new virtual hard disk” - Size: 16 - Units: GB - Bus: IDE
Virtual network adapter: Connected to: Internal Network
4) Click the “Create” button
Step 4: Install Ubuntu on our Virtual Machine
Follow the instructions within the Virtual Server Getting Started Guide to do this. Below are the steps I took:
1) Open the Virtual Server Administration web site withing IE
2) Click on the “UBUNTU” option within the “Configure” popup menu under the “Virtual Machines” section in the navigation bar on the left side. If you just created this Virtual Machine it will open up this page upon finishing its creation.
3) Click the “CD / DVD” link under “UBUNTU Configuration”
4) Select the “Known image files” option and enter the fully qualified path to the Ubuntu installation ISO image file. In my case I am using the location of “E:\UBUNTU\ubuntu-6.10-desktop-i386.iso”.
5) Click the “OK” button
6) Now that you’re back at the Virtual Machine Status page; point to the the Virtual Machine name (in this case it’s UBUNTU) and Click “Turn On”
7) Once turned on; run the Virtual Machine Remote Control Client - this can be found in Start Menu - All Programs - Virtual Server
9) Type in the location of the Virtual Machine to connect to and connect to it. In my case it’s “vmrc://chrisdesktop/UBUNTU”
10) Follow the Ubuntu setup program
If you have any issues getting your Virtual Machine setup within Virtual Server 2005 R2 just reference the Getting Started Guide.
For help with the install process of Ubuntu check out the How To Configure Ubuntu For Microsoft Virtual PC 2004
This blog post is licensed under the Creative Commons Attribution 3.0 United States License, unless explicitly stated otherwise within the blog post content. All other content on this website is not licensed under Creative Commons licensing.