Symptoms
Consider the following scenario:
-
You perform the restart computer step in a System Center Configuration Manager 2007 task sequence.
-
You advertise the task sequence to an embedded device that has System Center Configuration Manager 2007 Service Pack 2 (SP2) clients.
-
The embedded device has a RAM disk or has a hard disk drive that has no free disk space.
In this scenario, the restart computer step does not work, and the embedded device does not restart after the task sequence runs.Additionally, one of the following error messages is logged in the Smsts.log file on the embedded device:
Failed to get unique id (0x80070001)]Failed to convert <drive letter> to unique volume id. Code : 0x80070001 Failed to convert protected paths to unqiue ID. Error code 0x80070001Failed to reboot the system. Error 0x(80070001)Failed to initialize a system reboot.
Failed to reboot the system. Error 0x(80070070)Failed to initialize a system reboot. There is not enough space on the disk. (Error: 80070070; Source: Windows)Fatal error is returned in check for reboot request of the action (Disable Write Filter Action). There is not enough space on the disk. (Error: 80070070; Source: Windows)
Resolution
The following hotfix package resolves issues for both site server and client roles. You have to run the hotfix package on the site server roles, and then you have to deploy the generated packages to client roles.Note The 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. For more information about installation guide, click the following article number to view the article in the Microsoft Knowledge Base:
2477182 System Center Configuration Manager 2007 Hotfix Installation Guidance
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:
http://support.microsoft.com/contactus/?ws=supportNote 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 2 (SP2) installed.
Restart requirement
You do not have to restart the computer after you apply this hotfix.Note You have to close the ConfigMgr admin console before you install this hotfix package.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
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
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Mcs.msi |
Not Applicable |
7,280,128 |
01-Feb-2010 |
15:30 |
Not applicable |
|
Pxe.msi |
Not Applicable |
5,837,824 |
01-Feb-2010 |
15:30 |
Not applicable |
|
Sccm2007ac-sp2-kb2516850-x86-enu.msp |
Not Applicable |
697,856 |
01-Feb-2010 |
15:30 |
Not applicable |
|
Tscore.dll |
4.0.6487.2179 |
1,172,328 |
01-Feb-2010 |
15:30 |
x86 |
|
Tscore.dll |
4.0.6487.2179 |
2,133,864 |
01-Feb-2010 |
15:30 |
x64 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
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
References
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
