IT Management Suite

 View Only
  • 1.  Patch Management on Startup

    Posted Dec 07, 2016 01:33 PM

    I just took over handling all 3rd party updates for my company through the Symantec Management Console.  Right now, when scheduling 3rd party updates, it will only let me schedule at specific times of the day or days of the week.  What I would like to do is schedule it to run on each system the next time it starts up.  I know this can be done with policies, but would like to have it done for our 3rd party updates as I have a number of users who forget to sign out of their computers on update nights.

     

    Capture.JPG



  • 2.  RE: Patch Management on Startup
    Best Answer

    Trusted Advisor
    Posted Dec 19, 2016 10:12 AM

    Not what you're asking for, but just as a data point wanted you to know that we push all 3rd party updates while users are logged in on the 'agent default' schedule.  I've never had an issue (I patch Chrome, Reader, Acrobat, Flash, 7zip, iTunes, Wireshark, Google Earth, maybe a few more I'm forgetting).  If we patched on startup, we'd constantly be chasing the few users who rarely reboot.

    The only 3rd party app I update via software delivery because I don't want it installing when a user is logged in is Java.  I haven't tested it installing while user is logged in for a few years, but when I was first testing, if a user had IE opened, the install would sometimes get corrupted.  I wrote up my Java procedure here:  https://www.symantec.com/connect/articles/updating-java-8-through-managed-software-delivery-policy

    Lucky for me, Java doesn't update monthly & we minimize where it gets installed wherever possible.

    Also, if you'd like to submit this as a feature request, go to create content at the top of connect and select 'idea' and then link it here for others to vote up if they agree.



  • 3.  RE: Patch Management on Startup

    Posted Dec 19, 2016 12:10 PM

    Java is actually why I was trying to schedule this.  We have updates that run every Thursday that force users to reboot.  Java will not install anymore if a user is logged in, so I was trying to find an efficient way to do it at startup.  I guess building a policy to do the updates is going to be my best bet.  Oh well.  Thank you.