{"id":5737,"date":"2020-04-29T20:11:48","date_gmt":"2020-04-29T19:11:48","guid":{"rendered":"https:\/\/www.n-able.com\/?p=5737"},"modified":"2022-06-14T15:19:52","modified_gmt":"2022-06-14T14:19:52","slug":"patching-automation-best-practices-part-one","status":"publish","type":"post","link":"https:\/\/www.n-able.com\/pt-br\/blog\/patching-automation-best-practices-part-one","title":{"rendered":"Patching Automation Best Practices\u2014Part One"},"content":{"rendered":"
\n

This two-part blog series looks at some of the best practices for patching\u2014combining what we usually recommend and what we see our successful partners doing. While this blog series looks at best practices for patching, if you\u2019d like more specific information on how to implement them in your business, we\u2019ll be releasing courses for\u00a0SolarWinds\u00ae<\/sup>\u00a0RMM<\/a>\u00a0and\u00a0N‑central\u00ae<\/sup><\/a>\u00a0in the near future.<\/p>\n

Windows updates are a staple for all managed services providers (MSPs). As a result, this process is often either very time consuming or easily overlooked. In either case, it can create issues for MSPs\u2014but it doesn\u2019t have to be a major pain point.<\/p>\n

In most remote monitoring and management (RMM) platforms patching is flexible, easy to use, and can be configured once for most or all devices (though the amount of time this takes may vary based on which RMM platform you use).<\/p>\n

I\u2019ve found that partners patch in different ways. Today, we\u2019ll break the process into five main phases and document each separately:<\/p>\n

    \n
  1. Finding new patches<\/li>\n
  2. Approving patches for install<\/li>\n
  3. Downloading the patches<\/li>\n
  4. Installing the patches<\/li>\n
  5. Rebooting the computer<\/li>\n<\/ol>\n

    We\u2019ll cover the first three phases in part one of the blog series and cover phases four and five in part two.<\/p>\n

    Finding new patches<\/b><\/h3>\n<\/div>\n
    \n
    \n
    \n
    \n
    \n