Microsoft Windows Compute Cluster Server 2003 brings together the Windows operating system, the ease-of-use of Active Directory, and the power of x64-based computers to provide an affordable high-performance computing (HPC) solution. Windows Compute Cluster Server 2003 is a cluster of servers that includes a single head node and one or more compute nodes. The head node deploys compute nodes and schedules jobs for the compute cluster. To automatically deploy compute nodes to the cluster, you can install and configure Remote Installation Services (RIS) on the head node. Then, you can stage an image to deploy the compute nodes. RIS has been part of the operating system since the release of Microsoft Windows 2000 Server.
For more information about the latest service pack for Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for Windows Server 2003
In a high-performance computing environment, you can use Windows Compute Cluster Server 2003 to deploy compute nodes to a supercomputing cluster. To do this, you install and configure Remote Installation Services (RIS) on the head node. However, you must then modify RIS. The update that is described in this article modifies the Boot Information Negotiation Layer (BINL) service so that you can automatically deploy compute nodes.
The BINL service answers clients, examines the directory service for validation, and passes client information to and from the server. When the Risetup.exe process runs, the process installs the BINL service. Risetup.exe then configures the service to use default registry parameters. These parameters are sufficient for optimal performance in an organization. In a compute cluster, the Compute Cluster Management snap-in performs RIS setup and RIS image management.
The changes to the BINL service comply with the model that is implemented by the Windows Compute Cluster Server. In this model, the head node automatically deploys compute nodes on a private network. Therefore, the head nodes cannot be serviced by a corporate RIS server that is already configured.
- You cannot use a corporate RIS server to deploy compute nodes if the server is not running on the head node.
- A head node that has a single network adaptor cannot use RIS to deploy compute nodes.
Changes to RIS behaviorImportant
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
How to back up and restore the registry in Windows
This update makes the following changes to RIS behavior:
- The RIS service can now bind to a specific interface. When you install RIS in Windows Compute Cluster Server 2003, the RIS service binds to the network that is identified as the private network. To do this, RIS uses the following registry subkey:
Value: IPAddress of the private network adaptor
- Authorization is no longer required to operate a RIS server on the private network. Additionally, the RIS server does not require write access to the Service Control Point (SCP) in Active Directory. This change uses the following registry subkeys:
Note Because you can apply this update to RIS servers that are not part of a compute cluster, a corporate network may include unauthorized RIS servers.
- You can now use the media access control (MAC) address of the network adaptor that supports the Pre-Boot Execution Environment (PXE) instead of using the GUID. This change has been implemented because computers that run x64-based versions of Windows Server 2003 may have duplicate GUIDs. To use this functionality, configure the BannedGuids entry in the following registry subkey:
Note The value of the BannedGuids entry must contain one GUID per line. The contents of the entry must exactly match the values that appear during the PXE client start process. The entry must not include hyphens.
- Incorrect: 47f4cb1a-9339-43e5-a92a-fadb5140f1c8
- Correct: 1acbf4473993e543a92afadb5140f1ca
- So that a node can be reimaged, the Startrom.n12 file or the Startrom.com file is now sent on demand by using the netbootMachineFilePath Active Directory attribute. This change clears only the value of netbootMachineFilePath for the client that is being served.
For example, suppose an administrator sets the value of netbootMachineFilePath to Startrom.n12. Then, the administrator uses the following path in the ADSIEdit utility to restart the computer independently:
RIS-Server\OSChooser\i386\Startrom.n12When the client restarts, the client automatically goes through the PXE and Client Installation Wizard (CIW) screens. During the OSChooser screens, BINL clears this entry in Active Directory. Therefore, the client does not receive startrom.n12 again when the client restarts. This change uses the following registry subkey:
The following files are available for download from the Microsoft Download Center.
Windows Server 2003, x64-based versionsDownload the 907639 package now.
Windows Server 2003, 32-bit versionsDownload the 907639 package now.
Windows Server 2003, Itanium-based versionsDownload the 907639 package now.
Release Date: October 18, 2005
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Technical support for x64-based versions of Microsoft Windows
Your hardware manufacturer provides technical support and assistance for x64-based versions of Windows. Your hardware manufacturer provides support because an x64-based version of Windows was included with your hardware. Your hardware manufacturer might have customized the installation of Windows 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 x64-based version of Windows. 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 x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site:
About Remote Installation Services and Windows Compute Cluster Server 2003
In Microsoft Windows Server 2003,you use Remote Installation Services (RIS) to automate the deployment of both client and servers. For more information about how to use Remote Installation Services in Windows Server 2003, visit the following Microsoft Desktop Deployment Center Web page:
For more information about Microsoft Windows Compute Cluster Server 2003, visit the following Microsoft Web page:
For more information about how to deploy Windows Server 2003 using RIS, click the following article number to view the article in the Microsoft Knowledge Base:
How to use Remote Installation Services to install Windows Server 2003 on remote computers