SCOM Managmement Packs not compatible with View 4.6?!

[lennyburns]

I have an issue with the VMWare View Management Pack for SCOM that ships with the 4.6 Connection Server.

The issue is that the MP doesn’t work with/hasn’t been updated for VMWare View 4.6.

I was finally able to get the MP to work by changing the ProductVersion Reg key value of the View Connection servers from 4.6.0.366101 to 4.5.

See attached.

When I changed this value and reran the discovery scripts monitoring kicked on.

So the issue now is that VMWare has to update this MP to work with 4.6.

I am attempting to modify the MP, becuase i dont want to modify the View Server.

Anyone have thoughts on what happened here, why this is this way, or if i'm ignoring some new SCOM pack out there?

[lennyburns]

I believe they only need to change 1 line in their MP Script (VMware.View.Cluster.Node.ScriptProbe.Discovery.vbs ) see below.

Please make a note of this.

I will attempt to contact Support about this too.

Default Script Code:

' Discovery version

Const VIEW_DISC_VER = "4.5"

Updated Script Code:

' Discovery version

Const VIEW_DISC_VER = "4.6"

[mpryor · Accepted solution]

This is a known issue and a KB article was written for it, but for some reason isn't currently marked as public - I'll see if I can find out why and unblock it. URL is: http://kb.vmware.com/kb/2001298, it contains a download link for the updated management packs to be used with 4.6.0, I've attached a copy to this thread.

[joansp]

Hello, we've the same problem with scom and view 4.6, the discovery script doesn't discovery any connection server.

Does someone try the new  management pack? When I try to import, it shows the 5.0 version. Is it confidence?

[lennyburns]

Read the last post. the pack is there as an attachment.

[joansp]

Hello lennyburns, firt sorry for my english.  I was download the mp and tried to import to scom, but I saw the 5.0 version mp for vmware view. For that, my question is if that mp are really for confidence to vmware view 4.6?

[lennyburns]

If that is true, then they messed up again.

I'll check.

[uday_s]

Even if the MPs show the version as 5.0, they'll work with 4.6. This has been validated.

Thanks,

Uday

[joansp]

Hello uday s,

how can you afirm the mp have been validated?

You've been validated? or vmware have been validated?

thank's

[uday_s]

These MPs were validated by me and VMware.

[DamirSalaka]

Hello All!

I'm trying to assist my VM guys in setting up MP in our environment and understand the MP myself.

I wondered if anyone knows how exactly  those script monitors work.

Domain Connectivity Health

Event Database Connectivity Health

Virtual Center Database connectivity

We have one node where the "Virtual Center Database connectivity" fails. So i tried to run it locally from the node itself.

When run locally i get error JAdmin queue not present (running it with my own domain admin account)

"cscript VMware.View.ConnectionServerRole.v0405.VcConnectivityCheck <NETBIOS_NAME>".

The funny part is though if i substitute the <NETBIOS_NAME> with one where the monitor is Healthy i still get the same error.

So i'm kind of confused 🙂

I can see script uses COM Objects but i can't seem to find reference of it.

Thanks in advance....

[CDarazs1]

HI,

I downloaded the latest MP from the website and re-imported in the SCOM but the discovery script still contains the wrong version number.

Where can I find the discovery script?

I found in the SCOM temp folder on the Connection server but still doesn't pick up the server

I tryied to run manually the script but for that I need SCOM ID-s

the other issue is if I restart the SCOM agent service the SCOM overwrite it with the centrally stored script

Any suggestion about how can I change the discovery script permanently?

Thanks,

Csaba