TrustViewerPro distributions are distributed under a free license by default. Just download the full set of distributions and documentation from our website and get started immediately, no registration is required. You can use the free version for commercial purposes, subject to the license agreement provided in the documentation.
The free license provides full functionality for both the server and client modules, with a single limit of up to 10 simultaneous connections to the server. However, the number of installed copies of client modules is not limited.
A paid license differs from a free one only in the large number of devices connected to the server at the same time. At the same time, the transition from using a free license to a paid one, as well as the transition between different tariff plans, is performed centrally using the server control panel. Just enter the license activation code once on the server, and all client modules will be activated automatically.
If the maximum number of devices connected to the server at the same time is exceeded (according to the license), the operation of client modules is not blocked (the connection to the server is not disrupted), but until the server has a sufficient number of free connections, it will not be possible to initiate a new communication session (some features, such as sending messages to users, will be available).
The TrustServer server allows you to manage the rights and settings of registered users and computers, acts as a proxy server when creating a secure communication channel between computers, provides centralized storage and access to session records, and much more. However, using the Trust Server is a prerequisite for the client modules to work.
During a communication session, the connection between computers is prioritized using p2p connections, however, if this is not possible, the computers use TrustServer as a proxy server, thus providing a connection between each other even when working in different networks/subnets. Moreover, in the framework of a secure network without access to the Internet also ensures complete functionality.
The program supports several protocols: http/https, socks5, and websockets, and in most cases no special proxy/firewall settings are required. The program automatically selects the appropriate Protocol every time you connect to the server and remote computer, even in the case of Kerberos/NTLM authorization. You can also manually set the proxy connection parameters and the protocols used in the client module settings.
Setting up permanent access to computers via the Internet is no different from setting up access in a local network: you must install the client module on the computer, specify the username and password of a special group account in the program settings (after creating it on the server using the server control panel), and explicitly allow access to this computer without a request in the program settings. After that, all operators who have the appropriate permissions on the server automatically get permanent access to the specified computer (within their rights set by the TrustServer administrator using the server control panel). At the same time, to ensure greater security, it is possible to configure advanced settings directly for client modules, as well as for computers, group accounts, and operator accounts. In particular, you can prohibit / allow the required operators to access individual computers or entire groups, and you can also prohibit the required group accounts and operator accounts from logging in via the Internet (i.e. restrict work only in the local network).
The TrustServer server runs on all versions of the Windows operating system starting from Windows Server 2003/Windows XP SP3, on all GNU/Linux distributions starting from kernel version 3.0, and on All FreeBSD distributions starting from version 5.0 (in binary compatibility mode with Linux).
The TrustViewerPro client module works on all versions of the Windows operating system starting from Windows Server 2003/Windows XP SP3, as well as in limited functionality mode on GNU / Linux, Apple macOS, and other UNIX-like systems with support for the x86 and AMD64 CPU architectures (in WinE compatibility mode starting from version 2.0). At the same time, the minimum requirements for the full operation of both the server and the client module are: processor-Pentium IV 1 GHz; RAM-128 MB; free hard disk space-10 MB.
Yes, as part of branding, the client module can change the logo and Wallpaper of the main form, as well as configure the display of its banner (flash video, gif animation, or static image with the optimal size), with the ability to click on the link (the link will be opened in the browser used by “default”). The banner, logo, and Wallpaper are managed centrally in the TrustServer control panel. it is enough to change the branding settings once on the server and all client modules will use the new design automatically. You can also change the icon and even the program name by configuring the msi package distribution.
Yes, in General, it is enough to rename the distribution in a special way, so that the name of the executable file contains the address of the coordinating server of the organization “TrustServer” (for example, “TrustViewerQS_mysite.com.exe”. For more information about this feature, see the official documentation distributed with distributions). It also supports branding and displaying your advertising materials. In addition, to provide instant support, you can use the standard Trust Viewer distribution (you can download it from a public server www.trustviewer.com).
Yes. The distribution of the client module is also distributed as an msi package, which can be configured for automatic deployment using Active Directory. At the same time, you can change the settings of some installation parameters directly in the distribution package using any msi installer editor, or you can simply pass them in the command line.
Along with the usual connection to remote computers in desktop sharing mode, TrustViewerPro also provides private remote access to terminal servers and offline workstations based on the RDP Protocol, which allows you to quickly and safely set up full-fledged remote workstations for employees. However, the built-in Windows tools are used for connecting, so the process is similar to normal RDP connections using Windows. The main advantage of using TrustViewerPro is that the user does not need to establish a VPN connection to the corporate network before connecting to the terminal server, or use the remote desktop gateway in addition. Instead, hidden from the user, the same secure communication channel with the TrustServer server is used as for normal connections.
TrustViewerPro has a built-in helpdesk service that allows you to connect to remote computers based on request tickets that define the permissions and access expiration date. The request is submitted by the user using a built-in simplified form with fixed fields and no constructor. To implement more complex forms and scenarios, you can integrate with third-party Helpdesk/ServiceDesk services. At the same time, a combined mode of operation is possible, when some of the operations for managing requests are performed using the services directly from the Helpdesk/ServiceDesk service, and some – using the interface of the client module “TrustViewerPro”.
If centralized record storage is enabled on the server, operators with the appropriate permissions can access not only session recordings, but also session broadcasts. The main difference between these two modes is that you can only access the recording after the end of the communication session, and the broadcast can only be accessed during an active communication session, thus allowing you to watch the remote desktop of the computer in real time without having to connect to a remote computer. In addition, access to broadcasts can be obtained using a special seven-digit identifier that is unique for each broadcast, thus enabling mass broadcasting even for users who do not have operator/administrator rights. Moreover, after the completion of a broadcast session, it is automatically converted to a recording session, allowing, for example, keep it in video format using any codec.
Yes, you can send any settings to all client modules in bulk, including settings for connecting to a new server. You can also send these settings to computers that are currently offline. In this case, the new settings will be automatically accepted by the client modules when they first connect to the server. However, for successful migration to the new server, the old server must also continue working until all client modules receive the new settings.
For security reasons, by default, immediately after installing the client module on computers, administrators do not have access to it without a request, and they can not remotely send commands/scripts or change settings, even if they have all the necessary permissions. To enable this feature, a user with administrator rights must complete the necessary program settings immediately after installation, while being directly at the computer. However, to enable mass deployment and configuration of client modules on computers without having to be present for them personally, you just need to send a special command “Enable remote settings”, after which you can manage the settings of client modules remotely, including configuring access without a request. However, to send a command to enable remote settings, you will need to enter a username/password pair for an account with computer administrator rights (both a local computer account and an Active Directory account can be used here). If a password is not set for the administrator account on the remote computer, this command cannot be sent.
Yes, by default, commands/scripts are sent in monitoring mode, with the ability not only to display the results of execution, but also with the ability to interrupt, for which it is enough to simply close the window corresponding to the required mailing list. At the same time, you can send several commands/scripts to the same computers at the same time, all of them will be executed in parallel and independently, and you can also expect/manage them in separate Windows.
Menu item “Send commands (System)” intended for sending commands/scripts to remote computers and executing them on behalf of the system account (System). The “Send commands” menu item is also intended for sending commands/scripts to remote computers, but they are executed on behalf of the currently active or explicitly specified user.
Wake-on-LAN technology for turning on a computer remotely means sending a special data packet to its network card within the same local network, that is, sending this data packet must be carried out from a device located in the same local network as the computer that is turned off. TrustViewerPro allows you to remotely turn on the computer even over the Internet, using the network of enabled computers that have client modules installed, as well as the computer that has the TrustServer server installed. This means that in addition to the standard conditions and settings WOL (support Wake-on-LAN motherboard, power supply and network card, and the resolution of the corresponding option in BIOS), for the successful introduction of the computer through the Internet, local network off of a computer must be the server TrustServer or at least one computer with an installed client module.
TrustViewerPro supports its own update format, which is a single file for each of the available versions. It allows you to use the TrustServer control panel to centrally update both client modules and the server itself. However, you can manually download update packages from the developer’s site if necessary, or you can configure the server to automatically download and install updates on a schedule. It is possible to install both newer versions of packages relative to the current version (upgrade) and earlier ones (downgrade).