Scribd
Upload
139 views3 pages

Enable Remote WMI Access Guide

This document provides instructions for enabling remote access to Windows Management Instrumentation (WMI) on Windows servers and workstations. It outlines three main steps: 1. Enable remote WMI requests by configuring the WMI Control properties and allowing the monitoring user to make remote requests. 2. Allow WMI through the Windows firewall by using the netsh command if the server has a firewall enabled. 3. Enable DCOM calls on the remote machine if the monitoring user is not an administrator, by granting DCOM remote launch and activation permissions. Following these steps should provide remote access to WMI for server monitoring purposes. Additional troubleshooting is suggested if the steps do not resolve connectivity or permission issues.

Uploaded by

HildaMontoya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
139 views3 pages

Enable Remote WMI Access Guide

This document provides instructions for enabling remote access to Windows Management Instrumentation (WMI) on Windows servers and workstations. It outlines three main steps: 1. Enable remote WMI requests by configuring the WMI Control properties and allowing the monitoring user to make remote requests. 2. Allow WMI through the Windows firewall by using the netsh command if the server has a firewall enabled. 3. Enable DCOM calls on the remote machine if the monitoring user is not an administrator, by granting DCOM remote launch and activation permissions. Following these steps should provide remote access to WMI for server monitoring purposes. Additional troubleshooting is suggested if the steps do not resolve connectivity or permission issues.

Uploaded by

HildaMontoya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Original article from http://www.poweradmin.com/help/enableWMI.

aspx

Enable WMI (Windows Management


Instrumentation)
WMI comes installed on all of Microsoft's modern operating systems (Windows 2000, Windows XP, Windows
2003, Windows Vista and Windows 20081). What this page will describe (and the reason you were directed
here from the server status view) is how to enable remote access to WMI. The following steps should only take a
minute or two of your time.

1. Enable remote WMI requests


This setting is usually all that needs to be changed to get WMI working. (Steps 2 and 3 are typically not needed,
but they might be in some circumstances)
1. On the target server, go to
Administrative Tools -> Computer
Management.
2. Expand 'Services and Applications'
3. Right click for Properties on 'WMI
Control'.
4. Select the Security tab
5. Press the Security button

6. Add the monitoring user (if


needed), and then be sure to check
Remote Enable for the user/group that
will be requesting WMI data.

At this point go back and see if this fixes the problem. It might take a couple of minutes for the reports to re-
generate.

2. Allow WMI through Windows firewall


All users (including non-administrators) are able to query/read WMI data on the local computer.
For reading WMI data on a remote server, a connection needs to be made from your management computer
(where our monitoring software is installed) to the server that you're monitoring (the target server). If the
target server is running Windows Firewall (aka Internet Connection Firewall) like what is shipped with
Windows XP and Windows 2003, then you need to tell it to let remote WMI requests through2. This can only
be done at the command prompt. Run the following on the target computer if it is running a Windows firewall:
netshfirewallsetserviceRemoteAdminenable

3. Enable DCOM calls on the remote machine


If the account you are using to monitor the target server is NOT an administrator on the target server, you
need to enable the non-administrator to interact with DCOM by following the simple steps listed here. Follow
the steps for:
To grant DCOM remote launch and activation permissions for a user or group
To grant DCOM remote access permissions

Further Investigation
If the above steps didn't help, we recommend installing the WMI Administrative Tools from Microsoft. This
includes a WMI browser that will let you connect to a remote machine and browse through the WMI
information. That will help to isolate any connectivity/rights issues in a more direct and simple environment.
Once the WMI browser can access a remote machine, our products should be able to as well.
WMI Administrative Tools:
http://www.microsoft.com/downloads/details.aspx?FamilyId=6430F853-1120-48DB-8CC5-
F2ABDC3ED314&displaylang=en

References
1. See http://www.microsoft.com/technet/scriptcenter/resources/wmifaq.mspx#ENAA

2. See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/connecting_through_windows_firewall.asp -- "To Configure Connection 1". Our software doesn't


use or need Connection 2.

You might also like