Hello everyone,
I would like try and clarify something which for me, is inexplicable, before opening a Case at Symantec.
Long story short, using SEP since 2012, i've always tested every versions that Symantec releases, so that i won't create damage to my customers environment.
Never have i had these inexplicable issues when trying to just do a simple and classic upgrade from one version to another.
The problem is like this.
I have in my environment SEPM (2 servers in fail-over) which manage our customer environments.
I was dreaming of planning my customers for SEP agents upgrade, but when i started testing the (so called) 14.3 version, i came across a strange issue.
From the beginning i would like to point out that my Liveupdate Policy settings is to use JUST the SEPM.
My agents do not go to the internet to download definitions.
And here is where the fun began...
I run a 14.3 558 over a 14.2 5323 (PLEASE keep in mind what i've said about the Liveupdate policy settings)... and after reboot my agent began experiencing errors.
The message:
...corrupt definitions...
Honestly i didn't understood why is this happening, so i started testing a little bit more... TO DISCOVER :( after a day of building-rebuilding test environment because i didn't understood why this is happening, to find out that IF i
CHECK the USE A LIVEUPDATE SERVER in my Liveupdate policy, the upgrade performs smoothly, without any errors afterwards.
BUT of course i don't want to have
Use a liveupdate server CHECKED, because i want my agents to download definitions from SEPM.
Thing that it's not happening after upgrading to 14.3
KEEP in mind, i tested all the versions after 14.3, until RU1, on all i experience the same thing.
Therefor my simple question is...
Why is this happening ?
Why a simple and classic upgrade, a 14.3 package run over a 14.2 5323 is behaving like this ?
What is going on ?