Hi mitchelw,
thanks for your reply. Indeed I did not realize that there is a new version out despite checking the rss feed.
What doesn't make sense for me yet though is, as the catalog sync wasn't done yet, the 'old' update has not been marked as superseded / expired. So I would assume the update would install fine over the currently installed one (9.1.x).
Can someone please enlighten me about how the detection / applicable rule is working as I may see some issues with rolling out updates like that.
If I deploy an update of any kind of software it usually takes some time until every client has been online and installed the update.
So if the update gets superseded (or not applicable) without synchronizing my SUP I will have a deployment that runs into errors for every client that is not updated yet.
In my understanding an update was applicable until SUP is synchronized again and it will receive the updated metadata.
Thank you
Best regards