An update rollup package is available that adds some basic support in Microsoft System Center Configuration Manager 2007 Service Pack 1 (SP1) for clients that are running Windows Server 2008 R2 or Windows 7. This update addresses the following issues.
Windows 7 clients and Configuration Manager clients that are running on Windows Server 2008 R2 cannot successfully assign to a native mode site and will be unmanaged.
Configuration Manager clients that are running on Windows Server 2008 R2 and Windows 7 clients experience a crash with the SMS Agent Host service (CcmExec.exe) during the process of creating a pending Network Access Protection (NAP) statement of health (SoH). This can result in these clients having an unreliable value for their NAP health state.
When the NAP health state is sent to a NAP Network Policy Server, this can incorrectly result in compliant clients being unable to access network resources and noncompliant clients having unlimited network access. Note
For more information about the limits of the support that is provided by this update rollup package for clients that are running Windows Server 2008 R2 or Windows 7, visit the following Microsoft blog site:
To resolve these issues, install this update on all Configuration Manager 2007 SP1 site servers, and then deploy the package to all Windows Server 2008 R2 and Windows 7 clients.Note
If the site server is running in native mode, this update is not installed on Windows 7 or Windows Server 2008 R2 clients. Therefore, issue 1 occurs. You can work around the issue by using one of the following methods:
- Manually install the SCCM2007AC-SP1-KB974236-x86.msp package on Windows 7 or Windows Server 2008 clients. To do this, use the following command:
msiexec.exe /p SCCM2007AC-SP1-KB974236-x86.msp /L*v %TEMP%\ SCCM2007AC-SP1-KB974236-x86.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous
- Distribute the SCCM2007AC-SP1-KB974236-x86.msp package to Windows 7 or Windows Server 2008 clients by using Windows Server Update Services (WSUS) or Group Policy.
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.
To apply this update, you must have Configuration Manager 2007 Service Pack 1 installed.
You do not have to restart the computer after you apply this hotfix.
Update replacement information
This update does not replace any other updates.
The English version of this update 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.
|File name||File version||File size||Date||Time||Platform|
|Mcs.msi||Not Applicable||7,266,816||01-Dec-2008||02:15||Not Applicable|
|Mp.msi||Not Applicable||9,515,520||01-Dec-2008||02:15||Not Applicable|
|Pxe.msi||Not Applicable||5,504,000||01-Dec-2008||02:15||Not Applicable|
|Sccm2007ac-sp1-kb974236-x86.msp||Not Applicable||3,077,120||01-Dec-2008||02:15||Not Applicable|
|Smp.msi||Not Applicable||3,493,888||01-Dec-2008||02:15||Not Applicable|
Install KB974236 during a task sequence
For operating system deployments, the KB974236 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 Software
task 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 KB974236 hotfix during a ConfigMgr 2007 OSD task sequence, use the PATCH=
option that is described in the following Microsoft Knowledge Base article:
How to include an update in the initial installation of Systems Management Server 2003 Advanced Client
To install the KB974236 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 KB974236 hotfix in the directory \i386\hotfix\KB974236\ 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 KB974236 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\KB974236\ 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.