cancel
Showing results for 
Search instead for 
Did you mean: 
Reliable Contributor Mcafee_SWISS
Reliable Contributor
Report Inappropriate Content
Message 1 of 16

ENS: Unable to UPDATE some customer to ENS 10.6.1 DEC 1124 or 1125

Jump to solution

Hello,

We have problems with several customers (SBS or ENT) to update from ENS

10.6.1.1103 (NOV REL) to 10.6.1124 (DEC) or 10.6.1.1125 (DEC RE-POST)

* W7/W10/SRV2008R2/2012R2/2016 no difference

* Master repo. cleaned OU from 10.5.X or 10.6 HOTFIXES and PATCHES

* We can get ONLY around 1-2% of the machines W7/W10/SRV2012/SRV2016 to UPDATE to 1124

* Global Update included 10.6.X Platform, Deployment Task running, Update Task running with ENS

We have 1-2 customer who are at 10.6.1124/10.6..1125

BUT nothing there was done different.

 

I see in other posting that there may be other partners with that problem BUT Mcafee is focussin TOO much on the 1123/1125 confussion which was cleared up by Jessica in a posting.

Since this impacts around 30+ customers i an not willing to open a TICKET and do the FULL mer report

stuff for 1 x CLIENT, 1 x EPO, 1 x SRV until someones moves. We can take a closer look at any customer if someones has time and is willing to help.

Any other partners or customer see same effect?

Any help welcome.

Long time mcfafee partner,

Greetings

2019-01-24 13-09-07_local - visionapp Remote Desktop 2009.jpg

2019-01-24 13-10-22_local - visionapp Remote Desktop 2009.jpg

Deployment Task Full Version running each 2H

2019-01-24 13-11-16_local - visionapp Remote Desktop 2009.jpg

 

One client has 10.6.1.1124 ALl others not.

2019-01-24 13-07-24_local - visionapp Remote Desktop 2009.jpg

2 Solutions

Accepted Solutions
McAfee Employee jess_arman
McAfee Employee
Report Inappropriate Content
Message 9 of 16

Re: ENS: Unable to UPDATE some customer to ENS 10.6.1 DEC 1124 or 1125

Jump to solution

@Mcafee_SWISS If I'm understanding correctly, you're attempting to upgrade from ENS 10.6.1 November Update to 10.6.1 December Update? If so, the reason your efforts are failing is because it is not possible. All hotfix/minor update packages that would have allowed this type of upgrade scenario were pulled at release due to issues found in the installer scripting for the hotfixes. There is no way to upgrade 10.6.1 Nov Update until the planned 10.6.1 February Update release. If it were needed immediately for any reason, an uninstall/reinstall of the product would be your only option due to the availability of a full installer package for all 10.6.1 Dec modules.

 

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?

McAfee Employee jess_arman
McAfee Employee
Report Inappropriate Content
Message 15 of 16

Re: ENS: Unable to UPDATE some customer to ENS 10.6.1 DEC 1124 or 1125

Jump to solution

@Mcafee_SWISS  Targeted communications were sent out in December to cusotmers who we saw had downloaded the 10.6.1 December minor update packages which were pulled (and the patch package for the ATP module). We also updated release notes to outline how the full installer and patch packages available could be used.

Yes, my recommendation would be to stop attempting upgrades until the planned release of the February Update.

 

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?

15 Replies
Reliable Contributor bretzeli
Reliable Contributor
Report Inappropriate Content
Message 2 of 16

Re: ENS: Unable to UPDATE some customer to ENS 10.6.1 DEC 1124 or 1125

Jump to solution
Same here:
Customer has 10.6.1.1103 on W7 German, EPO5.9.1, Agent 5.5.1.338 and
is unable to Update/Migrate to the latest version which seems

10.6.1 DEC Release

Any help welcome and please keep us in cc.
McAfee Employee chealey
McAfee Employee
Report Inappropriate Content
Message 3 of 16

Re: ENS: Unable to UPDATE some customer to ENS 10.6.1 DEC 1124 or 1125

Jump to solution

Thank you for raising this issue however the community is not the place to be troubleshooting such issues in detail. For this please raise a Service Request and attach a procmon/ amtrace gathered during the installation attempt and a MER of the system after this installation attempt. Providing these logs will ensure that we have all needed logs and information to provide you with an analysis of why the installation/ upgrade failed.

Any findings that come of the investigation can be fed back to this community post to keep other users informed. 

Bear in mind that not all installation failures are caused by the same thing, so @bretzeli I would also encourage you to gather the same data set and provide it to support.

 

If you wish to troubleshoot the issue yourself, you can use these steps:

