Wow, months later............ Too little, way too late.
The problem started December 2011, and went through first part of November 2012, nearly a full year of SEP upgrade #@$%. It's a bit late, now.
I've known about and had SEP RU2 in my hands for a couple of months, so waiting and replying with "RU2 is out and solves a lot of problems" months later isn't a good feeling.
RU2 isn't the point, and it came way late - well after we had all the problems for over a year. The problem should have been solved months ago. And not by RU2. It should have come way before that.
I hope most problems aren't answered this late in the game. It was so bad we came close to "no more SEP upgrades from now on".
The logs will be long since gone. There really isn't any use trying to troubleshoot it a year later.
The issue wasn't taking forever for the files to get TO the computers,
it was AFTER the files were copied to the computer that the problems came into play.
When the computer rebooted is when the nightmare on 12th Street started. Whatever SEP installs did after the files were copied into a parallel position to the prior version, then the computer rebooted it took in some cases 30 minutes to get control of the computer back. One poor person waited FORTY minutes. The only thing going on was nothing, literally - Windows was not writing to ANY logs during that time. SEP was done writing to logs. But whatever happens immediately after the computer reboots was nothing but trouble. Further, many installs failed. Some "install failed, rolled back", some simply failed to update then lost all connection with the SEPMs. The only cure in each and every case was a full uninstall and reinstall. Basically, it started when we moved from 11. The very first SEP 12.xxx we installed as upgrades over 11 were nothing but trouble. It was a disaster. It even caused some people to report computer screens going black at random times, then coming back. This would happen the time of the install after the reboot, and now and then during the day, then by the 2nd or 3rd day after the SEP upgrade, the computer would behave again. SEP even seemed to be killing video processes.
I still to this day find a computer now and then that for some reason appears, but SEP is broken. The management piece seems to ping the server so I get a current last check-in time, but that's it.
The nighmare is over thanfully - at least we THINK it is - I'm now in testing mode of RU2, not at all willing to run head-first into yet another SEP total nightmare, I'm taking it VERY slow, a computer here and there just to see if we get complaints again. Imagine rebooting your computer and having to wait 30 minutes, or the upgrade going out over night and you come in to log in and your computer takes a half hour to respond and allow you to work. That was the norm for us - with EVERY upgrade we made. Basically SEP and I were put on a software upgrade diet - very limited upgrades or updates, only if absolutely needed, and only with full controls and tons of testing. Even then there were problems.
I'm shocked that for 3 months there wsn't a single reply (no, not really, because frankly, no one even in Symantec knew what was going on and in the online community, when there's no answer, you get no reply), suddenly the answer is SEP RU2? No, SEP RU1 was broken, MP1 was broken, and everything in between was b roken as far as we're concerned - at least as far as the install process. So having to wait a full year until RU2 wasn't the answer. It is now as we've got no choice, but when we were in the middle of the problems, there was no answer at all.
........... SEP RU2 is old news. Logs will be long since gone, and I scoured them myself, inclding every single log Windows makes and found nothing other than SEP upgrade process was doing "something" mysterious after the reboot - not before, not during file copy. And during that time, no logs were written to. On ones that "install failed, rolling back" happened, that's pretty much all the install logs indicated. Failure, rolling back. No other clues. For the ones that sat for 30 minutes, most of those were successful, thus no errors were ever entered in any logs. It's sort of like a trip to the store - and the store is only 1 mile away, but it took you 2 hours to get there. Did you have any breakdowns or problems? No, you simply crawled there and took your time, sat down now and then for a rest, then finally decided to sprint the last 10 feet.
Can't blame our computers - we install more heavy stuff than SEP - MS office, Office and Windows service packs, 300 meg of patches, etc. - those all go very well every single time. The one and only application we've ever hated the upgrade process on was SEP 12. When heavy Microsoft service packs and patches install more reliably, there's a problem. But it seems over a year later they might finally have it right - after SEP earned a very bad reputation with us for their horrible upgrade processes.