( Custom – Check Existence of RegKey Monitor Type) On the General tab – give the MonitorType a display name. In your custom management pack, using the Authoring Console, create a new Composite MonitorType. We want a monitor for this, and since no existing MonitorType exists – we will need to create one. The purpose is to ensure we don’t have servers that are unset, as they will not get put into the appropriate group and we could miss some critical monitoring. The goal of this monitor will be to ensure this value has been set, between 1 and 4. We use these values to dynamically assign these servers to custom groups in OpsMgr, for the purpose of scoping notifications, paging, and ticketing, as described HERE. Level 1 servers are critical production, level 2 servers are production, level 3 are pilot, and level 4 are development. Within that Key – we have a Reg Value named “ServerLevel” which will be a number, 1 through 4. Scenario: We have a policy that we stamp the registry on all machines with the HKLM\Software\CompanyX key. I recommend starting with the previous post for greater details, as this article will leverage the same process. This post will be an example of how to create a custom MonitorType to do that, very similar to how we did for existence. But what if you want to inspect the contents of a registry value for specific data?įor instance – what if we want to inspect a specific critical service, and ensure it is always set to “Automatic” startup? Or perhaps we have a custom registry value that should always be set to a range of specific integers or string values, and we want to know if it exists, but it not set correctly? In my previous post similar to this topic, we discussed how to check for the existence of a registry key or value, and alert/change state if it was missing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |