Allowing User Input During the Upgrade

Most SMS administrators consider it good practice not to allow user input during package installations. When users buy and install software by themselves, the Setup program generally prompts them for responses, such as which disk to install the software on or what options to install. Every user interaction introduces the opportunity for error that can cause problems. Users might not understand the implications of the answers they provide. If even a small percentage of users makes mistakes, the number of help desk calls can be overwhelming at a time when you are upgrading thousands of computers.

Another reason to eliminate user input during upgrade is to allow the installation to occur while no one is present at the computer so that you minimize the inconvenience to users.

Finally, providing all the answers in an answer file ensures that you maintain configuration standards. When you follow those standards, you simplify future computer maintenance and support by reducing the number of variables that could be relevant to a problem.

Providing an answer file with all the details required for the upgrade will prevent the Windows 2000 Setup program from asking for user input. If some details are not provided (and the UnattendMode line in the answer file allows it) or if the /unattend command-line switch is not specified, the program prompts the user for the details. An answer file for a server upgrade might look like the following (you must change the JoinDomain line):

[Unattended]

FileSystem = LeaveAlone

UnattendMode=FullUnattended

NTUpgrade=Yes

[Networking]

InstallDefaultComponents = Yes

[Identification]

JoinDomain = RED1DOM

Note

You must specify the answer file by using the command winnt32 /unattend:answer.file. The command winnt32 /unattend performs an unattended upgrade, but it gets the information it needs from the current configuration.

© 1985-2000 Microsoft Corporation. All rights reserved.