Cluster discovery - NOT WORKING
Hi, I am unable to discover a 2008 cluster. The version of MP "Windows Server 2008 Cluster Management Library" is 6.0.6720.0. It's running under a user specified in the account profile "Windows Cluster account" which has local admin rights. The error messages from the nodes are related to WMI: Object enumeration failed Query: 'SELECT * FROM MSCLUSTER_Node where Name=""' HRESULT: 0x80070005 Details: Access is denied. Module was unable to execute the notification query. Error: 0x80041003 Details: Access denied Alert triggered based on the result of connection attempt the local cluster. <br/>Discovery module failed connecting to local cluster while cluster service is registered. Module will try reconnect after allotted time Error: 0x80070005 Details: Access is denied. The servers are R2 enterprise. I've tried to add specific( meaning all) rights in wmimgmt.msc and to query myself in wbemtest towards mscluster_node class, but I also get access denied when I do these actions locally. Is there a malfunction with WMI ? What is happening? I will be very thankfull for your help! Best Regards Thanks in advance, Best Regards
September 19th, 2012 9:50am

Troubleshoot or rebuild WMI. For troubleshooting WMI you can reference: http://support.microsoft.com/kb/875605http://technet.microsoft.com/en-us/library/cc180763.aspxhttp://blogs.msdn.com/wmi/archive/2009/03/13/let-s-troubleshoot-wmi-part-1-remoting-and-security.aspx Roger
Free Windows Admin Tool Kit Click here and download it now
September 19th, 2012 10:42am

I've managed to confirm that my rights are sufficient after I ran wbemtest as an administrator. Still, the discovery is not working. I found this ( http://msdn.microsoft.com/en-us/library/windows/desktop/aa826699(v=vs.85).aspx#uac_effect_on_wmi_data_returned_to_scripts_or_applications ): UAC Effect on WMI Data Returned to Scripts or Applications If a script or application is running under an account in the Administrators group, but not running with an elevated privilege, then you may not get all the data returned because this account is running as a standard user. The WMI providers for some classes do not return all instances to a standard user account or an Administrator account that is not running as a full administrator because of UAC filtering. I'm thinking that this might be related. Question is how to test this, how to get the run as account to run "with an elevated privilige"....? Thanks in advance, Best Regards
September 20th, 2012 2:32pm

Stupid question but did you configure the agents as proxys?
Free Windows Admin Tool Kit Click here and download it now
September 20th, 2012 3:28pm

Stupid question but did you configure the agents as proxys?
September 20th, 2012 3:34pm

NOT a stupid question! And I guess I would have felt stupid also if it weren't for the fact that the online documentation of the MP is COMPLETELY LACKING! There is absolutely no info here http://technet.microsoft.com/en-us/library/dd491026.aspx . Not easy for newbie. Enabling the proxy on the agents seems to have done the trick, but watching the "Clusters" diagram view I only see one of the nodes. All the cluster resources are hosted on this node so I'm guessing this might change if some of the resources failed over, that both nodes will be viewable? Reason why I feel a little uncertain that the whole cluster is completely discovered is that in the view "Cluster Service State" it says that only one of the cluster nodes have "Proxying Enabled". Both agents have proxy enabled, so perhaps this refers to something else? Again, the documentation would have been nice ;) Anyway, thanks a lot for your help, Julia! Thanks in advance, Best Regards
Free Windows Admin Tool Kit Click here and download it now
September 21st, 2012 4:02am

Hello, I had the same issue. The agents were enabled as proxies. Initially the agent action account was configured to run with an account based on the least privilege principal but the cluster action account had every single right necessary but to no avail. I then proceeded to configure the agents to run with the local system account and discovery worked after that. I hope this helps.
October 26th, 2012 2:16pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics