The Registry on a Clustered Node Could not be Accessed Remotely
[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-13
Microsoft Exchange Server 2007 setup cannot continue because the registry on a cluster node could not be accessed.
Exchange 2007 setup requires access to the registry of all nodes in the cluster to retrieve various settings.
To address this issue, do the following:
Verify that the Remote Registry service is running on all nodes of the cluster.
Verify that File and Printer Sharing for Microsoft Networks is enabled for the network adapter that is listed first in the binding order.
Verify that the values of the following registry keys are the same on each node of the cluster and are valid for the relevant group policy:
For more information about troubleshooting registry connectivity issues, see the Troubleshooting Registry Connectivity Issues section in "Microsoft Exchange Server Best Practices Analyzer Tool Troubleshooting Connectivity Problems" (http://go.microsoft.com/fwlink/?linkid=56285).