Active Directory MP
A new version (6.0.6452.0) has been released. It now supports
Active Directory 2008.
Download
http://www.microsoft.com/downloads/details.aspx?FamilyId=008F58A6-DC67-4E59-95C6-D7C7C34A1447&displaylang=en
DHCP MP
A new version (6.0.6452.0) has been released. This MP update fixes some high CPU utilization issues
Download
http://www.microsoft.com/downloads/details.aspx?FamilyId=2694E87C-76E0-417B-AD0F-5897E46FFF88&displaylang=en
I must be one of the last SCOM bloggers to post about it but I was kinda lazzy busy lately.
We've heard weeks ago about the rumour that SCOM SP2 will be in fact a R2 and it's now no more a rumour since the annoucement Brad Anderson made at the European TechEd in Barcelona.
The main new features will be:
A beta version should be available very shortly. More info about the R2 here : http://technet.microsoft.com/en-us/opsmgr/dd239186.aspx
As one of my co-worker wrote on his blog, a R2 version means licence upgrade so it migth be painful for customers who didn't subscribe for software assurance...
I recently did some work about modifying Operations Manager roles using the command shell. I started with this post from Eugene Bykov. Many thanks to Marco Shaw for his help and his time.
I worked on the creation of a read-only operator role. That role is scoped on a group and only views in a specific Management Pack are reachable. Note that tests are made with a non-sealed MP.
Create a Read-Only Operator Role:
$RoleName = "My New ROO role"
$mg = (get-item .).ManagementGroup
$profil = $mg.GetMonitoringProfiles() | where {$_.Name -eq "ReadOnlyOperator"}
$role = new-object Microsoft.EnterpriseManagement.Monitoring.Security.MonitoringUserRole
$role.Name = $RoleName
$role.DisplayName = $RoleName
$role.Description = "This is my new readonly operator role"
$role.MonitoringProfile = $profil
$mg.InsertMonitoringUserRole($role)
Scope the role on a group:
$GroupName = "Name of my group"
$ID = get-monitoringobject | where {$_.Displayname -eq $GroupName}
$role = get-userrole | where {$_.DisplayName -eq $RoleName}
($role.Scope).MonitoringObjects.add($ID.id)
$role.Update()
Adding all views contained in a MP to the role:
$MpName = "My MP"
$Mp = get-ManagementPack -Name $MpName
$Mp.getviews() | ForEach-Object {
$pair = new-object "Microsoft.EnterpriseManagement.Common.Pair``2[[System.Guid, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.Boolean, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]" $_.Id,$false
($role.Scope).Monitoringviews.Add($pair)
}
$role.Update()
If you have any question don't hesitate to add a comment.
I post this after one of my customers requirement. He asked me to create a rule that raises an alert if a service in automatic startup mode is stopped.Here is how i did:
-
Enter
root\cimv2 for the WMI Namespace and the following query:
select * from __InstanceOperationEvent within 60 where TargetInstance isa 'Win32_Service' and TargetInstance.StartMode = 'Auto' and TargetInstance.State = 'Stopped'. This query will catch wmi events raised each time a windows service in automatic startup mode enters the stopped state. Enter 60 seconds as the Poll Interval. More info about such WMI queries here
-
To get this value inside our alert description, open the rule we created and open the alert properties. By doing some logic comparison with the built-in parameters available for alert description I established that the following text would return our service's caption: $Data/EventData/DataItem/Collection[@Name="TargetInstance"]/Property[@Name="Caption"]$.
Here is a tip I've been told by Michael Pearson from MS. It allows you to directly start the Web console on a view instead of the Overview page.
-
Open the property of the .url file, modify the URL parameter from javascrpt:onNodeClicked('StateView',%20'e3d720de-f6dd-185c-6fdc-0832377d910a'); to http://WEBCONSOLESERVER:51908/default.aspx?ViewID=e3d720de-f6dd-185c-6fdc-0832377d910a&ViewType=StateView and rename the file
Windows Server Operating System
Download
http://www.microsoft.com/downloads/details.aspx?FamilyId=3529D233-5E3E-4B51-8F66-5D6F27005EC3&displaylang=en
Description
The Windows Server Operating System Management Pack consists of the following five management packs: Microsoft Windows Server Library, Microsoft Windows Server 2008 Discovery, Microsoft Windows Server 2008 Monitoring, Microsoft Windows Server 2003, and Microsoft Windows 2000 Server. The Microsoft Windows Server management packs monitor the performance, health, and availability of Windows Server 2008, Windows Server 2003, and Windows 2000 Server.
By detecting, alerting on, and automatically responding to critical events and performance indicators, management packs reduce resolution times for issues and increase the overall availability and performance of your Windows Server 2008, Windows Server 2003, and Windows 2000 Server operating systems, thereby helping to reduce the total cost of ownership.
Windows Terminal Services
Download
http://www.microsoft.com/downloads/details.aspx?FamilyId=1428ECFD-8C3E-4779-A383-4C491D2684F3&displaylang=en
Description
The Terminal Services Management Pack helps you manage your computers running Terminal Services on Windows Server 2008, Windows Server 2003, or Windows 2000 Server by monitoring the health of the Terminal Services with the help of server role services.
Feature Summary
Terminal servers running Windows 2000 Server use the following role services:
- Terminal Server: With the Terminal Server role service, a server can host Microsoft Windows–based programs or the full Windows desktop. Users can connect to a terminal server to run programs, to save files, and to use network resources on that server.
- TS Licensing: Terminal Services Licensing (TS Licensing) manages the Terminal Services client access licenses (TS CALs) that are required for each device or user to connect to a terminal server. You use TS Licensing to install, issue, and monitor the availability of TS CALs on a Terminal Services license server.
Windows Server 2003 adds the following role service:
- Session Directory: The Terminal Services Session Directory service tracks sessions on terminal servers running Windows Server 2003 and ensures that client computers connect to their existing sessions.
The following additional role services are used in conjunction with Windows Server 2008:
- TS Web Access: With Terminal Services Web Access (TS Web Access), users can access RemoteApp programs and a Remote Desktop connection to the terminal server through a Web site. TS Web Access also includes Remote Desktop Web Connection, with which users can remotely connect to any computer where they have Remote Desktop access.
- TS Gateway: With Terminal Services Gateway (TS Gateway), authorized remote users can connect to resources on an internal corporate network from any Internet-connected device that can run the Remote Desktop Connection (RDC) client.
- TS Session Broker: Terminal Services Session Broker (TS Session Broker) supports session load balancing between terminal servers in a farm and reconnection to an existing session in a load-balanced terminal server farm.
Note:
- In Windows Server 2008, the name of the Terminal Services Session Directory feature was changed to Terminal Services Session Broker (TS Session Broker).
- When there is problem with the availability or performance of one of these components, Microsoft System Center Operations Manager 2007 uses the Terminal Services Management Pack to detect the issue and alert you so that you can diagnose the problem and fix it.
Windows Server 2008 Application Server
Download
http://www.microsoft.com/downloads/details.aspx?FamilyId=77EB6EC5-6932-4310-A426-F9B34C6C5BE9&displaylang=en
Description
The Windows Server 2008 Application Server Management Pack includes monitors, rules, views, tasks, knowledge, and reports for the monitoring of Application Server included in the Windows Server 2008 operating system. It provides a knowledge base of useful information to help administrators resolve an issue when the Application Server role becomes unhealthy.
With this management pack, Information Technology (IT) administrators can collect the events that the components of the Application Server role place in the Windows Server 2008 event logs. This management pack highlights events that might indicate possible service outages or configuration problems so that you can quickly take corrective or preventive actions, simplifying administrative tasks and reducing IT costs.
Feature Bullet Summary:
The Windows Server 2008 Application Server Management Pack manages the logical parts of Application Server that an operator or administrator is interested in monitoring, configuring, or reporting on. The following component events are captured in this management pack:
- Component Object Model (COM)
- Component Object Model extension (COM+)
- Distributed Component Object Model (DCOM)
- Remote Procedure Call (RPC)
- Distributed Transaction Coordinator (DTC)
Windows Key Management Service
Download
http://www.microsoft.com/downloads/details.aspx?FamilyId=A330D876-C965-4433-AFDF-7C61A9126FB3&displaylang=en
Description
The Key Management Service is used to activate computers running Windows Vista and Windows Server 2008. Each activation request is logged on the KMS host. The KMS Management Pack collects data from the event logs of defined KMS hosts, and monitors those hosts for availability. This monitoring provides visibility into the activation traffic and the license status of volume activation clients on the network.
Windows Server 2008 Group Policy
Download
http://www.microsoft.com/downloads/details.aspx?FamilyId=12A29DE3-7147-4488-8B1D-5825892F2B05&displaylang=en
Description
The Windows Server 2008 Group Policy Management Pack includes monitors, rules, views, and knowledge for the monitoring of the application of group policy settings on Windows Server 2008. It provides a knowledge base of useful information to help administrators resolve an issue when group policy fails to process.
The new ISA 2006 Management Pack for SCOM 2007 is now available.
Download
http://www.microsoft.com/downloads/details.aspx?FamilyId=C576FCDF-42F0-4EB5-990D-E8E7C7E9C07E&displaylang=en
Description
This management pack monitors ISA Server 2006 and includes monitors and rules to track the performance, availability, and reliability of ISA Server 2006 components. With detailed alert information, you can quickly identify and troubleshoot ISA Server 2006 issues, minimizing time-to-resolution when problems occur. You can collect and analyze performance trends and metrics, and obtain performance information that allows you to manage bottlenecks, identify capacity requirements, and proactively manage your ISA 2006 deployment to resolve issues before problems occur.
The title says it all. Microsoft released some .ppt about how they implemented SCOM 2007 on their IT.
Download files here : http://www.microsoft.com/downloads/details.aspx?FamilyID=120c0d6f-38bf-482b-bb15-421d66403430&DisplayLang=en
KB949969
Some data partition tables that exceed the data retention period are not groomed from the Audit Collection Services database in Operations Manager 2007.
Lien
http://support.microsoft.com/kb/949969/en-us
Description
Symptoms
Consider the following scenario:
- You use the Audit Collection Services (ACS) feature in Microsoft System Center Operations Manager 2007 to collect security events from managed computers.
- You configure database grooming policies for the ACS database.
However, some data partition tables that exceed the data retention period are not groomed from the database as expected. Over time, the ACS database may run out of disk space.
When this problem occurs, you may discover that these partition tables have a status of 1.
Cause
This problem occurs for one or more of the following reasons:
- When a partition is closing, ACS tries to calculate the last event insertion time for the partition. ACS uses the last event insertion time to determine whether the partition is still within the retention period. However, the calculation operation may time out if the partition is too large. In this situation, ACS saves an invalid time to the last event insertion time field.
- ACS marks the partition status to 1 (This means that the partition status is "in transition") when a partition is closing. ACS sets the partition status to 2 (This means that the partition status is "closed") only after re-indexing is completed. However, the re-indexing operation may time out if the partition is too large. In this situation, the partition remains in the "in transition" status indefinitely.
KB950853
A memory leak occurs when you monitor Exchange Server 2007 by using the MOM 2007 agent in System Center Operations Manager 2007
Lien
http://support.microsoft.com/kb/950853/en-us
Description
Symptoms
Consider the following scenario:
- You import the Microsoft Exchange Server 2007 Management Pack for Operations Manager 2007 into a management group in Microsoft System Center Operations Manager 2007 Service Pack 1 (SP1).
- Then, you install the Operations Manager 2007 agent on an Exchange Server 2007 computer to monitor Exchange rules and processes.
In this scenario, a memory leak occurs on the Exchange Server 2007 computer.
KB951979
Problems occur on a management server that is running System Center Operations Manager 2007 Service Pack 1 when certain management packs are installed
Lien
http://support.microsoft.com/kb/951979/en-us
Description
Symptoms
Consider the following scenario. You are using a management server that has Microsoft System Center Operations Manager 2007 Service Pack 1 (SP1) installed. This management server also has certain management packs installed. In this scenario, the following problems occur.
Problem 1
The management server cannot collect the CSDVersion property from Windows Vista-based client computers. Additionally, the following event is logged in the Application log:
Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 31876
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
Data item returned no information for parameter '$Data/Property[@Name='CSDVersion']$'
This usually indicates that the query is incorrect.
Problem 2
The management server cannot collect operating system properties from Windows 2000 Service Pack 4-based client computers. Additionally, the following event is logged in the Application log:
Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 10409
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
Object enumeration failed Query: 'SELECT Version,Caption,BuildNumber,CSDVersion,ServicePackMajorVersion,ServicePackMinorVersion,SerialNumber,InstallDate,SystemDrive,WindowsDirectory,TotalVisibleMemorySize FROM Win32_OperatingSystem' HRESULT: 0x80041017 Details: Invalid query One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DiscoverWindowsOSProperties Instance name: InstanceName Instance ID: {Instance ID} Management group: GroupName
Problem 3
The HandleCountThreshold agent monitor does not restart the HealthService service on the Microsoft Exchange Server agent even when the HandleCountThreshold value has been exceeded. Additionally, the following event is logged in the Application log:
Event Type: Warning
Event Source: Health Service Script
Event Category: None
Event ID: 6026
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description:
RestartHealthService.js : Restarting Health Service. Monitoring Host exceeded Process\Private Bytes threshold.
Problem 4
Audit Collection Services (ACS) events cannot be collected correctly. Additionally, Operations Manager displays the following error message:
An error occurred while performing a database operation. The error code was {0}
Problem 5
Incorrect warnings are raised for Performance Data Source Module when some services in the system are disabled. Additionally, Operations Manager displays the following error message:
Performance Module could not find a performance counter
Problem 6
Cluster discovery does not work correctly when the Virtual Server Name is a substring of the Physical Server Name.
KB951380
Some computer properties for a cluster node may not be collected by the discovery process in System Center Operations Manager 2007 Service Pack 1
Lien
http://support.microsoft.com/kb/951380/en-us
Description
Symptoms
When you run a discovery operation in Microsoft System Center Operations Manager 2007 Service Pack 1, and a cluster node is discovered, some computer properties may not be collected for the cluster node. For example, the DNS host name, the security identifier (SID) and the Active Directory organizational unit of the cluster node may not be collected. Therefore, some Operations Manager workflows may not function correctly. For example, if the DNS host name is not collected in an Operations Manager 2007 environment that has the Microsoft Exchange Server 2007 Management Pack applied, the following event may be logged:
Event Type: Warning
Event Source: Health Service Modules
Event Category: None
Event ID: 10720
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: The Backwards Compatibility mapper module was not able to start because discovery has not fully completed for this Health Service. This is a transient issue, the affected rule(s) will be unloaded and the Health Service will restart them when initialization is complete.
KB951526
The Root Management Server (RMS) of System Center Operations Manager 2007 Service Pack 1 becomes unstable or unusable if a management pack is imported (DELL MP 3.1 is mentioned in French version of the article...)
Lien
http://support.microsoft.com/kb/951526/en-us
Description
Symptoms
Consider the following scenario
- You import a management pack to monitor certain network devices in a Microsoft System Center Operations Manager 2007 Service Pack 1 environment.
- You perform a network device discovery by using Simple Network Management Protocol (SNMP).
In this scenario, you may receive one or both of the following error messages:
Error message 1
Health service host process has stopped working
Error message 2
Health service Host process encountered a problem and need to close
Chris Scoville de l'équipe produit Operations Manager a mis à jour son gadget Vista de recherche orientée sur les produits de la gamme System Center.
Téléchargement
http://gallery.live.com/LiveItemDetail.aspx?li=49e26ad0-113d-4f3d-a711-57f6530c75d9
Description
This gadget makes it easier to find help for Microsoft System Center products because it uses Live Search macros to search specific sites instead of the entire web. Search results are only returned from sites that are known to contain helpful information about System Center products. Use the settings in the gadget to pick the System Center product that you want to find information about, and then enter a search term in the gadget to get customized search results.
Captures
Le Management Pack CRM 4.0 pour MOM 2005 est disponible.
Téléchargement
http://www.microsoft.com/downloads/details.aspx?FamilyID=2e2b747d-1947-474c-91c6-246348871174&DisplayLang=en
Description
The views, tasks, rules, and knowledge specific to Microsoft Dynamics CRM 4.0 that comprise this Management Pack provide the means for MOM users to centrally manage the server application, its component services, and the computers on which they run. The Microsoft Dynamics CRM 4.0 Management Pack also collects performance analysis and capacity planning data by tracking application performance and user load.
By managing these Microsoft Dynamics CRM components in MOM, the administrator can respond quickly to critical events and key performance indicators, and take action to prevent service outages, reduce the resolution time for alert conditions, and increase the overall availability and performance of the Microsoft Dynamics CRM system.
Feature Bullet Summary:
- Monitors the availability and health of the following component services:
- Microsoft Dynamics CRM Asynchronous Processing service
- World Wide Web Publishing
- Microsoft Dynamics CRM Deletion service
- Microsoft Dynamics CRM databases
- Monitors the availability and health of the following application components and functionality:
- Deletion of deleted records
- Operability of ISV plug-ins
- Web application requests processing, SOAP exceptions, and unexpected failures
- Detects brute-force attacks and denial of service attacks.
- Monitors the performance metrics of the following components:.
- Web application requests processing
- Database query processing
- Monitors the system for configuration-related failures.
Release History
- 6/5/2008 - Initial Release, version 04.0.0000.0000.
Certains d'entre vous arriveront peut-être sur ces pages grâce au message de bienvenue qu'Aurelien BONNIN m'a fait sur son blog http://blogcastrepository.com/blogs/aurelienbn/default.aspx. J'en profites pour faire également l'éloge de son excellent blog très fourni sur les technologies System Center et plus particulièrement sur SMS/SCCM/Poste de travail. Entre amis nous aurions tord de ne pas nous faire une petite promo mutuelle 
. J'avais d'ailleurs discrètement rajouté un lien vers son blog dans ma section News
Merci de ton accueil Aurelien 
Le Management Pack Message Queuing 3.0 pour SCOM 2007 est disponible.
Téléchargement
http://www.microsoft.com/downloads/details.aspx?FamilyId=1D2B4398-8BC2-4A43-850C-852EBB0D983B&displaylang=en&displaylang=en
Description
Message Queuing (also known as MSMQ) is a server application that enables applications to communicate across heterogeneous networks and systems that may be temporarily offline or otherwise inaccessible. Instead of an application communicating with a service on another computer, it sends its information to Message Queuing, which sends the information to a Message Queuing service on the target computer where it is made available to the other application. Message Queuing provides guaranteed delivery, efficient routing, security, and priority based messaging.
Feature Summary
The Message Queuing Management Pack provides monitoring for the following:
- MSMQ Servers
- MSMQ Triggers
- MSMQ Queues
- Dependant Clients
Release History
6/3/2008 - Initial Release, version 6.0.6278.23. Refer to the MP guide for further details.
L'éditeur hollandais Savision a sorti il y a quelques jours la seconde version de son produit LiveMaps pour SCOM 2007.
Cet outil ajoute une dimension géographique à SCOM 2007 en permettant de créer des vues sous formes de cartes sur lesquels sont disposés les serveurs ou tout autres ojbets monitorés. Les cartes, étant liées entre elles, permettent de cibler les problèmes globalement sur un carte mondiale puis de "rentrer dans le détail" et cibler les problèmes dans une salle serveur voire dans une baie.
Comme nouveautés dans la version 2.0 on notera des améliorations dans le rendu et la création des cartes, l'ajout d'alarmes sonores et d'une console web.
Microsoft vient de mettre a disposition sur son site Connect la version Beta de Service Level DashBoard for Operation Manager 2007. Ce produit offrira aux DSI un outil de reporting concernant l'état de santé et la mesure de la conformité des engagements de niveaux de service(SLA) des applications métiers.
Inscription au programme Beta ici: https://connect.microsoft.com/programdetails.aspx?ProgramDetailsID=2198
Description plus détaillée de l'outil:
The Service Level Dashboard for Operations Manager 2007 is designed to work with an existing Operations Manager infrastructure (it is assumed that Operations Manager is already configured to monitor the business-critical applications). Service Level Dashboard for Operations Manager 2007 uses the following components to gather and process additional data (see figure for reference):
The SLA agreement is identified and defined by the IT Manager for a given business-critical application or service. Web application monitors and synthetic transactions. The IT administrator configures and deploys watcher nodes to perform the actions of a synthetic transaction, such as connecting to the Web site or querying the database. A Web application monitor runs on the watcher node and uses these synthetic transactions to perform actions to check availability and to measure performance of a Web page, Web site, or Web application. The IT administrator configures the thresholds for identifying an error or warning state during a synthetic transaction.
An Operations Manager Distributed Application (DA) model is used by the IT administrator uses to define the application or service. Using the DA model, the IT administrator groups Web application monitors and other monitors into applications and regions for the dashboard. One can use the dashboard interface to analyze the SLA compliance data as soon as the Service Level Dashboard for Operations Manager 2007 components are configured and operating.
The Service Level Dashboard for Operations Manager 2007 evaluates each application over the defined reporting period, determines whether the application was in or out of compliance during that period (and for how long). The dashboard then lists the application as compliant or non-compliant, based on defined service level targets.
Le modèle System Center Operations Manager 2007 pour System Center Capacity Planner 2007 est disponible depuis début Mai à l'adresse suivante: http://www.microsoft.com/downloads/details.aspx?FamilyID=6fec1f12-a62c-4e8d-8a19-56879192adc3&displaylang=en
Pour rappel la source de Capacity Planner (qui contient par défaut un modèle pour Exchange 2007) est disponible ici : http://www.microsoft.com/downloads/details.aspx?FamilyId=E754F35D-59DB-4BC4-8386-E83E66A16FAD&displaylang=en