The maximum number of concurrent connections is reset to 10 after you run the Sysprep tool in Windows Server 2003 Compute Cluster Edition

Consider the following scenario. During the initial installation of Microsoft Windows Server 2003 Compute Cluster Edition, you set the number of concurrent connections to a number other than the default setting. You set this number on the Licensing Modes screen. Then, you run the Sysprep tool (Sysprep.exe) on the computer to prepare the image for deployment to multiple computers. Finally, you run Mini-Setup on one of the deployed Windows Server 2003 Compute Cluster Edition-based computers.

In this scenario, the number of concurrent connections is reset to 10 on the deployed Windows Server 2003 Compute Cluster Edition-based computer. You can use the Licensing item in Control Panel to verify this.

Note In Microsoft Windows Server 2003 SP1 x64 Edition, the Licensing Modes screen is displayed during Mini-Setup. Because you can set the number of concurrent connections on the Licensing Modes screen, this problem does not occur in Windows Server 2003 SP1 x64 Edition.

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. To work around this problem, edit the ConcurrentLimit registry value in the following registry subkey to change the number of concurrent connections that are allowed by Windows Server 2003 Compute Cluster Edition: To edit this registry value, follow these steps:

1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LicenseInfo\FilePrint
3. Right-click the ConcurrentLimit entry, and then click Modify.
4. In the Value data box, type a number that is sufficiently large to handle the maximum number of concurrent connections that the Windows Compute Cluster Server 2003-based computer might experience. Then, click OK. For example, type 999.
5. Exit Registry Editor, and then restart the computer.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Windows Compute Cluster Server 2003 is an integrated, standards-based compute clustering platform that is built into Windows Server 2003 SP1 x64 Edition. Two CDs are required to run the Windows Compute Cluster Server 2003 installation. The first CD includes Windows Server 2003 Compute Cluster Edition. The second CD includes the Compute Cluster Pack. The Compute Cluster Pack is a combination of the interfaces, utilities, and management infrastructure that make up Windows Compute Cluster Server 2003. Administrators use this CD to configure a head or to configure a compute node. For more information, visit the following Microsoft TechNet Web site: Windows Compute Cluster Server 2003 is licensed as a server license without incremental client access licenses (CALs). For more licensing information about Windows Compute Cluster Server 2003, visit the following Microsoft Web site: For more information about Windows Compute Cluster Server 2003, visit the following Microsoft Web site: