[Issue]: New SEP client (14.4 RU6) not recognized by the script

[philipp-mair-acp]

Describe the bug

Hello,
one of our customers just upgraded Symantec Endpoint Protection from version 14.4 RU3 to 14.4 RU6.
The part of BISF (10_PrepBISF_AV-SEP.ps1) was running fine before but now it's not running because the script doesn't detect SEP.
I noticed that after the upgrade the program path changed from C:\Program Files (x86) to C:\Program Files. I tried changing the path in line 71 and 248 but the script still doesn't detect the client.

It also looks like the Vietool has now been renamed to vietool64.exe
Is there anything else to modify?

Regards,
Philipp

Steps to reproduce

Running BISF on a server with SEP 14.4 RU6

Expected behavior

BISF should be able to detect the SEP client if it's installed under "C:\Program Files" instead of "C:\Program Files(x86)"
Also, the new name of vietool64.exe should be updated in the script.

Screenshots

No response

Desktop, please complete the following information.

No response

Smartphone, please complete the following information.

No response

Additional context

No response

[matthias-schlimm]

Is there some vendor informations that you can share in addition.

I can reference to this only https://techdocs.broadcom.com/us/en/symantec-security-software/endpoint-security-and-management/endpoint-protection/all/using-in-virtual-infrastructures-v57269588-d81e6/how-to-manage-the-license-count-for-non-persistent-v75347177-d81e1218.html

[philipp-mair-acp]

I found only this information in the release notes: 14.3 RU6 no longer supports computers that run the Microsoft Windows 32-bit operating system. 32-bit computers should run the 14.3 RU5 client.

https://techdocs.broadcom.com/us/en/symantec-security-software/endpoint-security-and-management/endpoint-protection/all/release-notes/Whats-new-for-Symantec-Endpoint-Protection-14-3-RU6.html

I could ask the customer to open a case to get more information if that helps?

[matthias-schlimm]

A case at the vendor will be great , thank you.

Awaiting your feedback

[philipp-mair-acp]

Hi Matthias, unfortunatelly the case didn't really help. All we got is that there are new paths and new file names:

• Program Directory is now "C:\Program Files\Symantec"
• Registry Key is now HKLM\Software\Symantec\ (instead of WOW6432Node)
• Vietool is now "vietool64.exe"

Can you maybe give us a hint which parts of the script should be changed?

[philipp-mair-acp]

Was finally able to test Fix #371 and it works like a charm. Thank you :)

[trondr]

I added two commits to the pull request #379 to correct an exception thrown by Test-Path on machines where SEP is not installed.