/build/static/layout/Breadcrumb_cap_w.png

Software Deployment Question


K1000 patch management reboot issue

10/13/2016 1231 views
We are using the K 1000 to patch our PC's and some of the PC's are auto rebooting even though the task is set to delay, does anyone have an idea on how to stop the auto reboots?

KaceĀ Version: 6.4.120822

SILUuk.png
5 Comments   [ + ] Show comments

Comments

  • Seeing the same thing this month! It's not even waiting more than a minute or so after I run the schedule. I just had 35% of my boxes IMMEDIATELY restart with no warning. KACE shows "Error (Log Upload Failed), but the reall smoking gun is this entry in the event log of the affected machines:

    The process C:\windows\system32\dism.exe (PCNAME) has initiated the restart of computer PCNAME on behalf of user NT AUTHORITY\SYSTEM for the following reason: Operating System: Upgrade (Planned)
    Reason Code: 0x80020003
    Shutdown Type: restart
    Comment:
  • Also happened to us on Friday. Even though I have it set to no reboot.
  • Same. Rolled out October patches to our pilot group which is about 20 systems. Only 2 of them exhibited the behavior above but it was exactly as user kelleyplumos described. Subsequent repush of the packages worked without issue but I'm worried on Friday when we deploy to 900 systems on what type of failure rate we'll have. Patches included both the new Security and Quality updates for .NET and Security patches. I've opened a case with KACE support but no updates from them yet.
  • Anyone get an update on this? I have a ticket open but was only directed to https://support.software.dell.com/k1000-systems-management-appliance/kb/211378
  • I opened a ticket with KACE support and they worked on it for days, kept me in the loop the whole time and eventually came to the following conclusion: MS16-120 October, 2016 Security and Quality Rollup for .NET 3.5.1 on Win 7 SP1 and Win 2008 R2 SP1 for x64 (KB3188740) caused the issue by crashing the KACE agent itself. Should be fixed by the November MS patches. I removed that patch from my October payload.
    • Thank you so much for the update!

Be the first to answer this question

 
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