Problem: While deploying a Windows XP image, the following error messages may be logged during the State Restore phase when USMT is being installed:

·      USMT installer found at \\Server\Packages$\SMSPKG\E000019B\InstallUSMT301_X86.msi.           ZTIUserState            18/01/2008 16:00:12       0 (0x0000)

·      About to run command: msiexec.exe /I "\\Server\Packages$\SMSPKG\E000019B\InstallUSMT301_X86.msi" /quiet /passive /norestart ZTIUserState   18/01/2008 16:00:12  0 (0x0000)

·      Return code from command = 1618       ZTIUserState     18/01/2008 16:00:15       0 (0x0000)

·      Non-zero return code from USMT 3.0.1 installation command, rc = 1618   ZTIUserState     18/01/2008 16:00:15       0 (0x0000)

·      FindFile: The file USMT30_X86.cab could not be found in any standard locations.           ZTIUserState     18/01/2008 16:00:15            0 (0x0000)

·      ERROR: Unable to find USMT30_X86.cab file so it is not possible to install USMT 3.0, aborting   ZTIUserState            18/01/2008 16:00:15       0 (0x0000)

·      ERROR - Unable to install USMT 3.0 to restore user state.           ZTIUserState     18/01/2008 16:00:15       0 (0x0000)

The last three lines of the log file are an attempt at recovering from the initial behavior—the MDT scripts have logic that attempts to install USMT by extracting the bits from a .cab file but only after the initial Windows Installer–based installation fails.

The problem is a result of a previous task sequence step in the deployment process. The 1618 message translates to, “Another installation is already in progress. Complete that installation before proceeding with this install.” This error is probably the result of an incorrect command that caused execution of subsequent task sequence steps to continue immediately even though the installation was just starting.

Possible Solution 1: Check the event log to see what other installations were initiated at or near the time of the USMT installation, and verify that the commands for those installations are appropriate.

Possible Solution 2: You can avoid this problem by creating a USMT .cab file, but you will likely encounter other issues if you do not correct the cause of the original error.

Because of a bug in the Windows Vista installation program, Wusa.exe (used to install Microsoft Update Standalone Package files), USMT would not install quietly using the standard /quiet option, which resulted in a workaround implemented in the ZTIUserState.wsf script.

Repeat the following steps for the x86 and x64 versions of USMT to repackage the USMT files into .cab files from which MDT can extract USMT to the target computer during deployment:

1.   Manually install the x86 or x64 version of USMT—whichever is applicable to the environment—on a computer running Windows Vista or Windows XP.

2.   Copy C:\Program Files\Microsoft Deployment Toolkit\Samples\USMT30_platform.ddf, where platform is either x86 or x64, from a computer on which MDT is installed.

Note   If USMT is installed in a location other than the default (C:\Program Files\USMT301), edit USMT30_platform.ddf to indicate the correct path to the USMT program folder.

3.   Run the command Makecab /F USMT30_platform.ddf; then, copy the newly created .cab file (USMT30_platform.cab) to the \Tools\platform folder in the MDT deployment share.

Possible Solution 3: An update is available for Windows Vista that may fix the USMT installation problem. If this update is included in the Windows Vista image, you may not need to perform the steps outlined in “Possible Solution 2” in this section. For more information about the update, see the Microsoft Help and Support article When you run Wusa.exe together with the /quiet option to try to install certain software packages on a Windows Vista-based computer, the installation fails.

Related Topics

The User State Migration Tool