ConfigMgr 2007: Error message "Failed to deserialize settings (0x00221006)" when deploying a Windows OS as an Operating System Install Package via an Configuration Manager 2007 OSD Task Sequence

When deploying a Windows OS from installation source files (Operating System Install Package) via an Configuration Manager 2007 OSD Task Sequence, if the Windows version has multiple editions/versions as part of the installation source files, the following error message may be displayed when the PC is rebooted from the WinPE stage:

Boot mgr is missing

Examining the contents of the hard drive reveals that no Windows OS has been installed on the hard drive and that the only contents on the hard drive are a C:\SMSTSLog folder. Examining the SMSTS.log in this folder reveals the following error message:


Loading existing answer file "C:\_SMSTaskSequence\unattend.xml" ApplyOperatingSystem
FALSE, HRESULT=00221006 (e:\nts_sms_fre\sms\framework\osdcore\smiinterface.cpp,498) ApplyOperatingSystem
Failed to deserialize settings (0x00221006) ApplyOperatingSystem

Set command line: "C:\_SMSTaskSequence\Packages\<Package_ID>\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot OSDSetupWindows
Executing command line: "C:\_SMSTaskSequence\Packages\<Package_ID>\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot OSDSetupWindows
Process completed with exit code 31 OSDSetupWindows
Windows Setup completed with exit code 31 OSDSetupWindows
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\<Package_ID> OSDSetupWindows
reference count 1 for the source C:\_SMSTaskSequence\Packages\<Package_ID> before releasing OSDSetupWindows
Delete source directory C:\_SMSTaskSequence\Packages\<Package_ID> OSDSetupWindows
Released the resolved source C:\_SMSTaskSequence\Packages\<Package_ID> OSDSetupWindows
exitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,440) OSDSetupWindows
Windows setup failed, code 31 OSDSetupWindows
setup.run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,1707) OSDSetupWindows
Exiting with code 0x80004005 OSDSetupWindows
Process completed with exit code 2147500037 TSManager
!--------------------------------------------------------------------------------------------! TSManager
Failed to run the action: Setup Windows and ConfigMgr.
Unspecified error (Error: 80004005; Source: Windows) TSManager

Taking a look at the setuperr.log and setupact.log from the C:\SMSTSLog folder reveals the following error message:

setuperr.log
<Date> <Time>, Error      [0x0603ef] IBS    CallBack_SelectImageOrShowUi: There are no matching OS images[gle=0x00000490]
<Date> <Time>, Error      [0x06066d] IBS    CallBack_SelectImageOrShowUi: Couldn't decide which Windows image to use and was asked to never show the UI in unattend mode. hr =0x80004005[gle=0x00000490]

setupact.log
<Date> <Time>, Error      [0x0603ef] IBS    CallBack_SelectImageOrShowUi: There are no matching OS images[gle=0x00000490]
<Date> <Time>, Error      [0x06066d] IBS    CallBack_SelectImageOrShowUi: Couldn't decide which Windows image to use and was asked to never show the UI in unattend mode. hr =0x80004005[gle=0x00000490]
<Date> <Time>, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [The product key entered does not match any of the Windows images available for installation. Enter a different product key.]

<Date> <Time>, Info       [0x0601d7] IBS    InstallWindows:Error Type = 3211266

This problem can occur if an unattend.xml file has been specified in the "Apply Operating System" task, but the image index for the version of Windows being installed and specified in the unattend.xml file does not match up with the the edition of Windows selected in the "Apply Operating System" task under the option "Apply operating system from an original installation source".

This problem is common when using MDT integration and the "Import Microsoft Deployment Task Sequence"/"Create Microsoft Deployment Task Sequence" Wizard to create a Task Sequence. When using this Wizard, the "Apply Operating System" task in the Task Sequence is automatically assigned the unattend.xml file from the MDT Settings Package. If after the MDT Task Sequence is created the Edition of Windows is changed under the option "Apply operating system from an original installation source" in the "Apply Operating System" task, then the problem will occur because the change is not also made automatically in the unattend.xml file, causing the Edition of Windows specified in the "Apply Operating System" task not to match the Edition specified in the unattend.xml file.

There are two ways to resolve the problem:

Method 1

The first method used to resolve the problem is to delete the lines that contain image index value in the unattend.xml file. These lines are not necessary since the "Apply Operating System" task will automatically regenerate these lines and add them back into the unattend.xml file with the proper values:

1) Right click on the affected Task Sequence and choose "Edit".

2) Click on the "Apply Operating System" task.

3) Under "Use an unattended or sysprep answer file for a custom installation", determine the Filename of the unattend.xml file and the Package where it is stored.

4) Under the "Software Distribution" node in the ConfigMgr 2007 Admin console, find the Package where the unattend.xml file is stored as determined in Step 3, and then right click on it and choose "Properties".

5) Click on the "Data Source" tab, and then under "Source directory", determine the source directory of the package.

6) In Windows Explorer, go to the source directory as determined in Step 6.

7) Find the unattend.xml file in the source directory and open it in Notepad to edit the file. Please note that the file MAY not be called unattend.xml and instead may be called something else as determined in the "Filename:" box in Step 3.

8) In the unattend.xml file, find the lines

                        <MetaData>
                            <Key>/image/index</Key>
                            <Value>1</Value>
                        </MetaData>

and delete them.

10) Save the unattend.xml file.

11) Update the Distribution Points of the Package where the unattend.xml file is stored as determined in Step 3.

 

Method 2

In most circumstances, an unattend.xml does not have to be specified under the option "Use an unattended or sysprep answer file for a custom installation" in the "Apply Operating System" task as the Configuration Manager 2007 OSD Task Sequence will automatically create and generate an unattend.xml file based on the settings in the Task Sequence.

Unless specific customizations are being performed in the unattend.xml file that cannot be performed in the GUI of the Task Sequence (i.e., customization of the default display resolution), there is not a need to specify an unattend.xml file. This includes scenarios where the MDT "Import Microsoft Deployment Task Sequence"/"Create Microsoft Deployment Task Sequence" Wizard was used to create the Task Sequence.

If a custom unattend.xml is not needed, then the custom unattend.xml option can just be deselected in the "Apply Operating System" task of the Task Sequence:

1) Right click on the affected Task Sequence and choose "Edit".

2) Click on the "Apply Operating System" task.

3) Uncheck the option "Use an unattended or sysprep answer file for a custom installation".

4) Click on the "OK" button to save the Task Sequence.

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 (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.