Article ID: 907639
Article Last Modified on 11/16/2007
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
INTRODUCTION
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:
889100 How to obtain the latest service pack for Windows Server 2003
MORE INFORMATION
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.
Notes
- 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 behavior
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
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:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BINLSVC\Parameters
Name: BindInterface
Type: REG_SZ
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:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
Name: Reminst_DontAuthorizeDHCP
Type: REG_DWORD
Value: 1HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup
Name: Reminst
Type: REG_DWORD
Value: 1HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BINLSVC\Parameters
Name: DisableRogueDetection
Type: REG_DWORD
Value: 1
- 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:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BINLSVC\Parameters
Name: BannedGuids
Type: REG_MULTI_SZ
Value:GUIDs
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:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BINLSVC\Parameters
Name: ResetBootProgram
Type: REG_DWORD
Value: 1
Download information
The following files are available for download from the Microsoft Download Center.
Windows Server 2003, x64-based versions
![[GRAPHIC: Download]](/wiki/index.php?title=File:Download.gif){kind=small}
Download the 907639 package now.
Windows Server 2003, 32-bit versions
Download the 907639 package now.
Windows Server 2003, Itanium-based versions
Download 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:
119591 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:
325862 How to use Remote Installation Services to install Windows Server 2003 on remote computers
REFERENCES
Windows Compute Cluster Server 2003: Beta 1
http://www.microsoft.com/windowsserver2003/hpc/default.mspx
Overview of High-Performance Computing
http://www.microsoft.com/windowsserver2003/hpc/whitepaper.mspx
How Remote Installation Services works
http://technet2.microsoft.com/windowsserver/en/library/a8c68dce-57e6-4710-bef6-d7adb1e9e8c31033.mspx
Remote Installation Services (RIS) for 64-bit operating systems
http://technet2.microsoft.com/windowsserver/en/library/96a68f1f-e397-4429-9b3e-44e1532f37951033.mspx
Additional query words: supercomputer binlsvc Winx64 Windowsx64 64bit 64-bit hotfix rogue
Keywords: kbwinserv2003sp2fix kbqfe kbhotfixserver atdownload KB907639
