Upgraded a fairly new environment to 9.5 MR2. Only bug encountered was with the receivers flagged as critical status stating it wasn't communicating with the ELM. Support verified that it is communicating and that the alert is a cosmetic bug where it was checking for the wrong build number. This is to be resolved in MR4. From support MR4 is to be release around the end of April and MR3 won't be released to the public. He also stated that they are only focused on stabilizing code during the 9.5 release so we shouldn't see any new features until the next major release.
Upgraded both of our environments from 9.4.2 MR6 to 9.5.0 MR4, both are stand alone appliances, no VM's or combo boxes. One environment is mostly all old Orange Nitro gear, newer environment is a mostly new gear.
The upgrade itself went smooth, with the typical issues we always see on our older Orange ESM & ELM relating to the 3ware controller initializing on the first boot.
Post upgrade we have had multiple issues:
Our APM & DSM (older Nitro boxes - 8 cores and 8GB of RAM) both are getting Kernel panics due to being out of memory, system hangs and has to be hard booted, development is trying to figure out why.
Ran across a "known bug" on at least one of our receivers:
If you see this message in the System Log or /var/log messages -
Health Monitor Alert - Bad data files detected; they have not been fully parsed!
and the commands you ran show no entries under the NORMALIZED_ENCODING column (command shown below)
tq - 'select id, type, collector, parser, NORMALIZED_ENCODING() where type == 49190 and parser == "asp"'
Then you have the known bug.
And all of our scheduled reports have the wrong Logo on them, this typically happens every time we do a significant upgrade, however this time I can't fix it, I even tried deleting the old logo's.
Download the new ePolicy Orchestrator (ePO) Support Center Extension which simplifies ePO management and provides support resources directly in the console. Learn more about ePO Support Center