This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
You create a task sequence to install an existing Operating System Deployment (OSD) image package.
On the State Migration page, you select the Save user settings locally option.
You deploy this package to some clients.
The deployment process fails.
In this scenario, you may find that the captured user data is deleted from the User State Migration Tool (USMT). This means that a computer that captures user data may wipe the hardware drive that contains the user data, and then you cannot restore the deleted user data.
You expect the user data to be saved in another location during the OSD process instead of being deleted.
The task sequence in System Center Configuration Manager 2007 Service Pack 1 (SP1) deletes all data in the C:\_ SMStasksequence directory when the task sequence engine recognizes that a successful deployment has occurred.
If the task sequence process fails at any step of the process (especially during the loadstate step) and if the Continue on error check box is selected for that step, the error will not be passed to the task sequence engine. Therefore, the task sequence engineer deletes the user data.
971348 List of hotfixes and updates that are contained in System Center Configuration Manager 2007 Service Pack 2
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To apply this hotfix, you must have System Center Configuration Manager 2007 Service Pack 1 (SP1) installed.
You do not have to restart the computer after you apply this hotfix.
However, make sure that you follow these steps:
Install the 958808 hotfix on the System Center Configuration Manager site servers.
Create a task sequence to install an existing Operating System Deployment image package. Select the Save user settings locally option.
Right-click the task sequence that you created to edit it.
Click Set Local State Location, and then locate the OSDStateStorePath variable. This variable's default value is %_SMSTSUserStatePath%.
Change this variable's value to another value, such as to "c:\userdata." Make sure that this directory exists.
Save your changes, and then run the new task sequence.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Note The file attribute information applies to the x86 platform, to the x64 platform, to International Client Pack 1 (ICP1), and to ICP2.
To work around the issue, select the Save user settings on a State Migration Point option.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates