I thought I read that there was no v9.0.853.0 client released, but I’m showing 412 machines reporting just that. v9.0.853.0 to a relevance query of “Version of Client”.
How is this possible? Did I miss something?
I believe the patch from 835 to 853 also updated the client install from the console… but there was no action to update them, just new installs.
You are correct.
I did a little digging and in the fixlet “Updated Windows Server/Console Components for pre 8.2 Deployments - IBM Endpoint Manager version 9.0.853.0 Now Available! (Superseded)” there is a prefetch command …
prefetch BESClientUpgrade.exe sha1:a53b141d30d0e9ad4b01871dc13fc62eb0ef8c8a size:10644528 http://software.bigfix.com/download/bes/90/BigFix-BES-Client-9.0.853.0.exe
Lovely! Here I sit about to tell my Console Operators that the highest BES Client version in the 9.0 family is v9.0.835.0, and yet I discover 412 machines reporting v9.0.853.0 clients! At least I caught it before clicking send!
IBM, any chance the documentation can be updated? There CLEARLY was a IEM Client version 9.0.853.0 released, but there’s no mention of it in the Change List in the FullChangeList-90.txt file. Was it simply a version of the client with the Version number bumped up, or were there actual changes rolled into the client?
Not having this kind of information makes living in an ITIL world … difficult sometimes.
And even better … As I was creating the above posting, IBM released v9.9.876.0.
Still no reference to changes in the clients, but there are several changes to the server and the REST API.
1 Like
9.0.853.0 (Patch 6) was a release specifically for the server services and the server API. However, due to the agent and server dependency, the 9.0.853.0 agent was uploaded for the server upgrade Fixlets. For more information about the 9.0 Patch 6 release, see platform-releases/9.0/patch6 at master · bigfix/platform-releases · GitHub.
Also, the relay! And as I mentioned above, the server and relay have a dependency to the agent.
Part of this reason was due to what we call the “Installation Generator” which is the large download that has the server/console and agent within it.
This makes it a bit more difficult to update one component without the others so we are going to look at fixing this in upcoming releases.
There are going to be cases though where we release a server upgrade or a console upgrade or a single component upgrade only, so versions will not always match. The limited upgrade you mentioned here was due to the packaging not because any fixes made it into the release in question from the standpoint of the client.