Microsoft KB Archive/933553

Knowledge Base

You cannot deploy an operating system image to a computer that has a hidden partition when you use Systems Management Server (SMS) 2003

Article ID: 933553

Article Last Modified on 3/14/2007

---

APPLIES TO

• Microsoft Systems Management Server 2003

---

SYMPTOMS

You use Microsoft Systems Management Server (SMS) 2003 to deploy an image to a computer that already has an operating system that is installed. However, you cannot deploy the image, and you receive the following error message in the Execmgr.log file:

Script for Package: <PackageName>, Program: <ProgramName> failed with exit code 5

CAUSE

This issue occurs if the following conditions are true:

• The hard disk on the destination computer contains two or more partitions.
• Partition 1 is hidden.
• The existing operating system is installed on a different partition than partition 1.

RESOLUTION

To resolve this issue, you must change the Diskpart.txt file to point to the partition where you want to install the operating system. To do this, follow these steps:

1. Log on to the computer that is acting as the distribution point by using an account that has administrative permissions.
2. Use Windows Explorer to locate the folder that contains the Operating System Deployment (OSD) package.
3. Right-click diskpart.txt, click Open With, and then click Notepad.
4. In the Diskpart.txt file, change Select partition=1 to Select partition=<installation partition>. In this example, the <installation partition> placeholder represents the partition in which you want to install the operating system.
   

In the scenario where the destination computer contains two partitions, and partition 1 is the hidden partition, the syntax in the Diskpart.txt should be changed from Select partition=1 to Select partition=2.

1. Click File, and then click Save.

Note If the destination computer has fewer partitions than specified (For example, the computer has only one partition, and Partition=2 is specified in Diskpart.txt), the installation will still run and succeed on the single partition.

OSD automatically runs the Diskpart tool and uses the default Diskpart.txt file at the beginning of the installation phase. You can add Diskpart.exe to the Preinstall Actions if you want to use a custom Diskpart.txt file. However, OSD may overwrite the customized Diskpart.txt in the package. Therefore, you must always use a different file name for a custom Diskpart.txt file.

Note If you right-click the package, and then click Update Operating System Package Files, the partition setting in the Diskpart.txt file is reset to Partition=1.

REFERENCES

For more information about the Diskpart command-line utility, click the following article number to view the article in the Microsoft Knowledge Base:

300415 A description of the Diskpart command-line utility

Keywords: kbexpertiseinter kbprb KB933553

---

Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.