LazyTS is a PowerShell script to manage Sessions and Processes on local or remote machines. It allows you to Query/Disconnect/Stop session(s), Query/Stop process(es) and Send Interactive message to one or more sessions.

This tool is using the module PSTerminalService which relies on the Cassia .NET Library.I used Sapien PowerShell Studio 2014 to which make life easier if you want to start building WinForms tools and add PowerShell code.

Version

1.1 Update

Add support for RDP Shadow (View and Control)
Add small highlighting util
Fix some minor bugs

Highlighting util

Remote Desktop (Shadow View and Control)

1.0 Initial version

Features

Session Management: Query/Disconnect

Stop

Processes Management: Query/Stop
Message : Send message to Session(s)

Requirements

PowerShell 3.0
Cassia Library (included in the download)

LazyTS is relying on the Cassia .NET Library (A DLL file). This file need to be present in the same directory as the script (Either when you use the PS1 or EXE file)

Of course you also need the appropriate permission on the remote machine to be able to manage it.

If the Cassia.dll is not present, the script won't start:

Download

TechNet Gallery
GitHub: LazyTS Repository

Features

Querying session on local or remote machines

After entering the ComputerName, click on the button Sessions

Disconnecting Session(s)

Select one session or multiple sessions and right click, click on Disconnect Session
This will only disconnect the user, its session State will become "disconnected", but will remain opened on the host.

When getting disconnected, the user will get the following window

Your Remote Desktop Services session had ended.
Your network administrator might have ended the connection. Try connection again, or contact technical support for assistance

Stopping a Session(s)

Select one session or multiple sessions and right click, click on Stop Session
This will close the session of the user without warning. Any current work in progress will be lost.

Here is the confirmation window after you select "Stop Session"

Querying Processes

After entering the ComputerName, click on the button Process.
This will list all the running processes (for all sessions)

Stopping Process(es)

Select one process or multiple processes and right click, click on Stop Process
This will Stop the process(es) selected.

Confirmation Window

Sending Message(s)

After entering the ComputerName, click on the button Message.
Note that you must select one session or one process in order to use this option (the script need to know which session(s) it should send the message to.

This will Send a message to the selected session. If multiple sessions are selected only one message will be sent to each session.

Confirmation windows

Message to send

Default message: "IMPORTANT: The Server is going down for maintenance in 10 minutes. Please save your work and logoff."

Example of message received by each session selected

Remote Desktop: Shadow

When right clicking on a row you'll have the possibility to open a Shadow RDP on a selected Session ID. After you request to View or Control the session, the user will get this message

"<Domain>\<samaccountname> is requesting to control your session remotely. Do you accept the request"
Message showed to the user when trying to control his session id.

If the user deny the request, you'll get the following message

"The operator or administrator has refused the request"

Using the tool

Launching the tool from the PS1

Launching the tool from the EXE

Frequent issues

Loading Error: Unable to find type [Cassia.Impl.TerminalServicesSession]. Make sure that the assembly that contains this type is loaded.

Verify that you have at least PowerShell version 3.0

Verify and Unblock the files if needed
When you download file from internet they are blocked by default.

Unblock the zip before you extract the content or unblock each files

LazyTS.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170.

Verify you PowerShell Execution Policy

If you are using the ExecutionPolicy 'Restricted', you might get this error.
See the link below to help you choose the appropriate Policy. (in my case I user RemoteSigned)

http://technet.microsoft.com/en-us/library/hh847748.aspx

"Exception calling "Set_Item" with "2" argument(s): "Cannot set Column 'CurrentTime' to be null. Please use DBNull instead.""

Solution: This is fixed in the last update of v1.1. Download from TechNet or GitHub

"This computer name is invalid"