When a user is able to exclude their personal desktop from auto-scale, it should also exclude the user session's MaxIdleTime & MaxDisconnectTime. without this in place, if a user has a process going on under their profile, it will simply disconnect and logoff the user making the exclusion useless. ideal scenario would be that when a user excludes themselves of Auto-Scale, both these registries should be over-written and based on the timeline the user adds exception, the registry keys would be written back to the hive and resume the auto-scaling & disconnect/logoff ability on the session host.
Session Timeout over-ride when using Exclusion from Auto-Scale (Completed)
3
what i have done as a workaround is to create a custom script and educating user to run that script when excluding from auto-scale. here is what the script is supposed to do
- remove the 2 registry keys from hive
- add the registry keys into a powershell script and save the script locally on the VM
- create a scheduled task to run the powershell script n+1 days after the script is run. where n is the max number of days allowed for auto-scale exclusion
- the scheuled task is supposed to run at that specific time OR anytime after when the user logs back in, in case the VM is powered off when the scheduled task was supposed to run.
need to do some more tweaking to the script but that is the only work around i could get where i could get users to exclude themselves from session timeout limits and auto-scale and then put it back on.
Please sign in to leave a comment.
Comments (1 comment)