Exchange Server 2010 installation is stopped if WinRM-IIS-Ext is installed on the server

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at]  

Topic Last Modified: 2011-01-21

The Microsoft Exchange Server Best Practices Analyzer Tool determines whether Windows Remote Management IIS Extension (WinRM-IIS-Ext) is installed on a Windows Server 2008-based computer or on a Windows Server 2008 R2-based computer on which you want to install Exchange Server 2010.

WinRM-IIS-Ext cannot be installed before Exchange Server 2010 is installed. If WinRM-IIS-Ext is installed, installation of Exchange Server 2010 is stopped.

The WinRM-IIS-Ext feature is included in Windows Server 2008 R2. WinRM-IIS-Ext can also be installed through an update for Windows Server 2008. For example, the updates that are described in the following Microsoft Knowledge Base articles include WinRM-IIS-Ext:

To resolve this problem, you must uninstall WinRM-IIS-Ext, and then install Exchange Server 2010.

Use Server Manager to uninstall WinRM-IIS-Ext. After Exchange Server 2010 is installed, you can reinstall WinRM-IIS-Ext.

After you install WinRM-IIS-Ext on a computer on which Exchange Server 2010 is installed, you may receive one of the following error messages when you try to use the Exchange Management Shell (EMS) or the Exchange Management Console (EMC):

  • The requested HTTP URL was not available.

  • HTTP server error status (500).

  • The connection to the specified remote host was refused.

  • HTTP status code of 403.

  • It cannot determine the content type of the HTTP response from the destination computer.

For more information about this issue, view the following Knowledge Base articles: