Correct me if I am wrong but If you have ENS 10.6 checked in your evaluation branch then the extensions for it apply to "current" and "previous" branches... Therefore if you are actually using ENS 10.5.4 it is impossible to import monthly updates for extensions because you will always have a higher version checked in already... even though it was published months before:
This makes me wonder, why is there monthly patches for ENS 10.5 and not for ENS 10.6... ? Second, if McAfee felt the need to fix something in extensions for 10.5 how can I be confident those fixes already existed 3 months ago for 10.6 ... is it really safe to deploy and manage September security updates for ENS 10.5 when we are stuck with June's ENS 10.6 extensions?
Things that make you go hummmmcafee. 😉
I have the exact same concerns. I upgraded to 10.6 for some testing, and now none of the 10.5 extension hotfixes are able to be installed since 10.6 will always be the "more current" version.
I opened a ticket with McAfee for this and they claim that the extensions are backwards compatible, which is expected, but what about the tiny tweaks/fixes made to the 10.5 extensions that I am missing out on with the 10.6 extension from June?
If you have 10.6.X extensions checked in, then you cannot check in updated 10.5.X extensions because the Service Pack version number is higher.
I would make sure to update to the 10.6.1 extensions if you're managingin 10.5.4 September Update with 10.6.0 extensions.
I can't say if you will experience a problem, however, it is more likely for you to experience an issue when managing a newer version of the product with older extensions.
Sometimes it's not a huge deal because the only thing you're really missing out on are new features/settings added in the latest extensions. However, the older versions of the product can't necessarily make use of the new features/settings because it wasn't incorporated in that version of the product. In which case, it's not a huge deal. However, it's always best practice to update extensions to a version that was released with the latest update or in this instance I would install a version of 10.6.X that was released at the same time/after 10.5.4 September Update.
Refer to the ENS Supported environments KB: https://kc.mcafee.com/corporate/index?page=content&id=KB82761
Typically we release the 10.6.0 monthly fixes on the same cadence as 10.5.4, assuming that there aren't any problems identified that cause us decide to make the updated a "Support Managed Release".
Aye, with our Windows 10 rollout, we needed either 10.5.5 or 10.6.1, so I made the jump to 10.6.1 as that was the currently recommend upgrade path for 10.6.
Using the opportunity to upgrade all of our point products to the latest current versions.