The Lync Server 2010 MP has been updated to version 7577.723 and is available here.
At the time of this posting the documentation has not been updated with fixes and new features.
The Lync Server 2010 MP has been updated to version 7577.723 and is available here.
At the time of this posting the documentation has not been updated with fixes and new features.
An updated SCCM MP has been released and is available here.
The guide refers to itself as being an RTM release and doesn’t include any change log so testing will be required. There is however an extensive appendix which includes a list of rules/monitors for every SCCM component.
A Community Technical Preview has been released for all of the SQL server versions and components they are available for download here. This MP is accompanied by a refresh of the SQL MPs released earlier this month v6.6.7.6, could this be an attempt to improve QA and testing on management pack releases, especially considering the issues with the SQL MP over the past year.
The new features and fixes introduced in CTP1 management packs are as follows:
New Reporting Services 2016 MP Features and Fixes
New SQL Server 2005-2012 MP Features and Fixes
New SQL Server 2014-2016 MP Features and Fixes
This posting will be part of my SCOM basics series and covers the key concepts of Objects and Classes.
Objects
An object is the basic unit of management in Operations Manager. An object typically represents something in your computing environment, such as a computer, a logical disk, or a database. It could also represent something more abstract, such as an application, an Active Directory domain, or a DNS zone. An object can also be referred to as an instance of a particular Class.
Classes
A class represents a kind of object, and every object in Operations Manager is considered an instance of a particular class. All instances of a class share a common set of properties. Each object has its own values for these properties which are determined when the object is discovered.
Most management packs define a set of classes that describe the different components that make up the application that is being monitored and the relationships between those classes
Targeting
A target in the Operations console represents all instances of a particular class. For example, a viewlists all of the objects that are instances of the class that is used as the target class for the view, and a monitor is applied to all objects that are instances of the monitor’s target class.
Classes have two further categories. Base Classes and Hosted Classes
Base Classes
Every class in Operations Manager has a base class. A class has all the properties of its base class and could add more. All of the classes from the different management packs installed in your management group can be arranged in a tree with each class positioned under its base class.
When you select a class as a target that is a base class for other classes, the monitor or rule applies to all instances of each of those classes. For example, if you use Windows Operating System as the target for a monitor, then the monitor applies to all instances of Windows Client Operating System and Windows Server Operating System. This is because those two classes use Windows Operating System as their base class.
Hosted Classes
Most classes are hosted by another class. When one class hosts another, the hosting class is called the parent, and the class being hosted is called the child. Instances of the child class cannot exist without a parent.
For example, several classes are hosted by Windows Computer because they are components on a computer. It would not make sense to have a logical disk if there was no computer for the disk to be installed on. Therefore, Logical Disk is hosted by Windows Computer. This means that every instance of Logical Disk must have one instance of Windows Computer as its parent.
Note about Groups
I’ve included groups in this posting because it can be a common mistake to try and use a group as a target for a rule / monitor this can cause that rule / monitor to not function correctly as the class for a group only exists on a management server, the group will not be enumerated into it’s members from the target selection.
OpsLogix, a company long involved in developing management packs to improve the functionality of SCOM, have released an update to their VMware management pack. It is already available if you have a valid support contract.
Version 1.3.2.10 contains following changes or additions:
Microsoft has finally officially recommended a workaround that some of us have been using for some time to keep the SQL dashboards in a usable state.
Issue: When used rarely or after a long break, the dashboards may work rather slowly due to large amounts of the collected data to be processed; especially, it is related to large environments (2000+ objects).
Resolution: Below is a “warming up” script, which may be used to create an SQL job to run on some schedule. Before scheduling it as an SQL job, please test how long these queries will be executing (if you will schedule it to run too often or execution time is too long, that may kill the performance). If you have dashboards with thousands of objects to load, then time to load the content will be 10+ seconds anyway. It was tested with 600 000 objects, and the dashboard loading time was 1-2 minutes.
USE [OperationsManagerDW]
EXECUTE [sdk].[Microsoft_SQLServer_Visualization_Library_UpdateLastValues]
EXECUTE [sdk].[Microsoft_SQLServer_Visualization_Library_UpdateHierarchy]
It is also worth noting that the following versions of SQL Server Management Pack are considered as deprecated and suspended:
Several SQL Management packs have been updated, version 6.6.7.6 for each of them can be found at the following locations:
As usual treat new management packs with caution, especially considering the recent issues with SQL and Base OS ones and test, test, test!
SQL Server 2014 Analysis Services – here
SQL Server 2012 Analysis Services – here
SQL Server 2008 Analysis Services – here
SQL Server 2014 Reporting Services (Native Mode) – here
SQL Server 2012 Reporting Services (Native Mode) – here
SQL Server 2008 Reporting Services (Native Mode) – here
Management Pack for SQL Server Dashboards – here
Updated in this version
Dashboards
“Known issues and Troubleshooting” section of the guide is updated
SQL Server Reporting Services
SQL Server Analysis Services
Microsoft has released an updated list of monitoring supported network devices for SCOM 2012.
The full list is available here, below is an extract:
A while ago I had a request from one of my clients to monitor their new Fortigate Firewalls, as there is no existing management pack for this it required a bit of custom work.
First on the firewall you’ll also need to configure SNMP, as well as what trap notifications will be sent.
Then discover the Fortigate using the standard network monitoring discovery.
This is the address for the Fortigate MIB file contents which you will need in order to map OIDs for the next part.
In SCOM create an SNMP Trap alerting Rule targeting the Node Class.
For now leave the OID properties filter empty
This rule will be used to identify any OIDs in the future that may be missing from your specific alerting rules.
Now using the MIB list provided earlier each alert ticked in the Fortigate configuration needs to be mapped to the relevant OID and a specific alerting rule created for it, for example 1.3.6.1.4.1.12356.101.4.4.2.1.2 is the OID for HIgh Processor Usage. So in order to generate an alert for High CPU on the Fortigate you will need a rule with this specific OID in the filter 1.3.6.1.4.1.12356.101.4.4.2.1.2.
Repeat for each OID that you need to monitor and use the catch all to identify anything you may have missed.
A management pack for windows 10 OS has been release, v10.0.0.0 is available here and is supported by System Center Operations Manager 2012 or higher.
Two types of client monitoring are available in this management pack:
· Aggregate client monitoring for gathering health information on the selected representative clients, and aggregating information for reports that display the trends
· Monitoring of mission-critical business clients
It is also important to note that agentless monitoring is not supported