FIX: You cannot use a different SSL certificate for each array member in an ISA Server 2004, Enterprise Edition-based array (898066)
The information in this article applies to:
- Microsoft Internet Security and Acceleration Server 2004, Enterprise Edition
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 SYMPTOMSYou cannot configure a different Secure Socket Layer (SSL) certificate for each enterprise array member server in a Microsoft Internet Security and Acceleration (ISA) Server 2004, Enterprise Edition-based array.
Consider the following scenario. You configure an ISA Server 2004, Enterprise Edition-based server that uses SSL to help protect HTTP connections. When you configure the Web listener to listen to an SSL connection, you must select a certificate that is installed and shared on all the array members.
Additionally, when you use an SSL hardware accelerator for each member server in the array, each accelerator will have a unique certificate.
However, ISA Server 2004, Enterprise Edition requires that you use the same certificate for all member servers in the array.CAUSEISA Server 2004, Enterprise Edition does not support assignment of multiple Web listeners for Web publishing. You cannot configure multiple Web listeners that use a different certificate for each Web listener and then assign each Web listener to a Web publishing rule.RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Internet Security and Acceleration Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 891024 How to obtain the latest ISA Server 2004 service pack Hotfix InformationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem. To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesYou must restart the Firewall service. Restart requirementYou do not have to restart the computer after you apply this hotfix. Hotfix replacement informationThis hotfix does not replace any other hotfixes. File Information
The English version of this hotfix 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 tool in Control Panel. Date Time Version Size File name
---------------------------------------------------------
15-May-2005 06:26 4.0.3440.267 2,382,616 Msfpcui.dll
15-May-2005 06:26 4.0.3440.267 4,601,112 Msfpcsnp.dll
15-May-2005 06:26 4.0.3440.267 394,008 Msphlpr.dll
15-May-2005 06:26 4.0.3440.267 663,320 W3filter.dll Registry entry requirementWarning 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. After you apply the hotfix, ISA Server 2004, Enterprise Edition will support a new registry entry that is named AllowPerServercertificate. You must add this registry entry to the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fpc\w3proxy
Notes- You must apply the hotfix on all servers that are members of the ISA Server 2004, Enterprise Edition-based array. Additionally, you must add the AllowPerServercertificate registry entry on all the servers that are members of the ISA Server 2004, Enterprise Edition-based array.
- Make sure that the Firewall service is stopped before you add the registry entry. Restart the Firewall service after you add the registry entry.
- If the w3proxy registry subkey is not found, you must create the w3proxy registry subkey.
To add the AllowPerServercertificate registry entry, follow these steps: - Click Start, click Run, type regedit in the Open box, and then click OK.
-
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fpc\w3proxy - On the Edit menu, point to New, and then click DWORD Value.
- Type AllowPerServercertificate, and then press ENTER.
- Right-click AllowPerServercertificate, and then click Modify
- Type 1 in the Value data box, and then click OK.
-
Quit Registry Editor.
- After you add the AllowPerServercertificate Registry entry, restart the Firewall service.
STATUSMicrosoft 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 Internet Security and Acceleration Server 2004 Service Pack 2.
Modification Type: | Minor | Last Reviewed: | 10/12/2006 |
---|
Keywords: | kbBug kbfix kbQFE kbHotfixServer KB898066 kbAudITPRO |
---|
|