Lors d’un precedent article je vous expliquai comment superviser vos NetApp dans System Center Operation Manager 2007 avec les Traps SNMP, maintenant NetApp fournit gratuitement a ces clients, un management pack « ApplianceWatch PRO 2.0 is a free product and does not require a license. » Le management pack est compatible avec SCOM 2007 SP1 et R2. 

Les prè-requis côté des Baies NetApp :  »ApplianceWatch supports the following versions of Data ONTAP »

• 7.2.6 or later in the Data ONTAP 7.2 product family
• 7.3 or later in the Data ONTAP 7.3 product family
• 8.0 (7 mode) in the Data ONTAP 8.0 product family

L’installation d’appliance Watch doit s’effectuer sur le RMS ou un MS SCOM.

Vue Diagram :  

 Rémy

Vous avez peut etre eu la mauvaise supprise de vous retrouver avec tous les packs de langue pour le management AD en important le management pack AD depuis le catalogue en ligne

La ligne de commande ci-dessous vous permet de supprimer tous les packs de langue pour le monitoring AD

get-managementpack|where{$_.name -like « *.AD.*.Monitoring.* »}|uninstall-managementpack

Rémy

L’equipe System Center Operation Manager propose en téléchargement un guide pour nous aider à dimensionner les bases de données Operations Manager.

Le fichier Excel est téléchargeable sur leur site : http://blogs.technet.com/momteam/archive/2009/08/12/operations-manager-2007-r2-sizing-helper.aspx

Rémy

L’une des premières erreurs remontées par SCOM est souvent celle-ci :

Échec du service SDK de System Center Operations Manager lors de l’inscription d’un nom principal de service. Un administrateur de domaine doit ajouter MSOMSdkSvc/SCOMR2 et MSOMSdkSvc/SCOMR2.scala.msft au nom principal de service de SCALA\opsmgrsdk

Il est important de respecter la casse pour que la commande fonctionne dans ce cas :

• Setspn.exe –A MSOMSdkSvc/SCOMR2 SCALA.MSFT\opsmgrsdk
• Setspn.exe –A MSOMSdkSvc/SCOMR2.scala.msft SCALA\opsmgrsdk

Une autre solution est fournit par Kevin Holman’s : http://blogs.technet.com/kevinholman/archive/2007/12/13/system-center-operations-manager-sdk-service-failed-to-register-an-spn.aspx

Rémy

OpsMgr SDK Service

Un nouveau management pack Operation Manager est disponible depuis ce week end, il est téléchargeable depuis le catalogue Operation Manager 2007 ou en cliquant sur le lien ci contre Management Pack Operation Manager R2

Ce nouveau management pack apporte des nouveautés sur : les agents, la distribution des comptes Run As.

Feature Summary
The Operations Manager 2007 R2 Management Packs includes the following features:

• Local and Remote Monitoring of an Agent’s Health
  • Operations Manager agents monitor themselves for events and performance indicators that signal an issue with the agent’s health.
  • Management servers also maintain an external perspective of an agent’s health via the Health Service Watcher.
  • The ‘Agent Health State’ view provides a side-by-side dashboard of both perspectives on the agent.
• Optional, Automatic Agent Remediation Capabilities
  • If the Health Service Watcher determines that an agent is unhealthy, a series of diagnostics and recoveries can be enabled to further diagnose the problem and event take actions to attempt to fix the problem (e.g. Ping the server to see if it is completely offline, start a stopped agent, trigger a reinstall, etc.). Refer to the management pack guide for more details.
  • Agents are monitoring their own process to ensure that memory utilization is not sustained at unacceptable levels. If this condition is detected then the agent will automatically restart itself to force the freeing up of memory.
• Detection of Problems and Misconfigurations with Run As Accounts and Profiles
  • Checks are run on a regular basis to detect if any of the management group’s “Windows” type Run As Accounts have credentials which are about to expire. Alerts will be raised, and where possible this will be done in advance of the credentials expiring to avoid outages.
  • Alerts will be raised if any errors are encountered during the distribution of Run As Accounts.
• Monitoring of problems with Running Workflows in Management Packs
  • Numerous rules are provided to detect if workflows within management packs are failing. Examples of workflows include discoveries, rules, monitors, etc. Failures can range from bad configurations on the workflows themselves, script failures, permissions problems, etc.

Rémy