ID: Usage

:

emc297159 4

Date Created: 06/19/2012 Last Modified: 07/04/2012 STATUS: Audience: Approved Customer

Knowledgebase Solution Environment: Problem: EMC SW: ProSphere 1.6 Cannot discover Windows 2008 host in ProSphere Receive the following message when trying to discover Wndows 2008 R2 vi WMI in ProSphere: Problem: DCOM Access Denied, please check host password used in access profile used for discovery and verify that DCOM Service is enabled on the target Host. Receive the following message when trying to discover Wndows 2008 R2 vi WS-MAN in ProSphere: Problem:

Failed while detecting host:xx.xx.x.xxx, Reason: 2221: WS-MAN data collection failed as there was no response from the target host. Check if the host is available and verify the credentials and IP Address u for connection. The above issues occur because the prerequisites for a successful Windows host discovery were not met. The following outlines the required Windows Management Instrumentation (WMI) prerequisites and also the required DCOM configuration procedure for Windows 2008 R2 hosts (see Note statement). Windows Management Instrumentation (WMI) prerequisites: The following WMI prerequisites must be met to support ProSphere discovery of a Windows 2008 host:

Root Cause:

   

The user (defined in the access credentials) through which the discovery is done must be an administrator, or should be part of an administrator group. The WMI service must be running on the target host. Firewall and WMI must be properly configured.

DCOM communication must be enabled between the target host and ProSphere. On the target host, make sure the following registr key is set to Y: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole ->EnableDCOM

Fix:

Only NTLM v2 authentication security is supported for WMI discovery

Windows 2008 R2 DCOM configuration procedure In addition to the above WMI configuration prerequisites, following must be done in Windows 2008 R2 releases to configure DCOM to support ProSphere discovery: 1. Run the regedit command to open the Registry Editor and navigate to the following key which is for the WBEM Scripting Locator: HKEY_CLASSES_ROOT\CLSID\76a64158-cb41-11d1-8b02-00600806d9b6 2. 3. 4. 5. 6. 7.

Right-click and select Permissions to launch the Permissions for dialog. Select the Administrators group in the Security tab and click Advanced to launch the Advanced Security Settings for dialog Select the Owner tab and change the owner to Administrators group. Click OK to return to to the Permissions for dialog. Ensure that the Administrators group has the Allow checkbox selected next to Full Control. Click OK and then exit the Registry Editor.

Sign up to vote on this title
UsefulNot useful