@ph7
So when you used my script it worked aside from the backup hiccup? My script for the node version I added the ability to choose a node version or stick to LTS releases. If that helps you pin down the node version issue. When switching use the --rebuild option to rebuild xo on the new version. Otherwise if there are xo updates it will upgrade node if change or new LTS. It should downgrade but not tested safe to use the rebuild to make the change.
@probain same, fsck on boot disk was clean.
but backups were making the XOA crashing in loop... we had to search the culprit, and the kernel update it was...
[image: image.jpeg]
.56 is releasing on some xo proxies
@dinhngtu I will mention that the package was deployed via windows SCCM deployment tools so that may have also played a part in leaving the old product code behind. After running the above script we were able to deploy 9.2.445 via SCCM without issue and no old product codes were left behind.