I’m trying to prevent updates from being installed on a specific client. It is an older client that needs to stay on v9 because the iDA is no longer supported.
I am following the suggestion posted here:
I created the Additional Setting at the client level to test, and then kicked off an Update Software job. The job ran and it didn’t seem to honor this setting as it showed “Update In Progress” and eventually failed out due to another issue on the box.
Can we verify that this should work on v11.24.69, and that the key is correct [bSkipUpdate]?
I also attempted to use the Excluded Machines list from Software Configuration but that didn’t seem to work either (it says on that screen that the list only applies to automatically discovered machines, so I assume this was originally used for install software jobs where there were automatic discovery rules).
Also wondering which log I would see this bSkipUpdate being logged in? I’m assuming it is on the client side so that it would prevent someone who logged in and ran a service pack interactively. But even with that additional setting and the hostname listed in the excluded machines, the install updates job still proceeded. What can we do to blacklist these clients so that update attempts fail?
Best answer by Remi SprangersView original