Windows IT Pro is the leading independent community for IT professionals deploying Microsoft Windows server and client applications and technologies.
  
  
  Advanced Search 


August 24, 2005

Customizing Windows Vista Deployments

RSS
Subscribe to Windows IT Pro | See More Installation Articles Here | Reprints | Or get the Monthly Online Pass—only $5.95 a month!

In last week's Windows IT Pro UPDATE, I discussed Microsoft's newly released Windows Automated Installation Kit (WAIK) for Windows Vista Beta 1, which lets administrators and IT pros work with the company's new image-based setup and deployment tools. This week, I look at some of the ways in which you can customize installation images for Vista Beta 1.

Setup Manager As with earlier Windows versions, you can use WAIK's Setup Manager to customize some aspects of a Vista installation. Although the WAIK version of Setup Manager creates XML files, the customization features haven't really changed much over earlier versions. In short, you can use Setup Manager to customize the End User License Agreement (EULA) acceptance, user name and organization, computer name, product key, various disk configuration options (including where to install Vista), and the standard "Run Once" list of commands that will run after the installation. If you've performed any type of automated installation of Windows in the past, these options should be familiar to you.

Customizing Live Images The most exciting new deployment change with Vista, potentially, is that you can edit in place the Windows Image (WIM) installation files you've created, then save the changes to the existing image or as a new image.

Here's how the functionality works. The base Vista Beta 1 installation image is called install.wim and is located in the /sources/ directory of the Vista Beta 1 DVD by default. The other WIM file located in that directory, boot.wim, is the Windows Preinstallation Environment (WinPE), which you use to boot the DVD and load the Vista Beta 1 installation image onto your PC's hard disk; WinPE runs in RAM off the DVD.

To edit install.wim, copy it to the hard disk of a system on which you've installed WAIK. Then, use a command line window to navigate to the folder in which the WAIK tool ximage.exe is found. (There are separate versions for 32-bit x86 and 64-bit x64 versions of Windows Vista.) The first time you navigate to this folder, you need to install the WIM File System Filter (WIM FS Filter) driver. This tool lets you navigate through the file system of a mounted Vista installation image in Windows Explorer as if it where already installed on the PC. To install the driver, open Windows Explorer, locate the file called wimfltr.inf (which is in the same folder as ximage.exe), right-click it, and select Install.

Now you're ready to mount a Vista installation image so that you can view and customize it in Windows Explorer. You use Ximage's mount (view only) and mountwr (read/write) commands to accomplish this. If your install.wim file is stored in C:\images and you want to mount the image in C:\mount, you'd use the following command:

ximage /mountwr c:\mount c:\images\install.wim 1

Now, you can customize the image, in place, by simply navigating through its file structure in Windows Explorer. If you open a My Computer window and navigate to C:\mount, you'll see the standard Vista Beta 1 installation folder structure spread out before you, with the following folders present in the root:

Boot
build
Documents and Settings
inetpub
InstalledRepository
Program Files
Users
Windows
wmpub

Note that the bizarre combination of mixed case and multiple words in a single folder name will likely change by the final release of Vista; Microsoft is working to ensure that most system folders use simple names (e.g., Users) instead of the complex names of the past, such as "Documents and Settings."

If you want to add files or even entire directory structures to the resulting Windows installation, simply add them wherever appropriate within the mounted image. (I've had mixed results doing this: Often, dragging files over in Windows Explorer doesn't work, but copy-and-paste operations seem to work more consistently.) You can also view the contents of files within the image and edit individual files where needed.

When you finish making changes to the image, unmount the image--which removes it from the namespace of the Windows shell on your PC--and save your changes (if any). To unmount the image without saving any changes, simply type the following command:

ximage /unmount c:\mount

Typically, you'll want to save the changes, however, so you'll need to add the commit command to the previous command-line sequence. If you use the following command sequence, ximage will write the changes back to the original file (Note that this process could take a while because the install.wim file is larger than 820MB by default):

ximage /unmount /commit c:\mount

Before you edit an image, you should make a copy of it and edit the copy. This, after all, is one of the biggest benefits of image-based deployment tools. Because the images are single files, they're easy to manipulate in the file system.

Well, I'm out of space once again, but I hope this basic tutorial has whetted your appetite for the deployment changes in Vista. I hope to speak to Microsoft soon about how these tools will evolve over subsequent betas--the command line stuff works fine but is needlessly arcane in my mind--and I'll report back soon about that. If you have any questions about Vista deployment, please drop me a note.

End of Article



Reader Comments
Yawn!

Anonymous User August 25, 2005 (Article Rating: )


Macs suck!


Anonymous User August 25, 2005 (Article Rating: )


>>Macs Suck!

Yawn!

I never met an OS that did not suck. Whats your point?

Anonymous User August 25, 2005 (Article Rating: )


Great instruction. Thanks

Cascate September 30, 2005 (Article Rating: )


great article

cpqalve October 31, 2005 (Article Rating: )


how do i remove the restrition of 256mb of ram and pentium iii?

misternt January 27, 2006 (Article Rating: )


Paul: Will there be the equivalent of transform for these WIM files, a la MSI/MST? This way you can separate the prestine copy of the OS from the customizations without creating honking big WIM files.

aenagy@hotmail.com February 24, 2006 (Article Rating: )


You must be a registered user or online subscriber to comment on this article. Please log on before posting a comment. Are you a new visitor? Register now




Top Viewed ArticlesView all articles
What You Need to Know About Microsoft's x64 Server Product Plans

What do Longhorn Server, Windows Compute Cluster Server, and Windows Vista have in common? The x64 platform. ...

Anti-Virus Vendors Prepare for War with Microsoft ... Again

When Microsoft announced its Windows Live OneCare security and PC health product over five years (as MSN OneCare), Symantec, McAfee, and the other consumer-oriented security vendors reacted with stunning vigor. ...

Command Prompt Tricks

One reader shares his tip for setting up the command prompt to reflect a remote path. ...


Windows OSs Whitepapers Why SaaS is the Right Solution for Log Management

Related Events WinConnections and Microsoft® Exchange Connections

Configuration Manager SP1 and R2 Overview

Check out our list of Free Email Newsletters!

Windows OSs eBooks Understanding and Leveraging Code Signing Technologies

A Guide to Windows Certification and Public Keys

SQL Server Administration for Oracle DBAs

Related Windows OSs Resources Introducing Left-Brain.com, the online IT bookstore
Looking for books, CDs, toolkits, eBooks? Prime your mind at Left-Brain.com

Discover Windows IT Pro eLearning Series!
Clear & detailed technical information and helpful how-to's, all in our trademark no-nonsense format

Test Drive IT Solutions and Get Free Music Downloads
Solve your toughest IT problems with these free downloads and receive 5 free music downloads!


Windows IT Pro Home Register FAQ for Windows WinInfo News
Europe Edition About Us Contact Us/Customer Service Media Kit Affiliates / Licensing  
SQL Server Magazine Office & SharePoint Pro DevProConnections IT Job Hound ITTV
IT Library Technology Resource Directory Connected Home asp.netPRO Windows SuperSite 
 
 Windows IT Pro is a Division of Penton Media Inc.
 © 2009 Penton Media, Inc. Terms of Use | Privacy Statement | Reprints and Licensing