Article ID: 2018593 - View products that this article applies to.
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.
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:
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
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:
To resolve the issue when using an MDT 2010 stand alone Task Sequences, please see KB977565:
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:
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.