Only two expired user-state stores are deleted on a site server that is running System Center Configuration Manager 2007 Service Pack 1

Consider the following scenario:

• On a site server that is running Microsoft System Center Configuration Manager 2007 Service Pack 1, you configure a state migration point role.
• On the state migration point, you capture several user states and then restore them.
• You wait for state store deletion to occur on the state migration point.

In this scenario, you notice that only two expired user-state stores are deleted. Additionally, the Smpmgr.log file indicates that the first user-state store deletion was successful but that the second deletion failed, and you receive the following error message:

When the state migration point module deletes the first in a series of expired user-state stores in a loop, the module does not correctly initialize the computer-name length for the next iteration of the loop. Therefore, after the second expired user-state store is deleted, you receive the error message, and additional user-state store deletions are aborted.

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft System Center Configuration Manager 2007, available from this Microsoft web site: http://www.microsoft.com/downloads/details.aspx?FamilyID=3318741a-c038-4ab1-852a-e9c13f8a8140 (http://www.microsoft.com/downloads/details.aspx?FamilyID=3318741a-c038-4ab1-852a-e9c13f8a8140)
For a list of issues resolved in this service pack, click on the following article number in the Microsoft Knowledgebase:

Hotfix information

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.

Prerequisites

To apply this hotfix, you must have System Center Configuration Manager 2007 Service Pack 1 installed.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

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.

Note This information applies to the following platforms:

• x86
• x64
• International Client Pack 1 (ICP1)
• International Client Packs 2 (ICP2)

System Center Configuration Manager 2007 Service Pack 1

.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about log files for operating system deployment in System Center Configuration Manager 2007 Service Pack 1, visit the following Microsoft TechNet Web site: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: