/build/static/layout/Breadcrumb_cap_w.png

Schedule Patch in Kace 1000

Target : We are trying to automate Patching process , where by we don't have to start or stop patch schedule. It runs always.

Question: Is there a way we can have patch allocated to specific label if it is release after 2 Tues of every month ( patch day )

Solution :  still looking for



5 Comments   [ + ] Show comments
  • How Many Workstations are you targeting? - Desktop Jockey 6 years ago
  • all workstation in environment. close to 6000 - rock_star 6 years ago
  • how do i create a dynamic patch Label based on 2nd Tuesday for every month. I don't see any option for automatic. i can create one with release date but it would be manuall. - rock_star 6 years ago
  • Are you running the latest released version? This feature (Patching Schedules) was enabled in version 7.0:
    Patching schedules. Administrators can now schedule patching jobs using a desired schedule, as required. You can run a patch job based on a particular day of the week within a month (for example, second Wednesday of every month). - RichB 6 years ago
  • ahh nice to see that option.. I am still on 6.4 .. Let me check and get back..

    Looks like , we do have option to set sechedule but no label creation based on day of month. - rock_star 6 years ago

Answers (1)

Posted by: chucksteel 6 years ago
Red Belt
1
I'm pretty sure that you are asking about applying labels to patches, and you can create smart labels for patches. I'm not clear on what criteria you have for patches, however. Do you only want to include new patches? The K1000 will automatically make old patches inactive, so you shouldn't have to worry about that part. 
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