Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 1 subscriber
  • Views 15924 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

reboot after deploy

rino19ny

when deploying the av to clients, where is the setting to force the computer to install after deployment is done?

i have seen this option with kaspersky but i'm unable to find it in the enterprise console.

:50472


This thread was automatically locked due to age.
Parents
  • 0

    There is no option in the push from SEC to force a restart but in most cases typically all functionality works before you restart.  If memory serves, the firewall and full disk encryption are exceptions (not sure if you're using the firewall or encryption), and for certain hooks to be loaded into all existing running processes: New ones would get them.  It is for this reason that a reboot is requested but most of the time it's not 100% essential.  The target OS also plays a part, so I guess it is easier to to say restart to ensure 100% coverage.

    You can perform a pull install, by running setup.exe as part of a script/batch file, and at the end of the install that could call a restart

    These article may prove useful for the "pull"/scripted approach:

    http://www.sophos.com/en-us/support/knowledgebase/12570.aspx

    http://www.sophos.com/en-us/support/knowledgebase/13090.aspx

    Regards,

    Jak

    :50478
Reply
  • 0

    There is no option in the push from SEC to force a restart but in most cases typically all functionality works before you restart.  If memory serves, the firewall and full disk encryption are exceptions (not sure if you're using the firewall or encryption), and for certain hooks to be loaded into all existing running processes: New ones would get them.  It is for this reason that a reboot is requested but most of the time it's not 100% essential.  The target OS also plays a part, so I guess it is easier to to say restart to ensure 100% coverage.

    You can perform a pull install, by running setup.exe as part of a script/batch file, and at the end of the install that could call a restart

    These article may prove useful for the "pull"/scripted approach:

    http://www.sophos.com/en-us/support/knowledgebase/12570.aspx

    http://www.sophos.com/en-us/support/knowledgebase/13090.aspx

    Regards,

    Jak

    :50478
Children
No Data