This message was deleted.
# _general
s
This message was deleted.
👍 1
j
UPD in 2020??? Its FSLogix time my friend 🙂
⤴️ 1
a
you are right , we are planning to migrate to fslogic soon . Do you think UPD is the problem ?
m
Windows firewall enabled? Sounds like you have a sh*t load of firewall rules. This is a common issue with firewall enabled and UPD
a
yes , firewall enabled
on each host the default config + some rules for internal applications
m
Please check the amount of firewall rules on one of your rds host.
a
i have only see that each host has the default rules x the number of the users logged in
m
that sounds ok
a
ok
m
Do you have set this key as well? HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DeleteUserAppContainersOnLogoff (DWORD) and set it to 1
a
let me check
no i dont have it
so this key delete the user firewall rules when it log off ?
m
Yes and cleanups up the cached rules created during user logon in the UPD
a
if the user are just disconnect and wont log off ?
m
Don’t know if its still requred for 2019. But for 2016 it’s a best practice
a
thanks for the tip
m
You’re welcome
p
This was a bug in Server 2016 that took Microsoft two patch runs to "fix" but then required this registry key to make the fix "work". 😛 EDIT: "This" being the user profile aggregation of firewall settings for each session they had/have on all session hosts.
It was a real pain. 😞
a
this is why we love MS
thanks philip for the info
j
Wonder if you have potentially hit a vhd mounting bug here - vaguely recall seeing something similar in 2016 where a scheduled reboot resolved it, don’t think we ever got to the bottom of it :-(
a
no nothing like that