Cluster Names show as errors in various reports

[AdmJLovejoy]

1. Error: WMI access denied
2. Error: RPC Server unavailable
3. OS: Never scanned OS

I’m sure there are others. It would be helpful if Cluster Names were not scanned as normal Windows Servers are. Please advise.

[Hemoco]

We are testing this internally, biggest problem is when there is no active directory available and cluster contains only one node.

Cluster specific scanning has been added in the 2019 spring release.

[AdmJLovejoy]

Nothing?????

[AdmJLovejoy]

This could be handled programmatically in Lansweeper a couple of different ways.

1. WMIERROR will report the scan error as follows: WMIERROR DNS redirected to <NODE> but expected computer <CLUSTENAME>
2. Probably the easiest way would be to query the Cluster Account description field in Active Directory for the entry “Failover cluster virtual network name account”, and excluding it from scans this way.

Clusters come and go in our environment, having to manage manual exclusion lists is not very efficient or practical.

[Hemoco]

Lansweeper cannot know that this is a cluster name if the computer cannot be scanned.

For cluster names (and dns/round robin, ... names) we suggest to add the virtual name to the scan exclusions list.