Open the installation log location and sort files by date and time > you'll want to look at the first installation-log present and for ENS this will be the Common Installation log first.

Open the first installation related log i.e. Common_Install.log and scroll to bottom, you will see the installation failure code i.e. “return code: 1603” (all MSI installation error codes are listed here, https://msdn.microsoft.com/en-us/library/windows/desktop/aa372835(v=vs.85).aspx)

If you do see 1603, then scroll back up to the top of the log file and search for “value 3” (the word value may be different pending on log language). The first entry you find shows you point of failure.
e.:
!> Error - SysCore install failed: 255
<= leave custom action Install_SysCore()
CustomAction Install_SysCore returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Fin de la acción 12:28:11: InstallExecute. Return value 3.
MSI (s) (98:70) [12:28:11:908]: Note: 1: 2265 2: 3: -2147287035 >> with these entries “Error - SysCore install failed: 255” and “-2147287035” you can search on the agent portal for errors

It may also point you to look at another log file, in which case you can go to the mentioned log file and search for "error" or "fail". Again you can then search for these in agent portal.

We also have a KB which might help you: https://kc.mcafee.com/corporate/index?page=content&id=KB87589

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?
Reliable Contributor Mcafee_SWISS
Reliable Contributor
Report Inappropriate Content
Message 4 of 16

Re: ENS: Unable to UPDATE some customer to ENS 10.6.1 DEC 1124 or 1125

Jump to solution

Thank you,

 

Then only 1603 i see is this one. But its marked as: "but will be translated to success due to continue marking". Maybe because he sees it's EPO managed and does not think he needs to reimport like with a stanalone ENS install?

****

15:4:54:607 - The restore setting directory: C:\ProgramData\McAfee\Endpoint Security\McAfeeSettingsBackup\
15:4:54:607 - The command for EsConfigTool util : "C:\Program Files\McAfee\Endpoint Security\Endpoint Security Platform\Upgrade\MfeUpgradeTool.exe" /import "C:\ProgramData\McAfee\Endpoint Security\McAfeeSettingsBackup\ESP\ESP_Config_Setting.xml" /module ESP
15:4:54:607 - RunCommandLine: "C:\Program Files\McAfee\Endpoint Security\Endpoint Security Platform\Upgrade\MfeUpgradeTool.exe" /import "C:\ProgramData\McAfee\Endpoint Security\McAfeeSettingsBackup\ESP\ESP_Config_Setting.xml" /module ESP
15:4:58:325 - RunCommandLine: Process return code : 4294967295
15:4:58:341 - EsConfigTool util:- Restore Settings failed : -1

****

MSI (s) (8C:A4) [15:04:58:341]: Executing op: ActionStart(Name=StopProvisioningMode,,)
CustomAction RestoreSettingUsingMfeUpgrade returned actual error code 1603 but will be translated to success due to continue marking

****

At the end of the Logfile we see:

MSI (s) (8C:A4) [15:05:30:591]: Note: 1: 1728
MSI (s) (8C:A4) [15:05:30:591]: Transforming table Error.

MSI (s) (8C:A4) [15:05:30:591]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (8C:A4) [15:05:30:591]: Transforming table Error.

MSI (s) (8C:A4) [15:05:30:591]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (8C:A4) [15:05:30:591]: Transforming table Error.

MSI (s) (8C:A4) [15:05:30:591]: Transforming table Error.

MSI (s) (8C:A4) [15:05:30:591]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (8C:A4) [15:05:30:591]: Transforming table Error.

MSI (s) (8C:A4) [15:05:30:591]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (8C:A4) [15:05:30:591]: Transforming table Error.

MSI (s) (8C:A4) [15:05:30:591]: Produkt: McAfee Endpoint Security-Plattform -- Die Konfiguration wurde erfolgreich abgeschlossen.

MSI (s) (8C:A4) [15:05:30:591]: Das Produkt wurde durch Windows Installer neu konfiguriert. Produktname: McAfee Endpoint Security-Plattform. Produktversion: 10.6.1. Produktsprache: 1031. Hersteller: McAfee, LLC.. Erfolg- bzw. Fehlerstatus der neuen Konfiguration: 0.

This looks like he does an MST Transform BUT at the end is still at 1031 Version. Which

reflects exact our problem.

 

 

Reliable Contributor Mcafee_SWISS
Reliable Contributor
Report Inappropriate Content
Message 5 of 16

Re: ENS: Unable to UPDATE some customer to ENS 10.6.1 DEC 1124 or 1125

Jump to solution

Other customer with Server 2016.

McAfee_ThreatPrevention_Install_1311201809495740.log

9:50:15:899 - File copy of msi to Repair Cache successful
9:50:15:915 - Added the Repair Cache path to source list successfully
9:50:15:915 - File setupTP.exe from C:\Program Files\McAfee\Endpoint Security\Threat Prevention\RepairCache\\setupTP.exe called for delete
9:50:15:915 - Moving file to temp failed, last error : 3
9:50:15:915 - Bootstraper copy successful
9:50:15:915 - Copy mst file failed. Source : |C:\Windows\Temp\McAfeeTmpMSTPath\1031.mst. Dest : C:\Program Files\McAfee\Endpoint Security\Threat Prevention\RepairCache\\1031.mst. Last error: 123.  Continuing...

Reliable Contributor Mcafee_SWISS
Reliable Contributor
Report Inappropriate Content
Message 6 of 16

Re: ENS: Unable to UPDATE some customer to ENS 10.6.1 DEC 1124 or 1125

Jump to solution
@chealey can you catch up on this please if we open a Ticket. I will post the Ticket number here.
I don't want to strugle with Foreign Eastern Country support with 4H.?
McAfee Employee chealey
McAfee Employee
Report Inappropriate Content
Message 7 of 16

Re: ENS: Unable to UPDATE some customer to ENS 10.6.1 DEC 1124 or 1125

Jump to solution
Yes, please share the case number and I will review the data provided and work with the assigned case owner to get a quick response for you.
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?
Reliable Contributor Mcafee_SWISS
Reliable Contributor
Report Inappropriate Content
Message 8 of 16

Re: ENS: Unable to UPDATE some customer to ENS 10.6.1 DEC 1124 or 1125

Jump to solution
Service Requests 4-19674636951
McAfee Employee jess_arman
McAfee Employee
Report Inappropriate Content
Message 9 of 16

Re: ENS: Unable to UPDATE some customer to ENS 10.6.1 DEC 1124 or 1125

Jump to solution

@Mcafee_SWISS If I'm understanding correctly, you're attempting to upgrade from ENS 10.6.1 November Update to 10.6.1 December Update? If so, the reason your efforts are failing is because it is not possible. All hotfix/minor update packages that would have allowed this type of upgrade scenario were pulled at release due to issues found in the installer scripting for the hotfixes. There is no way to upgrade 10.6.1 Nov Update until the planned 10.6.1 February Update release. If it were needed immediately for any reason, an uninstall/reinstall of the product would be your only option due to the availability of a full installer package for all 10.6.1 Dec modules.

 

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?

Highlighted
Reliable Contributor Mcafee_SWISS
Reliable Contributor
Report Inappropriate Content
Message 10 of 16

Re: ENS: Unable to UPDATE some customer to ENS 10.6.1 DEC 1124 or 1125

Jump to solution

Here we GO that's why i was asking you and not someone else.

Was this planed? "this type of upgrade scenario were pulled at release due to issues found in the installer scripting for the hotfixes" > Seams NO ;-)

