Configuring the agent to connect to the remote Windows® Management Instrumentation (WMI) and WinShell components on Windows Server 2008 R2 systems requires certain modifications to the registry keys. In some situations, these registry keys may be owned by TrustedInstaller instead of the Administrators group, which prevents modifications from being made even by Administrator accounts.
2 |
Right-click the registry key and click Permissions. |
3 |
4 |
5 |
6 |
Click OK. |
In order to allow the agent to connect to the remote Windows® Management Instrumentation (WMI) components on Windows Server 2008 R2 or Windows 7 systems, special registry settings are required.
a |
On the desktop, right-click My Computer and navigate to Groups (My Computer > Manage > Configuration > Groups). |
b |
Double-click the Administrators group. |
c |
Add the required domain\user to the Administrators group. |
d |
2 |
Edit the Wbem Scripting Locator registry key. |
a |
Run regedit. |
c |
For each key, right-click the key and navigate to the owner permissions (Permissions > Advanced > Owner). |
d |
Click Other Users and Groups, and add the Local Administrators group. |
e |
Select the Replace Owner on subcontainers and objects check box. |
f |
3 |
Close regedit. |
When attempting to monitor a Windows® XP Professional machine, the remote agent sometimes fails to connect with an Access Denied error message. This error can be caused by the Windows ForceGuest setting, which is enabled by default on machines that are not part of a domain. To resolve the issue, ensure that remote connections are not being coerced to log on as the guest account by following the procedure below.
1 |
2 |
3 |
Choose Local Policies > Security Options. |
4 |
Select the entry: Network access: Sharing and security model for local accounts. |
5 |
6 |
In the dialog box that appears, on the Local Security Setting tab, select Classic - local users authenticate as themselves from the list. |
7 |
Click OK. |
For more information, see step 5 in the following VMWare KB article:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2013
The agent uses Windows® authentication to Negotiate the monitored instance. In some cases, the negotiation can fail if there is a mismatch between the authentication types used by the client and the server.
The following symptoms indicate an authentication issue:
To resolve these issues, you may need to disable the NTLMv2 authentication.
1 |
Run regedit to edit the registry. |
2 |
Locate the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa |
3 |
Locate the value named LMCompatibilityLevel, and change the DWORD value to 2 (send NTLM authentication only). |
4 |
Close regedit and restart the machine. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center