Software Deployment Question

K1000 not installing patches needed after 1st reboot

11/14/2019 548 views

K1K Version: 10.0.290

Clients: Windows 10 and Server 2012r2

Schedule set to Deploy only per Quest's instruction. Detect runs every night

I deployed updates to a group of four 2012r2 servers today and some patches installed, but a few were NOT PATCHED. I made a dup of that schedule. After they "force rebooted" from the 1st run, I ran the dup on the 3 servers that missed some patches. Note that the 4th server did receive all the patches including those that were missed by the other 3 servers. 

The 3 servers received the missing patches on the second run. I don't know when this started, but the K1000 used to complete patching after reboots.

How can I get our K1000 to continue patching after client reboots? We do have it set to force reboot.


1 Comment   [ + ] Show comment


  • I feel like I'm having the same issue. Although I was under the impression that you had to have detect and deploy to have it continuously deploy/reboot until it was completed.

All Answers

If the systems have a deploy only the deployment ends wit the first reboot.
After a new detect and a new deploy the next batch of patches will be deployed.
If you have outdated systems which need multiple reboots you can run a detect + deploy. This will start a new detect after the reboot followed by a deploy until done.

Regarding your issue: it is possible, that Nr 4 already had the patch which needed the reboot.
But this will be seen in the logs what really happened.
Support can help you reviewing the logs.
Answered 11/15/2019 by: Nico_K
Red Belt

  • This makes sense and is why I asked support about it last month. Support told me to use only "Deploy" about a year ago after we had been using Detect/Deploy for years. I questioned it last month and they confirmed that "Deploy" only is the recommended method for patching. Never sat right with me.

    Thank Nico. As always, much appreciated.
    • Well, Deploy only _IS_ the best choice because it is clear and structured and runs shorter.
      It has a few flaws but is the by default the best choice.
      A D+D task (I use one for newly deployed machines only) can run for a long time (had it with a W7 device which deployed longer than the "new machine" life, which was disturbing ;)
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