So a few weeks ago, we upgraded from BES 7.2 to TEM 8.1.608. Since then, 2 new updates have been released. Obviouslly we cannot keep upgrading TEM every single week when a new update is released, so we’re going to hold tight on 8.1.608 for a bit. The problem is that our clients are still on 7.2. Before we could upgrade our clients the following day, I opened the console to see 8.1.608 gone and only 8.1.617 was available.
This leads me to my main question.
Can we push the Fixlet “Updated Windows Client - Tivoli Endpoint Manager version 8.1.617.0 Now Available!” while the server, relays, and consoles are still on 8.1.608 and have everything function normally???
There’s a nice bold red text stating that you must upgrade the relays before upgrading the clients. JUST GREAT!!!
So now what? OK, i’ll schedule a time to upgrade the server, database, etc to 8.1.617 next week, but what happens when there’s a new version released as we go through the upgrade process?!?! Then we have to do it all over again!!
Unlike what’s been suggested, we actually like to TEST everything before we do it and don’t have the luxury to do everything in the same day.
So now can we just upgrade the relays & clients to 8.1.617 with the servers/consoles still on 8.1.608 or are we stuck upgrading EVERYTHING again?
yeah, BigFix modifies the fixlets for the new version, so you no longer can see the old fixlets for your 8.1.608 upgrades. we have the same problem. What we had to do was go out and download all the fixlets for the old version and bring them into the console. Then delete them when you go on to the next version.
this page gives you the link to download the old fixlets:
Did you have to add it into BES as a task using the Software Deployment Wizard and then write relevance to show only applicable computers? I was thinking about doing that before submitting this post, but was trying to be lazy and not have to do all of that.
Could you leave the previous versions of the client active/visable in the external site after new client versions are released?
I am having the same issue. A new client has been released but am not yet ready to upgrade, however I still need the ability to push out the client that matches my server/relay version!!
We went to deploy a new relay for 8.2.1093 and now all we have is 8.2.1175. We are nowhere near ready to deploy this version but still need to support our environments.
Would it be odd if I fifth and sixth agreed to this??!!
IBM, most people do not upgrade their systems as soon as new version is release. Unles there is a specific reason to upgrade (aka bug fix) I would bet most users wait 1-3 months if not longer before upgrading. It would be great, dare I say essential, that we can continue to push out the client and relay that match our currently installed server version. Maybe you could “hide” the older versions rather than removing them allowing users to “unhide” the client if required.
I will “fifth/sixth” this! However, I am guessing that you could actually install the Client 8.2.1175 build level when the TEM Server is still at the 8.2.1093 build level… it’s not like it’s a whole new version or point release. Anybody else try this yet?