Hello,
We're pushing the upgrades from our SEP Mgmt Server to clients running Windows Server 2008 and Windows Server 2012.
This is to address this: https://www.symantec.com/security_response/securityupdates/detail.jsp?fid=security_advisory&pvid=security_advisory&year=&suid=20160628_00
I've noted that for some client servers, after I use the SEP Mgmt Server to push the update to a client, the Mgmt Console will display "Reboot needed" (for the client), but when I remote desktop to the client and start SEP it doesn't display that a reboot is needed (but for other client servers it will display that a reboot is needed). Some of the client servers are hard to schedule downtime for, so no reboot would be the preference.
If anyone has answers to the below questions, I would appreciate it:
1. Is it possible to avoid a reboot with a SEP upgrades from 12.1.5 (12.1 RU5) to 12.1.7004.6500 (and still be protected from the issues listed in the above advisory link)?
2. If we push this SEP update 12.1.5 (12.1 RU5) to 12.1.7004.6500 to a Windows server and delay the reboot, is the machine any more vulnerable than if we had not pushed the update?
I've looked through the forums, can't see a definitive summary/answer on this.
Thank you in advance for any info someone has on this.
-Max2000