The Exchange Server Outlook Anywhere feature does not work correctly if it is installed on a Windows Server 2008-based server that has Terminal Services Gateway installed

Consider the following scenario:

• You have a Windows Server 2008-based server.
• This server has Terminal Services Gateway (TS Gateway) and the Microsoft Exchange Server Outlook Anywhere feature installed.

In this scenario, one of the following symptoms occurs:

• Users cannot connect to Exchange Server by using the RPC-over-HTTP protocol. This symptom occurs if you install the Outlook Anywhere feature before you install Terminal Services Gateway.
• The Outlook Anywhere feature works correctly after you install Terminal Services Gateway. However, after you open the TS Gateway Manager snap-in, users cannot connect to Exchange Server by using the RPC-over-HTTP protocol. This symptom occurs if you install Terminal Services Gateway before you install the Outlook Anywhere feature.

Note Terminal Services Gateway and the Outlook Anywhere feature both rely on the RPC-over-HTTP protocol.

This problem occurs because the Basic Authentication setting is disabled when TS Gateway is installed and when you open the TS Gateway Manager snap-in. Outlook Anywhere authentication supports Basic authentication and NTLM authentication. If NTLM authentication is also disabled, Outlook Anywhere cannot function correctly. For example, this problem occurs in Windows Small Business Server 2008 where NTLM authentication is disabled by default.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This 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 item in Control Panel.

Windows Server 2008, x86-based versions

Windows Server 2008, x64-based versions

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

For more information, click the following article number to view the article in the Microsoft Knowledge Base: