Solved! Go to Solution.
Dear @Glenn_Bolton
I would like you to know that the new extensions for ENS are released on 12th March.
Endpoint Security Platform extension |
10.6.1.1105 |
Endpoint Security Threat Prevention extension |
10.6.1.1107 |
Endpoint Security Firewall extension |
10.6.1.1088 |
Endpoint Security Web Control extension |
10.6.1.1089 |
Endpoint Security Adaptive Threat Protection extension |
10.6.1.1084 |
I would like you go through the below documentation for your clarification.
If the above information is helpful, you may accept this as a solution.
@Pmaquoi If you have Linux and Mac clients you want to install the 10.6.1 version of the extensions that were just released March 12th. The reason the version numbers are different is because the core extensions--upon which ENSL and ENSM are dependent--are versioned in line with the Windows version. ENSL and ENSM are dependent upon these extensions, even though their build numbers differ.
In order to allow for the new features in the latest 10.6 releases of ENSL and ENSM (released 3/12/19), the mainline extensions (10.6.1) had to also be updated despite there being no Windows ENS release in March.
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?
Dear @Glenn_Bolton
I would like you to know that the new extensions for ENS are released on 12th March.
Endpoint Security Platform extension |
10.6.1.1105 |
Endpoint Security Threat Prevention extension |
10.6.1.1107 |
Endpoint Security Firewall extension |
10.6.1.1088 |
Endpoint Security Web Control extension |
10.6.1.1089 |
Endpoint Security Adaptive Threat Protection extension |
10.6.1.1084 |
I would like you go through the below documentation for your clarification.
If the above information is helpful, you may accept this as a solution.
Thank you.
I was able to locate the pdf file which provided information regarding the newly released extensions.
Regards.
@Glenn_Bolton The extension updates were released in order to support new features that came in the new 10.6 ENS for Linux and 10.6 ENS for Mac releases that were also released this past Tuesday. ENS for Linux and ENS for Mac are dependent upon the ENS for Windows extensions, and so this is why the ENS 10.6.1 "mainline" extensions had to be updated to accommodate that.
You can update the extensions if you like, but do not need to if you don't want to or don't use 10.6 ENSL or ENSM.
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?
Have the same question but would like a more precise answer. sorry but there is still a confusion i think
the same daywe have twoversion of the same extension. One for the feburary update and one for the Linux / Mac update. So the question is. Do the Mac / linux extension contains the february update change too ? I read the docs and it is not clearly mentionned.
so to be clear, if you have both windows and linux client on an ePO, you have to install the linux and MAC version of the february extension instead of the legitime ens february upodate extension.
If correct, isn't it a little bit (or more than a little bit) a mistake because it is the same extension published in two different version numbers for all module the same day.
This could confuse the customers.
Thank you.
I was able top locate the pdf file which provided information regarding the newly released extensions.
Regards.
@Pmaquoi If you have Linux and Mac clients you want to install the 10.6.1 version of the extensions that were just released March 12th. The reason the version numbers are different is because the core extensions--upon which ENSL and ENSM are dependent--are versioned in line with the Windows version. ENSL and ENSM are dependent upon these extensions, even though their build numbers differ.
In order to allow for the new features in the latest 10.6 releases of ENSL and ENSM (released 3/12/19), the mainline extensions (10.6.1) had to also be updated despite there being no Windows ENS release in March.
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?
To make it EVEN more clear:
a) Currently MCAFEE ENS and VSE with TIE (With certain rules) have a massive problem with the 04/2019 windows Updates. This is BECAUSE Microsoft changed something and did not tell OR Mcafee has used soemthing in the grayzone to make Mcafee faster and did not understand why Microsoft releases the PREVIEW Updates (You had 14 days of TIME to test right?)
All customer stopped installing the 04/2019 and HIGHLY and dialy are lokking for an update and sign from MCAFEE (And also other producers of Antimalware software)
v) The EXTENSION Update is confusing and in THESE times should be detailed more with INFO.
So:
If our 50 customers DO NOT have and manager any LINUX/TUX/APPLE Endpoints nothing has to be done related the shortly released EXTENSION Updates? Is that correct and do we understand that right?
Regards
Mike
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.
Thousands of customers use our Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership: