ScreenConnect

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
ScreenConnect
400px
Developer(s) Elsinore Technologies
Stable release 5.2 / March 2015
Operating system Windows
Linux
OS X
Android
iOS
Type Remote desktop software
License Proprietary
Website www.screenconnect.com

ScreenConnect is a self-hosted remote desktop software application that has remote support, remote access, and remote meeting capabilities. ScreenConnect was developed by Elsinore Technologies in 2008.

History

Elsinore Technologies originally developed ScreenConnect in 2008 as an add-on to their RMM Software IssueNet in order to assist in providing remote support to end users. Following positive feedback from users, the company later decided to distribute the software as a standalone product in light of its ongoing popularity among clients.[1]

Acquisition by ConnectWise

On February 11, 2015, PSA company ConnectWise announced their acquisition of the ScreenConnect software in order to improve the remote control features of the latest release of their RMM Software, LabTech.[2] ScreenConnect, LLC announced that, despite being acquired by ConnectWise, they will continue to operate under their original name in addition to offering their software as a standalone product.[3]

Product

How it works

The product is a self-hosted server application[4][5] that permits the primary user to host the software on their own servers, PC, virtual machine (VM), or virtual private server (VPS). Once installed, the central web application can be made visible inside and outside of the local area network (LAN). ScreenConnect has a proprietary protocol and exposes an open architecture structure that can be utilized by product owners to implement custom plugins, scripting, or various integrations.

A generic use model would start with the host, technician or meeting presenter, initiating a session through the central web application. A guest, customer or participant, would then join a session by clicking on an email link or via the guest page of the application. For access to machines without an end-user, an unattended client can be created and deployed to a targeted machine.[6][7]

Features

Most commonly expected features for a product in this arena are present. Examples include reboot and reconnect, drag and drop file transfer, screen recording, safe mode support, multiple monitor, command line access, wake-on-LAN, VoIP, chat, and a custom toolbox for quick deployment of support tools.

In addition to features that facilitate communication, ScreenConnect also offers complete control over branding and customization of the product design, logo, color scheme, icons, text strings, and localization.

Security

The software is self-hosted providing users the ability to control the flow of data behind their own firewall and security implementations. ScreenConnect uses 256-bit AES encryption to package and ship data, supports two factor authentication, has server level video auditing, and granular role-based security. Forms-based and Windows Authentication are optional authentication methods for security purposes.

Compatibility

Host (presenter or technician): can utilize Mac, Linux, Windows, iOS or Android operating systems. Guest (customer or participant): can connect from Mac, Linux or Windows. ScreenConnect can also be utilized to remotely support Android devices, with complete view/control available for devices manufactured by Samsung.

Technology

Server

The ScreenConnect server is self-hosted, and runs as a .NET Framework application. On Microsoft Windows it runs as a set of services. On Linux and OS X it runs as a daemon on a bundled fork[8] of the Mono Runtime.

The ScreenConnect server runs as a set of three discrete services:

  • The Web Server service is an outward-facing ASP.NET HTTP application and serves as a portal for both technicians and their end-users
  • The Relay service provides outward-facing in-session communication and operates on TCP sockets. Communication is encrypted with the AES-256 block cipher.
  • The Session Manager service provides a data store for both the Web Server and Relay services. It is implemented as WCF SOAP web service.

Clients

ScreenConnect sessions are arranged through the web application. Once users join sessions, a ScreenConnect client is launched to connect to the Relay service. ScreenConnect targets clients based on device and operating system:

  • The .NET client is targeted to Microsoft Windows computers and is activated with a custom URI Scheme which starts the session from an installed handler on the controller's workstation.[9] For end-users joining a support session, a variety of bootstrappers can be used including Microsoft's ClickOnce technology.[10]
  • The Java client is targeted to OS X and Linux computers and is activated with Java Web Start.
  • The iOS client is targeted to iPhones and iPads.
  • The Android client is targeted to Android phones and tablets.

Licensing Model

ScreenConnect is commercial software. Licenses are concurrent based and are therefore not restricted to users or workstations. The licenses sit in a pool and can be used by any member of the organization. The company provides three types of licenses: a single concurrent that allows one simultaneous connection per license, an unlimited which allows an unlimited number of concurrent sessions as long as all sessions are utilizing the same server, and enterprise licenses which provide flexible options for SaaS, multi-user, or custom functionality.

The concurrent license types are bought as one-time purchase and come with lifetime support. A subscription model is used not for the software licenses themselves, but instead for updates to the product. Updates are provided free during the first year after purchase, after which the "update license" must be renewed. Pricing for subsequent updates depends on how much time has passed since the update license was last-renewed, though renewing said license resets the purchase date and allows for another year of free upgrades.[11]

See also

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Wareprise Remote Support Software
  5. ↑ Ohlhorst, Frank (June 9, 2013). eWeek ScreenConnect Shifts Remote Support From the Cloud Back to the Desktop
  6. ↑ Jon Jacobi PCWorld Reviews ScreenConnect
  7. ↑ http://www.screenconnect.com/LearnMore.aspx
  8. ↑ https://github.com/screenconnect/mono
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Softsea reviews ScreenConnect
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=ScreenConnect&oldid=687186269"