Posted on 09-21-2016 05:06 AM
https://support.symantec.com/en_US/article.TECH131045.html
Posted on 09-21-2016 09:35 AM
Did anyone else have a situation where the upgrade to Sierra moved Symantec to an unsupported app, and then when you try to install the new version, it says you must uninstall the old one first?
I had to run the .app uninstaller that came with it (PKG didn't appear to work fully), reboot, then install the new one, then reboot.
I'm trying to avoid this menagerie of installers, uninstallers, and reboots.
Posted on 09-21-2016 11:29 AM
Can you simply run the uninstaller and then reinstall without rebooting? I think you only need to reboot so SEP can unload some components that are probably not even loading anyway since it's unsupported.
Posted on 09-21-2016 11:32 AM
@alexjdale it seems to force a reboot when you run the .app.
When I ran the .pkg version of the uninstaller and did not reboot, the new installer still complained about needing to run the uninstall routine. :D
Posted on 09-22-2016 10:55 AM
What happens if you update Symantec and then update to Sierra? Will the update work on older macOS versions?
Doesn't help folks that have already updated to Sierra...
We require a number of updates before making the latest OS available in Self Service (yea, smart groups!)
Posted on 02-23-2017 03:29 PM
We never did work out a good way to do this.
We just force uninstalled the old one prior to the OS upgrade, updated to Sierra, then kicked off the new install.