Home » Articles posted by Anders Bengtsson (Page 45)
Author Archives: Anders Bengtsson
MOM 2005 User Interfaces in Vista
If you want to run MOM 2005 user interfaces in Vista you will have to first install .NET Framework 1.1. If you then want to run Vista interfaces with another domain account you can create a new shortcut and use the runas.exe command. For example
runas.exe /user:DOMAIN\LOGONÂ “C:\Program Files\Microsoft Operations Manager 2005\mom.ui.opsconsoleexe.exe”
System Center Essentials RC1
System Center Essentials RC1 are now available on the Microsoft Connect site.
What’s New in Essentials RC1?
Capabilities:Support for upgrading from WSUS 2.0 and 3.0 Emailed Daily Health Report Automatic scheduled discovery of computers from Active Directory Enhanced network monitoring of SNMP-enabled network devices including a network topology diagram view Remote Control support for remote control of managed client and server computers Ability to import Update catalogs from third-party software publishers SQL Services based reporting on monitoring, hardware and software inventory Setup experience improvements for SQL Server selection and file locations More management packs including support for Exchange 2003, Dynamics CRM 3.0, and Active Directory
Enhanced Platform support
non-English US locales
installing Essentials on x64 servers
managing Windows Vista
managing x64 systems
Support for managing systems in multiple domains in a single forest
Updated Management Packs
There is a new version of the Client OS Management Pack and the addition of the Information Worker Management Packs available at the MS Connect website.
The Client Operating System and Information Worker Management Packs enable System Center Operations Manager 2007 to monitor the health, reliability, and performance of Windows Client Desktops and Information Worker Applications.
Client OS Supported
- Windows 2000 PRO
- Windows XP
 Vista support will be available later
The Microsoft Information Worker Management Pack monitors the reliability and performance of Windows and Office Information Worker applications. By detecting, alerting, and reporting on critical reliability related events and performance indicators, this Management Pack helps identify top issues that are affecting for Windows and Office Information Worker applications and end users.
The Microsoft Windows Client Operating System Management Packs monitor the availability and performance of Windows Client operating systems (2000 Professional and XP). By detecting, alerting, and responding to critical events and performance indicators, this Management Pack helps identify, correct, and prevent possible Windows Client related outages.
Â
Â
Check regkey and service startup mode
Last week me and some friends found a strange mismatch with a server that has remote desktop enable and the terminal service application computer group. I have done a script that will check a regkey (not the one in this example) and a service startup type. If the startup type is not auto, the script will change it and generate a information event in the local event viewer. It is a little bit strange script, but I am sure someone more that us can use it 🙂
The event that is generated in the local event viewer has event id 0 and the type is information
Unfortunately my WordPress theme dont really like long lines in scripts, so I have uploaded it as a file instead. You can download it here
Is your MOM to sensitive?
Is your MOM to sensitive and sending you alerts in early stage? As you presumably know you can change thresholds and modify all rules to suite your environment better. I will show one way to do that in this post. In this example I will collect event ID 2 from the Application log and when there has been two alerts with event ID 2 within one minute I will generate an alert.
Start by create one rule to consolidate similar events with the following settings
- Data Provider – Provider Name: Application
- Data Provider – Provider type: Windows NT Event Log
- Criteria – with event id 2
- Schedule – Always process data
- Consolidate – Choose Event number, Source Name, and input set that events must occur within 60 seconds
- Knowledge Base: Input a suitable text
- General: Input a suitable name and verify that the rule is enabled
- Data Provider – Provider Name: Application
- Data Provider – Provider type: Windows NT Event Log
- Criteria – event ID 2 and repeat count is at least 2 (Advanced criteria)
- Schedule – Always process data
- Alert – Check the box to generate alert
- Alert Suppression – leave default settings
- Responses – add suitable if needed
- Knowledge Base: Input a suitable text
- General: Input a suitable name and verify that the rule is enabled
That’s it. After two events with event ID 2 and the same source name you will get an alert.
Detailed Notification without notification workflow.
Your IT department presumably includes a number of team and roles. None of them want to get alert notification about machines or services that they do not administrate. If you want to setup a more detailed notification within your MOM environment I would recommend you to use MOM notification workflow. There is only one thing, MOM notification workflow does not work on SQL 2005. If your OnePoint database is running on a SQL 2005 machine you can´t use MOM notification workflow.
But :)Â There is another way to setup detailed notification. It takes a little more planning but it will work.
- Create a new rule group, name it something suitable like “Notification – All Critical Alerts”
- Associate it with a computer group, for example “Microsoft Windows 2003 Servers”
- Create a new alert rule in your new rule group
Alert Criteria: of severity = Critical
Responses: Send a notification to a notification group - Commit Configuration Changes
So what have we done? We have a rule that will send a notification on any alert that have severity critical. This rule is associated with a computer group including all Windows 2003 servers, so it will only be alerts with severity critical from a machine running Windows 2003 server. How can we include management packs then?
- open properties for your new alert rule and click the alert criteria tab
- check the “only match alerts generated by rules in the following group:” and click “Browse”
- choose a management pack, for example Active Directory, click ok and then ok to close the properties window
What have we now done? We have added one more criterias to our alert rule, now a alert must be critical and come from a Windows 2003 server and be generated from the Active Directory management pack.
- We control “which computers” with the associated computer group at the rule group level.
- We control “which management pack” with the “only match alerts generated by rules in the following group:” criteria
You can also add advanced criteria for example severity is at least warning.
You can find more information about Notification Workflow Solution Accelerator here. If you decide to use NTWF Pete Zerger has done a great step by step guide that you can find here.
Â
Â
Â
Links during january
MOM 2005 request sequences are not imported successfully when you follow the steps in the “Microsoft Operations Manager Web Sites and Services Management Pack Guide”
System Center Operations Manager 2007 Webcasts on TechNet
 Microsoft IT Showcase: Manageability Services at Microsoft
