I would say, it depends on the organizations change control and upgrade strategy. Some environment that i worked with, have auto upgrade enabled and some have more conservative approach. Basically there is canary/pilot group (IT group themselves) have auto upgrade setup for certain # of weeks for evaluation and testing, then next change control after is where they will roll out the auto upgrade setting.
Also you still have options below depending on your strategy (upgrade process)
I only do the minor release automatically.
having said that I do test out new versions on key assets (servers, workstations, supported builds of win10 and apple).
Once I am ready to roll out a major version I use either the platform to push to my different sites or sometimes manually and sometimes, use the auto update feature only to turn it off once I have my assets on the new version I am going for.
I have found that using the auto update feature sometimes will just stop working for whatever reason (kind of annoying).
I then have to go back to my RMM tool and ensure that it is installing that new version for new/freshly imaged assets.
How's your network in general meaning Do you have plenty of bandwidth? Also there is any broker VM involved in your setup?
On the other hand the issue you were mentioning it's between 7.0 and 7.3 which are end of life at the moment ... Is this happening as well between 7.5 and 7.7?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!