Microsoft KB Archive/932548

= A custom help option that uses a fully qualified domain name does not work in Communicator 2005 =

Article ID: 932548

Article Last Modified on 2/23/2007

-

APPLIES TO


 * Microsoft Office Communicator 2005

-



Important This article contains information about how to modify the registry. Make sure that you 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



SYMPTOMS
Consider the following scenario:
 * An administrator creates a custom help option in Microsoft Office Communicator 2005 that uses a URL that contains a fully qualified domain name (FQDN).
 * The help URL is not included in the Trusted sites zone on the Security tab of the Internet Options dialog box.
 * The help URL is included in the Exceptions list in the Proxy Settings dialog box in Internet Explorer.

In this scenario, you experience the following symptoms:
 * If you click the custom help option in Communicator 2005, nothing happens. The Web browser program does not start, and you do not receive an error message.
 * If you start Help in Communicator 2005 before you click the custom help option, the custom help option starts the Web browser as expected, and the custom help content appears.



CAUSE
This problem occurs because the Communicator 2005 security manager cache does not include the sites that are listed in the Proxy Exception list. Therefore, the custom help URL is mapped to the Internet security zone. Therefore, the custom help option is not able to start successfully. If the built-in Help program is started before you start the custom help, the Web browser program populates the Security Manager cache. In this situation, later attempts to start the custom help option are successful.



RESOLUTION
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 the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, a hotfix has been created that allows for the use of a new registry entry that you can use to bypass the process that maps the URL to a security zone. This functionality lets you have an implied trust of the custom help URL.

How to obtain the hotfix
This issue is fixed in the Communicator 2005 Hotfix Package dated February 16, 2007. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

929000 Description of the Communicator 2005 hotfix package: February 16, 2007

To enable this hotfix, follow these steps:  Quit Communicator 2005. Click Start, click Run, type regedit, and then click OK. Locate and then click to select the following registry key:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator

 After you select the key that is specified in step 3, point to New on the Edit menu, and then click DWORD Value. Type DisableHelpMenuSiteCheck, and then press ENTER. Right-click DisableHelpMenuSiteCheck, and then click Modify.</li> In the Value data box, type 1, and then click OK.</li> On the File menu, click Exit to quit Registry Editor.</li></ol>

After you configure this registry entry, you must restart Communicator 2005. This registry value is read when Communicator 2005 starts.

<div class="workaround_section">

WORKAROUND
To work around this problem, use one of the following methods: <ul> In the custom help URL, use the host name of the Web server instead of the FQDN of the Web server. For example, configure a URL that resembles the following:

http://InternalHelp/Help.htm

</li> Add the custom help site to the Trusted sites zone on the Security tab of the Internet Options dialog box.</li></ul>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

Keywords: kbqfe kbbug kbfix kbpubtypekc KB932548

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.