We have periodic password changes in our environment, which sometimes can cause account lockouts if the user has many open (or disconnected and not logged off) remote desktop sessions. This post describes a Powershell script that will help prevent this problem by logging the specified user off all machines in a particular OU.
There are various native tools in Powershell that help with logging a user off of a single remote desktop session, but they are buggy or limited. In the end the old qwinst/rwinsta commands seemed to work more reliably for me to enumerate remote sessions and log a user off.
Despite needing this functionality myself a few times, I looked around and I couldn’t find a solution that put everything together. I wrote a simple PowerShell script that will run against a domain and log a user off of all of the servers in that domain. I’ve cleaned up the code from this script a bit and made it more plug-and-play to enumerate all servers in a specific OU, prompt for a specific user, and log that one user off of all of the servers in the OU.
It does a quick ping test before attempting to enumerate sessions, but otherwise there is no error checking. Just quick and dirty.
The script is composed of two files: a simple powershell module with two commands, disconnect-wsession and get-wsession. The second file is the action script. To get it to work in your environment, edit disconnect-all-sessions.ps1 to point to the OU where your servers are located, and run the script on a machine with the AD Powershell modules installed.
The script defaults to logging off the current user and will exclude the current machine from the forced logoff.
Check out the full remote desktop logoff script on my GitHub page.
2 Comments
Chris · November 20, 2020 at 12:48 pm
Is it possible to modify this to only check servers from a list I provide?
NA · July 4, 2023 at 4:26 am
Try this with a list of servers in servers.txt file: –
foreach ($_ in get-content C:/servers.txt) {(gwmi win32_operatingsystem -ComputerName$_).Win32Shutdown(4)}