An updated version of the Disk Partition tool for Windows Server 2003 is available

An updated version of the Disk Partition tool (Diskpart.exe) for Microsoft Windows Server 2003 is available. This version of the Diskpart.exe tool is required to execute performance optimization as described in the "Manual Optimizations" section of OEM Guide to Windows Storage Server 2003 R2.

Disk alignment is a required optimization and must be applied by OEMs during Setup. Disk alignment provides a significant increase in system performance. Failure to perform disk alignment can decrease performance by 10 to 15 percent in RAID array systems.

The updated Disk Management service together with the Diskpart.exe partitioning utility lets you use the Create Partition Primary command together with the align=N and size=N parameters to align any or all primary partitions (0-3) on a boundary. Earlier versions of the tool let you align only the first partition on a boundary.

Note Align=N is the number of kilobytes (KB) from the beginning of the disk to the closest alignment boundary. Size=N is specified in megabytes (MB). If no size is given, the partition continues until there is no more unallocated space in the current region. For example, "align=32 size=1000" is the same as aligning 32 KB of I/O for a partition size of 1000 MB (1GB).

Example of aligning by using 32 KB of I/O

Assume that you use the following command.In this case, all four partitions are correctly aligned to a 32-KB boundary. If you assume a 512-byte sector size, "align=XX" results in the following:

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Update 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 this specific problem. 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 update, the computer must be running one of the following operating systems:

• A 32-bit version of Windows Server 2003 with Service Pack 1 (SP1)
• An Itanium-based version of Windows Server 2003 with SP1
• An x64-based version of Windows Server 2003.
• An R2 version of Windows Server 2003.

Restart requirement

You do not have to restart the computer after you apply this update.

File information

The English version of this update 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.

Windows Server 2003, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003, Itanium-based versions

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

How to apply an update to a Windows Preinstallation Environment (Windows PE) .iso image

1. Download the appropriate update package for the Windows PE image that you are creating.
2. Extract the package to a folder by using the /x command-line switch. For example, to extract the x86 version of update 923076 to the C:\923076 folder, type the following at a command prompt:
   WindowsServer2003-KB923076-x86-ENU.exe �x
   When you are prompted, provide a destination path, such as C:\923076.
3. Re-create the Windows PE image by following the steps that are listed in the Windows PE documentation. However, when you run the Mkimg.cmd command, do not include the option to create an *.iso image. For example, type mkimg.cmd %sourcedir% %destination_dir%.
4. When the Mkimg.cmd command has finished, locate the destination folder where the command has put the newly created Windows PE image flat. For example, the destination folder may be C:\Winpe_temp.
5. Copy all the files from the folder that you created in step 2 to the newly created Windows PE image flat folder. For example, copy the files from C:\923076 to C:\Winpe_temp.

After the process has finished, run the OSCDimg.exe utility to create the .iso image. For information about how to use the OSCDimg.exe program, see the Windows PE documentation.

Technical support for Windows x64 editions

Your hardware manufacturer provides technical support and assistance for Microsoft Windows x64 editions. Your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.

For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site: For product information about Microsoft Windows Server 2003 x64 editions, visit the following Microsoft Web site:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.