Endpoint Protection

 View Only

  • 1.  Any problems with 12.1.6 RU6 update

    Posted Oct 21, 2016 05:36 AM

    Hi All, I have just finally managed to upgrade 12.1. RU6 MP5 but I see that MP6 is now available. Before I go ahead with the upgrade again, are there any known bad problems with MP6 that could make me hold off from upgrading?

    Thanks

    PaulC



  • 2.  RE: Any problems with 12.1.6 RU6 update

    Trusted Advisor
    Posted Oct 21, 2016 06:05 AM

    So far upgraded 3 systems with it and not seen any issues 



  • 3.  RE: Any problems with 12.1.6 RU6 update

    Posted Oct 21, 2016 07:47 AM

    Here's one to be aware of:

    https://www.symantec.com/connect/forums/1216-mp6-tray-icon-not-displaying



  • 4.  RE: Any problems with 12.1.6 RU6 update

    Posted Oct 21, 2016 08:09 AM

    Thanks Brian,

    I cannot afford to have problems like that with 1,000's of machines. I see Hans's work around, but this is not an option especially when I have to keep the client happy. We also have a very strict RFC regime to follow, so even just a reboot of a server outside of the patching cycle will need a RFC!!!!

    What do you think? Symantec will release RU7 to fix the problem?

     

    Cheers

    PaulC



  • 5.  RE: Any problems with 12.1.6 RU6 update
    Best Answer

    Posted Oct 21, 2016 08:24 AM

    Sounds like a code fix may be in order here so yes it would be ina later release. Which one, I can't say for sure though.



  • 6.  RE: Any problems with 12.1.6 RU6 update

    Posted Oct 21, 2016 10:30 AM

    Also adding this thread:

    https://www.symantec.com/connect/forums/sep-icon-no-longer-showing-system-tray



  • 7.  RE: Any problems with 12.1.6 RU6 update

    Posted Oct 24, 2016 04:51 PM

    We ran into an issue with SEP 12.1.6 MP6 unmanaged clients that we upgraded with the installer we downloaded from fileconnect.  (The clients are not connected to the SEPM).

    We are unable to make a permanent change to Download Insight Actions through the client UI.   The Download Insight Actions always revert back to the Symantec defaults (First action:  "Quarantine risk" - If first action fails:  "Leave alone (log only)" and for unproven files: "Prompt") 

    We reverted back to SEP 12.1.4 pending resolution from Symantec.