Hello, I have a cluster with the name byt1sql002cluster (to long NETBIOS name). How do I monitor it with SCOM because the backwards compatibility i scuting the name BYT1SQL002CLUST.ppc.corp\ROOT\CIMV2. I have created a DNS registration for it with BYT1SQL002CLUST.ppc.corp still nothing.. Please help!Alert

Hey Byty Do you have any other clusters being successfully monitored by SCOM. It sounds like your discovery is not running... Paul Keely

Yes I have. It is working ok for all except the ones that have long names... The script does not detect corectly the name.. The name is Cluster at the end and he only detects NETBIOS+Domain. In AD the Netbios is BYT1SQL002CLUST and the FQDN is BYT1SQL002CLUSTER.ppc.corpAlert

hi Check this.This might answer you question. http://social.technet.microsoft.com/Forums/en-US/operationsmanagergeneral/thread/3754d09a-7ac9-47a2-b520-14be626e4ed0 Omkar umarani SCOM STUDENT

Sadly..... I have created a DNS registration to be like NETBIOS name +DNS suffix for the Clsuter. Now I can ping that name, and acces the WMI but still it does not want to have it monitred :( Maybe a reinstall of the agent...Alert

Hi, Put the virtual node in Agent less.And on physical machine push the agent and enable the agent proxy tab on that machine and tell that machine to monitor those agent less machine. Omkar umarani SCOM STUDENT

I am tracking an identical issue. The problem is with how we discover the cluster network name resource. We use the cluster API to get the network name - which is delivered to us by the API as the truncated (NetBIOS) name. We take that name - and append the DNS dmain name - to create the FQDN. Then - we try and attach to this FQDN for future discoveries.... you will see this truncated-FQDN name in the network name for the discovered Windows Server and Windows Computer objects. I am struggling to find a workaround. The best guidance is never to create server names which are longer than 15 characters.... because the DNS name will never match the NetBIOS name. You can create a new agentless computer - to be monitored by a proxy node - but that is not a good solution. Since this solution would not be cluster aware - the monitoring would not change with a cluster failover, and the manually created agentless relationship would contain a lot of duplicated computer based monitoring. Kevin Holman

Hi Kevin, Just tried the solution to add a new agentless monitoring.. before trying to see what is new on the technet :) I added to be monitored by SCOM and it was monitoring only PING, now just moved it to the active node and is monitoring things :) from anywhere else is doing only ping! PS: Nice blog.. you and Marnix Wolf are my favorite bloges related to SCOM. Maybe MS will change the Script in the next update CU4 :) .. or let`s wait the new anounced SCOM vNext .