That sucks for you. We have a few 5.13 clients left, but I know they're broken, otherwise they'd be at 5.17. I use controlled groups for everything, except the default build group. If I need to work on an individual machine, I can move it to that (small) group, and change whatever I need to in order to get it working again. Once fixed, it gets put back into a controlled group.
We're about to upgrade the whole fleet to 5.22, and it'll be done by controlled groups. (~24,000 machines, so I couldn't possibly use individual machines)
Yea I figured I was out of luck. I got here a little late in the game to actually make any decisions and all my suggestions to have a standard coe get laughed at because it would work and makes sense. Just not going to fly in an environment of this size. I was hoping I'd be able to make the changes via the API but I'm sure that's not going to work either. Oh well...
Question? Can I create a new controlled group with my regular settings and client files for each....5.1.3, 5.17, 5.19, etc. and then apply my changes that I need to make without reset the group to the config? Would the clients get the changes on next sync?