Symantec_Endpoint_Protection_14.3.0_RU3_b5427_SEPM_EN.exe

[Aleksandar Devecerski]

Hello

Noticed mentioned archive in the downloads this morning.

When extracted it looks like the new SEP Manager version (14.3.5427.3000).
No Release Notes / New Fixes / Whats-new files, nothing new in "Versions, system requirements, release dates, notes, and fixes for Symantec Endpoint Protection and Endpoint Security" Article: 154575 as well.

Could somebody please provide some more info about this.
Thank you

Regards

[atb86]

14.3.5427.3000 upgrades Log4j to 2.16.

https://knowledge.broadcom.com/external/article?articleId=230359

[Aleksandar Devecerski]

Thank you atb86.
Should clients be updated asap as well?

Regards

[VACCA ANDREA]

applyed SEPM build 5427 (14.3.5427.3000)

the 64bit client packet is disappeared from sepm
i added it manually
after few seconds it desappeared again

i rolled back to previous version of the virtual machine

[UCLAT]

ok so we will not install this and keep the fix via environment variable.

is a newer version of apache included in this version or only log4j?

will there be a fixed version which will not make client packages invisible?

[VACCA ANDREA]

very frustrating, when a solution is indeed a new problem !!!

[Aleksandar Devecerski]

Happened here as well

[VACCA ANDREA]

thanks for the feedback

can symantec release an efficient solution ?

[atb86]

I'm not an employee of Broadcom. I have upgraded two environments and none of them has the issue Andrea describes. I wouldn't hold of upgradering because one user reports a problem.

I believe this build only upgrades Log4j. An upgrade of Apache HTTPD is planned for 14.3 RU4.

[Aleksandar Devecerski]

My SEPM isn't on the virtual machine.
So now we have several client groups with 64-bit installer package unavailable.

@VACCA ANDREA
Just a question for you. In my case setup didn't perform as usual, which would be:
- add new installer packages (v14.3.5247.3000)
- leave existing installers (v14.3.5213.3000 & for Mac v14.3.4625.2000)
so there would be two sets of installers

Instead what happened was:
- Win 32/64 bit installer packages got their versions upgraded -> the same package name remained, the same version "14.3 RU3", but 'Latest Update' column showed "Build 5427 added on 16. December 2021, 11:45:25 CET"
- new Linux installer package was added, and
- Mac installer remained the same (client upgrade dialog showed something like "Latest Mac installer package already present")

So, after successful setup (no error messages or anything else unusual) the situation was:
- Win 32bit installer: only new (v14.3.5247.3000)
- Win 64bit installer: only new (v14.3.5247.3000), which latter disappeared
- Linux installer: both old (v14.3.5213.3000) and new (v14.3.5247.3000)
- Mac installer: only old (v14.3.4625.2000)

Win 64bit installer disappeared a little later with "The binary file[3D8DF15E2538192938ECBE2ED6D8009B] referred at the physical file[8D9A82E2F1D6A7E2FB6D1DA561EA6B30], which is referred at the software package[81CA5865545747AFC6FC6F68B70E37C0,SEP v14.3.5427.3000 (RU3) for WIN64BIT], does not exist. [Site: Site s-006] [Server: s-006]" message in Database Server log.

Is that what happened in your case as well? ​

[VACCA ANDREA]

exactly the same that i saw on my server

[Aleksandar Devecerski]

So, outside SEPM 14.3.5213.3000 re-install, followed by database restore, is there anything that could be done to remedy this?

[VACCA ANDREA]

i can't help you on this
i recovered the entire HD of my virtual machine

[UCLAT]

after upgrading it looks like this:


no error about missing files. but why is this release dropping build 5413 windows client setup packages. whats the difference between client build 5413 and build 5427?

is it required to update all installed clients now to build 5427?

ok i was too fast. after deleting the older linux build and the older mac os build. i got this

so for now i have no 64 bit windows package to deploy.

and


so looks like the upgrade breaks more than it fixes.

please broadcom fix this. also is it possible only to replace to old log4j package in the previous sepm build with the one from that package? or will this not work?

[VACCA ANDREA]

hi

exactly the same that i saw on my server

very very bad !

[UCLAT]

ok. when i try to add the packages again. it shortly appears, but when doing an update of live update content it disappears again.

[VACCA ANDREA]

yes

it is so also for me

[Vladimir Cihlar]

Mee too.

[UCLAT]

we had this issue that packages disappeared and logs with binary file xxx does not exist appeared when we tried to update from a 14.3 ru2 build to build 14.3 ru3 build 5413 (14.3.5413.3000).

we could only fix this when making a complete new installation with build 14.3 ru3 build 5413. so as they were only fixing log4j in v14.3.5247.3000 this bug when updating with this version may still be present.

that's not so good.

see also anyone already installed RU3 ? | Endpoint Protection (broadcom.com) 

[UCLAT]

where are the updated tools? no cleanwipe tool in the file

[atb86]

https://knowledge.broadcom.com/external/article?articleId=178870

[John Rather]

Well, just tried to install the patch and it failed roughly 50% through - now my SEPM service will not start - I opened a case.

Thanks,

John R.

[atb86]

I have made the upgrade on yet another SEPM instance and it also works without issues. You guys should open cases with support for further investigation.

[UCLAT]

ok. as long as i'm not trying to delete the old mac and linux packages. everythings seems ok. 


do you  also have 2 linux packages and 2 mac packages on your manager?

