Jump to content

DougS

Members
  • Content Count

    3
  • Joined

  • Last visited

About DougS

  • Rank
    Candidate
  1. I'm seeing the same errors and KSC is not really functional.
  2. This is not isolated to just a few incidences... KES 10.2.5.3201(MR3) is blocking Office365 Updates too.
  3. This only clears Kasperky definition updates which do not take up much space at all. They are asking for the ability to clear Microsoft Updates as they take up 100's of GB of space. Also, updates that are applicable to machines are not showing as applicable. The entire WSUS portion of KSC seems to be hit or miss whether it is going to apply a Microsoft/Windows update or not. If I enable KSC as WSUS and run a find updates and vulns., then sync/download windows updates, then approve updates, then run the task "Install updates and vulns..."(which is configured to apply approved MS updates), none of my devices actually update, I get "no action required". I have created a task to install specific updates, added said updates to that task and run it and I get "no actions required". If I disable KSC as WSUS and then enable my WSUS server and the GPO specifying the WSUS server, all the sudden I have tons of updates to run on all of my devices.
×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.