Archive | SCOM

Monitor a process in Operations Manager 2007 using a script

Create a “Timed Script 2 State Monitor”.

Set your target as “Windows Server 2003”. Set the Monitor to disabled.

Use this script below (Set the processname = to the process you want to monitor)

————————————————-

On Error Resume Next

Dim oAPI, oBag
Set oAPI = CreateObject(“MOM.ScriptAPI”)Set oBag = oAPI.CreateTypedPropertyBag(StateDataType)

strComputer = “.”processname = “AeXNSAgent.exe” ‘Process name here

Set objWMIService = GetObject(“winmgmts:” _ & “{impersonationLevel=impersonate}!\\” &
strComputer & “\root\cimv2”)

strQuery = “Select * from Win32_Process Where Name = ‘” & ProcessName & “‘”Set colProcesses = objWMIService.ExecQuery (strQuery)

If colProcesses.Count = 0 Then

Call oBag.AddValue(“State”,”BAD”)Else Call oBag.AddValue(“State”,”GOOD”)

End If

Call oAPI.Return(oBag)

Continue Reading

Operations Manager 2007 SP1 RC1

Operations Manager 2007 SP1 RC1 is set to be released on Monday or Tuesday next week.

This RC1 will be fully supported by Microsoft Professional Support Services and should be used in production

Continue Reading

Watchanator 2.0 Heartbeat Alert Tool

The Watchanator is a tool that was developed to populate your dynamic computer groups in System Center Operations Manager 2007 with the associated Health Service (Agent) watchers.

The reason you would want to populate your groups with the Health Service (Agent) watchers is to receive heartbeat (up/down) alerts for your servers.

Setup of the Watchanator.

  • Import the All Watcher Management Pack “All Watchers.mp” .

 

  • Any groups that you want the Watchanator to populate. Rename them to start with and underscore. For example if I wanted the Watchanator to populate the “Tim Servers” group I would rename the group to be called “_Tim Servers” (The Watchanator will only populate servers that start with an underscore)

 

  • Explicitly include one Health Service (Agent) watcher in the group. To do this Open the group you want to populate and choose the tab Explicit Members. Click Add/Remove Objects. Leave the Search for on Entity. In Filter by part of name: type the server name of one of the servers in your dynamic group. Click on the watcher for that server and click add. The watcher is the one that looks like eyeglasses.

     

  • Run the Watchanator. The Watchanator will now populate all groups that start with and underscore; with the health watchers for that particular group. *The Watchanator must be run on the RMS Server.
  • Run the Watchanator on a scheduled task on the RMS server daily. Now any changes that happen to groups that start with and underscore; watchers for those groups will be automatically updated.

Watchenator Download Link https://www.scom2k7.com/downloads/Watchanator2.zip

Continue Reading

System Center Operations Manger 2007 Heartbeats Explained

There is a lot confusion on how SCOM heartbeats work so I am going to try to explain. First In SCOM there are really only two important pieces or entities.

This first is the Windows Server entity which encompasses everything about a server except heartbeat.

The windows server entity looks like this


The second important entity is the Heartbeat.

The heartbeat or agent watcher entity looks like this.


So when you are creating a group of servers that you want to monitor you would search for Entity and then you would include both Windows Server and the Heartbeat entity (AKA Agent Watcher).


Click Add to add the Windows Server and the Agent Watcher to the group

Now when you create a subscription to this group you will get alerts for everything related to the server and the hearbeats.

Continue Reading

Microsoft Windows Server 2000/2003 Operating System Updated Management Pack

Microsoft Windows Server 2000/2003 Operating System Updated Management Pack

QFE Fixes:

1. Network Adapter Connection Health Monitor is now functional for long descriptions, multiple network adapters with the same description, and enhanced monitoring of network adapters

2. Localization Issues of script of executable failing to run on agent machines in Hungarian and French local versions are fixed

Version: 6.0.5000.25

Continue Reading

Microsoft Enterprise Management Gateway Approval Tool Hangs

I ran into a problem on my production server SCOM RMS server where when I ran the
Microsoft.EnterpriseManagement.GatewayApproval.exe tool all it did was hang. No error message onscreen or in the event logs.

After troubleshooting for many hours and using process explorer I found out the problem was the account I was using didn’t have permissions to the SQL database. It didn’t say anywhere in documentation that it need SQL access but it does. After granting SQL DBO access to the account I was using it ran fine.

Continue Reading

Discovery of Cluster Servers in Operations Manger 2007

The process to discover cluster servers in 2007 is similar to MOM 2007 but is not as intuitive.

– Go to the Administrator Console

– Expand Device Management and Select Agent Managed.

– Look For your servers that are running in a cluster and select one of them.

– Right click and go to properties.

– Click on the Security tab

– Check the box that says Allow this agent to act as a proxy and discover managed objects on other computers.

null

– Repeat this process on all of your cluster servers.

– Wait about 30 min and go back into the discovery view and your clustered servers should show up.

Continue Reading

System Center Operations Manager 2007 Management Pack Update

