You are browsing the archive for Operations Manager 2007.

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

How to monitor the hardware of an HP server when running VMWARE ESX in SCOM R2

12:25 pm in MOM, Operations Manager 2007, Opsmgr 2007, SCOM 2007, Virtual machine, Vmware by Kenny Buntinx [MVP]

I ran into a situation that a customer did not want to pay for an expensive management pack to monitor their ESX server Hardware . They all ran on HP Proliant hardware. Here is a small tutorial on how to integrate & configuring the Insight Manager Agents for VMware ESX Servers and let them report into System center Operations Manager 2007 R2

  1. Go to the HP website and search for HP Insight Manager Agents for VMware ESX Server 8.2.0
  2. Download the Agents
  3. Open WinSCP and upload the .tar file you just downloaded to a folder
  4. Log into putty with your root account
  5. Issue the following command to unzip the contents: tar -zxvf hpmgmt-8.2.0-vmware.tgz.
  6. Stop the pegasus services : “Service pagasus stop”
  7. Run “ –install”
  8. Reboot
  9. Stop the pegasus services : “Service pagasus stop”
  10. Run “ – install”
  11. Follow the wizard, when asked for the public string enter (if you use this string) public 2 times (it will not be visible), and be sure to have the HP SIM server’s IP or FQDN. Always answer Y when asked to activate the port 2381 (HPMHP) & the Snmpd deamon.
  12. After the config you need to start the pegasus services : “Service pagasus start”
  13. To check if the configuration has succeeded, log in to the HP System Homepage https://<esx server>:2381/. You should see the servername on the right side.Log in with Root
  14. Check your snmpd.conf  at /etc/snmp/snmpd.conf . It should look like this :


# Following entries were added by HP Insight Management Agents

dlmod cmaX /usr/lib/

rwcommunity public

rocommunity public

rwcommunity  public <The FQDN name of your RMS server>

rocommunity public <The FQDN name of your RMS server>

trapcommunity public

trapsink <The FQDN name of your RMS server> public

syscontact root@localhost (edit snmpd.conf)

syslocation DATACENTER

# ———————- END ——————–

# Sample snmpd.conf containing VMware MIB module entries.

# This is a simple snmpd.conf that may help you test SNMP.

# It is not recommended for production use. Consult the

# snmpd.conf(5) man pages to set up a secure installation.

# VMware MIB modules. To enable/disable VMware MIB items

# add/remove the following entries.

dlmod SNMPESX            /usr/lib/vmware/snmp/


You are done on the ESX Level ! Now we move on to the SCOM R2 Level .

It is relatively simple to monitor the hardware status of your ProLiant servers with Operations Manager. HP  has a free management pack (HP ProLiant Management Pack for System Center Operations Manager 2007), that discovers and monitors them. However if your ProLiant servers happen to have a different OS than Windows installed, it will not not work without a hassle.

I was looking for a way to include the hardware status of our HP servers that ran VMware ESX 3.5 update 4  into OpsMgr. HP does provide a specifically adapted Management Agent for ESX (HP Management Agents for VMware ESX Server as described above ). That allows accessing hardware information about the server using SNMP queries.

On Raphael Burri’s blog you will find a custom written MP that will collaborate with the HP Management pack for Windows and let you monitor your HP hardware . Many thanks to him !!!!

  1. Download the custom made management pack from Raphael Burri on
  2. Download the official HP Management pack for HP Proliant Servers
  3. Install the SNMP stack on your RMS server
  4. Import the both Management packs in your RMS
  5. Configure the SNMP stack of the non-windows ProLiants to allow access from the OpsMgr server or gateway that is going to act as SNMP proxy.
  6. Discover the ProLiant servers as SNMP Network Devices
  7. You are done . Create your own views and rules as you want .


Hope it Helps ,

Kenny Buntinx

Sccm, Scom, Remote SQL 2005 & the Windows server 2008 firewall

7:49 pm in ConfigMgr 2007, MOM, Operations Manager 2007, Opsmgr 2007, SCCM 2007, SCOM 2007, SMS, Sms 2003 by Kenny Buntinx [MVP]

Hi All,

Let’s start by saying that this blog post is probably more OpsMgr related, but all topics are valid for a remote SQL Install for Sms, SCCM or any of the other System center products, so I guess it’s still ok to post it here.

Look, I am not all that good with popular quotes, never seem to be able to remember them just right. But this is one of them that I have never had trouble remembering. “It is all fun and games until someone throws a firewall into the mix”.


Not sure who the quote is from, but I am pretty sure he was refering to my lab environment. Yesterday, I redeployed my Opsmgr 2007 environment, to test the installation on windows server 2008. I figured, install a new sql server on 2008 on one machine, then install opsmgr 2007 on another, shouldn’t take more than a single evening. I’ll start rolling out agents and importing management packs the day after. Seemed like a plan at the time.


So I installed, powershell, IIS, the II6 compatability tools in short all the requirements to install SQL 2005 reporting services on a Windows Server 2008 as listed here:

Then I installed SQL 2005, the database engine and a default install of SQL reporting services, followed by applying SP2.

Next, I installed the Scom database, no problem at all, I am on a role here.


Then I started the management server and console install on the remote box. Err.

