@russm @Daniel_S So to clarify, the confusion comes from the fact that the Full Installer and Patch packages for ENS 10.6.1 Dec Update had different build numbers than the minor update/hotfix package. This could lead to siginificant confusion about what was "the latest" despite them all being the same from a code-base perspective. So, there is no need to apply the Hotfix on top of the builds. Since release, all of the the hotfix packages were pulled due to confusion and issues with the differing build numbers causing repeated installation attempts on top of versions that didn't need it because it was already up to date. Below are the "latest" build numbers. Anything else, you'll need to wait for February update for newer or to upgrade systems that were on, for example, a 10.6.1 Nov Update.
Adaptive Threat Protection client | 10.6.1.1120 | PD27825 | KB82450(Firewall, Threat Prevention, and Web Control) KB88788 (ATP) |
December 11, 2018 |
Common client | 10.6.1.1124 | |||
Firewall client | 10.6.1.1106 | |||
Threat Prevention client | 10.6.1.1208 | |||
Web Control client | 10.6.1.1082 |
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?
Large Mcafee reseller here speaking for all our customer in SBS and ENTERPRISE:
Please then specify in Detail and with screenshots or seperate KB what customers should do right.
The fact that customer machines COULD get extreme slow if they try updates every hour is enough.
Do they need to adapt their Deployment jobs with complex task and queries? Only run the deployment job on machines which need the updates? How far or fast does the regular Deployment JOB from mcafee notice (Find out he does not need to update)? Why does one customer write his machines get slow (What we all don't want)
@SWISS As we've discussed, there were several unique challenges that were found with the 10.6.1 December Update that we're fully aware of and have been extensively reviewing and working on. These hurdles will be eliminated by the planned 10.6.1 February Update release.
The minor update packages for ENS 10.6.1 December Update were pulled shortly after release and are not available. Thus the only ways to get to 10.6.1 Dec Update is in scenarios similar to the following:
ENSTP 10.5.4 RTW --> ENSTP 10.6.1 Dec Update | Customer will need the Full Install Package
ENSTP 10.6.0 RTW --> ENSTP 10.6.1 Dec Update | Customer will need the Patch Package
ENSTP 10.6.1 Nov Update --> Customer will need to wait for February Update
If for some reason you are seeing build numbers for 10.6.1 December update that are different than the ones listed in the previously provided table, then you likely have the pulled minor update/hotfix packages which we do not advise be used as you will experience problems with the upgrades/updates.
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?
They totally botched December Update... I have a total mess also in ePO regarding Windows cilents... ton of Endpoinds showing status pending upgrade.. and they never upgrade.
The February 2019 update has now been released
It is a hotfix only. Not a new version.
@vandreytrindade It is an update that contains fixes and improvements, not a hotfix. Hotfixes are releases made out of cycle for specific customer issues.
It is true that this release only includes an incremental update type package, and not a full installer.
Full installers for this year are only set to be released in April and October to line up with the Microsoft Redstone OS releases.
Additional planned releases/updates for this year will come in April, June, August, and October as we have moved to an every other month cadence for ENS in order to allow customers to have an easier time keeping pace. Customer specific hotfixes can be released at any time, as needed in the interim periods between releases.
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?
Noted! Sorry!
What I tried to say is that you can't install it from scratch. Need to install the December Update and then update to the February Update.
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA