Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. ConfigMgr 2007: An OSD Task Sequence that utilizes USMT 4 fails if a pre-ConfigMgr 2007 SP2 client is installed

ConfigMgr 2007: An OSD Task Sequence that utilizes USMT 4 fails if a pre-ConfigMgr 2007 SP2 client is installed

Symptoms

When attempting to use either the "Capture User State" ("Capture USer Files and Settings") task or the "Restore User State" ("Restore User Files and Settings") task, the capture or restore tasks fail. Inspecting theSMSTS.log reveals the following error:


Capture User State

Executing command line: osdmigrateuserstate.exe /collect /continueOnError:%OSDMigrateContinueOnLockedFiles% /skipefs:%OSDMigrateSkipEncryptedFiles% TSManager
==============================[ OSDMigrateUserState.exe ]============================== OSDUSMT
Command line: "osdmigrateuserstate.exe" /collect /continueOnError:true /skipefs:false OSDUSMT

USMT package path = '<PATH_TO_USMT4_PACKAGE>\<USMT4_PACKAGE_ID>\' OSDUSMT
uSize > 0, HRESULT=80070714 (e:\nts_sms_fre\sms\client\osdeployment\osdusmt\userstateaction.cpp,95) OSDUSMT
IsUsmtPreLonghorn failed (0x80070714). OSDUSMT
VerifyIfPreLonghornBinary(sUsmtBinary, m_bUSMTPreLonghorn), HRESULT=80070714 (e:\nts_sms_fre\sms\client\osdeployment\osdusmt\userstateaction.cpp,523) OSDUSMT
UserStateMigrationAction::GetUSMTBinary failed (0x80070714). OSDUSMT
SetUSMTBinary(), HRESULT=80070714 (e:\nts_sms_fre\sms\client\osdeployment\osdusmt\userstateaction.cpp,955) OSDUSMT
Failed to initlialize, (0x80070714) OSDUSMT
usmAction.Init(::GetCommandLineW()), HRESULT=80070714 (e:\nts_sms_fre\sms\client\osdeployment\osdusmt\main.cpp,235) OSDUSMT

OSDMigrateUserState finished: 0x80070714 OSDUSMT
Process completed with exit code 2147944212 TSManager
!--------------------------------------------------------------------------------------------! TSManager
Failed to run the action: Capture User State.
The specified image file did not contain a resource section. (Error: 80070714; Source: Windows) TSManager


Restore User State

Executing command line: osdmigrateuserstate.exe /apply /continueOnError:%OSDMigrateContinueOnRestore% TSManager
==============================[ OSDMigrateUserState.exe ]============================== OSDUSMT
Command line: "osdmigrateuserstate.exe" /apply /continueOnError:true OSDUSMT
Initializing from environment successful OSDUSMT

USMT package path = '<PATH_TO_USMT4_PACKAGE>\<USMT4_PACKAGE_ID>' OSDUSMT
uSize > 0, HRESULT=80070714 (e:\nts_sms_fre\sms\client\osdeployment\osdusmt\userstateaction.cpp,95) OSDUSMT
IsUsmtPreLonghorn failed (0x80070714). OSDUSMT
VerifyIfPreLonghornBinary(sUsmtBinary, m_bUSMTPreLonghorn), HRESULT=80070714 (e:\nts_sms_fre\sms\client\osdeployment\osdusmt\userstateaction.cpp,523) OSDUSMT
UserStateMigrationAction::GetUSMTBinary failed (0x80070714). OSDUSMT
SetUSMTBinary(), HRESULT=80070714 (e:\nts_sms_fre\sms\client\osdeployment\osdusmt\userstateaction.cpp,955) OSDUSMT
Failed to initlialize, (0x80070714) OSDUSMT
usmAction.Init(::GetCommandLineW()), HRESULT=80070714 (e:\nts_sms_fre\sms\client\osdeployment\osdusmt\main.cpp,235) OSDUSMT

OSDMigrateUserState finished: 0x80070714 OSDUSMT
Process completed with exit code 2147944212 TSManager
!--------------------------------------------------------------------------------------------! TSManager
Failed to run the action: Restore User State.
The specified image file did not contain a resource section. (Error: 80070714; Source: Windows) TSManager

 

Additional analysis reveals that either a ScanState.log or LoadState.logwere not created and that ScanState.exe or LoadState.exe never ran.

↑ Back to the top

Cause

This issue is caused when USMT 4 is attempted to be used on a client PC that has a pre-ConfigMgr 2007 SP2 client installed. This could be either the ConfigMgr 2007 RTM or ConfigMgr 2007 SP1 client. Since USMT 4 was released after ConfigMgr 2007 RTM or ConfigMgr 2007 SP1, both the RTM and SP1 ConfigMgr 2007 clients will not work with USMT 4.

The issue can occur under the following circumstances:

  1. On the original Windows OS, a pre-ConfigMgr 2007 SP2 client was installed on the client PC when the "Capture User State" task was run.

  2. On the new Windows OS installed by the Task Sequence, a pre-ConfigMgr 2007 SP2 client was installed on the client PC when the "Restore User State" task and LoadState.exe was run. The pre-ConfigMgr 2007 SP2 client was installed as part of the "Setup Windows and ConfigMgr" task.

↑ Back to the top

Resolution

To resolve the problem, make sure that the following steps are taken:

  1. The ConfigMgr 2007 SP2 client is installed on any client PC where a Task Sequence that utilizes USMT 4 is going to be run on. The ConfigMgr 2007 SP2 client needs to be installed on the client PCBEFORE the Task Sequence begins. The ConfigMgr 2007 SP2 client cannot be installed on the original Windows OS as part of the Task Sequence.

  2. In the "Setup Windows and ConfigMgr" task of the Task Sequence, make sure that the package that is selected in the task points to ConfigMgr 2007 SP2 client installation source files.

For #1, normal client installation and client upgrade methods should be used to upgrade the ConfigMgr 2007 clients to the SP2 client. It is advisable that if ConfigMgr 2007 SP2 is being run in the environment that all client PCs in the environment should be upgraded to the ConfigMgr 2007 SP2 client, regardless if the Task Sequence is going to be run on them or not. For further information regarding installing and upgrading ConfigMgr 2007 clients, please see:

Tasks for Installing Configuration Manager Clients
http://technet.microsoft.com/en-us/library/bb632762.aspx

The following additional method can also be used to make sure that the ConfigMgr 2007 client is upgraded to the SP2 client before the Task Sequence executes:

  1. Right click on the Task Sequence and choose "Properties".

  2. Click on the "Advanced" tab.

  3. Click on the option "Run another program first:", and then select the appropriate Package and Program that installs the ConfigMgr 2007 SP2 client.

The above method installs the ConfigMgr 2007 SP2 client before the Task Sequence starts executing. It does not install it as part of the actual Task Sequence.

↑ Back to the top

Keywords: vkball, kb

↑ Back to the top

Article Info
Article ID : 2028451
Revision : 1
Created on : 1/8/2017
Published on : 11/22/2010
Exists online : False
Views : 124