The user installs a persistent client that allows an administrator to log in and manage the computer on-demand. Once that connection ends, it cannot be re-established.Īlternatively, users can download a client to establish an unattended session. The session lasts only as long as the connection lasts. Users download the client and establish the support session from a shared URL. An attended session connects the technician to a remote computer for a limited amount of time. Next, create a folder for all computers in the domain by right-clicking Global Host List and selecting Add > Add Folder.ĭameware Remote Support offers two options to connect to computers outside the local network. In the example below, start at the Dameware Server Administration Console. You can add folders to the groups to further organize the contents. These groups can be personal, which are only available to an individual user, or global, which are available to all Dameware Remote Support users.

Managing Dameware groupsĭameware uses groups to manage collections of computers. These ports are configurable, should you require other port numbers. Setting up the proxy requires modifications to the firewall to allow ports 80, 443, 6129, 6130, 6132, and 6133. The internet proxy facilitates support with clients outside the network. Once the installation is finished, it's time to move on to configuring the internet proxy component. For production environments, I suggest configuring multiple servers and hosting the internet proxy in a DMZ. The installation offers an Express mode, installing all options on a single server. The centralized version of Remote Support is used in this example to support external clients. The standalone installation is sufficient for small deployments or testing but does not support sessions with users outside the network. There is an option for a standalone server installation or a centralized version.

Installation is a straightforward process.

Dameware remote