Markus Bäker » Core

SCOM: Neue Management Packs Ende Oktober 2011

markus — Sun, 30 Oct 2011 16:02:14 +0000

In den letzten 20 Tagen wurde erneut das OS Management Pack aktualisiert.

Neue Management Packs im Zeitraum zwischen 10.10.2011 und 30.10.2011

Diesmal gibt es keine großen Änderungen, sondern nur ein paar kleinere Korrekturen:

Disabled BPA Rules by default.
Added appropriate SQL Stored Procedures credentials
Updated Knowledge of Logical Disks
Updated Overrides for Logical Disks

SCOM: Neue Management Packs Ende September 2011

markus — Sat, 01 Oct 2011 17:05:10 +0000

Juhu! Endlich wieder ein paar neue Management Packs (MP) auf der SCOM 2007 Front!. Nach langem wurde wieder das Core OS MP aktualisiert.

Folgende Änderungen wurden dabei gemacht:

The September 2011 release (version 6.0.6957.0) of the System Center Monitoring Pack for the Windows Server Operating System includes the following changes:

Optimized operating system performance collection rules.
Added two new operating system-specific reports:
- Performance by System
- Performance by Utilization

Added support for the Server Manager Best Practices Analyzer (BPA). The monitoring pack now collects BPA results from monitored servers and returns the BPA state to Operations Manager.
Added support to discover and monitor Cluster Shared Volumes (CSV).
Modified collection rules to include the latest service packs and hotfixes.
Changed the threshold for the “Average Disk Seconds Per Read”, “Average Disk Seconds Per Transfer”, and “Average Disk Seconds Per Write” monitors to 0.04.
Added new monitors for “Disk $ Idle Time” and “Current Disk Queue Length”.
Changed the monitor types for disk performance from Average Samples to Consecutive Samples to reduce noise and improve collected data.
“Logical Disk Availability Monitor” has been renamed to “File System Error or Corruption”.

Auch das SCCM 2007 Management Pack wurde aktualisiert. Wichtige Neuerungen sind:

Added Support for 64-bit Operations Manager 2007 R2 Agent
Added Support for Configuration Manager 2007 Features
Und viele weitere Monitore zur Überwachung von Teilbereichen von SCCM.

Hier die direkten Links:

Neue Management Packs im Zeitraum zwischen 17.09.2011 und 01.10.2011 :

Monitoring Fedora Core 4 with SCOM 2007 R2 – Part 3

markus — Sun, 19 Jun 2011 11:20:58 +0000

In the part 3 of the Fedora Core 4 discovery pack I will explain the creation of the discovery management pack in detail.

Creating the new MP for Discovery:

Open the Authoring Console (please use the newest on. I have used 6.1.7221.49)
File –> New and enter the required values
File –> Management Pack Properties
Select the tab References –> Add Reference
Add Reference to Microsoft.Linux.RHEL.4, change the alias to RHEL4 (it’s shorter and easier to use) and a reference to the Microsoft.Unix.Library with the alias Unix. Your reference tab should look like the picture 1 (the picture has another reference to linux but this will be added automaticly with the discovery)
Switch to Health Model, select Discovery
new Custom Discovery, name Technidata.Fedora.4.Computer.Discovery
- Target: Microsoft.Linux.RedHat.Computer
- Discovered Classes: Add class Microsoft.Linux.RHEL.4.Computer
- Configuration: Browse… and select: Microsoft.Unix.WSMan.TimedEnumerate.Filtered.MatchesRegularExpression.DiscoveryData and add a module id like discovery
- Press Edit and enter the xml from part 2 into the editor: replace the text between Configuration> and with the XML text […]
- Close the editor
- your discovery tab should look like picture 2
Do the same with the second xml from part 2
Your discovery pack is ready to be imported into your test SCOM environment.

Picture 1: Reference Tab

Picture 2: Discovery

SCOM: Neue Management Packs Mai 2011

markus — Sun, 05 Jun 2011 10:41:38 +0000

Neue Management Packs im Zeitraum zwischen 01.05.2011 und 31.05.2011

Aktualisiert wurde das SQL Server Management Pack mit:

SQL Server Management Pack version 6.1.400.00 includes the following changes:

Documented association of Run As profiles and targets for account mapping.
Made minor fixes in string resources.
Made security improvements.

Hier die direkten Downloadlinks: (Die Word-Dokumente mit den Beschreibungen sind ganz am Ende der Liste)

Monitoring Fedora Core 4 with SCOM 2007 R2 – Part 2

markus — Fri, 03 Jun 2011 09:00:42 +0000

The creation of the troja management pack is easy. You only have to add to discovery tasks which create the RHEL4 computer object and the operating system object and fills them with some basic informations.

In the authoring console you have the add a reference to the Microsoft.Linux.RHEL.4 MP because we will use the RHEL4 Computer object.

This is the XML code of the first discovery task:

Discovery

$Target/Property[Type="Unix!Microsoft.Unix.Computer"]/NetworkName$
http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_OperatingSystem?__cimnamespace=root/scx

