why "%LOCALAPPDATA%\Microsoft\Teams\current\Teams.exe" not possible in FW policy?

[HSW 9]

Hi, why i cant use this in firewall policy?

I need to setup to many ports and IP ranges for MS products, so why you use this not like normal?

Actual the server translate this to "C:\Windows\ServiceProfiles\Networkservice\Appdata\Local\..."

MS365 mostly work over Userprofil so please provide a solution.

 

thanks HSW

[Marcos 5,070]

That's because the variable resolves so under the system account. There could be more user accounts on the machine so an individual rule would have to be created for each, even for the users that might be created in the future.

[HSW 9]

Sorry but i write about a 700 account domain, this is not useable.

[HSW 9]

we want to use ESET Security as second protection possibility additional to our Hardwarefirewalls.

[Marcos 5,070]

While it's not possible to use wildcards in the path of firewall rules, a solution should be available later this year, most likely in Endpoint v11.

[HSW 9]

1 minute ago, Marcos said:

While it's not possible to use wildcards in the path of firewall rules, a solution should be available later this year, most likely in Endpoint v11.

thanks for this information, than i will hope for this