banner

[Win9xUpg]

Answer File = Unattend.txt

The [Win9xUpg] section contains entries for specifying an unattended upgrade from Microsoft® Windows® 98, Windows 98 Second Edition, or Windows Millennium Edition to either Windows XP Home Edition or Windows XP Professional. These entries are not valid on any other upgrade path.

Requires Win9xUpgrade in the [Unattended] section of Unattend.txt.

For more information about reversing this upgrade, see the [Uninstall] section.

Note

Entry Description
Boot16 Specifies whether to enable MS-DOS boot mode.
DefaultPassword Provides a default password for all local accounts created during a migration process.
DomainJoinText Inserts the Hypertext Markup Language (HTML) text on the Join a Domain page of GUI-mode Setup.
ForcePasswordChange Specifies whether Setup requires a password change on all local accounts it creates during the migration process.
ForceWorkgroup Specifies whether Setup skips domain checks and runs the computer in Workgroup mode after the upgrade.
IgnoreNetworkErrors Specifies whether Setup retries a domain that fails.
KeepBadLinks Specifies whether Setup keeps all links.
MigrateDefaultUser Specifies whether Setup migrates the default user account settings of Windows 98 and Windows Millennium Edition to the default Windows XP user account.
MigrateUsersAsAdmin Specifies whether Setup adds all accounts created during migration to the Local Administrators group, giving those end users full control over the computer.
MigrateUsersAsPowerUser Specifies whether to add all accounts created during migration to the Power Users group.
MigrationDlls Specifies the location of upgrade packs that Setup needs to copy and process during an upgrade to Windows XP or a member of the Windows Server 2003 family.
ReportOnly Specifies whether Setup generates an upgrade report and then exits without changing the current Windows 98 or Windows Millennium Edition installation.
SafeMode Specifies whether Setup maintains a list of settings during the upgrade.
SaveReportTo Specifies the full path and file name of the upgrade report (text file) generated by Setup.
ScanDrives Enables scanning of drives that Setup normally skips.
UseLocalAccountOnError Specifies whether Setup creates a local account if Setup cannot automatically determine or resolve a network account.
UserDomain Specifies the domain for one or more end users.
UserPassword Provides Setup with the names of the passwords created for specific local accounts.

Sample

This sample demonstrates one use of the [Win9xUpg] section of Unattend.txt.

[Win9xUpg]
Boot16 = Yes
DefaultPassword = ABC123
DomainJoinText = MYDOMAIN
ForcePasswordChange = Yes
ForceWorkgroup = No
IgnoreNetworkErrors = Yes
KeepBadLinks = No
MigrateDefaultUser = Yes
MigrateUsersAsAdmin = No
MigrateUsersAsPowerUser = Yes
MigrationDlls = "%SYSTEMDRIVE%\MigFiles"
ReportOnly = No
SafeMode = Yes
SaveReportTo = "%SYSTEMDRIVE%\Upgrade Report%"
ScanDrives = C, D
UseLocalAccountOnError = Yes
UserDomain = MYDOMAIN, PatC
UserPassword = PatC, ABC12345

Boot16

Specifies whether to enable MS-DOS boot mode.

Syntax Boot16 = Yes | No
Values Yes

Enables MS-DOS boot mode.

No

Disables MS-DOS boot mode.

Default Value No
Example
Boot16 = Yes

icon Return to top

DefaultPassword

Provides a default password for all local accounts created during a migration process.

Syntax DefaultPassword = password
Value password
Example
DefaultPassword = ABC123
Comments Because Setup cannot migrate the Windows passwords of end users when upgrading a system, it must assign passwords for those created accounts. When Setup needs to assign one of these passwords, it checks first to see if a UserPassword entry exists for that end user. If an entry doesn't exist, Setup uses the value of this entry (if specified).

There are security concerns about using this key, because Setup stores the password as plain text in the Unattend.txt file. After the upgrade, Setup automatically deletes all passwords in the answer file.

If you need to create a local account for an end user without specifying the UserPassword and DefaultPassword entries, Setup creates a random password. After the first reboot, the end user must enter a password for all end users created during Setup.

icon Return to top

DomainJoinText

Inserts the Hypertext Markup Language (HTML) text on the Join a Domain page of GUI-mode Setup.

Syntax DomainJoinText = html_text
Value html_text
Example
DomainJoinText = MYDOMAIN
Comments The only supported HTML tags are anchor (<A>) and bold (<B>).

icon Return to top

ForcePasswordChange

Specifies whether Setup requires a password change on all local accounts that it creates during the migration process.

Syntax ForcePasswordChange = Yes | No
Values Yes

Requires a password change on all local accounts it creates during the migration process. Setup informs end users logging on with these accounts that the current password has expired. End users must select a new password before logging on.