false
300

//*[local-name()="Caption"]
.*Fedora Core release 4.*
$MPElement[Name="RHEL4!Microsoft.Linux.RHEL.4.Computer"]$

$MPElement[Name="Unix!Microsoft.Unix.Computer"]/PrincipalName$
$Target/Property[Type="Unix!Microsoft.Unix.Computer"]/PrincipalName$

$MPElement[Name="Unix!Microsoft.Unix.Computer"]/TimeZoneOffset$
$Data///*[local-name()="CurrentTimeZone"]$

As you can see it is mainly copied from the RHEL4 MP. Only the filer value has changed.
The second discovery does more or less the same but creates an OS object:

Discovery

$Target/Property[Type="Unix!Microsoft.Unix.Computer"]/NetworkName$
http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_OperatingSystem?__cimnamespace=root/scx

false
300

//*[local-name()="Caption"]
.*Fedora Core release 4.*
$MPElement[Name="RHEL4!Microsoft.Linux.RHEL.4.OperatingSystem"]$

$MPElement[Name="Unix!Microsoft.Unix.Computer"]/PrincipalName$
$Target/Property[Type="Unix!Microsoft.Unix.Computer"]/PrincipalName$

$MPElement[Name="Unix!Microsoft.Unix.OperatingSystem"]/OSVersion$
$Data///*[local-name()="Version"]$

$MPElement[Name="Unix!Microsoft.Unix.OperatingSystem"]/OSVersionDisplayName$
$Data///*[local-name()="Caption"]$

$MPElement[Name="System!System.Entity"]/DisplayName$
$Data///*[local-name()="Caption"]$

If you save and imports this management pack into SCOM the Fedora system will be discovered as a RHEL4 system and the normal RHEL4 MP will do the monitoring for you.

Monitoring Fedora Core 4 with SCOM 2007 R2 – Part 1

markus — Thu, 02 Jun 2011 16:58:28 +0000

Fedora bases upon Red Hat Enterprise linux which is supported by SCOM. Fedora Core 3 was the base of RHEL 4 and Fedora Core 6 RHEL 5. In this blog posts I will try to convince SCOM that the Fedora 4 based Asterisk telecom system is a RHEL 4.

First we have to install the RHEL4 scom agent manual onto the systems. In this case we had to install the OpenSSL library, too. Additional we add the scom user account to the system.

After that we sign the local created certificate by the scom server and replace it on the Fedora system.

Now we can test the connection from the SCOM server with this winrm command:

winrm enumerate http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_OperatingSystem?__cimnamespace=root/scx -username:scomuser -password:yourpassword -r:https://your.fedora.system:1270/wsman -auth:basic -encoding:UTF-8

The output shows detail information about the OS:

SCX_OperatingSystem

CSCreationClassName = SCX_ComputerSystem

CSName = your.fedora.system

Caption = Fedora Core release 4 (Stentz)

CreationClassName = SCX_OperatingSystem

CurrentTimeZone = 120

Description = Fedora Core release 4 (Stentz)

Distributed = null

ElementName = null

EnabledDefault = 2

EnabledState = 5

FreePhysicalMemory = 1399808

FreeSpaceInPagingFiles = 2039808

FreeVirtualMemory = 3439616

HealthState = null

InstallDate = null

MaxNumberOfProcesses = 32216

MaxProcessMemorySize = 0

MaxProcessesPerUser = 999

Name = Red Hat Distribution

[…]

Interesting for the monitoring are three settings: the caption, the description and the name.

If you want to know how the Red Hat Management pack discovers his systems you have to look into the signed management pack (MP). The authoring console only shows some information of a signed MP. If you want so see all information or want to copy some discovery routines you have to unsign it.

This is a very simple task with the SCOM powershell:

get-managementpack -Name “Microsoft.Linux.RedHat.Library” | export-managementpack -path “c:\export”

This one-liner retrieves the Microsoft.Linux.RedHat.Library MP and saves it unsigned to c:\export. You have to do it with the Microsoft.Linux.RedHat.Library and the Microsoft.Linux.RHEL.4 management pack.

If you look into the discovery routines with the authoring console you see that the discovery takes place in three steps. The Red Hat Library discovers all Red Hat systems by the operating system name. In this case the name of the Fedora OS is equal to the search name of the Red hat library: “Red Hat Distribution”. For the discovered systems an object of the type “Microsoft.Linux.RedHat.Computer” is created.

The Microsoft.Linux.RHEL.4 MP checks all this objects for a RHEL 4 distinguished caption value to create a “Microsoft.Linux.RHEL.4.Computer” object. So if you want to convince SCOM that a Fedora 4 is a RHEL 4 you have to create a MP that creates a RHEL4 object based on the Fedora Stentz caption.

SCOM: Diverse Management Packs

markus — Mon, 10 Jan 2011 13:32:53 +0000

Im Rahmen meiner beruflichen Tätigkeit sind diverse Management Packs für den Operations Manager (SCOM) angefallen.

