Configuring registry settings for WMI counter access through DCOM on Windows machines (4229811)

• The database agent fails even when the user credentials are valid.
• The agent log includes the following message:
  The user account has invalid login credentials.
• The agent log includes the error WMIConnection.Access is denied and error code 0x00000005.
• The agent OS verification fails on Windows Vista or Windows 7 installed with a non-English character set.

Windows 2008 R2 restrictions are more severe then previous Windows versions. Special registry permissions are required to be set, before the Agent OS user is allowed to connect to the remote WMI components.

When an agent connects to a monitored Windows host from a UNIX or Linux machine using WMI, you must make certain registry changes in order to allow the required DCOM services to run.

This KB is a subset of Setting up a DCOM connection for WMI (Windows Management Instrumentation) on host machines (4295692)

Grant Access to the Windows registry for WMI monitoring

Add the required domain\user to the Administrator's group

1. Right click on My Computer | Manage | Configuration | Groups
2. Double click on the Administrators group
3. Add (if not exist) the required Domian\user to the group
   
   

   Click To See Full Image.

4. Click "Apply", and then click "OK" to close the dialog box

Windows registry changes are often necessary on the monitored Windows server for WMI connections from Linux-based FglAMs to be successful.

Edit the Registry Key Permissions

1. From the command line, run REGEDIT
2. Navigate to the Registry item:
   HKEY_CLASSES_ROOT\CLSID\{76A64158-CB41-11D1-8B02-00600806D9B6}
3. Right click on the key and select Permissions
4. Click "Advanced"
5. Select the "Owner" tab. Change ownership to the Administrators group or currently logged in user.
   
   

   Click To See Full Image.

6. Enable the checkbox to "Replace owner on subcontainers and objects"
7. Click the "OK" button
8. Give Administrators group "Full Control"
   
   

   Click To See Full Image.

9. Click "OK" twice to accept the changes
10. Repeat steps 2-9 for all of the occurences of the first WBEM Scripting Locator registry key named 76A64158-CB41-11D1-8B02-00600806D9B6
11. Repeat steps 2-9 for all of the occurences of the second WBEM Scripting Locator registry key named 76A6415B-CB41-11D1-8B02-00600806D9B6 ONLY if it is present in the registry
12. Repeat steps 2-9 for all of the occurences of the Windows Script Host Shell Object registry key, named 72C24DD5-D70A-438B-8A42-98424B88AFB8
13. Repeat steps 2-9 for all of the the Windows Script FileSystem Object registry key named 0D43FE01-F093-11CF-8940-00A0C9054228
14. Exit regedit
15. Restart the Remote Registry Service, using Administrative Tools | Services.

Appendix: If the above still doesn't help...

In some cases hacking the Registry as described above doesn't help. In such a case, disabling User Account Control (UAC) can solve the issue or at least point to Windows permissions issue which should be checked on the Windows platform itself. In order to disable UAC (from Microsoft):

1. Click "Start", and then click "Control Panel".
2. In Control Panel, click "User Accounts".
3. In the User Accounts window, click "User Accounts".
4. In the User Accounts tasks window, click "Turn User Account Control on or off".
5. If UAC is currently configured in Admin Approval Mode, the User Account Control message appears. Click "Continue".
6. Clear the Use User Account Control (UAC) to help protect your computer check box, and then click "OK".
7. Click "Restart Now" to apply the change right away, or click "Restart Later" and close the User Accounts tasks window.

Core complete documentation

http://technet.microsoft.com/en-us/library/cc709691%28WS.10%29.aspx#BKMK_S3