Minimum 10.6.1 extensions requrired to manage ENS 10.5.5 with May 2019 update

[McDuff]

Greetings!

Just wondering if we need to upgrade our ENS 10.6.1 extensions to the May 2019 versions if we're planning to manage ENS 10.5.5 with the May 2019 update installs, in preparation for Windows 10 1903.

Currently, we have the following extensions checked in:

1. ENS Platform at 10.6.1.1038
2. ENS Threat Prevention at 10.6.1.1046

It's a little confusing that we have the 10.6.1 extensions yet we only have 10.5.5 installed but my understanding is the extensions are backwards compatible with older versions of ENS.  The question is do we need to apply the May 2019 update extensions for 10.6.1 in order to manage the May 2019 update for ENS 10.5.5.

According to https://kb.mcafee.com/corporate/index?page=content&id=KB82761 the minimum extension versions for 10.6.1 May 2019 update are:

1. ENS Platform: 10.6.1.1177

2. ENS Threat Prevention:  10.6.1.1171

I guess to be safe it would make sense to upgrade the extensions.

[jess_arman · Accepted solution]

@McDuff The 10.6.1 May Update extensions are backwards compatible to all 10.5.5 builds, so you're good to run those and deploy either 10.6.1 or 10.5.5 May Update!

Please keep in mind that until the 10.6.1/10.5.5 full installer packages are made available on July 2nd, you will need to upgrade ENS to 10.5.5 May Update before you upgrade the OS on the endpoint to 1903 in order to be compatible.

After the full installers are available, you'll be able to deploy fresh directly to a 1903 system.

Was my reply helpful?

If this information was helpful in any way, or answered your question, will you please select "Accept as Solution" in my reply, or give kudos as appropriate, so together we can help other members?

[McDuff]

Thanks very much that answers my question, we do need to apply the 10.6.1 May 2019 extension update.

And looking forward to the full installer packages!

[jess_arman · Accepted solution]

To manage 10.5.5 May Update, you should apply the 10.6.1 extension update, yes 🙂