- You create a task sequence object on a Microsoft System Center Configuration Manager 2007 Service Pack 1 (SP1)-based or a Microsoft System Center Configuration Manager 2007 Service Pack 2(SP2)-based site server.
- You edit the task sequence object to add a Run Command Line task.
- In this task, you run some scripts or a 64-bit application. The 64-bit application uses environment variables.
- The task sequence object is advertised to a 64-bit client, such as a computer that is running an x64-based version of Windows Server 2008.
Hotfix informationA 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 this specific problem.
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, submit a request to 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.
PrerequisitesTo apply this hotfix, your computer must be running System Center Configuration Manager 2007 Service Pack 1 (SP1) or System Center Configuration Manager 2007 Service Pack 2 (SP2).
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
File informationThe English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
System Center Configuration Manager 2007 SP1 file information notes
|File name||File version||File size||Date||Time||Platform|
|Sccm2007ac-sp1-kb977176-x86.msp||Not applicable||3,076,608||01-Dec-2008||01:35||Not applicable|
System Center Configuration Manager 2007 SP2 file information notes
|File name||File version||File size||Date||Time||Platform|
|Sccm2007ac-sp2-kb977176-x86.msp||Not applicable||358,400||31-Jan-2010||17:35||Not applicable|
Install KB977176 during a task sequence
For operating system deployments, the KB977176 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. The hotfix cannot be installed by using an
install software task. Doing that would cause the ConfigMgr 2007 client service to stop, which would cause the task sequence to fail.
To install the KB977176 hotfix during a ConfigMgr 2007 OSD task sequence, use the PATCH= option that is described in the following Microsoft Knowledge Base article:
- Apply the hotfix on the site server.
- After the hotfix has been applied on the site server, the ConfigMgr 2007 client installation files will be updated to include the KB977176 hotfix in the \i386\hotfix\KB977176\ directory of the ConfigMgr 2007 client installation files. Because the ConfigMgr 2007 client installation files have been updated, make sure that you 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:
For ConfigMgr 2007 SP1:PATCH="C:\_SMSTaskSequence\OSD\<Package_ID>\i386\hotfix\KB977176\SCCM2007AC-SP1-KB977176-x86.msp"For ConfigMgr 2007 SP2:PATCH="C:\_SMSTaskSequence\OSD\<Package_ID>\i386\hotfix\KB977176\SCCM2007AC-SP2-KB977176-x86.msp"
- 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 (but not the brackets around the placeholder) as part of the path.
- Make sure that the package ID of the ConfigMgr 2007 client installation package is used and not the package ID of the KB977176 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 use the variable _SMSTSMDataPath in the path because the drive letter in this path can enumerate differently in Window PE than 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\KB977176\ 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.
Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 977176 - Last Review: Jun 21, 2014 - Revision: 1