Cluster Managed Resources Need to be Moved or Taken Offline
[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 http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2007-04-09
Microsoft Exchange Server 2007 setup cannot continue because the attempt to install a new active cluster Mailbox server role failed.
Exchange Server 2007 requires that cluster-managed resources be inactive on the cluster node that setup is being run against.
To resolve this issue, move all cluster-managed resources owned by this node, including non-Exchange Server cluster resources, to another node in the cluster. Alternatively, take them offline, and then rerun setup.
For more information about how to move the Exchange-related clustered managed services, see the "Move-ClusteredMailboxServer" (http://go.microsoft.com/fwlink/?LinkId=86627) cmdlet topic in the Exchange Server 2007 product documentation.
For more information about how to take the Exchange-related clustered managed services offline, see the "Stop-ClusteredMailboxServer" (http://go.microsoft.com/fwlink/?LinkId=86635) cmdlet topic in the Exchange Server 2007 product documentation.
For more information about managing non-Exchange cluster resources, see "Manage Resources" (http://go.microsoft.com/fwlink/?LinkId=86637) in the Windows Server 2003 Product Help.