/build/static/layout/Breadcrumb_cap_w.png

Most likely reasons Win 7 fails patching a majority of the time?

Good morning.
In our system, we have a mix of Windows 10 and Windows 7 computers. When patching, the Windows 7 computers are most likely to fail, and a majority of them do fail. We have more success with Windows 10. We do have our computers set to not automatically download and install updates as we want KACE to do this. I also have it set to run at night and to force a reboot. Other than that, are there any known reasons that the Windows 7 computer typically will fail?

1 Comment   [ + ] Show comment
  • Make sure SMA server and agents are on the same version.

    Please specify the error code or message you are seeing.

    Please specify if you are using labels to Detect and Deploy Patches, you might want to build a label for Win7 and a Label for Win10 patches.

    Please specify if you are Using Detects jobs to detect missing patches, and deploy jobs to install them , or , if you are using Detect and Deploy Jobs

    Make sure you have these directories white-listed:
    https://support.quest.com/kace-systems-management-appliance/kb/111785/which-directories-and-executables-do-i-need-to-whitelist-for-the-sma-agent-

    Make sure those Windows machines are able to check-in fine.

    Check this video, make sure best practices are being followed:
    https://support.quest.com/kace-systems-management-appliance/kb/235389/kace-sma-patching-best-practices - Channeler 6 years ago
    • “Make sure SMA server and agents are on the same version.” – The agents are 8.1.52 and the Server is 8.1.107.

      “Please specify the error code or message you are seeing.” – I recently deleted all the patching schedules so that appeared to delete all the records of past attempts. Many had Log Upload Failed error messages. I also saw many detect statues of Not Patched with a Deploy Status of Success (102) messages which I understand to mean that the computer did not reboot as the deploy schedule was set to do (force reboot). I also see many that says the patching was complete but when I check the Patch Results, it shows Deploy Failures > 0. I am honestly finding it confusing and complicated to troubleshoot.

      “Please specify if you are using labels to Detect and Deploy Patches, you might want to build a label for Win7 and a Label for Win10 patches.” – I was not initially separating Windows 10 from Windows 7. I had them grouped into 9 deploy groups and they were all mixed in together. I am currently redoing the grouping so that each deploy group will be a single OS.

      “Please specify if you are Using Detects jobs to detect missing patches, and deploy jobs to install them , or , if you are using Detect and Deploy Jobs” – I was running the detects and deploys in separate schedules. I was also, per the recommendation of Quest Support, running one detect for one deploy (so there were 9 detects and 9 deploys scheduled. The detects were being run over the weekend, the download on Monday and the test deploy on Tuesday. So there was time between the different schedules.

      “Make sure you have these directories white-listed:
      https://support.quest.com/kace-systems-management-appliance/kb/111785/which-directories-and-executables-do-i-need-to-whitelist-for-the-sma-agent-“ – I have confirmed that they are all white-listed.

      “Make sure those Windows machines are able to check-in fine.” – I focused on the ones that were checking in. The devices that were not checking in are being troubleshooted separately.

      “Check this video, make sure best practices are being followed:
      https://support.quest.com/kace-systems-management-appliance/kb/235389/kace-sma-patching-best-practices” – I have watched this video and printed out the information below it. It has come in handy and I will be honest that I have had to watch it more than once. - jessburd 6 years ago
      • Ok, "Many had Log Upload Failed error messages.", is not good, could you attach a copy of the KAgent log for one of those machines?

        Should be in:
        C:\ProgramData\Quest\Kace\kace\user - Channeler 6 years ago
      • Channeler, I will try. However, the patch schedules in KACE have been deleted since I am redoing them. I have checked a few of them in KACE and it appears that the patching information is gone as well from KACE. So I will have to manually check some Win 7 computers to see if I can find a few that had some type of failure. - jessburd 6 years ago

Answers (0)

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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