Just wondering if anybody else is seeing this. I am in the process of doing expanded testing before rolling this out to our 8,000+ clients, after last night's expanded test group I noticed that about half didn't come back online. Dissappointing. Looking into one of the devices I noticed that it was in a self-managed state but on the new version. Did a few restarts but that didn't fix the problem. I then pushed a Communication Update Package through the SEPM to that client and it came back. Did that to the rest of the 60 or so devices and they all came back. Quick background information - this version update was done as an "install package" through the SEPM for that specific client group. Silent install, all previous logs and communication settings were to be removed with the upgrade, with a forced reboot happening at 10:20pm. I had done a smaller test group where I had kept previous logs and communcation settings and had experienced the same issue with one device, I thought that it was a one off but I guess not.
There is a case opened up with Symantec, I have given them SymHelp logs from a client and our SEPM's, they are reviewing the SymHelp logs now.
Has anybody else experienced this? If so, were you able to resolve this? I am holding all future expanded pilot tests and the production deployment until this is figured out. Thanks and good luck with your upgrade to remediate the zero day vulnerabilities!