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 in the Configuration Manager Console in Microsoft System Center Configuration Manager 2007. The task sequence runs more than one program.
The following option is not checked:
If an application installation fails, continue installing other applications in the list
A program in the task sequence returns a failure exit code.
In this scenario, the execution of the task sequence may continue. That is, the ContinueOnError task sequence variable does not work correctly when its value is FALSE. Therefore, some programs are executed unexpectedly.
This problem occurs because the task sequence engine misinterprets the process failure exit code.
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.
You must have System Center Configuration Manager 2007 Service Pack 1 installed to apply this hotfix.
You do not have to restart your computer after you apply this hotfix.
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.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Install KB959038 during a task sequence
For operating system deployments, the KB959038 hotfix must be installed during a ConfigMgr 2007 OSD task sequence in the Setup Windows and ConfigMgr task. Otherwise, the problem will continue to occur while the task sequence is executed. Additionally, the Install Softwaretask cannot be used to install the hotfix. Trying to do this will cause the ConfigMgr 2007 client service to stop, which will cause the task sequence to fail.
To install the KB959038 hotfix during a ConfigMgr 2007 OSD task sequence, use the PATCH= option that is described in the following Microsoft Knowledge Base article:
907423 How to include an update in the initial installation of Systems Management Server 2003 Advanced Client
To install the KB959038 hotfix during a ConfigMgr 2007 OSD task sequence, follow these steps:
Apply the hotfix on the site server.
When the hotfix has been applied on the site server, the ConfigMgr 2007 client installation files will be updated to include the KB959038 hotfix in the directory \i386\hotfix\KB959038\ of the ConfigMgr 2007 client installation files. Because the ConfigMgr 2007 client installation files have been updated, make sure to update the distribution points where the ConfigMgr 2007 client installation package resides.
Right-click the task sequence that you need to change, and then click Edit.
Click Setup windows and ConfigMgr.
In the Installation properties box, type the following:
The <Package_ID> placeholder is the package ID of the ConfigMgr 2007 client installation package in ConfigMgr 2007.
Make sure that you include the quotation marks as part of the path. However, do not include the brackets that are around the placeholder.
Make sure that the package ID of the ConfigMgr 2007 client installation package is used and not the package ID of the KB959038 hotfix package.
The _SMSTaskSequence cache folder will reside on the drive that has the most disk space. If the computer has multiple drives or partitions, the _SMSTaskSequence folder may end up on a drive other than drive C. In this scenario, change the path to point to the drive that contains the _SMSTaskSequence folder. We do not recommend that you use the variable _SMSTSMDataPath in the path because the drive letter in this path can enumerate differently in Windows PE and in the full Windows operating system.
As an alternative to using the local path that points to the ConfigMgr 2007 client installation files that are located in the local Task Sequence cache, you can specify a UNC path that points to the ConfigMgr 2007 client installation files on the original package source or on a distribution point.
Verify the name of the .msp file that is located in the \i386\hotfix\KB959038\ directory of the ConfigMgr 2007 client installation files. The name may differ depending on the locale. If the name differs from the name of the .msp file name that is used in the PATCH= command line in this step, adjust the name accordingly.
Click Apply or OK to save the task sequence.
For more information about software update terminology, 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