(imported topic written by SystemAdmin)
Hi,
The fixlet for upgrading the client to 8.1.551.0 seems to have gone A.W.O.L. There’s fixlets for 8.0.627.0 and 8.1.608.0 plus all the 7.x versions.
Is there a reason for this or just an oversight?
Cheers,
Mark.
(imported comment written by nberger91)
Same goes for BES Relay 8.1.551.0, please (re)propogate
(imported comment written by SystemAdmin)
Bump
(imported comment written by JasonHonda)
The 8.1.551.0 fixlets were replaced with the 8.1.608.0 fixlets when they were released. We replace fixlets when patch releases are released to try and ensure no one is using release versions that have issues that have been addressed in a patch.
The older fixlets are archived here http://support.bigfix.com/bes/install/beswindowsarchive.html
(imported comment written by SystemAdmin)
Hi Jason,
Thanks for the link.
I don’t know how any of your other customers feel, but for my part, we have a change process that we have to follow. Forcing us to upgrade by removing the task isn’t really acceptable especially as it’s only one release behind. I could understand if you removed the tasks for BES 7.x but not one minor release!
Again, thanks for the link, I can continue with my update cycle now.
Brgds,
Mark.
(imported comment written by nberger91)
Ditto
, this must be a new decision by IBM/BigFix. Can you please reinstate at least v8.x (to date)
(imported comment written by BenKus)
Hey guys,
As far as I know (and I can double-check) we have been pretty consistent with this behavior for the last 5 years or so.
The behavior is (for the version of major.minor.build):
Why do we do this? Because customers complained that we had so many damn upgrade Fixlets that it was a pain to find the latest and greatest and people often made mistakes by upgrading to older build versions (which often had serious issues compared to the newer versions). With the current scheme, there are 221 upgrade Fixlets for all components for the last 2 years of upgrades… If we kept every single patch release Fixlet in place, there would likely be 3-4x as many Fixlets and the majority of them would be “not recommended” to install.
We are definitely concerned about change-control processes for you guys, which is why we always go through the trouble of posting all upgrade Fixlets to http://support.bigfix.com/bes/install/beswindowsarchive.html as Jason mentioned.
The idea here is that when we have a patch update, it is always recommended over the earlier version (because patch updates are usually done when a significant problem arises) and so we want the Fixlets to reflect this by not allowing customers to accidentally update/install a version that is more broken than a comparable version… And for the customers that have not yet gotten the patched version approved (and are comfortable with the more broken version), we have a Fixlet available that can very easily be imported from the website.
It is certainly not a perfect system, but it is the best we have come up with so far to deal with all the complexities…
Ben
(imported comment written by SystemAdmin)
Thanks Ben - your explanation does make sense.
Would there be any mileage in having a housekeeping job that sets the ‘hidden’ flag on any Agent Upgrade tasks that are a) older than the lastest version and b) not in use by any existing end-points?
(imported comment written by BenKus)
I guess that could be something we look at… but we don’t have a technical capability to change the hidden flags for customers…
Is there something that you don’t like a about importing the upgrade Fixlets? We thought it would be easy and simple…
Ben
(imported comment written by SystemAdmin)
No Ben there’s nothing wrong with it, I just wasn’t aware of the URL that’s all.
I probably should have RTFM’ed somewhere heh??? 