WDK Automated Deployment Tools Quick Start Guide

  • Article

I’ve been talking with our TAP partners who are using the Automated Software Installer (ASI) every day recently.  First, I want to say how really cool it is that you’re willing to attempt to use a product in pre-beta form.  Let’s be totally honest, using ASI at this point is a challenge.  This blog is my attempt to help you out.  Below is a very early draft of the WDK Automated Deployment Tools Quick Start Guide.  This guide will be on the CD for Beta 2.  I’m hoping this will help you get past the initial hurdles and start seeing the value of this tool.  Please let me know what helps and what problems you find.

 

WDK Automated Deployment Tools

Quick Start Guide

 

ASI Setup

Setting up ASI is a two-step process.  First you setup the server, then you setup the clients.  The server may be installed on any system as long as the clients can get to the shares on the server.  However, most customers install the ASI server on the same system as their DTM controller. 

 

When setting up the client you have two choices, manual setup or using the ASI Client Setup CD.  If you plan to run ASI tasks from within the DTM we recommend using the ASI Client Setup CD.

 

ASI Server Setup

  1. Install the Microsoft .NET Framework; you can download from here.
  2. Insert the WDK CD.
  3. Browse to the ASI directory.
  4. Run AsiServer.msi.  Use the defaults.
  5. Ensure that file and printer sharing is enabled on your active network connection.
  6. Copy the .NET Framework redistributable v 1.1 to %systemdrive%\asi\asiserver\asi\data\external\x86.  You can download it here.
  7. Open a cmd window and navigate to %systemdrive%\asi\asiserver\tools.
  8. Open Computer Management and set the password on the ASIUser account.
  9. Add an ASI account to your server.  Use the following command “asimaintenance –addcredentials \\%servername%\images asiuser <password> <servername>.
  10. On the server, browse to Asi\AsiServer\Images.
  11. Copy the contents of any operating system CD you wish to deploy to this directory.

 

The WDK team suggests creating a directory structure under the images directory.  Internally we use images\%OS%\%release%\%SKU%.

 

For example, if I wanted to deploy Windows XP Pro Service Pack 2 I would create the directory “images\WinXP\SP2\Pro” and copy the contents of the CD to that directory.  Note that for i386 systems it is necessary to copy only the i386 directory, not the whole CD.

 

  1. Add the builds you’ve placed in the images directory to the ASI database.
    1. Open a console window and change to the Asi\AsiServer\Tools directory.
    2. Execute the following command “findbuild –startpath %systemdrive%\Asi\AsiServer\Images.

 

Client Setup

Manual Client Setup

  1. From the client, browse to the ASI client share, “%ServerName%\ASI\Client.
  2. Run AsiClient.msi.  Provide the name of your ASI Server and accept the default install path.
  3. Use either the ASI GUI client, which is on the Start Menu under the ASI group or the ASI command line interface.  Details on how to use these clients are in the ASI help documentation.

ASI Integrated with the Device Test Manager (DTM)

  1. Download the ASI Client Setup CD ISO from the WDK download site (Where?).
  2. Burn a CD and boot the client from the CD.
  3. Provide the name of your ASI server.
  4. Select the WTT option as the CD code.
  5. Choose option #2 (advanced).
  6. Choose yes to launch the GUI client.
  7. Select your OS and validate that the path is valid; if the path is not valid you will see “build not found” at the bottom of the client.
  8. Enter a machine name.
  9. Enter the administrator password.
  10. Choose two partitions; make sure each is large enough to install the OS you want installed.
  11. Select the partition for your safe OS.
  12. Provide your DTM controller name.
  13. Provide credentials for an account which has access to %servername%\wttinstall.
  14. Let the process complete.  When it is done, the client will show up in the default system pool on your DTM controller.  You may now schedule jobs on the system.

 

ASI Tips and Tricks

Finding a matching Build

ASI works by taking a set of parameters, provided by you through the client, and matching those parameters to the builds indexed in the server’s database.  If the parameters you’ve provided do not match any of the builds on the server your ASI command will fail with a “build not found” error.  If you’re using the GUI client you’ll see “build not found” in the status bar.  From the command line you won’t see the error until you run the command. 

 

Here’s a common command line, “asi –install –product longhorn.”  If I don’t have a build of Longhorn on my server, this will fail.  Here is one that will never work, “asi –install –product longhorn –build 2600.”  Build 2600 of Windows is Windows XP, not Longhorn.

 

What can you do if you’re getting the “build not found” error?  Run the findbuild tool and use the –UpadteBuilds switch.  The output you see is the list of parameters which are being added to the database.  Make sure the parameters you’re adding match the build you want to deploy.

 

Ximage Setup

Ximage requires that the Ximage tools be installed on any system you wish to create images from, restore images to or view and edit image on.  You may install Ximage manually or, if you are installing on your test clients, use the job which is provided with the DTM.  To mount images you need to install the filter driver on the system you will use to mount the images.

Manual

  1. Browse to the \tools\Auotmated Deployment Tools directory on the WDK CD.
  2. Copy these files to the \Windows\System32 directory.
    1. Xmlrw.dll
    2. Wimgapi.dll
    3. Ximage.exe
  3. For help using the Ximage command line, type Ximage /?

Via Job

  1. Run the Ximage Install library job on each client you want to create images from or restore images to.
  2. For help using the Ximage command line, type “Ximage /?.”  The Ximage command line may be automated via a job.

Filter Driver

  1. Browse to the \tools\Auotmated Deployment Tools directory on the WDK CD.
  2. Copy these files to the \Windows\System32 directory.
    1. Xmlrw.dll
    2. Wimgapi.dll
    3. Ximage.exe
    4. Wimfltr.sys
    5. Wimfltr.inf
  3. In the System32 directory, right-click on the Wimfltr.inf file and select “install.”