You are browsing the archive for SCOM 2007 R2.

A new SCOM 2007/2012 MP is available for ConfigMgr 2012 RC2

7:48 pm in ConfigMgr 2012, sccm, SCCM 2012, SCOM 2007, SCOM 2007 R2, scom 2012, SCOM2012 by Kenny Buntinx [MVP]

If you are testing and evaluating the latest System Center 2012 components, you might be interested in this.

A new MP is available to Monitor ConfigMgr 2012 RC2 with OpsMgr 2007 R2, or OpsMgr 2012 RC:

Hope it Helps ,

Kenny Buntinx

SCOM and VEEAM nworks management pack for VMware : Guest VM’s are not visible

6:37 am in Operations Manager 2007, Opsmgr 2007, SCOM 2007, SCOM 2007 R2, VEEAM by Kenny Buntinx [MVP]

At one of my customers we had an issue with discovering VM guests thru there VEEAM nworks management pack and it seems that a lot of people on the forums have the same issue . If you look in the SCOM console you will see the following :


The SCOM Agent version that is running on the VEEAM collector is SCOM 2007 R2 CU4 on x64 win2k8 r2 server.
The script runs perfectly without errors and discovers all our ESX hosts and clusters  , but no VM Guests or Datastores . In any case – the event we copied below is VEEAMS nworks ‘first stage’ discovery (Discovery = ALL). It only inserts the basic topology – Clusters, Hosts (no sub-components of host).


You should see on the next cycle see this event (id 1010 in Operations Manager log), one event for each Host .That will insert host sub-components like CPU cores, VMHBAs, VMNICs etc.


Then on the next cycle, you should see this -  the “SV102” event, logged in Operations Manager as event 1011 –


Note that the above event could have multiple events for each Host, depending on how many VMs there are. Vms are processed in groups of 5 by default.

At first we thought we needed to enable this discovery in the VEEAM mgmt pack. We have looked in the Operational guide and there are 3 discovery scripts with VEAAM :

  • SV100
  • SV101
  • SV102

All objects (ESX hosts, VMs, nworks Enterprise Manager servers, etc.) are discovered automatically by default. However, your monitoring requirements may need certain objects to be included or excluded from monitoring. For example, to discover and monitor ESX hosts. but not the virtual machines , you should disable (with an override) the ‘SV102 third stage discovery’ rule (for VMs). This rule can be enabled/disabled on a per-Host basis.

We explicitly enabled the Guest discovery in the SV102 discovery , however we didn’t manage to see any VM’s in SCOM . After a lot of searching , we finally found the solution . This is not documented clearly in the VEAAM documentation.

Open your Vsphere console and define your rights but :

Make sure this account has at least Read-Only privileges on the vCenter level, not only the cluster level as shown below in the screenshot . It seems that the VMware API reports all his VM guest info to the vCenter level and not to the cluster level .

image  image


Hope it Helps ,


Kenny Buntinx