(imported topic written by jgstew)
This is early and so far we don’t have much certain to report, but this is a major issue. So far this seems to have only affected a small number of clients in certain circumstances, but it leaves the client in a broken state, which is very bad.
The issue occurs when having
Updated Windows Client - IBM Endpoint Manager version X Now Available!
targeted as an open action to all computers or an automatic computer group.
So far the problem only seems to be happening with clients that are being provisioned for the first time with a client installer older than that of the open update action. So far are best guess as to what is happening is that the older client gets installed and is starting to get up and running and process actions, but it gets updated too quickly which causes it to break.
Right now we are recommending the following Relevance be added to any client update actions to try to prevent the issue:
(1 * day) < (now - maximum of subscribe times of sites)
I’m still not certain what the cause is, or if this addresses the issue, but it will prevent the client from being upgraded while it is still in a state of flux.