Microsoft KB Archive/933510

= Known issues that occur when you create custom Windows PE images from Windows Server 2003 Service Pack 2 by using the Windows Server 2003 Service Pack 1 version of the OPK tools =

Article ID: 933510

Article Last Modified on 9/11/2007

-

APPLIES TO


 * Microsoft OEM Preinstall Kit for Windows XP

-



INTRODUCTION
You can use Microsoft Windows OEM Preinstallation Kit (OPK) tools to create custom Microsoft Windows Preinstallation Environment (Windows PE) images from Microsoft Windows Server 2003.

This article describes known issues that occur when you create custom Windows PE images from Windows Server 2003 Service Pack 2 (SP2). These issues occur if you are using the OPK tools that are included with Windows Server 2003 Service Pack 1 (SP1).



MORE INFORMATION
The procedures that are discussed in this article assume that you have disabled the version check. When the version check is enabled, you cannot use the Windows Server 2003 SP1 version of the OPK tools to create a custom Windows PE image from Windows Server 2003 SP2.

How to disable the version check
 Locate the following folder:

\Lang\ \Winpe

Note  represents the folder where the OPK tools are installed. varies depending on the language version of the OPK tools. For the English version of the OPK tools,  is &quot;ENG.&quot; Use Notepad to open the Mkimg.cmd file, and then change the &quot;Set VERSION_CHECK=yes&quot; statement to &quot;Set VERSION_CHECK=no.&quot; Save the Mkimg.cmd file.

The &quot;Diskpart&quot; command and the &quot;Net Use&quot; command do not work
The Diskpart command and the Net Use command do not work when you create custom Windows PE images from Windows Server 2003 SP2. For example, you receive the following error message when you run the Diskpart command at a command prompt:

The disk management services could not complete the operation

The Diskpart command and the Net Use command rely on some other services. These two commands do not work because these other services cannot start. For example, the Diskpart command does not work if the Virtual Disk Service (VDS) cannot start.

To resolve this issue, apply hotfix 933060. For more information about hotfix 933060, click the following article number to view the article in the Microsoft Knowledge Base:

933060 You experience problems when you use the &quot;net use&quot; command or the Diskpart.exe command-line tool after you start the system by using a custom Windows PE image

The BuildOptionalComponents.vbs script does not work correctly
You can use the BuildOptionalComponents.vbs script to add support for optional components to Windows PE. This script uses the /s:  command-line switch and the /d:  command-line switch.

Note  represents the path of the source Windows operating system. represents the path of the Windows PE image files.

This script validates the folder structure of the source Windows operating system. However, Windows Server 2003 SP1 contains a Docs folder that is removed from Windows Server 2003 SP2. When the script validates the folder structure, the Docs folder is not found. Then, you receive the following message:

The source location specified does not appear to contain a copy of Windows XP or Windows Server 2003.

To work around this issue, follow these steps:  Open the BuildOptionalComponents.vbs script, and then locate the following line:

TestForFolder(strSource&&quot;\DOCS&quot;)

  Comment out the line as shown in the following example. SUB Validate(a) TestForFolder(strSource&&quot;\&quot;&a&&quot;&quot;) 'TestForFolder(strSource&&quot;\DOCS&quot;) <--- This line is commented TestForFolder(strSource&&quot;\VALUEADD&quot;) TestForFile(strSource&&quot;\&quot;&a&&quot;\System32\smss.exe&quot;) TestForFile(strSource&&quot;\&quot;&a&&quot;\System32\ntdll.dll&quot;) TestForFile(strSource&&quot;\&quot;&a&&quot;\winnt32.exe&quot;) TestForFile(strSource&&quot;\setup.exe&quot;) SET Folder = FSO.GetFolder(strSource&&quot;\&quot;&a&&quot;\System32&quot;) IF Folder.Files.Count > 10 THEN FailOut END IF END SUB 

You cannot start the Windows Server 2003 SP2 version of Windows PE by using a bootable RAM disk
You can start Windows PE by using a bootable RAM disk. This RAM disk can be a hard disk or a CD. However, you cannot start the Windows Server 2003 SP2 version of Windows PE by using a bootable RAM disk.

To create a custom Windows PE RAM disk on a CD
To create a custom Windows PE RAM disk on a CD, follow these steps:  Create a custom Windows PE image, and then use the Oscdimg command to create an .iso image file from the custom Windows PE image. For example, create an .iso image file that is named Winpex86.iso.

