In "ADS Unplugged" (November 2006, InstantDoc ID 93625), I showed you how to build a basic
mobile Automated Deployment Services (ADS)
solution that lets you perform Windows OS migrations
with no impact on or reconfiguration of your production network. Now I want to show you how to kick it up
a notch so that you can use this mobile solution to perform physical machine to virtual machine migrations.
Although I'll be discussing how to expand a mobile
ADS installation, you can use the same concepts to
expand an ADS installation on a network.
So far, I showed you how to create the mobile ADS solution by assembling the
necessary hardware on a mobile cart and installing the basic software, which
consists of Windows Server 2003 Enterprise Edition, DCHP, and Automated Deployment
Services (ADS) 1.1. To expand this solution so that you can perform physical
machine to virtual machine migrations, you need to perform five steps:
- Install Microsoft IIS.
- Install Virtual Server 2005 Release 2 (R2).
- Install Virtual Server Migration Toolkit (VSMT) 1.1.
- Create the default virtual network.
- Load Virtual Machine Additions.
|
PROBLEM:
You want to perform physical machine to virtual machine migrations
without having to deploy ADS to your entire enterprise.
SOLUTION:
Extend the mobile ADS solution so that it has virtual migration capabilities.
WHAT YOU NEED:
The basic mobile ADS solution (see InstantDoc ID 93625), Virtual Server
2005 R2, VSMT 1.1
DIFFICULTY:
3 out of 5
|
Step 1: Install IIS
Because the mobile ADS solution is a single-server installation, you need to
run and manage Virtual Server 2005 R2 on the same platform. To run Virtual Server
2005's Web-based administrative console— that is, the Virtual Server
Administration Website—in this configuration, you must run IIS on the
mobile server, which in this case, is the MobileP2V server. (If you're expanding
an ADS installation on a network, it's possible to have a central installation
of the administrative console that manages multiple virtual server hosts. In
this situation, IIS isn't required on each virtual server.)
To install IIS, you can use either the Control Panel Add or Remove Programs
applet or the Configure Your Server Wizard. The wizard simplifies the process,
so let's use it. Using local administrative access, log on to the MobileP2V
server. You need the Windows 2003 CD-ROM to install IIS, so place it in the
machine's CD-ROM drive. Select Programs on the Start menu, then choose Administrative
Tools. On the Administrative Tools menu, select the Configure Your Server Wizard
option to launch the wizard.
On the main page of the wizard, click Next. On the Preliminary Steps page,
click Next. In some instances, you might be prompted with a Configuration Options
page. If this page appears, select Custom Configuration and click Next.
You should now be at the Server Roles page. Select the Application server
(IIS, ASP.NET) option and click Next. You don't need FrontPage extensions
or ASP.NET for the Virtual Server Administration Website, so click Next again.
On the Summary of Selections page, which lists all the roles that you selected
for installation, click Next and the installation of IIS will begin. Click Finish
to exit the wizard after the installation completes.
Step 2: Install Virtual Server 2005 R2
It's now time to install Virtual Server 2005 R2. It's important that you use
Release 2 because it addresses a DCOM permissions issue that its predecessor
doesn't address. (Windows 2003 Service Pack 1— SP1—increased the
security of IIS by changing the default DCOM permissions. As a result, when
you open the Virtual Server Administration Website in Virtual Server 2005, you
receive an error message.) You can download Virtual Server 2005 R2 for free.
For details and a link to the download, go to http://www.microsoft.com/virtualserver.
Double-click Setup.exe to start the installation of Virtual Server 2005 R2.
In the Microsoft Virtual Server 2005 Setup page, select the Install Microsoft
Virtual Server 2005 R2 option to start the installation process. Accept the
license agreement and click Next. In the Customer Information page, enter your
username, organization, and product key, then click Next. Because you're building
a single-server solution and need all the components, select Complete Install
and click Next.
Previous
