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


May 22, 2000

Performing Unattended Setups with Answer Files


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

Download the Code Here

Last week, I presented an overview of the different technologies that you can use to automate Windows 2000 deployments. This week, I discuss unattended setups using answer files, the text files that give the Win2K or Windows NT setup program the responses it needs during the setup process. With answer files, you can install Win2K Server and Win2K Professional using a network share or a bootable CD-ROM. I'll discuss each method after I explain the process of building an answer file.

Building Answer Files
Not long ago, building answer files was time consuming. You had to build a text file that specified all the correct configuration information, including the machine name, the IP address, and network card settings. To simplify the process, Microsoft included a utility called Setup Manager in the Microsoft Windows NT Server 4.0 Resource Kit. The Win2K Advanced Server, Win2K Server, and Win2K Pro CD-ROMs include an improved version of this utility. You can find the utility in the Support\Tools directory's cabinet file deploy.cab. To use Setup Manager, extract setupmgr.exe and setupmgx.dll to a folder on your hard drive, and run setupmgr.exe to begin creating your answer files.

Setup Manager provides an easy-to-use wizard interface that helps you build answer files. After the initial welcome screen, you encounter a configuration screen that prompts you to specify what kind of answer file you want to create. You can either create an answer file from scratch or create one that pulls its base settings from the machine you're running Setup Manager on. You can also use Setup Manager to modify an existing answer file by specifying its location, as Screen 1 shows.

On the next screen, you can use Setup Manager to create the full answer files that the system uses for traditional unattended installations. (You can also create the files that provide similar functionality for Sysprep and Remote Installation Services; I'll discuss these options in the next two installments of Windows 2000 Ready.) After indicating that you want to create an unattended answer file and specifying the OS you're installing, Setup Manager walks you almost completely through the process of creating your answer file, asking you all the questions you face during a typical manual setup and writing the information to the answer file in the proper syntax.

With Win2K, it's easier to use answer files to automate the setup process because there's less to automate than with NT. In most cases, Win2K uses Plug and Play (PnP) to identify hardware and configure it automatically. If the OS doesn't have a driver for hardware you're installing, you can add it to the distribution folder on the server you connect to when you perform the installation. Other improvements to Win2K's answer file functionality include support for multiple adapter cards and the ability to customize Internet Explorer (IE) and proxy settings.

Making Manual Additions to the Answer File
If you watch closely as Setup Manager runs, you'll notice that it prompts you for everything that a typical manual installation asks for except one piece of information—the product ID. You have to add the product ID to the answer file manually to prevent your automated process from pausing. To do so, add the product ID value with a valid license key in the User Data section of the answer file, as Listing 1 shows.

You're now ready to start using your answer files to perform setups either by installing over the network or using a bootable CD-ROM. To install over the network, run winnt.exe (for a clean install) or winnt32.exe (for an upgrade), and use the /u command switch to specify that this is for an unattended installation. To install from a bootable CD-ROM, name the answer file winnt.sif and place it on a diskette. Then, insert the diskette in the machine that you want to do the clean install on, insert the Win2K CD-ROM, and set the machine to boot from the CD-ROM drive.

As always, remember to test your installs to make sure they work properly and pass the correct configuration settings before running them in a production environment. And take a look at the unattend.doc file located in the Support\Tools directory for a complete list of values that you can use in your answer files. Even if you don’t need to add any values to the files that you create with the wizard, it's good to know how much capability is available.

End of Article



Reader Comments
Your article on answer files was timely and helpful. I do have a question about making a network boot diskette to connect to the NT server share - where can you get those files?

Cathy Wilson May 31, 2000


Awesome article!
Would you know of a way of putting the winnt.sif file on the W2K cd where the install will recognize and use the file? I have workstations without network connectivity or floppy drives and would like a fully automated install without having to open the system. I have successfully created a bootable W2K image that I can modify but I can't get the setup program to recognize the winnt.sif file. Any ideas?

Philip V. Valverde November 30, 2000


It seems to work wonderful for me due to this great article. Unfortunately, the only information I am having trouble with is the Product Key. Few questions,
1. Is there a space between the command and the = and the = and the product key?
2. Is this case sensitive?
3. Do you have to include the dashes between the letters?

Thank you for your time

Lucas December 13, 2000


Great information... but you forgot one important thing: How do I make a Bootdisk with all the necessary network files to connect to my server where the unattended file and all the installation files lay...

Andreas Larsson January 30, 2001


I like the example you have on the parameters. But when I'm doing the unattend I always endup having to click on next for Regional setting. Is there anything I can add to make it completely unattend. this is the only part I can't seem to get. I looked at the Intl.inf file for keys but not much help. I would like to make the default kbrd and regional settings.

clima April 04, 2001


I have read all your pages on Unattended But nowhere Have you explained what Unattended is in simple terms. I have just started my Mcse and new to it all, but i find this area very confusing. Could you please answer my question and tell me whether each Windows 2000 has unattended installed.
Thank you

Dipika July 01, 2001


A well thought out and informative article, but it's missing a few key items that are needed for a successfull install.

You need to make the disk an MS-DOS boot disk, which is a simple task (Which everyone is known).

Also it would have been helpfull if you would have included a list of the "technical" names for applications so you can choose to install them or not.

All in all a great article that helped me get through an unattended installation (And I'm just a co-op student at a tech company :)

Mike S. Griffith July 16, 2003


You mentioned saving the answer file to your hard drive. Is that on the client I want to use as the image pc or on the server in my distribution folder? Where do I save the answer files?
Thanks


Wikus November 05, 2003


The answer file shuold be saved in the disribution folder of the distribution server (that client computers connect to), which is the shared folder created in the c: drive.

macfarlane okonta November 13, 2003


It is really good. can you tell me whether we can include other applications like Antivirus, IE 6 with SP1 etc.

rajesh December 20, 2003


 See More Comments  1   2 

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
Battery Life Issues Almost Certainly Not Windows 7's Fault

While Microsoft is still investigating a notebook battery life issue that was supposedly caused by Windows 7, some interesting trends have emerged. ...

Confirmed: Battery Life Issues Not Windows 7's Fault

Microsoft on Monday issued a lengthy statement about the recent Windows 7 battery controversy, echoing my assessment from earlier in the day, but backing it up with hard, cold evidence. ...

Microsoft Warns of Windows Version Expirations

Microsoft warned that this year will see three out-of-date Windows versions slip into retirement. ...


Windows OSs Whitepapers Protecting Microsoft SharePoint

Related Events Deep Dive into Windows Server 2008 R2 presented by John Savill

Managing IT Across Multiple Locations

Windows, Unix, Linux Interoperability

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


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
Left-Brain.com Technology Resource Directory asp.netPRO ITTV Windows SuperSite 
 
 Windows IT Pro is a Division of Penton Media Inc.
 © 2010 Penton Media, Inc. Terms of Use | Privacy Statement