The Microsoft System Center Operations Manager Management Pack update is an update to the previously released System Center Operations Manager 2007 Management Pack with System Center Operations Manager 2007 RTM. The updated file list includes

• Microsoft.SystemCenter.2007.mp (6.0.5000.28)

• Microsoft.SystemCenter.Internal.mp (6.0.5000.28)

• Microsoft.SystemCenter.Library.mp (6.0.5000.28)

• Microsoft.SystemCenter.OperationsManager.200.mp (6.0.5000.28)

• Microsoft.SystemCenter.ServiceDesigner.Library.mp (6.0.5000.28)

• Microsoft.SystemCenter.WebApplication.Library.mp (6.0.5000.28)

• System.Health.Library.mp (6.0.5000.28) Update to address fixes and enhancements:

• OnDemandDetection for threshold monitors.

• Ability to override Priority / Severity settings.

• Alert rules/monitors added for Batch response.

• Added Knowledge for rules and monitors.

• Fixed Distributed Application health rollup state.

• Top customer impacting bugs found post-RTM Release History:4/2007- 6.0.5000.1 (Original RTM of Operations Manager 2007) 8/22/2007 – 6.0.5000.28

http://www.microsoft.com/downloads/details.aspx?FamilyID=0d7fc438-4eb9-496e-a664-54d43a577576&DisplayLang=en

Continue Reading

Offline Maintenance Mode powershell scripts for Operations Manager 2007

These powershell scripts will put your server or group of servers in Full Maintenance Mode or (Offline Maintenance Mode).

They will put the Server, the Health Service on that server and the Health Service Watcher into maintenance mode. (Essentially all objects related to a server)

Usage for Groups (All one Line)

GroupMaintenanceMode.ps1rootMS: ‘omrms1.contoso.com’ -groupName: ‘_AU 3AM Sunday Reboot’ –numberOfHoursInMaintenanceMode:4 -comment:’_AU 3AM Sunday Reboot MaintenanceMode

Usage for Individual Servers (All one Line)

AgentMaintenanceMode.ps1 –rootMS: ‘omrms1.contoso.com’ -computerPrincipalName: ‘ql1tmactest1.mi.corp.rockfin.com’ -numberOfHoursInMaintenanceMode:4 -comment:’ql1tmactest1.mi.corp.rockfin.com MaintenanceMode’

http://timothymcfadden.googlepages.com/FullMaintenanceMode.zip

These scripts are just modified versions of the great powershell scripts created by Boris yanushpolsky.

Continue Reading

How to Create a basic Probe-Based SNMP ESX Console CPU Monitor in Operations Manager 2007

1.) In the Authoring pane, expand Authoring, expand Management Pack Objects, and then click Monitors.

2.) Click the change scope. In the Scope MP Objects by target(s) dialog box, click View all Targets, in the Look for text box, type SNMP Network Device, select the SNMP Network Device target check box, and then click OK.
3.) In the Monitors pane, expand SNMP Network Device, expand Entity Health, right-click Availability, point to Create a monitor, and then click Unit Monitor.
4.) In the Create Monitor Wizard, on the Select a Monitor Type page, expand SNMP, expand Probe Based Detection, expand Simple Event Detection, click Event Monitor – Single Event and Single Event, and then click choose a management pack or create a new one and click Next.
5.) On the Name dialog box I called it ESX Server CPU Health.
6.) On the First SNMP Probe for Object Identifier Properties we are going to use (1 minute Load) “.1.3.6.1.4.1.2021.10.1.3.1” then select next. (You can also find additional common Linux OIDS at http://www.debianhelp.co.uk/linuxoids.htm)
7.) On the Build First Expression for Parameter Name use “/DataItem/SnmpVarBinds/SnmpVarBind[1]/Value” for Operator use “Greater than” and then choose a CPU value that you want to alert on. I choose “1” for demonstration purposes.

8.) On the Second SNMP Probe for Object Identifier Properties we are going to use the same thing (1 minute Load) “.1.3.6.1.4.1.2021.10.1.3.1” then select next.

9.) On the Build Second Expression for Parameter Name use the same as the first “/DataItem/SnmpVarBinds/SnmpVarBind[1]/Value” for Operator use “Less than or Equal to” and then choose a CPU value that you want to alert on. I choose “1” again for demonstration purposes. Click Next

 

10.) On the Configure Health Page Change the First Event Raised to Critical

 

(So what we are saying in this expression is “If CPU is greater then or equal to 1 set it to a critical State” “If CPU it Less than or equal to 1 set it to a Healthy state”’)

11.) On the Configure Alerts click Generate alerts for the monitor

12.) For testing I downloaded a tool called Manage Engine OpUtils 4 http://manageengine.adventnet.com/products/oputils/index.html I think any SNMP Walker tool will do. What I wanted to do I query the current Value of the CPU (or OID for CPU)

 

As you can it is currently 0.03. So the monitor should be in a healthy state.

13.) Currently there are no active alerts on the console.

 

Now I went to my ESX box and create some activity. A “vm-support” from an ssh session will create enough CPU activity.

14.) A SNMP walk on the object shows the value above 1


15.) There is my alert.


[ad]

Continue Reading