Hardware and software system requirements for Take Control
| Hardware & Software | Requirements |
|---|---|
|
Operating System - Technician Console & Remote Viewer |
|
| Operating System - Agent & Applet |
|
| Network | Ability to make direct outgoing TCP connections or availability of an HTTP proxy or a SOCKS server |
| Hard drive space | 100 MB |
| CPU | 450 MHz |
| RAM | 256 MB |
| Bandwidth |
1Byte/s and 5KB every 5 seconds |
Actual bandwidth for sessions is dependent on resolution and quality settings.
In Chrome version 77 and later, the checkbox for "always open these types of links in the associated app" is no longer displayed for URL custom protocols. The impact of this is that for all users on the Chrome browser, there is no longer an option to remember your protocol handling preferences, and the below dialog (or some variation, pending your local settings, etc) will be presented each time a Take Control session is launched. This is, in no way a bug, or a fault. Further, there is nothing the Take Control team can do to mitigate this. It is simply a change about how custom protocols are handled within the Chrome browser.
Important Notice: In some scenarios with Server Core operating systems, Windows may not display certain elements, like command prompts, for instance, in a way that can be captured by Take Control. In these rare cases, you can always use RDP (Remote Desktop Protocol) within the Take Control session as an alternative. Since RDP does not capture the screen directly, but instead references remote objects, it can bypass these limitations. Alternatively, you can also use RBM or RBMA for these situations.
Access to the Take Control network
Take Control's list of IP addresses is very large and highly dynamic. Many IP address ranges point towards the intelligent routing infrastructure that forms part of our global network. Additionally, it is not possible to curate a list of Gateway IP addresses – the components responsible for session connectivity. This type of IP address is negotiated upon session setup and is predicated by the geo-location of both the session host, the session recipient, as well as being subject to available network conditions.
To get the best performance out of Take Control, please make sure that there is no deep packet inspection applied to the Take Control domains. On the Agents' networks, you can also create an exclusion on inspecting outbound traffic on the TCP port 3377.
What do you want to do?