This topic explains the main differences between ISL Light Client and ISL AlwaysOn, and helps you choose the correct connection method for your remote access scenario.
Difference between ISL Light Client and ISL AlwaysOn
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 a Remote Access agent 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 the configured Access Password.
Here is a tutorial and overview of ISL AlwaysOn and the best ways to set up Unattended Access to a remote machine.
Computers with ISL AlwaysOn installed can also be sorted into Computer Groups and shared with other users within your organization.
ISL AlwaysOn 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.
When to use which
As a general rule, use ISL Light Client for occasional attended support, and use ISL AlwaysOn when the same computer needs to remain available for future remote access.
If you expect to connect to the same computer repeatedly, ISL AlwaysOn is usually the more suitable option.
Notification and local consent options in ISL AlwaysOn
ISL Light Client is often the preferred option when the remote user is present and wants to maintain control over how and when the session is started, including whether desktop control is allowed.
However, ISL Light Client is not the only option when notification or user consent is required. ISL AlwaysOn can also be configured with notification and local consent options:
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.
These settings allow administrators to configure ISL AlwaysOn according to their organization’s remote access policy.
Common scenarios
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.
Summary
Use ISL Light Client for attended support sessions where the remote user joins with a Session Code and no installation is required.
Use ISL AlwaysOn for computers that need to remain available for recurring, managed, or unattended remote access.
The recommended option depends on the remote access requirements, the ownership of the computer, and the organization’s security policy.