AGENT 5.7.9 x FRP

[JiriCZ]

Hello, We have deployed Agent 5.7.9 and now We hase problem with FRP.
We are using User-based policies for FRP but now after Agent update FRP is not getting right policies and is stuck in Block Write Operations for Removable and Optical media Policy.
If i change policy assignment in ePO manualy than the right policy is applied for FRP.
We tested new Agent with FRP 5.4.2/3/4 and having the problem on all versions.

Now we have roolback for Agent 5.7.8 and everything works fine.

Has anyone experiencing the same?
Thank you

[cdinet · Accepted solution]

That is a known issue with the agent.  Please follow the workaround in the following kb:

https://kcm.trellix.com/corporate/index?page=content&id=KB94448

[tttt1]

@cdinet

"known" where? I did not find any info about it in KB's.

Can this "workaround" be elaborated? What exactly LPC:1 will do? It's quite peculiar that workaround from agent 5.6 is going to be applicable to 5.7.9

[cdinet]

It is listed in the MA known issues kb - KB93773.  That workaround tells the agent to use lpc instead of msgbus for the agent to communicate to FRP.  It is applicable to 5.7.9 agent also and is known issue to development.

From the kb:

5.7.9

-

Issue: After an upgrade to TA 5.7.9, the FRP policies don't apply through the Policy Assignment Rule (User-Based Policy). Workaround: Follow the workaround in KB94448 - User-Based Policies aren't processed after you upgrade to File and Removable Media Protect... and reboot the client machine.

[JiriCZ]

Can you please send me link where are known issues and this one is there described? 
I can find only this one and there is no issue about MA 5.7.9
https://kcm.trellix.com/corporate/index?page=content&id=KB93773

[tttt1]

Indeed workaround fixes issue for now. thanks for info.
Anyway looking for permanent solution.

Edit:
@JiriCZ 
there is info under non-critical at the bottm in "Investigating" section

[cdinet]

There is a fix being worked on for it and we will let you know when we have more info on it.  I believe they have sent it to qa for testing, but that is all the info I have for now to share.