I'm looking for documents about patching schedule best practices. I saw a KKE were it is recommended to make a daily detection and a weekly detect & deploy. But i can't find papers that explain this.

So if you have some, I'm interested in you share.

Thank you.

Answer Summary:
1 Comment   [ - ] Hide Comment


  • is it possible to apply same patches that applied to test machines(10-20 Machines ) and later apply the same patches to end user machines without Smart Labels, as i want to make sure Patches are not causing any issues and later deploy same patches to user machines,
Please log in to comment

Answer Chosen by the Author



We've covered this topic in our KKE program.

Ron Colson
KACE Koach
Answered 03/18/2016 by: ronco
Second Degree Brown Belt

  • Thank you, I found most of what I'm looking for. But is it possible to download the slides of this recording ?
    • gwir,

      Unfortunately, that is not possible. However, you're welcome to come to any of our Open Forum KKEs to discuss any topic you want. We hold them most Thursdays. You can register to attend live KKEs here:


      The link is at the bottom of the page.

      Ron Colson
      KACE Koach
      • updated url: https://support.quest.com/kace-systems-management-appliance/training/154/kace-kontinuing-education
Please log in to comment
Answer this question or Comment on this question for clarity


I would start with the Administrator Guide

Answered 03/18/2016 by: rockhead44
Red Belt

  • Thank you for the link.
    There's lot of good informations, but nothing about scheduler timing good choices. Should we detect and deploy needed patchs daily ? Making multiple detect schedule, one for critical, one for recommended...

    That's what I'm lokking for.
    • I patch Windows Updates (critical and recommended) once per week and perform a Detect and Deploy at that time. I patch Flash/Reader/Shockwave/AIR on a different day, also doing Detect and Deploy. I do these after hours.
      • Is it a rule you define yourself ?
      • Yes. I use smart labels to ID the patches and then create patch schedules where I target machines (also smart labels).
Please log in to comment
Nine Simple (but Critical) Tips for Effective Patch Management
This paper reviews nine simple tips that can make patch management simpler, more effective and less expensive.