{"id":3635,"date":"2018-01-24T08:08:38","date_gmt":"2018-01-24T14:08:38","guid":{"rendered":"https:\/\/kevinjustin.com\/blog\/?p=3635"},"modified":"2019-08-20T10:48:04","modified_gmt":"2019-08-20T14:48:04","slug":"active-directory-2012-2016-addendum-management-pack","status":"publish","type":"post","link":"https:\/\/kevinjustin.com\/blog\/2018\/01\/24\/active-directory-2012-2016-addendum-management-pack\/","title":{"rendered":"Active Directory 2012-2016 Addendum Management Pack"},"content":{"rendered":"

\"\"<\/p>\n

A Post-it note is like an addendum, no?<\/p>\n

 <\/p>\n

 <\/p>\n

As an Operations engineer,\u00a0how many times do you get notified for a service restart?<\/p>\n

 <\/p>\n

Did you know about Service Recovery actions, or SCOM\u00a0Recovery Tasks?<\/p>\n

 <\/p>\n

Why didn’t the SCOM Recovery tasks get added to many of the common Microsoft Applications?<\/p>\n

 <\/p>\n

 <\/p>\n

Hopefully today, we can discuss some actions to help limit the amount of manual rework required to resolve service issues.<\/p>\n

 <\/p>\n

Let’s explain the basics<\/strong><\/p>\n

    \n
  1. Windows Servers\u00a0have a Recovery tab in the Services.msc<\/span> menu.<\/li>\n
  2. Does your monitoring tool allow for recovery actions?<\/li>\n<\/ol>\n

     <\/p>\n

     <\/p>\n

    To implement recovery actions, here’s an example of the Services Recovery Tab<\/strong><\/p>\n

    Here’s an example of the SCOM agent service<\/p>\n

    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 NOTE\u00a03 failures spaced 1 minute apart to restart the service<\/span><\/p>\n

    \"\"<\/p>\n

     <\/p>\n

     <\/p>\n

    Let’s take it one step further, and add a restart to the service from another tool\u00a0(insert your monitoring tool here).<\/p>\n

     <\/p>\n

    In SCOM, taking an action after identifying the problem can be handled different ways<\/p>\n