For more information, see the &quot;Creating a Customized Version of Windows PE&quot; chapter of The Windows Preinstallation Environment User's Guide. This guide is included in the OPK tools.</li> Create a folder on the hard disk to store the contents of the Windows PE RAM disk CD. For example, name this folder &quot;Work.&quot; To do this, run the following command at a command prompt:

md C:\Work

</li> Copy the .iso image file of the custom Windows PE image into the Work folder. To do this, run the following command at the command prompt:

copy C:\Winpex86.iso C:\Work

</li> Create a subfolder in the Work folder by using a name that indicates the platform. For example, run the following command at the command prompt to create an i386 subfolder:

md C:\Work\i386

</li> Locate the  folder of the Windows PE image, and then copy the Bootfix.bin file, the Ntdetect.com file, and the Setupldr.bin file into the C:\Work\  folder. The  folder is a folder in the Windows PE image. In this example, the  folder is i386. To copy these three files, type the following commands at the command prompt. Press ENTER after each command.

copy :\ \opk\i386\Bootfix.bin C:\Work\i386

copy :\ \opk\i386\Ntdetect.com C:\Work\i386

copy :\ \opk\i386\Setupldr.bin C:\Work\i386

Note  represents the drive letter for the CD drive that contains the OPK tools CD. represents the language version of the OPK tools.</li>  In the Work folder, create a text file that is named Winnt.sif. This text file should contain the following text. [SetupData] BootDevice = &quot;ramdisk(0)&quot; BootPath = &quot;\ \System32\&quot; OsLoadOptions = &quot;/noguiboot /fastdetect /minint /rdexportascd /rdpath= &quot; Architecture = &quot; &quot; Note  represents the path of the Windows PE boot image file. You can put the boot image either in the root folder or in a subfolder. You can put the boot image in any Advanced RISC Computing (ARC)-accessible location by specifying a full ARC path. For example, the boot image can have an ARC path of &quot;multi(0)disk(0)rdisk(0)partition(1)winpe.iso.&quot; The architecture entry must be present for x64-based computers. For i386-based computers, you can either omit this entry or set this entry to i386. </li> On the hard disk, locate the folder that contains the Windows PE build tools, and then run the Oscdimg command by using the minimum options of -b and -n. To do this, type the following command at the command prompt, and then press ENTER:

oscdimg -bc:\ \Etfsboot.com -n C:\Work C:\WinPEram.iso

Note  represents the appropriate build version, such as build_x86.</li> Use third-party CD-recording software to burn the WinPEram.iso image file to a blank CD.

Note If you copy the .iso image file to the CD, the CD cannot start Windows PE on the computer. You must use the .iso file as a CD image in the CD-recording software and then burn the whole image to a CD.</li> Use this CD to start Windows PE on the computer.</li></ol>

To create a custom Windows PE RAM disk on a hard disk
To create a custom Windows PE RAM disk on a hard disk, follow these steps:  Create a custom Windows PE image, and then use the Oscdimg command to create an .iso image file from the custom Windows PE image. For example, create an .iso image file that is named Winpex86.iso.

For more information, see the &quot;Creating a Customized Version of Windows PE&quot; chapter of the Windows Preinstallation Environment User's Guide that is included in the OPK tools.</li> Use a Windows PE RAM disk CD to start the computer, and then type the following commands at a command prompt to create an active partition. Press ENTER after each command.

diskpart

select disk 0

create partition primary

select partition 1

active

assign letter c:

exit

</li> Format the active partition that you created in step 2. To do this, type the following command at the command prompt, and then press ENTER:

format C: /fs:ntfs /q

</li> Copy the .iso image file that you created in step 1 to the active partition. We recommend that you put the .iso image file in the root folder of the boot partition.</li> Locate the :\ \opk\i386 folder.</li> <li>Copy the Setupldr.bin file to the root folder of the boot partition, and then rename the Setupldr.bin file to Ntldr.</li> <li>Copy the Ntdetect.com file to the root folder of the boot partition.</li> <li> In the root folder of the boot partition, create a text file that is named Winnt.sif. This text file should contain the following text. [SetupData] BootDevice = &quot;ramdisk(0)&quot; BootPath = &quot;\ \System32\&quot; OsLoadOptions = &quot;/noguiboot /fastdetect /minint /rdexportascd /rdpath= &quot; Architecture = &quot; &quot; </li> <li>Restart the computer. The computer will start Windows PE.</li></ol>

Keywords: kbexpertiseinter kbtshoot kbinfo KB933510

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.