Page History
In order to use WMI, the user account under which the Collection Service runs must have administrator permissions on the remote server. The most frequently encountered problems with WMI relate to RPC traffic failing to get through to the remote computer. Another issue involves DCOM/WMI permissions.
The following links link provide additional information about how to troubleshoot WMI connectivity issues:
Newtablink alias Securing a remote WMI connection url https://msdndocs.microsoft.com/en-us/library/windows/desktop/aa393266%28v=vs.85%29.aspx Newtablink alias Help with Scripts url https://technet.microsoft.com/en-us/scriptcenter/win32/wmisdk/securing-a-remote-wmi-connection
Using WbemTest (Windows Management Instrumentation Tester)
...
- Run
wbemtest.exe
. - Click Connect.
- In the NameSpace text box, enter \\server\root\cimv2 where the server is the name of the server to which you want to connect.
- Provide Username and Password.
- Click Connect.
- Click Query.
- Enter select * from win32_process.
- Click Apply.
...
- If the remote computer is running Windows XP, make sure it is not set to Force Guest. This setting forces impersonation of any connection as Guest.
- Open the Local Security Policy console from Administrative Tools.
- Browse to Security Settings > Local Policies > Security Options .
- Double-click Network Access: Sharing And Security Model For LocalAccounts.
- Change the settings from
Guest Only
to Classic.
- Make sure DCOM is enabled on the remote server:
- Run
DcomCnfg
on the remote server. - Click Component Services.
- Expand Computers.
- Right click My Computer and select Properties.
- Click the Default Properties tab.
- Make sure Enable Distributed COM on this computer is checked.
- Run
- Verify the configuration of the correct DCOM remote launch and activation permissions:
- Run
DcomCnfg
on the remote server. - Click Component Services.
- Expand Computers.
- Right click My Computer and select Properties.Make sure Enable Distributed COM on this computer is checked.
- Click the Com Security tab.
- Under Launch and Activation Permissions, click Edit Limits.
- In the Launch Permissions dialog box, make sure your user account or group is listed in the Groups or user names list. If your user account or group is not listed, click Add and add it to the list.
- In the Launch Permission dialog box, select your user account or group in the Group or user names list. In the Allow column under Permissions for User, select Remote Launch and Remote Activation, and then click OK.
- Run
- Make sure the correct DCOM remote access permissions are configured:
- Run
DcomCnfg
on the remote server. - Click Component Services.
- Expand Computers.
- Right click My Computer and select Properties.Make sure Enable Distributed COM on this computer is checked.
- Click the Com Security tab.
- Under Access Permissions , click Edit Limits.
- In the Access Permission dialog box, select
ANONYMOUS LOGON
name in the Group or user names list. In the Allow column under Permissions for User, select Remote Access, and then click OK.
- Run
- Make sure the correct WMI namespace permissions are configured.
- Run On the target machine, run
wmimgmt.msc
. - Right-click click WMI Control, and then select Connect to another computer .
- Enter the remote server name, and then click OK .
- Right-click WMI Control , and then select select Properties.
- In the Security tab, select the CIMV2 namespace, and then click click Security.
- Locate the appropriate account, and then check check Remote Enable in in the Permissions list.
- Run On the target machine, run
Scroll pdf ignore | ||||
---|---|---|---|---|
Newtabfooter |
|
SQL Diagnostic Manager identifies and resolves SQL Server performance problems before they happen. Learn more > >
...
...