No

Does not require a password change for local accounts.

Default Value Yes
Example
ForcePasswordChange = Yes

icon Return to top

ForceWorkgroup

Specifies whether Setup skips domain checks and runs the computer in Workgroup mode after the upgrade.

Syntax ForceWorkgroup = Yes | No
Values Yes

Skips domain checks and runs the computer in Workgroup mode after the upgrade.

No

Joins the computer to a domain after the upgrade.

Default Value No
Example
ForceWorkgroup = No

icon Return to top

IgnoreNetworkErrors

Specifies whether Setup retries a domain that fails.

Syntax IgnoreNetworkErrors = Yes | No
Values Yes

Does not try to join a domain again if the first attempt fails. In this case, Setup is completely unattended, but the domain account migration might fail.

No

Tries to join a domain again if the first attempt fails.

Default Value No
Example
IgnoreNetworkErrors = Yes

icon Return to top

KeepBadLinks

Specifies whether Setup keeps all links.

Syntax KeepBadLinks = Yes | No
Values Yes

Keeps all links.

No

Removes incompatible links.

Default Value Yes
Example
KeepBadLinks = No

icon Return to top

MigrateDefaultUser

Specifies whether Setup migrates the default user account settings of Windows 98 and Windows Millennium Edition to the default Windows XP user account.

Syntax MigrateDefaultUser = Yes | No
Values Yes

Migrates the default user account settings of Windows 98 and Windows Millennium Edition to the default Windows XP user account.

No

Does not migrate the default user account settings.

Default Value Yes
Example
MigrateDefaultUser = Yes
Comments

Important

  • If you set this entry to No, the default user settings of Windows 98 and Windows Millennium Edition do not persist. Subsequent user accounts created on the computer inherit the defaults of the upgraded operating system (Windows XP or a member of the Windows Server 2003 family).
  • Some applications rely on settings migrated to the default user. These applications might not work unless you enable default user migration.
  • Use this entry only in special cases (for example, when it is known that no applications require default user migration).

icon Return to top

MigrateUsersAsAdmin

Specifies whether Setup adds all accounts created during migration to the Local Administrators group, giving those end users full control over the computer.

Syntax MigrateUsersAsAdmin = Yes | No
Values Yes

Adds all accounts created during migration to the Local Administrators group, giving those users full control over the computer.

No

Does not add all accounts created during migration to the Local Administrators group. If you do not migrate end users as administrators, some migrated applications and settings might not work properly after the upgrade finishes.

Default Value Yes
Example
MigrateUsersAsAdmin = No
Comments For more information about group-level security settings, see Windows Help.

icon Return to top

MigrateUsersAsPowerUser

Specifies whether to add all accounts created during migration to the Power Users group.

Syntax MigrateUsersAsPowerUser = Yes | No
Values Yes

Adds all accounts created during migration to the Power Users group. Causes Setup to add all accounts that it creates during migration to the Power Users group, giving the new end users in the Power Users group more permissions than end users in the Users group, but fewer permissions than end users in the Administrators group. Power Users can perform any operating system task except tasks reserved for the Administrators group.

No

Does not add all accounts created during migration to the Power Users group.

Default Value Yes
Example
MigrateUsersAsPowerUser = Yes
Comments For more information about group-level security settings, see Windows Help.

icon Return to top

MigrationDlls

Specifies the location of upgrade packs that Setup needs to copy and process during an upgrade to Windows XP or Windows Server 2003 family.

Syntax MigrationDlls = migration_dll_path [, ...]
Values migration_dll_path [, ...]
Example
MigrationDlls = "%SYSTEMDRIVE%\MigFiles"
Comments If you specify multiple paths, you must separate the paths with commas. Setup searches each of these paths (and their subfolders) for upgrade packs. You can put multiple upgrade packs in a single path, but each upgrade pack must exist in its own subfolder of that path. Do not put more than one upgrade pack in a single folder.

Note

  • An upgrade pack consists of a migration .dll file (Migrate.dll) and any additional files required to properly upgrade a software component from Windows 98 or Windows Millennium Edition to either Windows XP Home Edition or Windows XP Professional.

icon Return to top

ReportOnly

Specifies whether Setup generates an upgrade report and then exits without changing the current Windows 98 or Windows Millennium Edition installation.

Syntax ReportOnly = Yes | No
Values Yes

Generates an upgrade report and then exits without changing the current Windows 98 or Windows Millennium Edition installation.

No

Upgrades the current Windows 98 or Windows Millennium Edition installation.

Default Value No
Example
ReportOnly = Yes
Comments The upgrade report contains a list of hardware and software incompatibilities. If you do not specify the SaveReportTo entry, Setup saves the upgrade report to the root of the system drive.

