Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > DameWare Remote Support & Mini Remote Control > DameWare Documentation > Dameware Administrator Guide > Dameware architecture overview

Dameware architecture overview

Updated: September 19, 2017

Dameware Remote Support and Mini Remote Control can be installed in centralized mode or as stand-alone applications. Your license determines which version you have. If your organization has Dameware Remote Support Centralized, you can install components on one server, two servers, or three servers. See Determine which Dameware Central Server deployment option to use for more information.

Dameware components and applications in a typical 2-server deployment

This topic describes how each component of Dameware is installed and configured in a 2-server deployment scenario. While there are other deployment scenarios, a 2-server deployment provides you the terminology you must understand as a Dameware Administrator.

This scenario depicts a technician within the corporate network connecting with both an internal end user and end user located in a hotel, outside of the corporate firewall.

Dameware consists of the following components and applications:

Central Server: Stores licensed users, sessions, Global Host Lists, and other shared information. Install the Central Server on a server in your network.

Internet Proxy: Controls Internet Sessions initiated by a technician to support end users outside the corporate firewall. In this scenario, for added security, the Internet Session is installed and configured on a server in the DMZ.

Dameware client agent: Each user must have the Dameware client agent installed for the technician and the end user computers to connect. See Install the Dameware client agent service on Windows computers for more information.

Dameware Administration Console: Used by Dameware Administrators or technicians with administrator privileges to manage global hosts, remote hosts, and Internet Sessions. You can install multiple instances of the Administration Console on your network.

Dameware Remote Support application (includes Dameware Mini Remote Control): The application used by the technician to connect with and support end users. The Remote Support application is installed on the technician's laptop or desktop computer, and configured to connect with the Central Server.

The following graphic illustrates a 2-server deployment.


Last modified