Update to 5.10.0 Service Pack 1 BUILD 4098
There is an issue with EPO 5.10.0 Service Pack 1 RE-Post.
We have seen some EPO 5.10.0 Service Pack 1 gone through smooth and some larger EPO fail. Trellix member CDINET from Trellix Forum stated a tip how to install sucessfully.
Here is how to solve the update. Worst the MSI Installer rollback does not work and keeps the EPO in a state of not working. Thus it is important to have a Hypervisor FALLBACKUP or VEEAM if this fails.
Make sure you install all PRE SP1 Updates UP TO “ePO_5.10.0_Update_15” (This are add. steps and we asume your ARE at level UPD15 already for the SP1). Please see Trellix KB
On how to get to those Patche Update 15 Level.
Process to patch EPO 5.10 to latest Service Pack 1 from 5.10 UP15 succesfully:
Backup all you have because we have a high % this will fail. It’s re-post Patch they already took back once.
Turn off/Shutdown all Mcafee/Trellix machines you have (EPO, DXL, Broker, TIE etc.)
Logon to TIE and DXL broker Console or SSH and use “shutdown –f 1”
Make a VM Snapshot for disaster fallback. The snapshot should be OFF and at same time because of DXL (If you use DXL)
Start all VM machines
On EPO Server disable the two WMI related Services
- WMI Performance Adapter (ENG) or WMI-LeistungsadapterService (DEU) name “wmiApSrv”
- Windows Management Instrumentation (ENG) or “Windows Verwaltungsinstrumentation” (DEU) or Service name “Winmgmt”
Reboot the EPO Server
Install SP1 will be success
Change back the two WMI Services as seen in Screenshot
Services before:
change to disabled/deaktiviert:
Reboot once
Check Events
Change back the Services like they where before
Services before:
If you want to 100% sure check the Logs
trail |
2023-06-07T10:54:26.226Z – info: Executed batch sql scripts for snapshot 2023-06-07T10:54:26.262Z – info: Successfully got connection 2023-06-07T10:54:26.266Z – info: Successfully got connection 2023-06-07T10:54:26.276Z – info: Successfully got connection 2023-06-07T10:54:26.290Z – info: Successfully got connection 2023-06-07T10:54:26.302Z – info: Sucessfully executed SQL DELETE FROM [dbo].[EPOSnapshotFiles] WHERE [FilePath] = ‘/simagent64.exe’ 2023-06-07T10:54:26.302Z – info: Successfully deleted entries EPOSnapshotFiles 2023-06-07T10:54:26.303Z – info: Sucessfully executed SQL DELETE FROM [dbo].[EPOSnapshotFiles] WHERE [FilePath] = ‘/eposignle.exe’ 2023-06-07T10:54:26.303Z – info: Successfully deleted entries EPOSnapshotFiles 2023-06-07T10:54:26.315Z – info: Sucessfully executed SQL DELETE FROM [dbo].[EPOSnapshotFiles] WHERE [FilePath] = ‘/simagent.exe’ 2023-06-07T10:54:26.315Z – info: Successfully deleted entries EPOSnapshotFiles 2023-06-07T10:54:26.317Z – info: Sucessfully executed SQL DELETE FROM [dbo].[EPOSnapshotFiles] WHERE [FilePath] = ‘/eposignse.exe’ 2023-06-07T10:54:26.317Z – info: Successfully deleted entries EPOSnapshotFiles 2023-06-07T10:54:44.004Z – info: Service EPOEVENTPARSERSRV status is started 2023-06-07T10:54:55.599Z – error: Service start error :Error: Timed out attempting to start EPOAHAPACHESRV. 2023-06-07T10:54:55.709Z – error: Service start error :Error: Timed out attempting to start EPOAHAPACHESRV. 2023-06-07T10:55:05.723Z – info: Service EPOTOMCATSRV5100 status is started 2023-06-07T10:55:05.821Z – info: Determining if service EPOAHAPACHESRV is started or not 2023-06-07T10:55:16.299Z – info: Service EPOAHAPACHESRV status is started |