When upgrading from SEP v11 to v12 after upgrading SEPM v11 to v12, we experienced loss of network connectivity. The system could not be identified. The following were attempted without any success:
SEP v12 was also installed on a brand new system in order to observe behavior that was none-upgrade related. Results were still the same.
In addition to loss of network connectivity, the following symptoms were experienced:
There seems to be a lingering option from v11 that needs to be disabled in order to make v12 work. This is found under "Application and Device Control Policies" and make sure "Protect client files and registry keys" is "unchecked". You also have to follow these steps when manually installing the v12 client:
Your v12 client should now run as expected.
The SEPM v11 to v12 upgrade did not end up working for us. A new SEPM v12 install was done on a new server, recreating previously configured policies. This worked flawlessly, and as a result have now almost completed all PC-based system SEP upgrades from v11 to v12. Focus will soon shift to Macs.
Same thing happening on version 14. This is ridiculous - get it sorted Symantec.
2 of my PC's have lost Local Area network connection when upgrading from version 14.01 to 14.02.
I uninstalled symantec and get the LAN connection back.
It's needed that more customers has to comment about issues
Yes, my understading is that the issue will be addressed in soon-to-be-released new 12.x version. In our case, we really needed to get the new version going quickly and thus the reason for the approach.
Thank you for sharing.
I've used tha chance to spoke about this problem with Paul Murgatroyd and he told me it will be fixed in the next couple of versions of SEP12.1. The Software will identify these Settings from tamper Protecion (SEP11) and will change all the stuff in SymProtect (SEP12.1)
Thanks for sharing this helpfull information.