You create a task sequence on a Microsoft System Center Configuration Manager 2007 Service Pack 2 (SP2) site server.
You add lots of Install Software steps to the task sequence.
For example, you add more than 100 Install Software steps to the task sequence.
You create an assignment that makes the task sequence mandatory when you advertise the task sequence to a client computer.
In this scenario, the task sequence does not run on the client computer.
Note This issue does not occur if the task sequence is assigned as an optional advertisement.
This issue occurs because the large number of Installing Software steps in the task sequence creates a heavy workload for the location service.
When the location service has a heavy workload, it cannot process all the callbacks for the location requests in a 10-minute window. Therefore, the issue that is mentioned in the "Symptoms" section occurs.
The following hotfix package resolves this issue in client roles. To resolve this issue, you must install the following hotfix package on the System Center Configuration Manager 2007 SP2 site server, and then you must deploy the generated packages to clients. After you install the following hotfix package, the hardcoded time-out is changed to 50 minutes.
For more information about how to deploy a hotfix package to the System Center Configuration Manager 2007 SP2 site server, click the following article number to view the article in the Microsoft Knowledge Base:
2477182 System Center Configuration Manager 2007 Hotfix Installation Guidance
Note The following hotfix package can be installed on a System Center Configuration Manager 2007 SP2 site server that is running an x86-based or x64-based version of an operating system:
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 hotfix, you must have System Center Configuration Manager 2007 Service Pack 2 (SP2) installed.
If you close the Configuration Manager administrator console before you install this hotfix, you do not have to restart the computer.
Hotfix replacement information
This hotfix replaces the one previously released under the following KB article: KB 2278056: A hotfix is available for System Center Configuration Manager 2007 SP2 clients to improve the functionality of virtual machines that are managed by Microsoft Enterprise Desktop Virtualization version 2
The 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 file information notes
Note Some other files might be updated because of dependencies. However, their binaries are not changed.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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