[client Security] Variable %userprofile% not recognized in firewall rules

Valerie_K
Valerie_K Posts: 6 Observer
edited April 6 in Business Security

Hi,

I try to create a rule which allows the execution of an exe file according to few criteria.

The exe file is in a directory under %userprofile%\AppData.

When I create the rule, after the remote adress, in the "application path", If I put %userprofile% in the path, the exe file is not found.

If I put exactly the path of the file - ie c:\users\martin.luther\Appdata, it works (but it's not the solution because on each PC, it's under a different directory).

Is there a way to find a solution ?

Regards,

Valerie, Paris, France

Accepted Answer

Answers

  • Jamesch
    Jamesch Posts: 357 Moderator
    edited May 2022

    Hi Valerie,

    Just to clarify - are you wanting the .exe file to be removed from scanning, or is our product blocking it ?

    The format %USERPROFILE% is not supported format. Advise to use wildcard as following. 

    Please configure 

    C:\*\AppData\*
    

    instead of 

    %USERPROFILE%\AppData\
    


    Jaims
  • Valerie_K
    Valerie_K Posts: 6 Observer

    hi Jamesh,

    I've tried what you mentionned but it didn't work.

    On the PC , I get an alert like "failed to upload rules"

    --> is there another solution ?

    Regards,

    Valerie

  • Valerie_K
    Valerie_K Posts: 6 Observer

    Jamesh,

    OK. I open a ticket to the support team.

    Regards,

  • JachymM
    JachymM Posts: 7 Explorer

    Hello,

    is there anything new on this case? I would like to use %USERPROFILE% to configure Defender firewall rule via FS PMS too. Is this variable supported for the Defender FW rule?

    Jamesch, mentioned scanning exception syntax but I mean firewall application configuration to allow traffic through Defender FW.

    Regards,

    Martin

  • Jamesch
    Jamesch Posts: 357 Moderator

    Hi Martin

    Currently user-specific variables are not supported for Firewall, it is under development, and may be included in the next release.

  • Valerie_K
    Valerie_K Posts: 6 Observer

    Martin,

    I've opened a support ticket. In fact, it doesn't work : It's a limitation of the Windows's firewall.

    You must create a "traditional" rule with ports and protocols.

    Regards,

    Valerie

This discussion has been closed.