First, let’s briefly explain the difference between the two.
ISL Light Client is a standalone executable that does not require installation. The person receiving support can save ISL Light Client locally, for example on their desktop, and run it when they receive a Session Code from their Operator. They enter the session code into the text field, choose whether they would like to allow desktop control, click “Join”, and a Remote Desktop session is established.
ISL AlwaysOn is our Remote Access agent, designed to be installed on computers that need to remain available for remote access. Once ISL AlwaysOn is installed and configured, an authorized Operator can connect to the computer by selecting it from their list of available computers and entering a configured Access Password.
These computers can also be sorted into Computer Groups and shared with other Users within our organization.
This solution is useful for recurring access, unattended access, system administration, server maintenance, software updates, and other scenarios where the same computer needs to be accessed regularly without starting a new session by Session Code each time.
So which one should I use?
As a general rule of thumb, use ISL Light Client for occasional attended support, and use ISL AlwaysOn when the same computer needs to remain available for future remote access.
In fact, a good way of looking at it is if you see yourself making more than a few connections to this machine a year, then it is best to use ISL AlwaysON wherever you can. Understandably, some organizations may be hesitant to install a remote access agent because they want the remote user to remain aware of incoming connections or have control over whether a connection is accepted.
This is what the next part of this topic will focus on.
Notification and local consent options in ISL AlwaysOn
ISL AlwaysOn includes notification and local consent options that can help address these requirements.
Show notification of incoming connection - This option displays a notification on the remote computer before a Remote Desktop session is established. Instead of the connection starting immediately, the person using the remote computer can be informed that an Operator is trying to connect.
Notification timeout - This defines how long the notification is shown on the remote computer before the configured default action is applied.
Allow local user to reject connection - This option allows the local user on the remote computer to reject the incoming connection before the notification timeout expires.
Allow or reject if the user does not respond - If the local user does not respond before the notification timeout expires, ISL AlwaysOn can be configured to either allow or reject the connection.
This lets administrators choose the behavior that best matches their security policy.
Why this matters
These options make ISL AlwaysOn suitable for environments where computers need to remain available for remote access, but where users or administrators still require visibility and control over incoming connections.
In other words, ISL AlwaysOn does not mean silent or uncontrolled access. It can be configured to show connection notifications, allow local users to reject connections, and follow the organization’s preferred security policy.
Below is a comparison table to help you understand the nuances of various scenarios and when which application comes in:
Below are some common scenarios that can help determine which application is more suitable.
School classroom computers, computer lab PCs, or staff workstations: Use ISL AlwaysOn. These are managed devices that can be prepared in advance and made available to authorized IT staff when support or maintenance is needed.
First-time customer or customer not comfortable installing a remote access agent: Use ISL Light Client. The person receiving support can join with a Session Code without installing ISL AlwaysOn or preparing the computer for future remote access.
Customer does not want to allow remote control immediately: Use ISL Light Client. ISL Light Client can be configured so the Operator does not receive remote control by default. The customer can first allow viewing only, and remote control can be requested later during the session if needed.
Computer managed by your organization: Use ISL AlwaysOn. ISL AlwaysOn is usually the better fit when your organization is responsible for the computer’s security, maintenance, and availability. Access can be configured according to your internal policy instead of being handled as a separate attended session every time.
Regular support for the same family member or colleague: Use ISL AlwaysOn. The computer can be prepared once, making future support sessions quicker and easier without requiring the user to enter a new Session Code each time.
Of course, there is no one size fits all. In some cases, even despite all of the notification and conditions upon which a computer is accessed, another organization will simply not allow you to install ISL AlwaysOn on their machines, and you will need to get by with ISL Light Client.
In others, you will need to assist someone less tech saavy, and it will save everyone time to just add their computer to your list.
At the end of the day, it is up to each individual entity to decide what is best for them. Of course, if you need any help making that decision, join us via our Live Chat.