They have many different VMware solutions in place. Much of them is being monitored by SCOM, using the nWorks Veeam MP. Some weeks ago the customer introduced a new item to the VMware mix: VMware View.
Nice but not working…
This product is shipped with a Management Pack for SCOM. How nice! However, the MP (version 126.96.36.19914) didn’t land. No matter what we tried.
Failing Discovery Script
As it turned out, the primary Discovery script failed. The version of VMware View the customer has in place is 4.6 and this version isn’t properly discovered.
Is there a newer version?
Time to look for another MP. Soon we found it here. The mentioned KB article is still locked, but the moderator attached the related MPs in his comment. The version of this MP is 188.8.131.5211 and works great with VMware View 4.6.
So whenever you have VMware View running at a version higher than 4.5, you need the latest MP (at the moment this posting was written version 184.108.40.20611) which can be found here. This MP can be imported while the older version is in place. They will be nicely overwritten.
The requirements for this MP are:
- Presence of the SCOM Core MP;
- Presence of the Base Server OS MP;
- Agent Proxy enabled on the Windows Servers which host VMware View Connectivity roles.
Not a requirement, but nice to have:
- The View Connection Server Group needs a proper name. In the SCOM Console it looks better compared to an empty string. The guide related to the MP describes how to achieve that.