- Overview of how the Microsoft Manageability Services group operates and changes the global Microsoft Information Technology environment utilizing the Microsoft Operations Framework with Systems Management Server and Microsoft Operations Manager. Download here
Availability of the Microsoft Operations Manager 2005 SP1 Agent Prerequisite Component for Windows XP Embedded software package
Reasons why you should use the Simple recovery model for the MOM 2005 OnePoint and SystemCenterReporting databases
Â
Â
Notification Setup Guide for Operations Manager 2007
Pete Zerger (MOM MVP) and I collaborated on a OpsMgr 2007 Notification How-to Guide.
One of the many enhancements in Operations Manager (SCOM) 2007 is the new notification framework. The new platform offers more flexibility in configuration of notification subscriptions out of the box than was available in the previous version of Operations Manager, as well as several new features. The addition of alert escalation and notification, via Instant Messenger (MS LCS 2005) are just a couple of exciting new offerings in SCOM 2007 notification services. This guide will step through the configuration steps and options for setting up SMTP and IM notification in SCOM 2007.
Read the Guide here.
Active Directory MP update for Operations Manager RC2
A new version of the Active Directory management pack is available for download at Microsoft Connect webpage. This updated version of the AD MP addresses several issues in the original AD MP that shipped with RC2. Specifically it fixes:
-
AD Topology Discovery
-
Discovery of DCs with non-US locales
-
Discovery of Windows Server 2000 DCs
-
Fixed problem: Defect: AD MP for Windows Server 2000/2003 – local discovery of the Domain Controller fails if targeted DC is using a non-US date/time/number formatÂ
-
Fixed problem: Defect: AD MP for Windows Server 2000 (all locales – under certain conditions) Â
Check two or more performance counters
I have done a script that will check two performance counters and generate an alert if both are over threshold values. It simple to add more performance counters and change the threshold values. I have test it on Windows Server 2003 and Window XP 32bit. Its fairly basic, but it will show you a way to generate an alert based on two or more performance counters.
strComputer = “.”
Set objWMIService = GetObject(“winmgmts:” _
& “{impersonationLevel=impersonate}!\\” & strComputer & “\root\cimv2”)
set objRefresher = CreateObject(“WbemScripting.SWbemRefresher”)
Set colItems = objRefresher.AddEnum _
(objWMIService, “Win32_PerfFormattedData_PerfOS_System”).objectSet
objRefresher.Refresh
For i = 1 to 2
For Each objItem in colItemsstrProc = objItem.Processes
strCPUQL = objItem.ProcessorQueueLengthIf strProc > 40 AND strCPUQL > 0 Then
Const EVENT_WARNING = 2
Set objShell = CreateObject(“Wscript.Shell”)
objShell.LogEvent 2, “Number of processer: ” & strProc & “. Processor Queue Lenght: ” & strCPUQL
End If
objRefresher.Refresh
Next
Next
1. Create a new script and paste the script source
2. Create a new event rule to run the script every X minute as respond
3. Create a new event rule to collect event ID 2 and event type of Warning
4. Commit configuration change
Override RunAs Logon Check Failed
Investigate most common alert
Recent Comments