FYI(Resolved) - Credentials Lost After Update 11080
I'd like to preface this by stating that we resolved the issue ourselves, but our environment did go 24 hours before realizing an issue was present. So, this is more like an FYI for others looking to update to 11.8/Build 11080, and feedback for the company as I haven't had this happen before. (FYI posts would be a great option).
The update for 11080 went smooth, and the alert stating ELA was updated came through no problem. Now, due to circumstances in our environment, I was not made aware until 24 hours later that alerts I have configured were not coming through, and that my reports were coming back with no data.
Going into ELA all of our managed devices reported an "undefined error" for their status. Looking at the configuration for scanning on one of the servers, everything appeared correct, including the account used for scanning. Yet when I told it to try another scan, it would give the same "undefined error". I entered the password for the account again, and this time I was able to get a successful scan.
I've never had this happen with an update, and we've been using ELA for a couple of years now with loads of updates. My recommendation to others is to go into managed devices after an update and attempt a scan manually, going 24 hours without monitoring is a difficult thing to explain in some companies. Live and learn, but it's now on my due diligence check list for every update. :)
Although, maybe I should submit an idea, but perhaps an alert for servers with unsuccessful scans for 1 hour, or other interval would be a great addition to this product. Or is this already an option and I've just been blind?
The update for 11080 went smooth, and the alert stating ELA was updated came through no problem. Now, due to circumstances in our environment, I was not made aware until 24 hours later that alerts I have configured were not coming through, and that my reports were coming back with no data.
Going into ELA all of our managed devices reported an "undefined error" for their status. Looking at the configuration for scanning on one of the servers, everything appeared correct, including the account used for scanning. Yet when I told it to try another scan, it would give the same "undefined error". I entered the password for the account again, and this time I was able to get a successful scan.
I've never had this happen with an update, and we've been using ELA for a couple of years now with loads of updates. My recommendation to others is to go into managed devices after an update and attempt a scan manually, going 24 hours without monitoring is a difficult thing to explain in some companies. Live and learn, but it's now on my due diligence check list for every update. :)
Although, maybe I should submit an idea, but perhaps an alert for servers with unsuccessful scans for 1 hour, or other interval would be a great addition to this product. Or is this already an option and I've just been blind?