What if customers are affected with ENS 10.6.1 NOV Faults which are solved in DEC Update.
Like per example 90% of our customer (And yours) who have OFFICE 2016 and a Exploit IPS Filter is blocking on some machines certain operations? And solved in DEC Update.

What about the current Problems in the Forum with Terminal Server Citrix that some seemed to be solved in the 10.6.1 DEC Update.

**bleep** happens but NONE of the employee could help until you.

* Mcafee USE Upgrade tool > No the Upgrade TOOL does not check down to NOV/DEV versions. It can only emulate and check 10.2/10.5.1/10.6/10.6.1 NOT anything behind and hotfixes or patches> Wrong recommendation?
* Check the LOGS and ANALYSE Windows Installer MST patches > NO but a good hint ;-) I am desktop engineer and found some things like table error which i don't like > However the Windows Installer Debug logs gave no hint THAT it can’t Update > Change MSP/MST and adapt so you see what happened now. OR Just DROP the Update Task in EPO.

 

Or FINALLY, oh finally change the TASK Error to something which we understand. Say CLIENT Offline (Get RED), Say (Windows Installer Pending), Say (Reboot Pending)?????

What a mess again after the mess with Actual/Previous Patch/Hotfix the last months.

Do not mess this UP. We have large extreme large TRUST in HOW EPO Deploys Software to thousands of endpoint through EPO over standing commercial Deployment tools.

Since ransomware does FORCE customers to almost deploy a NEW ENS version each month now THIS MUST work!

 

ePO Support Center Plug-in
Check out the new ePO Support Center. Simply access the ePO Software Manager and follow the instructions in the Product Guide for the most commonly used utilities, top known issues announcements, search the knowledgebase for product documentation, and server status and statistics – all from within ePO.