Monthly Archives: February 2015

SCSM: Update Rollup 5 for System Center 2012 R2 Service Manager

Update Rollup 5 for System Center 2012 R2 Service Manager has just been released which means we should be seeing the update for other System Center products in the coming days.

It is available for download here.

Changes in this update:

    1. Change request still stays “in progress” when last activity is skipped and all previous activities are completed.
    2. ActualStartDate and ActualEndDate field values for Change Request and Release Request do not set.
    3. Multiple System Center Service Manager Connectors to System Center Configuration Manager execute and complete successfully. However, the start, finish and status property values are not updated in the Service Manager Console under the “Connectors” view and event 3334 is logged.
    4. Trying to delete a Service Request template that is being used by a Request Offering causes a cryptic and non-user friendly error message.
    5. The “Group By” functionality in a View does not work correctly when “Group By” column has empty fields.
    6. The Console crashes when the user tries to open an already opened attachment from a Work Item form.
    7. Opening the Views for Groups takes a long if there are large number of explicit members in the groups.
    8. The OM CI connector fails if one tries to import a distributed application that contains an instance of the ‘Hyper-V Virtual Network Adapter’ class.
    9. Monitoring Host process crashes if there exists a Notification after the user who created it was deleted or has moved to a hidden organizational unit (OU) in the Active Directory.
    10. An exception is raised if the user tries to open a sorted View which is created by using TypeProjection on custom Class that is neither Abstract and nor a first Concrete class.
    11. An Exception is thrown when a user tries to open the “Service Components” tab on the Service Maps form, when there are large number of services in CMDB.
    12. Enhanced in event logging for DW jobs.
      Logging the batch start and completion events for all DW job categories in event log. The start and completion event will include the following:
      Process Category

      1. Process Name
      2. Batch Id
      3. Batch Start or completion Time
    13. Enhanced in event logging for DW cube processing.
      1. Time taken by Cube’s batch id to complete will be logged in seconds.
      2. Information whether the cube is processed under Analysis Services that are running in SQL Server Standard Edition or the SQL Server Enterprise Edition.
      3. Event logs will be added during processing of each Dimension and Measure Group for each partition (if applicable) for both enterprise and standard SQL editions.
    14. Added a new PowerShell cmdlet Get-SCDWInfraLocations Cmdlet on the Service Manager management server to retrieve the following location information about its data warehouse infrastructure:
      1. Service Manager database
      2. Service Manager data warehouse database
      3. Service Manager Analysis server database
      4. Data Warehouse Reporting Server database and Report Server URL

SCOM: Updated Management Pack for Windows Server Cluster v6.0.7291.0

Late last year an updated version of the Windows Server Cluster MP was released by Microsoft. Version 6.0.7291.0 contains primarily bug fixes and is available for download here.

Changes in this version:

  • Fixed a bug with 6.0.7230.0 that was preventing discovery of 2008/2003 servers.
  • Added an override for 2008 R2 called “Resource Group Type Filter”
  • Fixed a problem that was preventing the import of 2012 R2 language packs

SCOM: Cluster maintenance mode, resource groups and you

One of my colleagues brought an issue to my attention whereby placing a Cluster server into maintenance mode was causing a flood of  “Cluster resource or group offline or partially online” alerts from that clusters resource groups.

It turns out that the default maintenance mode setting for the Resource Group dependency rollup monitor is “Rollup monitor in maintenance mode as error”. This means that any objects rolling up as maintenance mode will cause the resource group monitor to go critical and generate “Cluster resource or group offline or partially online” alerts.

Changing the value to maintenance mode alleviates this issue. I’ve also has success placing the resource groups into maintenance mode before the cluster objects.

clusterb

SCOM Basics: Creating a Service Monitor with Automatic Recovery

I’ve decided to write a series of articles covering some of the tasks that could be helpful to the newer Operations Manager administrators.

This article will cover how to create a custom service monitor and how to implement an automatic service restart action associated with that service. In this example we will use the Print Spooler service.

Creating a custom service monitor:

First go to the authoring node of your console, you will see a section called Management Pack Templates, this is where we will create our custom service monitor.

go to auth A

Right click on Windows Service and select Add Monitoring Wizard.

add monitoring

On the first page of the wizard select windows service and click next.

windows service

Give your monitor a name and select the management pack that will be used to save it, you can also create a new management pack if required without leaving the wizard by clicking the New button to the right of the drop-down. Click next.

monitor name

On this screen we need to provide the name of the service to be monitored. Targeting a group will also limit the service discovery to only the grouped service, this prevents unnecessary load on servers that do not have the service. Tick Monitor only automatic services only if the service has automatic start.

service details blank

Clicking the  “…” button will open the below window allowing you to search for the required service. You can connect to any server using the “…” button next to Computer name.

Select the service and press OK.

select service

Once the service details are populated click next.

service details filled out

