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
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.
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.
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
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.ps1 –rootMS: ‘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.
1.) In the Authoring pane, expand Authoring, expand Management Pack Objects, and then click Monitors.
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]
Are you getting this error on all services you create using the management pack template?
Alert source : Nice CLS TRS The ‘Nice CLS TRS‘ service on computer My is consuming excessive resource
Path : Myserver1.contoso.com
Alert Monitor : Overrall Service Performance Health
Created : 8/13/2007 9:49:44 PM
I was creating overrides for each one until I found a better way.
What you need to do is disable it globally so that all services created with the Management Pack Templates will have it disabled.
All you need to to need to do is go into the Authoring console, Monitors and Target Windows Service. Drill down to Overall Service Performance Health. Create an Override For all Objects of type: Windows Service and set the Enabled to False.
Now all Windows Services objects have it disabled globally… It works because all NT service monitors are inherited from this type.
Resolution States
0 = New
255 = Closed
Severity Values for Alerts
0 = INFORMATIONAL
1 = WARNING
2 = CRITICAL
If you get an alert similar to this.
Alert: Health Service Configuration Not Up To Date
Source: myserver.contoso.com
Path: myserver.contoso.com
Last modified by: System
Last modified time: 8/11/2007 10:30:14 AM Alert description: The Health Service has requested new configuration, but no has not received it for more than 90 minutes.
The problem is that the Windows firewall is running on the server that you installed the agent on and it is not communicating properly to the Management Server.
Resolution is to open up port 5724
Boris Yanushpolsky created this nice utility for Enabling proxying for agents.
When deploying the AD or Exchange management packs you need to enable proxying on agents in order for discovery to work properly. This could be a time consuming process since there is no way to multi select all the required agents and enable proxyings for all of them at once. To help with this issue, I wrote a UI based utility that allows you to select a computer group, browse the members, and multiselect the right computers and enable/disable proxying.
The link to the zip file is at the bottom of this post.
http://blogs.msdn.com/boris_yanushpolsky/attachment/4195114.ashx