With the massive amount of testing and then end use experience doing release version upgrades, a small percentage of users end up struggling.
Of those successfully doing each update, not all of us do the updates the same way. Some like myself might even be prone to not reading the release notes until we have a problem (guilty).
There are few who end up in limbo, which FRS is very helpful doing remote and if needed bench service to fix.
From all the experience are there any leading indicators of a troubled or trouble-free upgrade ahead for a particular user?
Or is there simply too many variables to draw causal or even casual correlations from?
If there are sharable observations, what are best practices to minimize problems?
6500 windows 8.1
This sums it up. If you follow the instructions outlined in the Release Notes, then there is a high probability of not having any issues. But the 6000 is a multi-processor embedded system and with different subsystems that have to undergo firmware upgrades and sometimes something hangs or goes awry. The percentages of customers having issues compared to the installed base are VERY low and if "cold booting" the radio does not correct the issue, then a HelpDesk ticket is needed so we can investigate and try to correct the problems remotely. If not, then we'll expedite a repair process.
I think Flex's distributions are about as straightforward as such a complicated system could be. You might get in trouble if you've got a lot of extra stuff that has to coordinate - ddutil, waveforms, USB peripherals, amps, etc. That's life!
The interaction with Windows updates is another matter. :)