If you need to monitor performance of the service such as memory or CPU utilisation you can configure that here. If it’s not required just click next.

perf monitoring

The wizard will now display a final summary for your service monitor. Check everything is correct and click create.

final summary

Creating an automatic start service recovery:

Once your monitor has been created, right click on the service, select View Management Pack Objects and then Monitors.

recovery properties

On the monitors page expend the nodes until you find Service Running State, right click on the one that is listed in the same management pack from earlier and choose properties.

recovery properties 2

In the monitor properties click on the Diagnotic and Recovery tab, click Add under Configure recovery tasks and then select Recovery for critical health state.

add recovery action button

Choose Run Command. Click next.

run command

Give the recovery action a name and tick Recalculate monitor state after recovery finishes. Click Next.

recovery name

In order to start the service we will use the Net Start command, in full path to file enter the complete path c:\windows\System32\net.exe, next fill in the parameters field, begin with Start followed by the name of your service, in this case Start Spooler.

Note: If the service name contains spaces it is important to enclose the service name in quotes. For example “NetBackup Client Service”

recovery net start

Click create and close the monitor properties.

And there you have it, a custom service monitor with an automatic recovery action.

 

 

 

SCOM: Updated Cisco UCS MP v3.1.1

Cisco release a revised version of their UCS management pack late last year version 3.1.1 is available for download here.

New in this version:

  • Supports UCS Mini.
  • PowerShell cmdlets for adding or updating UCS instances in SCOM.
  • PowerShell cmdlets for managing discoveries and monitors.
  • Supports Proxy server.
  • Encrypted proxy password.
  • Support to upgrade existing UCS instances after upgrading the management pack.
  • Increase in the organization hierarchy discovery from root level to level 3.

SCOM: New MP for DPM 2012 R2

A new management pack has been released for Data Protection Manager 2012 R2. It includes Reporting, Discovery and Monitoring and is availible for download here. It is listed as version 4.2.1276.0.

The discovery and library management packs enable you to view, monitor and manage DPM servers, alerts, notifications and some other monitoring information.

The reporting management pack enables and supports collecting reporting data from all DPM servers deployed on your network. For example, if your domain deployment contains 250 DPM servers, each containing 10 data sources configured into a separate Protection Group (PG), this management pack will enable SCOM to monitor and report data on all 100 x 10 = 1000 data sources.

Prerequisites

The following requirements must be met to run the discovery, library and reporting management packs:

  • SC DPM (Data Protection Manager) 2012 R2 Update Rollup 5 (UR5) must be installed, up and running on all the DPM servers. Centralized Reporting from SCOM will not work for DPM servers that have not been upgraded to 2012 R2 UR5.
  • Set SLA Requirements on the DPM Server using the PowerShell command-let :

Set-DPMProtectionGroupSLA.

If SLAs are not set on the DPM Servers, you will not get SLA Trends in the Reports.

  • For enabling De-Duplication space savings data in your reports, import the De-Duplication management pack for File and iSCSI services.

SCOM: Updated Dell MP v6.0

Dell released a new version of their Management Pack for Microsoft System Center Operations Manager mid December 2014. There have unfortunatly been performance issues with some Dell MPs in the past so as always read the guide carefully and test, test, test before live deployment.

It is available for download on the Dell support website here.

Important: Upgrade from Dell Server Management Pack Suite version 5.1 and earlier versions to version 6.0 are not supported.

Changes in this version:

1. Support for 13th Generation of Dell PowerEdge Servers
2. Support for iDRAC8
3. Support for Precision Rack 7910 Workstations
4. Performance Monitoring and Views for CPU, IO, CUPS & Memory (Agent-free)
5. Inventory and health monitoring for License, Host NIC and vFlash (Agent-free)
6. Inventory and health monitoring for PCIe SSD (Agent-free)
7. Detailed sensor monitoring (Agent-based)

XPost: SNMP Trap monitoring with SCOM 2012 R2

Kevin Holman has written an excellent article on the murkey subject of SNMP Trap monitoring with SCOM 2012 R2. This is definitly worth a read if you’ve ever been unclear on how this works.

It’s also nice to know once and for all “First clarification (and update to this blog post) – There is NO NEED to install or configure the SNMP service on the management server.  We don’t use the SNMP stack.  In fact – if the SNMP TRAP service is running (it does not by default) then only thing I need to do is make sure it is disabled! “

He has also kindly included MP authoring examples which you can use to get this running for your own scenarios.

 

Go here to read it.

Management Pack Recap – January 2015 Wave

This is a summary of the wave of Management Packs that were released in January 2015.  Information and download location in the links provided:

Windows Server OS MP update 6.0.7296.0here (Actually a February release)

Windows Server OS MP update 6.0.7294.0 – here – Replaced by 6.0.7296.0

SharePoint 2010 Products MP  version 14.0.7135.5000 – here

Office 365 MP v7.0.5112.0 – here

SCSM MP v7.5.3079.183here