edit:

after deleting Linux Package Build 5413 the Win64 Package disappears.

[atb86]

Yes

[UCLAT]

additional test (vmware snapshot is a great feature).

keeping the 5413 linux build and deleting mac 14.3 ru2 packages keeps everthing fine. so deleting linux build 5413 will corrput things.

can someone verify this and check if i'm correct?

[Aleksandar Devecerski]

Being one of those not having SEPM on VM, to test this, I first added 5413 Linux installer (although 5427 was already present) and then re-added 5427 Win 64bit. It's been an hour now, it is still there!
Forced upgraded couple of clients, no issue to report. Everything went OK. What's more, after 5413 -> 5427 upgrade no reboot neccessary.

Thank you for sharing this with us UCLAT​​​

[Vladimir Cihlar]

This solution fixed my problem.

[Aleksandar Devecerski]

Upgraded SEPM RU3 Refresh (5427.3000) -> RU4 (7388.400). No issues to report.
Glad to report that "disappearing Win64 installer package" issue seems to be resolved. Couple of hours passed and, even with only one Linux installer package present, Win64 installer is still in the list and available.
Couple of test clients deployed as well. Everything seems OK so far.

[DAVID MATTHEWSON]

RU4? - where did you find that pls? Not listed at https://knowledge.broadcom.com/external/article?articleId=154575

I thought that page always gave the latest updates - is there somewhere better to look?

Thanks

​

[Aleksandar Devecerski]

Every once in a while I check my Download Management page. Yesterday I've noticed RU4 (released on Jan 31st), downloaded, installed and testing now.
After download I found 'What's new for SEP 14.3 RU4" and "SEP 14.3 RU4 Installation & Administration Guide" pages, but nothing in "Versions, system requirements, release dates, notes, and fixes for Symantec Endpoint Protection and Endpoint Security" you mention. I guess these articles will be updated in the next few days

[atb86]

That's pretty common that the information around a new release is updated a few days after the actual release.

You can find information about new fixes at https://knowledge.broadcom.com/external/article?articleId=233280.

[DAVID MATTHEWSON]

Thanks for that - now found it in my entitlement..

[Justin Moe]

I also am seeing the sepm removing the win64 5427 build being removed from the available clients.  Even after reimporting it from the install package files, it disappears from view.

I'm going to leave another VM with the old installer files intact from the previous version and see if the same thing ends up happening over the weekend

------------------------------
I touched it last, so I'm the "AV Guy"? Great....
I don't represent my employer
------------------------------

[John Rather]

This has been resolved...

[UCLAT]

additional issue. we are on premise only but when clicking at advanced security we got:


with build 14.3 MP1 this looked like


so I'm not sure if this is an issue

[atb86]

That should have already been resolved via Live Update on the 11th. 

https://knowledge.broadcom.com/external/article?articleId=230070

https://knowledge.broadcom.com/external/article?articleId=230078

[UCLAT]

thank you for clarifing this. will have a closer look on this and maybe open a case.

[Luis Ontiyuelo]

CleanWipe in Tools has not been updated
what a mess.. 1 thing to fix, 4 new issues coming up

[Luis Ontiyuelo]

I see now it's here:

https://knowledge.broadcom.com/external/article?articleId=178870

but should be packaged from the beginning where it corresponds.

[Luis Ontiyuelo]

Hi all,

Symantec_Endpoint_Protection_14.3.0_RU3_All_Clients_EN.zip

This is including the following, but Linux packages are not present:

How can I get Linux binaries to import in the SEPM? I installed SEPM 14.3 RU3, but Just got this about Linux:

Where are DKPG and RPM packages for 14.3.5427.3000? what is that LinuxSTUB?

Thank you.

[Torsten Knorr]

Starting with SEP 14.3 RU1 there is a new Linux agent based on DCS agent.

The old packages can be imported, download the client package source file and you will find them there.

The new agent has some benefits, but before testing or implementing, please read the release notes, especially the need for a connection to Symantec Repo or the capability to clone this Repo for local install.

[Luis Ontiyuelo]

Hi Torsten,

"The old packages can be imported, download the client package source file and you will find them there."

That's what I've done and they are missing in the SEPM full package and in the " Symantec_Endpoint_Protection_14.3.0_RU3_All_Clients_EN.zip"

How and where can I find new Linux installer packages to import in the SEPM 14.3.0_RU3 ?

Thank you.

[Torsten Knorr]

The new Linux installer is only 4 MB.

I checked again the Client package download and the new linux installer: Symantec Endpoint Protection version 14.3.5427.3000 for LINUXSTUB

This is only a script which downloads the sources from Broadcom directly and leads you to:

https://linux-repo.us.securitycloud.symantec.com/sep_linux/.../...

If you know how to clone a repositories, you can **** copy it and use it for your inhouse installations.

The SEPforLinux Admin Guide describe this very good. 

Kernel-Module Updates are now easily possible over this repo.

If you use LUA, you need to enable additional client content for this new client.

[Luis Ontiyuelo]

Hi Torsten,

thank you for your response,

I can see what you mention, here:

https://techdocs.broadcom.com/us/en/symantec-security-software/endpoint-security-and-management/endpoint-protection/all/getting-up-and-running-on-for-the-first-time-v45150512-d43e1033/installing-clients-with-save-package-v16194723-d21e1502/installing-the-client-for-linux-v95193124-d21e2986.html