This message was deleted.
# _generals
Slackbot
02/08/2022, 10:54 AMThis message was deleted.
j
James Rankin
02/08/2022, 11:04 AMYes, just use idle timeouts - all options discussed here https://4sysops.com/archives/securing-timeouts-in-remote-desktop-session-host-rdsh-and-virtual-desktop-infrastructure-vdi-environments/
đź‘€ 1
t
Touseef Rehman
02/08/2022, 3:38 PMCheers James - Stupid question I can use the policy on local machines non VDI/RDSH so regular local profiles , I presumme it's applicable to all types - if not I foudn this tool which looks pretty nippy - https://github.com/lithnet/idle-logoff
j
James Rankin
02/08/2022, 3:39 PMOh they're physical, not sure in that case. I guess you could install the VDA on them but just not use it.......
t
Touseef Rehman
02/08/2022, 3:45 PMHorizons installed on all the devices
j
James Rankin
02/08/2022, 3:46 PMDo they have similar policies to those that Citrix use?
t
Touseef Rehman
02/08/2022, 3:57 PMPossibly its an onprem vdi solution - non persistent horizon 7x , I guess I could check the policies in controlup , I may try the tool instead we can push it out via sccm after I've tested it assuming it works.
Touseef Rehman
02/09/2022, 10:50 AMGot this back from systems after my idea what they don't seem to get is on average 1 to 3 users login to these critical downtime machines, and on average there are logins going back to mid December say 80 logins across 125 machines where users should have signed out! so if they disable fast user switching and someone remains logged on do you have to force reboot the PC? if so this would break the sql as it's constantly syncing with the midtiers 247 lol - "
"Disabling Fast User Switching would (iirc) mean that the “switch user” option on the login screen is removed. Doing this would mean we would never be in the position of having to logoff multiple accounts because they are inactive. "