Microsoft KB Archive/939363

= SMS 2003 OSD Feature Pack continues to deploy new images even though the Windows USMT 3.0 or a later version returns an error code =

Article ID: 939363

Article Last Modified on 11/5/2007

-

APPLIES TO


 * Microsoft Systems Management Server 2003

-



SYMPTOMS
Microsoft Systems Management Server (SMS) 2003 Operating System Deployment (OSD) Feature Pack continues to deploy new images even though the Windows User State Migration Tool (USMT) 3.0 or a later version returns an error code.

This behavior prevents user information from being migrated to a new operating system.

After this problem occurs, the Scanstate.log file contains information that resembles the following: Error [0x000000] Migration failed to complete successfully

Error [0x000000] Execute Internal failed to complete successfully

Error [0x000000] USMT is unable to complete successfully.

Error [0x000000] Internal Error: USMT was unable to complete the migration. If you continue to receive this error, contact Customer Service and Support (CSS).

Info [0x000000] Please see the log file for more details. Info [0x000000] USMT error Code (status) = 11

In addition, the OSDusmtscanstate.log file contains information that resembles the following: Running USMTScan\osdUSMTScanState.exe osdUSMTScanState 6/15/2007 3:34:28 PM 1980 (0x07BC)

Exe = \scanstate.exe&quot; osdUSMTScanState 6/15/2007 3:34:28 PM 1980 (0x07BC)

Shared environment successfully initialized osdUSMTScanState 6/15/2007 3:34:28 PM 1980 (0x07BC)

Executing command line: \scanstate.exe&quot; /v:5 /o /uel:90 /i:MigUser.xml /l:&quot;C:\MININT\SMSOSD\OSDLOGS\scanstate.log&quot; &quot;C:\MININT\SMSOSD\StateStore&quot; osdUSMTScanState 6/15/2007 3:34:28 PM 1980 (0x07BC)

CreateProcess completed with exit code 11 osdUSMTScanState 6/15/2007 3:35:58 PM 1980 (0x07BC)

osdUSMTScanState 6/15/2007 3:35:58 PM 1980 (0x07BC)

Success : Exiting with return code 0. osdUSMTScanState 6/15/2007 3:35:58 PM 1980 (0x07BC)



CAUSE
This problem occurs because the OSDUSMTScanState.exe module returns an incorrect exit code of &quot;0&quot; when USMT returns an error code.



Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
This hotfix requires the following prerequisites:
 * Microsoft Systems Management Server (SMS) 2003 Service Pack 2 or a later service pack
 * Operating System Deployment (OSD) Feature Pack Update package

Restart requirement
You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
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.



WORKAROUND
To work around this problem, do not use the OSDUSMTScanState.exe wrapper. Instead, directly use the Scanstate.exe tool. To do this, follow these steps:
 * 1) Click Start, point to All Programs, point to Systems Management Server, and then click SMS Administrator Console.
 * 2) In the console tree, expand Image Packages, expand the operating system deployment package, and then click Programs.
 * 3) Right-click the program, and then click Properties.
 * 4) Click the Advanced tab.
 * 5) In the Phase list, select State Capture, and then click Add.
 * 6) In the list of action types, click Custom, and then click OK.
 * 7) Configure the command-line options for the Scanstate.exe file.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
You can use the Microsoft Systems Management (SMS) 2003 Operating System Deployment (OSD) Feature Pack to create operating system images in SMS 2003. Therefore, you can use Zero Touch Installation (ZTI) or Lite Touch Installation (LTI) to deploy the images to client computers and to manage the images. The Solution Accelerator for Business Desktop Deployment (BDD) recommends that you use the OSD Feature Pack to create, to deploy, and to manage operating system images.

To obtain the SMS 2003 Operating System Deployment Feature Pack Update package, visit the following Microsoft Web site:

http://technet.microsoft.com/en-us/sms/bb676770.aspx

You can use Microsoft Windows User State Migration Tool (USMT) 3.0 to deploy large user files and settings to Windows operating systems. USMT can help you improve your migration process. USMT can also help you simplify your migration process. For more information, visit the following Microsoft TechNet Web site:

http://technet2.microsoft.com/WindowsVista/en/library/91f62fc4-621f-4537-b311-1307df0105611033.mspx?mfr=true

For more information about the standard terminology that is used to describe Microsoft software updates, 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

Keywords: kbexpertiseinter kbbug kbfix kbhotfixserver kbqfe kbpubtypekc KB939363

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.