Edit1 Summary
With ScreenConnect setup its important to understand how a guest (client/customer) and host (technician) interface with the software. There are several supported methods of joining and hosting ScreenConnect support sessions. This INFO article will outline the options and requirements for the guest and host as it relates to the standard ScreenConnect remote support sessions (Attended). Remote Access Sessions (Unattended) are covered in
HOWTO-0007 Unattended Sessions.
Edit2 More Information
Edit2.1 System Requirements
Basically any computer/server that can connect to the internet can be controlled remotely via ScreenConnect. The primary requirements our system looks for when establishing the connection is the presence of .NET 2.0+, or the Java Runtime Environment (JRE) 1.5+. A complete list of specifications can be found at
INFO-0008: ScreenConnect System RequirementsIf you would like to verify you have either the .NET Framework or the JRE installed, go to the
Control Panel, then
Add or Remove Programs and check
Currently installed programs.
Edit2.1.1 Guest Machine Requirements
The guest client is cross-platform compatible, and there are some slight differences in feature sets on different operating systems. A complete list of specifications can be found at
INFO-0008: ScreenConnect System RequirementsEdit2.1.2 Host Machine Requirements
The host has several more options for base hardware than the server. The host client can run on either a Mac computer, Windows computer, Linux computer, iOS devices such as the iPad or iPhone, or on Android phones. There are some slight differences in feature sets on the different platforms. A complete list of specifications can be found at
INFO-0008: ScreenConnect System RequirementsEdit2.3 Hosting a ScreenConnect Session
As the host there are several options available to create a remote support session outlined in the topic
INFO-0013: The Host Page. You will choose one of these options and provide the applicable instructions to the guest you will be supporting.
 The types of sessions the Host can create. |
If selecting an option other than Email Link, be sure to provide the URL of the Guest page to the client. This URL can be found in the upper right hand corner of the page (the link entitled "Guest").
 Location of the Guest page link. |
Please review the above system requirements for both the Host and the Guest. In some cases, the guest machine may not have the minimum requirements installed, and will need to do so prior to using ScreenConnect.
Remember that once you have created the session, you still need to click Join
in the Active Sessions section of the Host page.
 The Host page after the "Join" button has been clicked for a session. |
Edit2.4 Joining a ScreenConnect Session
This section details joining a ScreenConnect session as a guest.
 The Guest page with available sessions. |
After joining a session, the following disclaimer will appear.
 ScreenConnect disclaimer. |
After selecting, "OK, join the session," another dialogue box will appear. Clicking the link entitled, "Click to try another option" will trigger other options of deploying ScreenConnect.
- Tip- If the first option does not establish the connection after a few seconds (30 seconds), then select the "Click to try another option" as your environment or internet browser may not support ClickOnce.
 Dialog that is displayed after choosing to join a session. |
Edit2.4.1 .NET ClickOnce Bootstrapper
When you click on the "OK, join the session" button, the operating system will verify application requirements and then will open an Application Run dialog. Once you have clicked Run, the ScreenConnect guest client will run and you will be connected to your host.
If your machine does not have the .NET Framework installed, the program will attempt to use the .NET Framework Bootstrapper to install the .NET Framework. In order to install the .NET Framework you must have appropriate privileges on your machine. Once installed, you will be prompted to run the Guest Client to join the session.
Edit2.4.2 "Hybrid" Java Launcher for .NET
ScreenConnect now includes a Java Web Start Bootstrapper that will start the .NET guest client. This is useful for Windows machines that are having problems with ClickOnce.
 Using the Java Web Start Bootstrapper |
When the Java Web Start Bootstrapper is deployed, the ScreenConnect icon will appear on the screen, and the .NET guest client will run normally.
 Using the Java Web Start Bootstrapper |
Edit2.4.3 Java Client
If you are on a Mac or Linux system or unable to run the ClickOnce application, a Java client is also available. You can quickly use the Java Client (as long as Java is installed) by selecting the link,
Click to try another option and choosing Option #3.
 Trying Java Web Start instead of ClickOnce to launch the Guest Client. |
Edit2.4.4 .NET ClickOnce Direct
Another option is to run the ClickOnce application directly, separate from the bootstrapper.
 Running .NET ClickOnce directly. |
Edit2.5 Ending a ScreenConnect Session
At any time during the session, either the Host or Guest may terminate the session, in some cases the session is permanently ended, while in others it may be left open to be re-joined at a later time.
Edit2.5.1 Guest Ending Session
There are two ways for the Guest to end the session:
- Select End Session on the Guest page will immediately and permanently end the session. Please note that it is not necessary to keep this page open during the support session, and that closing the browser will not end the session.
- Right click the ScreenConnect icon in the system tray and select Exit.
Note: If the Host has ended the session but kept the session available to join at a later time, the ScreenConnect system tray icon will remain even across reboots. The Guest can end the ability of the Host to rejoin by right-clicking the system tray icon and selecting Exit.When Exit is selected, and Exit Application dialog will open with the following options:
- Yes- Selecting this option ends the session permanently for both the Host and the Guest.
- No-Selecting this option ends the session, but allows the Guest to join again at a later time as long as the Host does not permanently end the session.
- Cancel- Cancels the end session action.
Edit2.5.2 Host Ending Session
There are several ways for the Host to end remote sessions. If the Host disconnects without the ending the session, the Guest will remain connected continuously (even across reboots) until actively disconnected or the session is terminated. It is also important to keep in mind that the Guest may end the session at any time.
- File|Exit from ScreenConnect menu.
- Selecting End from the Active Sessions section of the Host.aspx page.
- Clicking the Exit button on the ScreenConnect window.
Regardless of the method used to end the session, an Exit Application window will appear with the following options:
- Yes- Selecting this option ends the session permanently for both the Host and the Guest.
- No- Selecting this option ends the session, but allows the Host to join again from the Active Sessions section of the Host.aspx page. It is important to keep in mind that the Guest machine may end the session at any time, making the session end permanently.
- Cancel- Cancels the end session action.
Edit3 References