/build/static/layout/Breadcrumb_cap_w.png
04/25/2019 273 views

Hey So i'm knew to using the k1000 to patch we've mostly been using it as a ticking system.

Anyway I've been looking into using it to patch updates, now the first thing i did wrong was under subscriptions i had it patch non security / security / software installer. It installed a load of random software on my machine and i quick google search showed me the error of my ways.

I removed all the software unticked software installer and then created a new schedule to patch my machine. It has now reinstalled all the software I removed again despite software installer being unticked and all the software being removed. Any idea why this is? 

I'm not using smart labels at all for my schedule i've just got it set to only patch my machine.

Answer Summary:
1 Comment   [ + ] Show comment

Comments

  • We had a similar issue. Kace would install what it detected as missing. Do you have software installer checked under types? That was my problem. But I also now use smart labels to further patch and deploy patches though Kace.
    • It was ticked originally and i had the set up as detect and deploy.

      but i've unchecked the box removed all the software from my PC and changed separated the detect and deploy functions into two separate schedules.

      do you have publishers set to all?

      I was thinking about smart labels but i'm not really sure where to start with them...I basically want everything patched every bit of software and every windows patch
      • terryj I have my publishers set to only the ones I wanted. I didn't want my SMA to download to much and worry about disk space. I'm running an older appliance that I need to convert to virtual (just haven not had time). Running a separate detect and deploy is good thing to do. Giving machines time to check in and give the end user fewer reboots. I'm only allowed to run patching once per week. It takes a little bit but everyone gets caught up.

Answer Chosen by the Author

0

I setup 2 Patch Smart Labels and 2 Patch Schedules, one for the computers that should get the updates early for testing, and one for the rest of the computers. I first run a detect on all the computers, then run the deploy on the different sets of computers. The main difference is in the Smart Labels, where I want to wait a few days after a patch is released before deploying it. They're something like this:


    For the early deploy, my Smart Label is 
        Status is Active
        Type is not Software Installer
        Missing is True
        Released is not within last 2 days

    For the main deploy, my Smart Label is 
        Status is Active
        Type is not Software Installer
        Missing is True
        Released is not within last 4 days

You could change the Released is not within x days to what you're comfortable with.
Answered 04/26/2019 by: PaulGibson
Senior Yellow Belt