Hello all,
thought I'd share this. There are endpoints which fail to update/upgrade, there are endpoints which seemingly can't be redirected to the new server ... and there are endpoints which "behave".
Last week an endpoint "appeared" in Unassigned, actually a reappearance - known once but deleted quite some time ago as it hadn't talked to the management server for months. RMS was apparently (still) working, the endpoint running XP reported version 10.0.5 (sic!), detection data 4.78G and an update failure. The Primary location pointed to a server gone for good years ago. This shouldn't have been a problem though as the old name is an alias for the current management server. Perhaps it was in a network segment where it couldn't make the UNC connection. Unfortunately the Secondary contained the legacy path to the WebCID which no longer worked.
I moved the endpoint to a group to assign the correct policy but meanwhile the UNC connection worked and the endpoint updated from 10.0.5 to 10.6.3 without a problem. A check of the logs confirmed that the endpoint was last used (and updated) end of June 2012! So both RMS and AutoUpdate are quite robust and backwards compatible and while the SAV/SESC major version was already 10 there were nevertheless the not-so-insignificant changes in 10.2 and 10.3. I've had a number of revenants but both the absence for more than four years and the upgrade from 10.0.5 to 10.6.3 set a new internal record.
Christian
This thread was automatically locked due to age.