The root management server complained that it couldn’t find the database. I splapped myself on the forehead, sure you silly you still need to enable The Tcp/ip protocol in the SQL Server configuration. I checked, and found that Tcp/ip was already enabled as a listening protocol.

Hum, strange, opened a dos box, and ran netstat -a -n -p tcp to see whether my sql box was listening on port 1433. Lo and behold, it wasn’t. You see, I know it was something like that. Still took me a while to figure out that my SQL Server, which was running in a specific named instance was listening on dynamic ports. (If anyone knows how that could have happened just let me know).

Now, I wasn’t going to let something silly as that stand between me and my plan, so I configured the SQL tcp/ip protocol for this instance to listen on port 1433, and restarted the SQL Server service as listed here:

I subsequently ran netstat -a -n -p tcp again and tada, the server was listening fine on port 1433.


Back to the original task at hand install the OpsMgr management server. Err.

Database still not found, ok, I am getting fed up with this, I download microsoft’s portqry tool, and verified whether I could access port 1433 from the remote machine. The portqry -n sqlserver01-e 1433 came back with a response of Filtered. Another slap on the forehead, you nitwit, you have the Windows Server 2008 firewall running. So I went to the Sql box, and decided NOT to disable the firewall but to configure it to open port 1433, as described here:

Once done, I ran my portqry again, and it showed up as listening, great, we’re back on track.


I launched the Opsmgr management server installation again, and the darn thing failed on me again.

Luckily for me the log file came around telling me that a custom action in the msi had close the handle to soon, and that it should be configured not to do that. _SetRootHealthService_Wizard unexpectedly closed the hInstall handle was the error message at hand. So after telling the setRootHealthService_Wizard that it wasn’t allowed to close the handle so soon, or that I would put it in the naughty corner, I retried the installation.


Apparently my authority, that still works on my 3-Year old soon, didn’t impress the setroothealthservice_wizard. In a illuminated attempt to still get this to work I went back to the Sql server box and configured the firewall to log dropped packets. Retried the installation again, which obviously failed, and went back to analyze the windows server 2008 firewall log on the sql box. This revealed dropped packets on udp port 1434. Oh, now that’s easy enough to fix, let’s just open that port and we’re set. Erm wait a minute, I thought all sql database engine communication went over tcp port 1433, what’s up with this 1434 udp port all of a sudden.


Great after having this miracle idea of deploying sql on a box with the firewall still running, I’ll have curiousity kick in, this is going to set back my planning on this a couple of hours, or at least that’s what I thought, but Live search and Sql Magazine to the rescue the udp port 1434 reportedly is needed to access a named instance:


Now, that I had settled my curiousity, I was free to open udp port 1434 in the SQL Server firewall, and retry the opsmgr root management server installation, and kadadzing the install completed with success.



“Everyone is an expert at something”
Kim Oppalfens – Sms Expert for lack of any other expertise
Windows Server System MVP – SMS

Unique Opsmgr 2007 training event (Belgium)

11:22 am in events, Operations Manager 2007 by The WMI guy


Technorati Tags: , ,


Since the event was a huge success for all parties involved, (The instructory received an 8.6 out of 9 average score.) And because some people keep bugging me about a new date, we have decided to repeat this event once more. The new date is 08-11/01/2008.

Register quickly as half this class is already filled by people on the waiting list from the previous event.



Hi all,

I am very proud to be able to announce that we will be able to host a Unique Opsmgr 2007 training event in Belgium.

Is the average training not meeting the depth of technical content you need? Would you like the receive your training from someone that received the prestigious MVP Award? Wished you could receive training from someone that co-authored a book on the topic he is teaching? Are you looking for real 300 – 400 level training? Want training from a consultant with plenty of real-life experience? Ever wished you could receive training from the folks that gave those sessions at Teched (Us or Europe)? Here is your chance.

What is being delivered?

The first two days consist of OpsMgr 2007 Installation and Configuration (more info on the actual content of each day can be found on the link at the bottom of this page)

The following two days consist of OpsMgr 2007 Fundamentals(more info on the actual content of each day can be found on the link at the bottom of this page)

Who is delivering this?

This course will be delivered by Rory McCaw, a multi-year Canadian MVP in the Operations Manager category. Rory co-authored “How to cheat at managing Microsoft Operations Manager 2005″ published by Syngress publishing, and runs a popular Operations management blog at

More info on Rory McCaw can be found here:

When will this take place?

This unique 4day training event will take place from Monday the 17th of September till Thursday the 20th of September 2007.

Class will from 9 AM till 5 PM, with a break before and after noon and a warm lunch at 12:00 AM.

Where Does it take place?

This event will take place at the training facilities of the “John Cordier Academy”

John Cordier Academy
Geldenaaksebaan 335
B-3001 Leuven-Heverlee


tel: +32 (0)16 38 28 18
0800 92 818 (only for Belgium)
fax: +32 16 40 02 54

What is it going to cost?

The course will cost 2100 € (Excl tva.) for the 4 day training including a hot lunch.

Where do I Sign up?

More info about the event, and details on how to signup for this event can be found here:


Please be advised that seats are limited and that there are currently no plans for repeating this event!

“Everyone is an expert at something”
Kim Oppalfens – Sms Expert for lack of any other expertise
Windows Server System MVP – SMS