Cody Lee

My feedback

  1. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SMA (K1000) » Reporting  ·  Flag idea as inappropriate…  ·  Admin →
    Cody Lee shared this idea  · 
  2. 20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SMA (K1000) » Appliance  ·  Flag idea as inappropriate…  ·  Admin →
    Cody Lee supported this idea  · 
  3. 9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SMA (K1000) » Service Desk  ·  Flag idea as inappropriate…  ·  Admin →
    Cody Lee shared this idea  · 
  4. 88 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  SMA (K1000) » Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Cody Lee commented  · 

    This is definitely needed. Currently KACE does not work or play nice with patching and the use of Cylance AntiVirus due to an issue with Patchlink.com.

    The current recommendation from KACE is to run a script to remove the Patchlink.com registry entry from each system to be patched before you run a detect or a deploy. Being able to just set all of our Patching Schedules to automatically run this kscript before hand would be amazing.

    The same thing could be said about running kscripts after patching has completed. In order to make sure there are no pending reboots or that KACE Agent did not properly kick off the forced reboot, we have to run another kscript scheduled for after the patching window.

    It would make my life a lot easier to change the schedule in one spot for both scripts running before a patching schedule, as well as the patching schedule itself.

    I wouldn't imagine it would be that difficult to add this functionality since as long as the script exists and as an ID in KACE, it would merely trigger a "Run Now" for each machine.

    Please add in this functionality to the next release.

    Cody Lee supported this idea  · 
  5. 10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SMA (K1000) » Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
    Cody Lee supported this idea  · 
  6. 117 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  SMA (K1000) » Scripting  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Cody Lee commented  · 

    The year is 2018, and somehow this "swiss-army knife" of the IT world still can't seem to do basic things.

    If someone has a sql report to get this information, please let me know!

    Thanks!

    Cody Lee supported this idea  · 

Feedback and Knowledge Base