Diese stehen jetzt kostenlos zum Download bereit: http://www.its-technidata.de/de/im_focus/microsoftsystemcenter/Seiten/KostenloserDownloadSCOM.aspx

Darunter sind (einfache) MPs für:

BlackBerry Email Router Monitoring
Microsoft CRM Email Router
Datacore Storage Server
FileZilla FTP Server Monitoring
Kiwi Syslog Server Monitoring
SAP MaxDB Monitoring
Oracle Database Server Monitoring
Basic SAP Monitoring auf Windows Servern
WAMP Monitoring

Fragen und Anregungen dürfen auch gerne an diesen Post als Diskussion angehängt werden!

Flash: Wie installiere ich einen Windows 2008 R2 Core Domänen Controller

markus — Sat, 13 Mar 2010 18:41:24 +0000

Ich habe mal mit Wink die Installation eines W2k8 R2 DCs aufgezeichnet. Das Vorgehen ist denkbar einfach:

W2k8 R2 Core installieren (von DVD booten)
Mittels sconfig.cmd den Rechner umbenennen
Eine unattend.ini erstellen. Details dazu unter http://support.microsoft.com/kb/947034 (Ergänzung Forest/Domainlevel 4 ist Windows 2008 R2)
In der unattend.ini muss das recovery Passwort hinterlegt werden (im Flash mittels * dargestellt, muss aber eine höhere Komplexität haben)
dcpromo /unattend:unattend.ini aufrufen
Neustarten

Und das alles in einem kurzen Film:
[video filename=/wp-content/uploads/2010/03/Core-DC-Install.swf height=800 width=600 /]
Lessons learned: Immer die Auflösung runterdrehen

Updateinstallation auf Windows 2008 Core

markus — Mon, 01 Feb 2010 19:30:35 +0000

Wenn in einer Organisation auf die Server nicht automatisch die Updates zu den Wartungsterminen installiert werden, sondern nur angeboten werden, dann ist dies auf Windows 2008 Core Systemen schwierig, da es keine Benachrichtigung in der (nicht existenten) Taskliste gibt.

Um dies zu lösen stellt Microsoft unter http://msdn.microsoft.com/en-us/library/aa387102%28VS.85%29.aspx ein Beispielskript bereits, dass sofort nach neuen Updates sucht und anbietet diese zu installieren:

cscript wsusinstall.vbs
Microsoft (R) Windows Script Host, Version 5.7
Copyright (C) Microsoft Corporation 1996-2001. Alle Rechte vorbehalten.

Searching for updates...

List of applicable items on the machine:
1> Update für Windows Server 2008 x64 Edition (KB968389)
2> Sicherheitsupdate für Windows Server 2008 x64 Edition (KB967723)
3> Sicherheitsupdate für Jscript 5.7 für Windows Server 2008 x64
Edition (KB971961)

Creating collection of updates to download:
1> adding: Update für Windows Server 2008 x64 Edition (KB968389)
2> adding: Sicherheitsupdate für Windows Server 2008 x64 Edition (KB967723)
3> adding: Sicherheitsupdate für Jscript 5.7 für Windows Server 2008 x64 Edition (KB971961)

Downloading updates...

List of downloaded updates:
1> Update für Windows Server 2008 x64 Edition (KB968389)
2> Sicherheitsupdate für Windows Server 2008 x64 Edition (KB967723)
3> Sicherheitsupdate für Jscript 5.7 für Windows Server 2008 x64 Edition (KB971961)

Creating collection of downloaded updates to install:
1> adding:  Update für Windows Server 2008 x64 Edition (KB968389)
2> adding:  Sicherheitsupdate für Windows Server 2008 x64 Edition (KB967723)
3> adding:  Sicherheitsupdate für Jscript 5.7 für Windows Server 2008 x64 Edition (KB971961)

Would you like to install updates now? (Y/N)
y

Installing updates...
Installation Result: 2
Reboot Required: True

Listing of updates installed and individual installation results:
1> Update für Windows Server 2008 x64 Edition (KB968389): 2
2> Sicherheitsupdate für Windows Server 2008 x64 Edition (KB967723): 2
3> Sicherheitsupdate für Jscript 5.7 für Windows Server 2008 x64 Edition (KB971961): 2

Das Script ist auch auf “normalen” GUI Systemen interessant, da es sicherstellt, dass sofort nach neuen Updates vom WSUS Server gesucht wird.

CCC – Core Configurator

markus — Thu, 13 Aug 2009 17:49:38 +0000

Da die GUI Core Configurator für kommerzielle Systeme nicht mehr kostenfrei ist, ist die Batch Datei CCC (http://www.nullsession.com/2009/06/18/release-of-ccc-0-98/) eine gute Alternative. Sie ist ähnlich wie die in Hyper-V Server 2008 R2 enthaltene Batch/VBS Datei sconfig – funktioniert aber bereits auf dem 2008 Server und hat teilweise mehr Funktionen!

Anschauen lohnt sich somit! (Trotzdem sollte man die zu Grunde liegenden Befehle kennen)