icon Return to top

SafeMode

Specifies whether Setup maintains a list of settings during the upgrade.

Syntax SafeMode = Yes | No
Values Yes

Instructs Setup to maintain a list of settings during the upgrade.

No

Does not instruct Setup to maintain a list of settings during upgrade.

Default Value No
Example
SafeMode = Yes
Comments If any setting causes Windows 98 or later to fail or stop responding, the next Setup skips that setting. Using this entry slows Setup, but it enables Setup to skip certain types of malfunctioning software installed on Windows 98 or later.

Important

  • Safe mode starts automatically if Setup detects a problem. If SafeMode = Off, you must run Setup three times. If SafeMode = Yes, you must run Setup only twice.

icon Return to top

SaveReportTo

Specifies the full path and file name of the upgrade report (text file) generated by Setup.

Syntax SaveReportTo = path_of_report
Value path_of_report
Example
SaveReportTo = "%SYSTEMDRIVE%\Upgrade Report%"
Comments If the Windows 98 or Windows Millennium Edition installation has network connectivity, the path_of_report can be a UNC path. Enclose path_of_report in quotation marks if it is a long file name.

You can use system environment variables enclosed in percent signs (%) in the path. If you specify the special environment variable %computername% in the path, the resulting file name contains the actual computer name. This is useful if Setup collects upgrade reports from several Windows 98 or Windows Millennium Edition computers to a central location.

For more information, see ReportOnly.

icon Return to top

ScanDrives

Enables scanning of drives that Setup normally skips.

Syntax ScanDrives = [drive][,drive,drive]
Values [drive][,drive,drive]
Dependencies

Requires ReportOnly. Enables Setup to check software on network drives.

For more information, see ReportOnly.

Example
ScanDrives = C, D

icon Return to top

UseLocalAccountOnError

Specifies whether Setup creates a local account if Setup cannot automatically determine or resolve a network account.

Syntax UseLocalAccountOnError = Yes | No
Values Yes

Creates a local user account if Setup cannot automatically determine or resolve a network account.

No

Does not create a local user account.

Default Value No
Example
UseLocalAccountOnError = Yes
Comments This is valid only on computers with the Microsoft Networking Client software installed.

Windows 98 and Windows Millennium Edition keep only the domain of the last logged-in user in the registry. Because neither Windows 98 or Windows Millennium Edition keeps the domains of other end users who might have logged on to the computer, Windows Setup searches all trusted domains on the network by default. Setup automatically uses a domain account when it finds an exact match.

If Setup does not find an end user on any trusted domain, or if it finds the user account on two or more domains on the network, a dialog box appears prompting the person performing the upgrade to resolve the conflict. This dialog box also appears if network errors occur.

Specifying UseLocalAccountOnError = Yes in the Unattend.txt file ensures a complete unattended Setup. This causes Setup to create a local account whenever Setup cannot automatically resolve a network account.

In addition, if Setup cannot add a computer to the computer domain during installation of the network on Windows, all user accounts change to local accounts.

For more information, see UserDomain.

icon Return to top

UserDomain

Specifies the domain for one or more end users.

Syntax UserDomain = domain_name, user_name [, user_name, user_name, ...]
Values domain_name, user_name [, user_name, user_name, ...]
Example
UserDomain = MYDOMAIN, PatC
Comments You can use multiple UserDomain lines to specify different domains for different users. When specified, this entry prevents Setup from searching all trusted domains on the network for a matching user account. (The search process can be time-consuming if a large number of trusted domains exist on the network.)

If Setup does not find the account in the specified domain, either because the account does not exist or the domain is not accessible, a dialog box appears prompting the end user to resolve the account unless the UseLocalAccountOnError entry is set to Yes.

For more information, see UseLocalAccountOnError.

icon Return to top

UserPassword

Provides Setup with the names of the passwords created for specific local accounts.

Syntax UserPassword = user,password [,user,password,...]
Values user,password [,user,password,...]
Example
UserPassword = PatC, ABC12345
Comments Because Setup cannot migrate the Windows passwords of end users when upgrading a system, it must create passwords for nondomain accounts during the migration process. Using this key, an administrator can predetermine what those passwords are for specific end users.

There are security concerns about using this key because Setup stores the password as plain text in the answer file. However, after the upgrade finishes, Setup deletes all the password entries from the copy of the answer file left on the computer. However, Setup does not delete the original copy of the answer file.

If you need to create a local account for an end user without specifying the UserPassword and DefaultPassword entries, Setup creates a random password. After the first reboot, the end user must enter the password created during Setup.

For more information, see DefaultPassword.

icon Return to top