When using USMT 4 in a Configuration Manager 2007 SP2 OSD Task Sequence, files are captured successfully but settings are not

Article ID: 2018593 - View products that this article applies to.
Expand all | Collapse all

Symptoms

When running a System Center Configuration Manager 2007 Service Pack 2 Task Sequence with a "Capture User State" task that utilizes User State Migration Tool (USMT) version 4 to migrate from Windows XP to either Windows Vista or Windows 7, files are properly captured and restored but settings are not. The SMSTS.log will not show any errors, however the scanstate.log will show the following:

<Date> <Time>, Info                  [0x000000] Downlevel Manifests folder is not present. System component settings will not be gathered.

Settings which are not captured include printers, mapped network drives, and wallpaper.

Cause

This can occur if the Scanstate.exe process cannot find the DlManifests folder. In order for USMT 4 to capture settings correctly via Scanstate.exe in Windows XP, it needs access to the DlManifests folder that is part of the USMT 4 binaries. Scanstate.exe looks for the DlManifests folder in the current working directory instead of the directory where scanstate.exe was run from. If the location where scanstate.exe runs from is not the same as the working directory and/or if the working directory does not contain the DlManifests folder, then scanstate.exe will not have the ability to capture settings.

When Scanstate.exe is run manually outside of a System Center Configuration Manager 2007 Task Sequence, the working directory usually matches the directory where Scanstate.exe runs from. However, when Scanstate.exe is launched using an outside process, such as an System Center Configuration Manager 2007 Task Sequence via the "Capture User State" task, the working directory may not match the directory where Scanstate.exe is run from.

In the case of System Center Configuration Manager 2007, the working directory for both 32bit and 64bit Windows OSs is:

%windir%\System32

If this is not the location that scanstate.exe was launched from and/or that the DlManifests folder is located, Scanstate.exe will fail to find the folder and thus fail to capture all of the settings.

This problem does not happen when migrating from Windows Vista to Windows Vista, Windows Vista to Windows 7, or Windows 7 to Windows 7 because both Windows Vista and Windows 7 have their DLManifests built into the Operating System, and therefore do not require the DLManifests that comes with the USMT 4 binaries. Instead of the above error in the scanstate.log, the following lines will be displayed instead:

<Date> <Time>, Info                  [0x000000] Replacement Manifests are processed because this OS version has built-in component manifests

Resolution

To work around the issue in USMT 4, add a task in the Task Sequence that copies the DlManifests folder from the USMT 4 package to the default working directory used by System Center Configuration Manager 2007 OSD Task Sequences:

  1. In the System Center Configuration Manager 2007 Admin Console, under the "Computer Management" --> "Software Distribution" --> "Packages" node, right click on the USMT 4 packages and choose "Properties".

  2. Click on the "Data Source" tab and ensure that the "Source directory" field is pointing to the root level of the USMT folder. It should not be pointing to either the x86 or amd64 folders. Only one package should be necessary for both x86 or x64 deployments. If the "Source directory" field is pointing directly to either the x86 or amd64 folders, correct this by pointing the source directory one level up to the root of the USMT folder. If corrections are necessary, after making the correction, make sure to update (not refresh) the Distribution Points that the USMT 4 package is on.

  3. In the System Center Configuration Manager 2007 Admin Console, under the "Computer Management" --> "Operating System Deployment" --> "Task Sequences" node, right click on the affected Task Sequence and choose "Edit".

  4. Click on the task immediately before the "Capture User State"/"Capture User Files and Settings" task, and then go to "Add" --> "General" --> "Run Command Line". This should add a "Run Command Line" task immediately before the "Capture User State"/"Capture User Files and Settings" task.

  5. In the newly created Run Command Line task:

    • In the "Name:" field, type in:

      Copy DlManifests folder to working
      directory

    • In the "Command Line:" field, type in

      xcopy /e .\%PROCESSOR_ARCHITECTURE%\DlManifests\*.* %windir%\system32\DlManifests\*.* /Y

    • Check the option "Disable 64-bit file system redirection".

    • Click on the "Package" checkbox, then click on the "Browse" button of the "Package" option. In the "Select a Pacakge" window, select the USMT 4 package, and then click on the "OK" button.

    • Click on the "Options" tab, and then click on "Add Condition" --> "Operating System Version". In the "Operating System Version" window, click on "All x64 Windows XP Professional" and "All x86 Windows XP". Click on the "OK" button.

  6. Click on the "OK" or "Apply" button to save the Task Sequence.

To resolve the issue when using an MDT 2010 stand alone Task Sequences, please see KB977565:

Network drives and network printers are not migrated when you use Microsoft Deployment Toolkit 2010 with the User State Migration Tool (USMT) 4.0
http://support.microsoft.com/kb/977565

This solution has now also been published as KB article KB2018593.  For the most up to date information on this issue please see the following:

When using USMT 4 in a Configuration Manager 2007 SP2 OSD Task Sequence, files are captured successfully but settings are not

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2018593 - Last Review: June 30, 2010 - Revision: 13.0
APPLIES TO
  • Microsoft System Center Configuration Manager 2007 Service Pack 2
Keywords: 
KB2018593

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com