
Â
W part one I described the monitors included in the Management Pack for Configuration Manager, whose behavior is more like rules than typical monitors.
Â
This time I will make a suggestion on how this behavior can be changed and get the effect corresponding to typical monitors. The following plan can be adopted:
Â
- Create a writable Management Pack that includes disabling the monitor from Manual Reset by Override
- Introducing a new monitor in which the reference to Manual Reset is replaced by Timer Reset
- Change the reference to the parent monitor, which is defined in the original MP, - just here add a prefix identifying the Management Pack by alias.
If you look at the configuration of any of the monitors described in the first part, you will notice that they originate from the same MP package named: "Microsoft System Center 2012 Configuration Manager Monitoring":
Â

Â
In order to obtain a viewable XML file, the Management Pack export must be performed. We can obtain this with the command:
Â
PS C:\> Get-SCOMManagementPack -Name Microsoft.SystemCenter2012.ConfigurationManager.Monitoring |Export-SCOMManagementPack -Path C:\Export.
Â
Now having the XML form, you can load the file into a convenient text file editor. Using search, you can find the name (Display Name) shown in the dialog box shown above (Fail to configure proxy setting on WSUS server).
This brings us to the Display String section.
Â

Â
This way you can find out that the real name of the monitor is:
Microsoft.SystemCenter2012.ConfigurationManager.WsusConfigurationManager.FailedToConfigProxy.
Another search eventually finds the right Unit Monitor:
Â

Â
This particular monitor needs to be included in our Management Pack (section ), but some changes will be needed from the original.
The changes are due to the type of monitor used, below is a comparison of the two types:
Â
TypeID="Windows!Microsoft.Windows.SingleEventLogManualReset2StateMonitorType"
Â

Â
TypeID="Windows!Microsoft.Windows.SingleEventLogTimer2StateMonitorType"
Â

Â
As you can see, the introduction of a second monitor type requires not only the renaming of TypeState, but also the introduction of the TimerWaitInSeconds variable. Also, it should be noted that the overriding monitor is specified (unlike in the original) in another Management Pack, here indicated by the alias CM20212Mon (this is, of course, Microsoft.SystemCenter2012.ConfigurationManager.Monitoring).
The contents of the Monitoring section of the sample MP. Changed or introduced additional records are highlighted.
Â



Â
After importing, you get a configuration in which the monitor configured as Manual reset is turned off, and the corresponding Timer Reset monitor runs in its place.
Â


Â
After the configured time has elapsed, the monitor returns to its "basic" state, that is, it is "healed". If the error condition persists and there are produced further events that rearrange the condition - the error condition will appear again. However, if the errors pass, our monitor automatically returns to a healthy state, without waiting for additional work from the operator.
For full effect, similar actions need to be repeated for the remaining 15 monitors of the same type, remembering to also complete the StringResource, the appropriate DisplayString and (possibly) the KnowledgeArticle. These items can be used from the original MP package (Microsoft.SystemCenter2012.ConfigurationManager.Monitoring), perhaps removing mentions of rules in the monitor descriptions.
Â
- Support and development of Microsoft and Nintex based applications
- Application design and development including digital processes
- Invoice management
- Requisition management
- Contract management
- Modern Intranet
ISCG sp. z o.o.
Al. Jerozolimskie 178, 02-486 Warsaw
NIP: 5262798378
KRS: 0000220621
Phone