Server requirements

From ScreenConnect Online Help
(Redirected from INFO-0008.ashx)
Jump to: navigation, search
For complete context, you might want to check out:

 ScreenConnect Server Setup Guide  System requirements 


Supported Operating Systems

Note.png Note: While we do our best to support end-of-life operating systems, we cannot guarantee successful performance in all cases.

Windows

  • Windows 7
  • Windows 8 & 8.1
  • Windows 10
  • Windows Server 2003
  • Windows Server 2003 R2
  • Windows Server 2008
  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016
  • Windows Vista
  • Windows XP SP2+

Linux

The ScreenConnect server software requires i386 or x86_64 architecture and glibc 2.5 or higher. If you don't know if your Linux meets these criteria, assume that it does.

  • Ubuntu Linux
  • Linux Mint
  • Debian Linux
  • CentOS Linux
  • Red Hat Enterprise Linux
  • Fedora Linux
  • OpenSUSE Linux


Note.png Note: ScreenConnect is compatible with ARM 7. For questions on installing ScreenConnect on your ARM 7 device, please visit our forum.

Mac OS X

  • Mac OS X 10.7+


Note.png Note: Server-side screen recording is unsupported on OS X. It may be possible to install libavcodec and related libraries using MacPorts, but this has not yet been done. This may be investigated further in the future depending on demand.

Recommended system requirements

It's difficult to pinpoint recommended system requirements as they will vary according to your use model. For instance, users that plan on connecting to many machines at once, or users that plan on view video remotely, will use more server resources.

For RAM, generally we recommend 2GB per 10 concurrent sessions ("concurrent" meaning both a Host and a Guest are connected). If you are expecting to use 15 or more active sessions at a time or have over 1000 Access clients, a server running Windows may better serve your needs.

The example server specifications below are not minimum server requirements, but they can be useful as "ballpark" numbers when deciding on a server for ScreenConnect On-Premise.

Example: Larger implementation of ScreenConnect On-Premise

For a ScreenConnect server that will have over ten concurrent sessions and over 500 Access clients:

  • Windows Server 2012 R2
  • Quad-core processor at 2.4 GHz
  • 8GB RAM
  • SSD recommended


Example: Smaller implementation of ScreenConnect On-Premise

For a ScreenConnect server that will only have a few concurrent sessions and around 200 Access clients:

  • Windows Server 2012 R2
  • Dual-core processor at 2.4 GHz
  • 4GB RAM
  • SSD recommended

Bandwidth usage

Bandwidth usage during a session is highly dependent on the activity within the session; viewing a video over a remote connection will use more bandwidth than a session with few screen refreshes.


References

Related articles

Additional resources