Resolving failure to run commands on Windows Servers during discovery in Service Mapping - Support and Troubleshooting

Resolving failure to run commands on Windows Servers during discovery in Service Mapping Issue Problem In some cases, Service Mapping may be able to connect to Windows Management Instrumentation (WMI) but fails to run all or specific commands such as netstat.

Symptom The business service map displays the warning icon ( ) on top or instead of the Windows Server. The following error message displays for the Windows Server: Failed to execute WMI command on host Possible Cause 1 The Administrators group on the Windows Server has reduced DCOM rights compared to the default Windows installation.

Resolution 1 Perform the following steps:

In the command-line shell, enter exe . In the Component Services window, navigate to Component Services > Computers . Right-click on My Computer and select Properties . Click the COM Security Click Edit Limits . In the Access Permission window, click Add . In the Select Users or Groups window, enter Distributed COM Users and click OK . In the Access Permission window, select Distributed COM Users and verify that the following permissions are allowed: Local Launch Remote Launch Local Activation Remote Activation

Possible Cause 2 Appropriate security policies are not configured correctly for the Service Mapping user or the group to which this user belongs.

Resolution 2 Perform the following steps:

On the Windows Server that you discover, click Start > Run and enter secpol.msc . In the Local Security Policy window, navigate to Security Settings > Local Policies > User Rights Assignment . Right-click My Computer and select Properties . Right-click relevant policies and check the Service Mapping user configured for them. If necessary, click Add User or Group and add the Service Mapping user to this policy. Perform this for the following policies: Debug Programs Restore Files and Directories Logon as a batch job Logon as service

Possible Cause 3 The Service Mapping user is not allowed to access the administrative share drive C$.

Resolution 3 Perform the following:

Configure the target host to allow the user to access the administrative share drive C$. Or

On the firewall, allow the relevant MID server access to the target host on port 8585. Possible Cause 4 The administrative share is not available for the current user.

Resolution 4 Verify that the administrative share is not available for the current user and if so, fix the problem:

On the MID Server, open the command line window. Run the following command: net use \\ip_address\C$ /USER:domain\user password. Check that the command completes successfully. If it does, run the following command: net use \\ip_address\C$ /DELETE to clear this connection. If there the net use \\ip_address\C$ /USER:domain\user password command fails, allow access to the administrative share on the host. Possible Cause 5 There is a permission problem with the Windows Server.

Resolution 5 Perform the following:

Download the attached run_command.txt script and change the extension to .vbs In the run_command.vbs script, change the IP, user, and password for those of the Windows Server. These are indicated with , , and On the computer that the MID is installed on, open the command line window. Run the following command: cscripts run_command.vbs This script tries to create a process on the Windows Server. If it fails to create a process, it means that there is a permission problem with the Windows Server. Need to consult the windows administrator in order to solve the permission problem.