Windows Management Instrumentation (WMI) Access Denied errors when using Capacity Planner Data Collector
search cancel

Windows Management Instrumentation (WMI) Access Denied errors when using Capacity Planner Data Collector

book

Article ID: 336729

calendar_today

Updated On:

Products

VMware

Issue/Introduction

What are some steps I can take to troubleshoot WMI access denied problems seen when using Capacity Planner Data Collector?

Environment

VMware Capacity Planner 2.1.x

Resolution

The most common error reported by the operating system for WMI problems is Access Denied. There are many reasons you may encounter an Access Denied message. Below are steps to check for the more common ones. You'll find a longer list, with more suggested solutions, in the "Troubleshooting" section of the VMWare Capacity Planner 2.x Data Collection Guide.
  1. If you are reading logs from another computer on the network, make sure that the user and password you have supplied for each feed correspond to an administrator account on the target computer. That account must have a non-blank password.

  2. Check that DCOM is enabled on both the host and the target PC. Check the following registry entry on both computers:
    Key: HKEY LOCAL MACHINE\Software\Microsoft\Ole
    Name: EnableDCOM
    Type: REG_SZ
    Data: Y

  3. Check that WMI is installed. WMI is present by default in Windows 2000 and later operating systems, but must be installed manually on Windows NT 4 systems. To check for the presence of WMI, select Start > Run and type wbemtest. If the Windows Management Instrumentation Tester application starts, then WMI is present; if it does not start, you must install it. Consult the "Troubleshooting" section of the VMWare Capacity Planner 2.x Data Collection Guide for details.

  4. Ensure that WMI permissions have been set correctly. Consult the "Troubleshooting" section of the VMWare Capacity Planner 2.x Data Collection Guide for details.

  5. For Windows XP Professional target systems, make sure that remote logons are not being coerced to the guest account (also known as "ForceGuest"), which is enabled by default on computers that are not attached to a domain. To turn off this coercion, select Start > Run and type secpol.msc to open the Local Security Policy editor. If it is not already expanded, click Local Policies > Security Options. Select Network access: Sharing and security model for local accounts. If this entry is set to guest only, right-click it and choose Properties. Select Classic - local users authenticate as themselves, and restart the computer.

  6. On Windows XP SP2 systems, configure the firewall to allow remote administration. To do this, open a command prompt and type netsh firewall set service RemoteAdmin.

  7. If you have other internal firewalls on your network, you may have to configure them to allow WMI messages. See the "Troubleshooting" section of the VMWare Capacity Planner 2.x Data Collection Guide for advice. Even if you are not knowingly running any firewall software, some antivirus solutions may contain their own firewall functionality. Such software that is not properly configured to allow WMI traffic may be the cause of the problem.

  8. Make sure that no remote access or WMI-related services have been disabled. In Windows XP, the following services should be running (or at least allowed to start on demand):
    • COM+ Event System
    • Remote Access Auto Connection Manager
    • Remote Access Connection Manager
    • Remote Procedure Call (RPC)
    • Remote Procedure Call (RPC) Locator
    • Remote Registry
    • Server
    • Windows Management Instrumentation
    • Windows Management Instrumentation Driver Extensions
    • WMI Performance Adapter
    • Workstation
These links at Microsoft's Web site also discuss WMI:

Note: The preceding links were correct as of April 24, 2015. If you find a link is broken, provide feedback and a VMware employee will update the link.

Additional Information

For translated versions of this article, see: