Dameware Installation Guide
Dameware Installation Guide
Dameware Centralized
Version 12.2.2
This document may not be reproduced by any means nor modified, decompiled, disassembled,
published or distributed, in whole or in part, or translated to any electronic medium or other means
without the prior written consent of SolarWinds. All right, title, and interest in and to the software,
services, and documentation are and shall remain the exclusive property of SolarWinds, its affiliates,
and/or its respective licensors.
The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of
SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office,
and may be registered or pending registration in other countries. All other SolarWinds trademarks,
service marks, and logos may be common law marks or are registered or pending registration. All
other trademarks mentioned herein are used for identification purposes only and are trademarks of
(and may be registered trademarks) of their respective companies.
Dameware Remote Support and Dameware Mini Remote Control system requirements 9
Install Dameware Central Server for a Mini Remote Control Centralized installation 50
Install Dameware Remote Support or Mini Remote Control from the command line 58
Arguments 58
System requirements 61
Install the client agent service from the Dameware Mini Remote Control application 61
Bind a self-signed certificate to prevent warnings during installation of the Dameware client
agent 77
Modify your firewall or router to support Internet Sessions in Dameware Mini Remote Control 83
Dameware Remote Support and Dameware Mini Remote Control provide you with tools to
troubleshoot and manage systems and support end users. If you are a customer, you are using either
a centralized version of Dameware, or a stand-alone version of Dameware. Each centralized license
includes a stand-alone license. If you are not a customer, and are interested in evaluating Dameware,
you can download a version of Dameware Remote Support or Dameware Mini Remote Control, fully-
functional for 14 days. After the evaluation period, you can convert your evaluation license to a
production license by obtaining and applying a license key.
Dameware Remote Support and Dameware Mini Remote Control offer different capabilities. With
Mini Remote Control, you can:
The following diagram illustrates how Dameware Mini Remote Control works with the Dameware
Central Server to support end users.
With a centralized version of Dameware Remote Support, you can perform all Dameware Mini
Remote Control actions, and many others. For example, you can:
The following diagram illustrates how Dameware Remote Support works with the Dameware Central
Server to support end users.
This guide provides installation instructions for a centralized installation of Dameware. For stand-
alone or evaluation instructions see Dameware Stand-alone Installation Guide.
.NET 4.5.2
Framework If .NET is not present on the computer, you may be prompted to restart the
computer after the .NET Frameworks are installed. Manually restart the
computer, and run the installer again.
*SolarWinds recommends that you install all Microsoft updates and enable TLS 1.2 before
Dameware is installed.
Dameware also installs the following components, which are embedded in the installer:
If you are unable to complete the installation due to missing prerequisites, download and install
them separately. See the following article for more information: Errors involving mandatory software
prerequisites when installing Dameware Server or Mobile Gateway.
*To operate Dameware on Microsoft Windows 7, an administrator must install the following two
mandatory Microsoft patches and then follow the instructions in the third KB article:
l See the following Win7 KB to update trusted root certificates (no longer maintained and now
redirects to an MSDN article): http://support.microsoft.com/kb/931125
l See the following Win7 KB to add SHA-2 code signing support:
http://support.microsoft.com/kb/3033929
l See https://microsoft.com/en-us/download/details.aspx?id=47442 to install required security
fixes.
CPU 1 GHz
RAM 4 GB
.NET 4.5.2
Framework If .NET is not present on the computer, you may be prompted to restart the
computer after the .NET Frameworks are installed. Manually restart the
computer, and run the installer again.
*SolarWinds recommends that you install all Microsoft updates and enable TLS 1.2 before
Dameware is installed.
The APIs used by Dameware Remote Support may require the Server Service and the NetLogon
Service (domain environments) for the user to authenticate to this remote machine over the network.
Dameware Remote Support also requires the Remote Registry Service for functions that require
access to the Registry.
To use Internet Session functionality, you must open port 443 in your organization's firewall to allow
the Dameware Internet Proxy to communicate with users outside of your internal network.
l Dameware Server and the Dameware Server Administration Console: Manage licensed users,
sessions, Global Host Lists, and other shared information. You can install multiple instances of
the Administration Console on your network. SolarWinds recommends that you install the
Administration Console on the same computer as Dameware Server.
l Dameware Internet Proxy: Create Internet Sessions to help users outside your internal network.
You cannot create Internet Sessions to support remote users with the centralized version
of Dameware Mini Remote Control. If you need to support remote end users, you must
install the centralized version of Dameware Remote Support.
l Dameware Mobile Gateway: Use this option feature to support end users from iOS and Android
devices. The users you connect to must be on Windows computers on your network. The Mobile
Gateway requires that you apply a separate license key that is available on the SolarWinds
Customer Portal. The Dameware Mobile Client applications are available for download from the
Google Play Store and iTunes.
Use the following table to determine if you should deploy Dameware Central Server components on
one, two, or three servers.
See Determine which Dameware Central Server deployment option to use for a description of all
deployment options.
l Obtain a copy of DamewareServer.exe, the Dameware Central Server installation file. The file is
available on the SolarWinds Customer Portal. If you have not obtained a copy, complete Task 1
below.
l Review the system requirements and port requirements.
l Are familiar with your IP routing tables so that you can configure port forwarding rules for the
port number to IP address and vice versa.
l Know how to set up a Domain Name Server (DNS).
l Know how to acquire a public IP address and set up Network Address Translation (NAT) rules.
l Open the following ports: 80, 443 (444 if 443 is not available), 6129, 6130, 6132, and 6133. You
can use other ports if these ports are already in use.
l Obtain administrator access to your Windows firewall.
l Obtain access to the physical firewall, if required.
The installation is divided into separate tasks that need to be completed before you can begin using
Dameware Remote Support.
4. Run DamewareServer.exe.
The Installation Wizard opens.
As the installation progresses, a dialog box opens, prompting you to enter an email
address. If you do not enter an email address, the installation does not complete.
1. On the Dameware Licensor dialog box, enter the Dameware Remote Support centralized license
key.
The Dameware Licensor dialog box opens at the end of the installation.
For detailed instructions on using the Licensor to activate your product, see Activate a
Dameware license.
2. If you are using the Dameware Mobile Gateway, enter that license key.
You are issued a separate license key for the Dameware Mobile Gateway.
To locate your Dameware license key is, log in to the SolarWinds Customer Portal, and click
Licenses > Manage License.
The Internet Session URL is the URL that you send out to your remote end users. This
field defines the DNS, which can be a fully qualified name or IP address. The Internet
Session URL must be NAT'd to a public IP address.
The Test Connection button is hard-coded to test against port 443. If you have changed
the port, the test fails, but the Internet Session URL can be valid. If the test fails and you
are using port 443, then troubleshoot the Internet Session URL.
4. Click Next.
For more information on configuring the Internet Session URL, see Install the Dameware
Internet Proxy with another web server, Specify the Internet Session URL in Dameware, and
Modify your firewall or router to support Internet Sessions in Dameware Mini Remote Control.
5. On the Configuration complete panel, accept the default user account credentials, or change
them, and click Finish.
See Determine which Dameware Central Server deployment option to use for a description of all
deployment options.
l Obtain a copy of DamewareServer.exe, the Dameware Central Server installation file. The file is
available on the SolarWinds Customer Portal. If you have not obtained a copy, complete Task 1
below.
l Review the system requirements and port requirements.
l Are familiar with your IP routing tables so that you can configure port forwarding rules for the
port number to IP address and vice versa.
l Know how to set up a Domain Name Server (DNS).
l Know how to acquire a public IP address and set up Network Address Translation (NAT) rules.
l Open the following port:s 80, 443 (444 if 443 is not available), 6129, 6130, 6132, and 6133. You
can use other ports if these ports are already in use.
l Obtain administrator access to your Windows firewall.
l Obtain access to the physical firewall, if required.
The installation is divided into separate tasks that need to be completed before you can begin using
Dameware Remote Support.
4. Run DamewareServer.exe.
The Installation Wizard opens.
As the installation progresses, a dialog box opens, prompting you to enter an email
address. If you do not enter an email address, the installation does not complete.
2. If you are using the Dameware Mobile Gateway, enter that license key.
You are issued a separate license key for the Dameware Mobile Gateway.
To locate your Dameware license key, log in to the SolarWinds Customer Portal, and click
Licenses > Manage License.
3. On the Dameware Server Components Configuration panel, click Run Locally for the Central
Server and the Mobile Gateway.
As the installation progresses, a dialog box appears, prompting you to enter an email
address. If you do not enter an email address, the installation does not complete.
Depending on the volume of traffic you anticipate on the Central Server, you can also
install the Dameware Mobile Gateway on the second server.
4. At the end of the configuration, the Configuration Wizards prompts you to enter the Internet
Session URL. Click Update Now.
The Internet Session URL is the URL that you send out to your customers. This field
defines the DNS, which can be a fully qualified domain name or IP address. The Internet
Session URL must be NAT'd to a public IP address.
The Test Connection button is hard-coded to test against port 443. If you have changed
the port, the test fails, but the Internet Session URL can be valid. If the test fails and you
are using port 443, then troubleshoot the Internet Session URL.
For more information on configuring the Internet Session URL, see Install the Dameware
Internet Proxy with another web server, Specify the Internet Session URL in Dameware, and
Modify your firewall or router to support Internet Sessions in Dameware Mini Remote Control.
6. After you have tested the connection, on the Edit Internet Proxy Connection Details page, click
Save.
On the Dameware Components Configuration panel, the Internet Proxy status turns green when
the URL test passes.
7. On the Dameware Components Configuration panel, click Next.
8. On the Configuration completed panel, make note of the pairing password, and click Finish.
In the next task, you go back to the first server and use the pairing password to authenticate
the connection between the Central Server and the Internet Proxy.
4. Enter the IP Address or hostname, and pairing password of the Internet Proxy server.
5. Click Test Connection, and click Save.
A successful test means that all components are interconnected and working.
See Determine which Dameware Central Server deployment option to use for a description of all
deployment options.
l Obtain a copy of DamewareServer.exe, the Dameware Central Server installation file. The file is
available on the SolarWinds Customer Portal. If you have not obtained a copy, complete Task 1
below.
l Review the system requirements and port requirements.
l Are familiar with your IP routing tables so that you can configure port forwarding rules for the
port number to IP address and vice versa.
l Know how to set up a Domain Name Server (DNS).
l Know how to acquire a public IP address and set up Network Address Translation (NAT) rules.
l Open the following ports 80, 443 (444 if 443 is not available), 6129, 6130, 6132, and 6133. You
can use other ports if these ports are already in use.
l Obtain administrator access to your Windows firewall.
l Obtain access to the physical firewall, if required.
The installation is divided into separate tasks that need to be completed before you can begin using
Dameware Remote Support.
4. Run DamewareServer.exe.
The Installation Wizard opens.
As the installation progresses, a dialog box displays, prompting you to enter an email
address. If you do not enter an email address, the installation does not complete.
For detailed instructions on using the Licensor to activate your product, see Activate a
Dameware license.
2. If you are using the Dameware Mobile Gateway, enter that license key.
You are issued a separate license key for the Dameware Mobile Gateway.
To locate your Dameware license keys, log in to the SolarWinds Customer Portal, and click
Licenses > Manage License.
3. On the Dameware Server Components Configuration panel, for the Central Server, click Run
Locally, and click Next.
6. On the Advanced Install Options dialog box, select the components that you want to install on
the Central Server, and click Next.
SolarWinds recommends that you install the Dameware Server and the Dameware Server
Administration Console.
As the installation progresses, a dialog box opens, prompting you to enter an email
address. If you do not enter an email address, the installation does not complete.
4. At the end of the configuration, the Configuration Wizards prompts you to enter the Internet
Session URL. Click Update Now.
The Internet Session URL is the URL that you send out to your customers. This field
defines the DNS, which can be a fully qualified name or IP address. The Internet Session
URL must be NAT'd to a public IP address.
The Test Connection button is hard-coded to test against port 443. If you have changed
the port, the test fails, but the Internet Session URL can be valid. If the test fails and you
are using port 443, then troubleshoot the Internet Session URL.
For more information on configuring the Internet Session URL, see Install the Dameware
Internet Proxy with another web server, Specify the Internet Session URL in Dameware, and
Modify your firewall or router to support Internet Sessions in Dameware Mini Remote Control.
6. After you have tested the connection, on the Edit Internet Proxy Connection Details page, click
Save.
On the Dameware Components Configuration panel, the Internet Proxy status turns green when
the URL test passes.
7. On the Dameware Components Configuration panel, click Next.
8. On the Configuration completed panel, make note of the pairing password, and click Finish.
In the next task, you go back to the first server and use the pairing password to authenticate
the connection between the Dameware Central Server and the Internet Proxy.
4. Enter the IP Address or hostname, and pairing password of the Internet Proxy server.
5. Click Test Connection, and click Save.
A successful test means that the Central Server can communicate with the Internet Proxy.
Remember to enter an email address. If you do not enter an email address, the
installation does not complete.
3. On the Dameware Server Components Configuration panel, click Run Locally for the Mobile
Gateway, and click Next.
4. On the Configuration completed panel, make note of the pairing password, and click Finish.
You will configure the first server to use the pairing password to authenticate the connection
between the Central Server and the Mobile Gateway.
4. Enter the IP Address or hostname of the Mobile Gateway server, and the pairing password.
For information about Dameware Central Server deployment options, see Determine which Dameware
Central Server deployment option to use.
l Install the Dameware Central Server in express mode, two-server mode, or three-server mode.
When you install Dameware Remote Support, you configure it to connect with the Central
Server.
l Collect the IP address and port number of the Dameware Central Server.
The installation is divided into separate tasks that need to be completed before you can begin using
Dameware Remote Support.
5. Enter the IP address and port number of the Central Server, and click Next.
The default port number is 6133, and is seldom changed to another value.
There is a known issue with Dameware where the Test button reports a failure to
connect, even though the connection to the Central Server is valid. SolarWinds
recommends that you click Next, and continue with the installation.
As the installation progresses, a dialog box opens, prompting you to enter an email
address. If you do not enter an email address, the installation does not complete.
The first time you log in, you are presented with a self-binding certificate. If you agree,
click Yes to proceed.
You are now ready to use Dameware Remote Support. Refer to the Getting Started Guide to begin
using Dameware Remote Support.
l Install Dameware Central Server for a Mini Remote Control Centralized installation
l Install Dameware Mini Remote Control client (centralized mode)
l Obtain a copy of DamewareServer.exe, the Dameware Central Server installation file. The file is
available on the SolarWinds Customer Portal. If you have not obtained a copy, complete Task 1
below.
l Review the system requirements and port requirements.
The installation is divided into separate tasks that need to be completed before you can begin using
Dameware Mini Remote Control.
4. Run DamewareServer.exe.
The Installation Wizard opens.
As the installation progresses, a dialog box opens, prompting you to enter an email
address. If you do not enter an email address, the installation does not complete.
The Dameware Licensor dialog box opens at the end of the installation. If you are unsure of what
your Dameware license key is, log in to the SolarWinds Customer Portal, and click Licenses > Manage
License.
3. On the Internet Proxy settings verification panel, select I do not want to test the Internet
Session URL, and click Next.
Dameware Mini Remote Control Centralized does not support Internet Sessions.
Dameware Mini Remote Control centralized does not support Internet Sessions, so you cannot
support end users outside of your network. To support remote end users, you must purchase a
license of Dameware Remote Support centralized.
l Install Dameware Central Server for a Mini Remote Control Centralized installation. When you
install the Dameware Mini Remote Control client, you configure it to connect with the Central
Server.
l Collect the IP address and port number of the Dameware Central Server.
l Review the system requirements and port requirements.
l Obtain a copy of the DamewareMRC32.exe (32-bit) or DamewareMRC64.exe (64-bit)
installation files. The files are available on the SolarWinds Customer Portal. If you have not
received a copy, complete Task 1 below.
The installation is divided into separate tasks that need to be completed before you can begin using
Dameware Mini Remote Control.
5. Enter the IP address and port number of the Central Server, click Test, and click Next.
The default port number if 6133, and is seldom changed to another value.
As the installation progresses, a dialog box opens, prompting you to enter an email
address. If you do not enter an email address, the installation does not complete.
You are now ready to use Dameware Mini Remote Control. Refer to the Getting Started Guide to
begin using Dameware Mini Remote Control.
To install Dameware Remote Support or Dameware Mini Remote Control using the MSI installer:
Use the following command at the command line or in an installer script. Replace the variables in
this example according to the variables in the Arguments section below.
See the following KB article for instructions to Extract the Dameware Centralized MSI installers from
their EXE files.
To install Dameware Remote Support or Dameware Mini Remote Control using the EXE installer:
Use the following command at the command line or in an installer script. Replace the variables in
this example according to the values in the Arguments section.
Arguments
The following is a list of command line arguments.
l /args "argumentsHere" (EXE only) instructs the EXE installer to pass the arguments inside
the quotation marks along to the MSI installer.
Arguments for the Dameware Centralized 12.2.2 upgrade and backup are available in the topic Back
up Dameware Mini Remote Control settings and hosts during upgrade to version 12.2.2.
Additional resources
For more arguments and additional information about CLI installs, see the KB article Install
Dameware Remote Support (DRS), Mini Remote Control Client (MRC) and the Agent from the
command line (silent install).
To configure a Mac or Linux computer as a remote host, see Configure a Mac or Linux
computer as a Dameware Remote Host.
The installation method you choose is up to you. The most common method is to install the client
agent on demand, but if you work for a large organization, you may find that using an MSI installer is
more convenient.
The Dameware Mini Remote Control application is backward compatible with Dameware Mini
Remote Control client agents from version 7.0. If the Dameware Mini Remote Control
application connects to an unsupported agent, it prompts you to install a newer version of the
client agent.
The Windows operating system requires local administrator rights to install, remove, start, stop, or
upgrade the Dameware Mini Remote Control client agent service on remote systems.
System requirements
Hardware and software Requirements
Before you begin, on the remote computer, open the File & Printer Sharing protocols and the File
& Printer Sharing ports.
1. Launch Dameware Mini Remote Control, and select File > Connect to local or remote sessions.
2. Enter the Host Name or IP Address and administrative credentials.
3. Click Connect.
4. When prompted to install the client agent service, click OK.
5. Click Install Options to enable any of the following options:
l Stop Service On Disconnect
l Remove Service on Disconnect
l Set Service Startup type to Manual. (Default is Automatic. Changing to Manual prevents
automatically starting up the service when Windows opens.)
l Include Configuration File (DWECS.reg)
l Copy FIPS modules (approximately 9 MB)
premise access and off-premise access through the Dameware Internet Proxy.
o Direct connection only: This enables you to connect to computers using on-premise
access only.
Before you begin, on the remote computer, open the File & Printer Sharing protocols and the File
& Printer Sharing ports.
1. Launch Dameware Mini Remote Control, and click File > Install Service.
2. Enter the host name or IP address of the computer on which you want to install the service.
3. To manually start the service each time a connection is opened, select Set Service Startup type
to Manual.
4. To configure the settings of the Dameware Mini Remote Control client agent service to copy to
the remote system, click Configure.
5. Copy the DWRCS.reg file from the local system to the remote system with pre-configured
Dameware Mini Remote Control client agent service settings, select Include Configuration File
(DWRCS.reg). This option is available after you have created configuration settings.
6. To connect in FIPS Encryption Mode, select Copy FIPS Modules (approximately 9 MB).
7. Select Overwrite any existing configuration on remote host to recreate the configuration file in
the remote machine.
8. Approve the agent on remote machine.
9. Click OK.
The Dameware Mini Remote Control application deploys the service to the remote computer.
The MSI and MST installers are saved to the following locations:
To deploy the remote host with the remote configuration, open the command line and enter the
transformation command:
By default, remote host installation does not overwrite the Remote Host configuration. To apply a
clear configuration, run the installation with OVERWRITEREMOTECFG=1.
After you add the custom installation arguments, specify the default arguments. Otherwise, the
remote host is installed without configuration and runs in Direct mode. SolarWinds recommends that
you use the following command line arguments:
2. Copy the following files to a location or device you can access from the remote computer:
l Dameware.LogAdjuster.exe.config
l SolarwindsDiagnostics.exe.config
l Dameware.Diagnostics
l cpprest110_xp_1_2.dll
l DWRCChat.dll
l DWRCK.dll
l DWRCRSS.dll
l DWRCSE.dll
l DWRCSET.dll
l DWRCSh.dll
l DWSGRWRP.dll
l ICSharpCode.SharpZipLib.dll
l log4cxx.dll
l log4net.dll
l SolarWinds.Logging.dll
l SolarWinds.Orion.Common.dll
l Dameware.LogAdjuster.exe
l DWRCS.EXE
l DWRCST.EXE
l SolarwindsDiagnostics.exe
l DWRCS.Logging.xml
l DWRCST.Logging.xml
l LogConfigurations.xml
3. On the remote computer, create a folder in the Windows directory called dwrcs
(c:\Windows\dwrcs).
4. Paste the copied files into the dwrcs folder.
To connect to the remote system in FIPS mode, copy the following files to c:\Windows\dwrcs on the
remote system:
l ccme_base.dll
l ccme_ecc.dll
l ccme_eccaccel.dll
l cryptocme2.dll
l cryptocme2.sig
l ccme_eccnistaccel.dll
l DWRCRSA.dll
Before you begin, configure the client agent with host names, log settings, authentication choices, or
other settings to deploy the custom configuration with the client agent.
1. Install and configure the client agent on the computer with the Dameware Mini Remote Control
application.
2. To open the Dameware Mini Remote Control Package Builder, click Start > All Programs >
SolarWinds > Dameware Mini Remote Control > Dameware Mini Remote Control Client Agent
MSI Builder.
3. Complete the following fields in the Package Builder dialog box:
l Profile: Select a pre-defined MSI package profile to populate the rest of the fields with
your preferred settings. To save a new profile, complete the rest of the Package Builder
dialog box, enter a new name in the Profile box, and click the save icon.
l Target O/S: The operating system on the target system(s).
l Include FIPS Modules: Includes the FIPS Modules in the MSI package. These files are
required to run the client agent service in FIPS Encryption Mode.
l Install the mirror driver: Includes the Dameware Mini Remote Control Mirror Driver in the
MSI package.
l Install the keyboard driver: Includes the Dameware Mini Remote Control Virtual Keyboard
Driver in the MSI package.
l Install the smart card driver: Includes the Dameware Mini Remote Control Smart Card
Driver in the MSI package.
l Client Agent Settings: Click the Client Agent icon to open the Dameware Mini Remote
Control client agent service settings dialog box:
l Output Folder: Enter or browse to the folder you want to install the service to on the
remote systems.
When you configure these settings through the Package Builder, the application saves the
settings in the installer to deploy to one or more remote systems.
4. Click Build MSI to build the MSI package and save it to the output folder. By default, the output
folder is the Dameware installation folder.
You can deploy the custom MSI package as you would any other MSI.
1. Open Remote Support, and then open the Services View on the computer running Dameware
Remote Support.
2. Add the target systems to the Batch pane at the bottom of the Services View.
3. Highlight the target systems in the Batch pane, and then select Batch Processing - DWMRC
Service Install from the Service menu.
4. Complete the following fields on the Dameware Mini Remote Control Service Installation -
Batch dialog box:
l Include Configuration File (DWRCS.reg): Copies the DWRCS.reg file from the local system
to the remote system with pre-configured client agent service settings.
l Configure: Click Configure to configure the settings of the client agent service to copy to
the remote system, if enabled.
l Set Service Startup type to Manual. (Default is Automatic.)
l Start Service after installation: Select this option to start the client agent service after
installation.
l Copy FIPS modules (approximately 9 MB): Copies the Federal Information Processing
Standard (FIPS) modules to the remote system when installing the client agent service.
5. Click OK.
For example, if you have purchased Dameware Remote Support, you enter a license key for
Dameware Remote Support centralized and the Dameware Mobile Gateway. The Dameware Mobile
Gateway is an optional feature of Dameware Remote Support that enables technicians to support
Windows end users from iOS or Android devices. Each centralized version of Dameware Remote
Support includes a license key for the Dameware Mobile Gateway. If you purchased Dameware Mini
Remote Control, you only enter a license key for Mini Remote Control centralized.
The Dameware Central Server and Dameware Internet Proxy are included with the centralized
version of Dameware Remote Support and are not separately licensed.
After you apply your purchased license, you must disable or delete any user accounts that
exceed the number of licensed seats you have purchased.
Complimentary Software
The following Dameware software is provide free of charge and is not licensed:
Dameware Mini Remote Control centralized does not support Internet Sessions.
The following procedure guides you in locating your license key on the SolarWinds Customer Portal,
and then how to manually launch the License Activation application.
If you are evaluating any Dameware product and have received a license activation key
from a SolarWinds representative, continue to Step 3.
4. Browse to your Dameware license list, and then locate the unregistered licenses list.
If you do not see the license activation keys, click the + sign to expand the license details.
5. Copy your unregistered activation key for the product you are activating.
6. On the computer on which you have installed Dameware, launch the License Activation
application.
7. Select your installation method:
l For a centralized installation, click Enter License by the product you want to activate.
l For a stand-alone installation, click Enter Licensing Information.
8. If the computer on which you installed Dameware is connected to the Internet:
a. Click I have internet access and an activation key from my customer portal license
management page.
b. Paste your unregistered activation key in the Activation Key field.
c. Click Next.
9. If the computer on which you are activating your Dameware product is not connected to the
Internet:
a. Click This server does not have internet access. Guide me through offline, manual
activation.
b. Click Next.
c. Click Copy Unique Machine ID and paste into a text file or Word document.
d. Go back to the SolarWinds Customer Portal and click Licenses > Manage Licenses.
e. Scroll down to license underneath the activation key.
f. Click Activate License Manually, and complete the fields, including entering the Unique
Machine ID you copied.
g. Click Generate License File, and save it to a shared location.
h. Go back to the screen where you generated the Unique Machine ID.
i. Click Browse and select the location where you saved the file.
j. Follow the steps and click finish.
k. Restart the installation for everything to update.
SolarWinds recommends using the License Manager when activating licenses because it is
continuously updated to be compatible with the SolarWinds license server. You can also use the
License Manager to deactivate and synchronize licenses.
If you do not see the license activation keys, click the + sign to expand the license details.
5. Copy your unregistered activation key for the product you are activating.
6. Open the License Manager and click Active/Upgrade on the license you want to activate.
7. If the computer on which you installed the Dameware product is connected to the Internet:
a. Click I have internet access and an activation key from my customer portal license
management page.
b. Paste your unregistered activation key in the Activation Key field.
c. Click Next.
8. If the computer on which you are activating your Dameware product is not connected to the
Internet:
a. Click This server does not have internet access. Guide me through offline, manual
activation.
b. Click Next.
c. Click Copy Unique Machine ID and paste into a text file or Word document.
d. Go back to the SolarWinds Customer Portal and click Licenses > Manage Licenses.
e. Scroll down to license underneath the activation key.
f. Click Activate License Manually, and complete the fields, including entering the Unique
Machine ID you copied.
g. Click Generate License File, and save it to a shared location.
h. Go back to the screen where you generated the Unique Machine ID.
i. Click Browse and select the location where you saved the file.
j. Follow the steps and click finish.
k. Restart the installation.
When upgrading to a new version or license, you manually sync the license key by opening the
License Manager and clicking Sync. If you do not have a Sync button, upgrade your version of the
License Manager. If you do not have an Internet connection, use the offline activation method.
You can reset the license of more than one machine at the same time.
4. Click I don't have access to the machine with the SolarWinds product.
Before you begin, ensure you install the latest version of License Manager.
7. To verify that the licenses were reset, locate your license key in the SolarWinds Customer Portal,
and click View install history.
The selected computer displays as Parked, which indicates that the license count was reset.
Is Apache installed Apache allows only one site to use port 443. See Installing the Dameware
as the web server? Internet Proxy with Another Web Server for more information.
Are you using a You cannot use a URL that already exists on your server. For example, if you
URL that is already use https://yourdomain.com/support, you cannot use that URL as the
in use? Internet Session URL.
Are the correct See Modifying Your Firewall or Router for more information.
ports open on your
router or firewall?
Is the Dameware The Dameware Internet Proxy may be turned off. Check the Central Server and
Internet Proxy use the Configuration Wizard to start it.
running?
Are there special Users receive an error if there are special characters in the Internet Session
characters in the URL. Use the Configuration Wizard to remove the characters.
URL?
Did you change the The Configuration Wizard automatically verifies the bounded certificate on the
port for the new port. If the bound certificate is not a Dameware certificate, you are
Internet prompted to choose one of the following:
Session URL? l Yes: SolarWinds recommends that you choose this option. This replaces
you may not be able to make remote connections over the internet if the
agent of the target remote host is not set up to trust the certificate.
l Cancel: This reverts any changes made.
l View Certificate: This opens a new window with the certificate details.
Users who do not have the Dameware Mini Remote Control client agent installed on their computers
are prompted to download and install either an Internet Session agent or a Dameware Mini Remote
Control client agent from the Dameware Internet Proxy. If you use the self-signed certificate, your
users encounter security warnings during the download and installation process.
To prevent these security warnings, install and bind a certificate from a certificate authority to port
443 or your designated Dameware Internet Proxy port.
1. After you have received your certificate from a third party certificate authority, log into the
Dameware Internet Proxy computer as an administrator.
2. Run certmgr.msc.
3. Copy the certificate to the personal and trusted root certification authentication folder.
4. Double-click the copied certificate, and click Install certificate.
5. Run services.msc.
6. Stop the Dameware Server service.
7. Open a command line prompt, and run the following command to remove the existing
certificate: netsh http delete sslcert ipport=0.0.0.0:443
If you use a port number other than 443, enter that port number.
8. In the Certificate Manager, view the details of the certificate you installed, and copy the
certificate hash.
9. In the command line prompt, run the following command to bind the certificate to the port:
netsh http add sslcert ipport=0.0.0.0:443 certhash={certificate_hash}
appid={appid-formated_number} certstorename=root
If you use a port number other than443, enter that port number.
10. Replace certificate_hash with the certificate hash you copied and replace appid-formated_
number with a number in the appid format, such as {00112233-4455-6677-8899-AABBCCDDEEFF}.
11. Start the Dameware Server service.
Error
Error Potential Solutions
Codes
System The credentials for The user account must have sufficient rights to log in locally to
Error: 5 the remote the remote computer.
computer were
rejected
System Windows cannot Verify that the network path is correct and the target computer
Error: 51 find the network is turned on.
path
System Cannot connect to l Ensure that File & Network sharing is enabled and the
Error: 53 the remote ports are open.
computer l Check that the operating system is configured for Names
Resolution.
l Enable NetBios.
Error
Error Potential Solutions
Codes
System Not all privileges or This is frequently related to User Access Control or the
Error: 1300 groups referenced Windows Firewall. Run the installer as an Administrator or log
are assigned to the into the computer with the Administrator or Domain Administer
caller account.
System A fatal error If you have uninstalled Dameware and try to reinstall it, you
Error: 1603 occurred during may need to remove the registry keys.
installation
System The network address This is related to the Novell Network Client. Try to connect with
Error: 1707 is invalid the host name or deploy the client agent with the MSI builder.
System The specified Some or all of the operating system's Standard Performance
Error: 1814 resource name Indexes (counters) are either missing or corrupt.
cannot be found in
the image file
Winsock Cannot establish a Ensure that the network is up, that you can access the remote
Connect connection to the computer, and that the firewall has not blocked the connection.
Error: 10050 remote computer
Winsock The connection was This can be caused if the application has stopped, the remote
Connect forcibly closed by computer rebooted, the remote computer uses a hard close, or
Error: 10054 the remote keep-alive activity.
computer
Winsock Connection timed This may be due to a firewall configuration issue, a names
Connect out resolution issue, or a network routing issue.
Error: 10060
Winsock The remote l Reset the TCP port on both local and remote computers.
Connect computer actively l Ensure that the default TCP port is the same on both
Error: 10061 refused the local and remote computers.
connection l Ensure that no other program is using the TCP port.
Winsock Host not found The host name could not be found in the database queried.
Connect Check that you can access the host with the name or use the
Error: 11001 IP address.
Error
Error Potential Solutions
Codes
Winsock Could not resolve Check your DNS table or use the IP address instead.
Connect the host name
Error: 11004
Dameware and IIS use the http.sys web server engine. The http.sys engine allows multiple
applications to use the same IP address and port number. However, two different engines cannot
bind to the same port number.
You can turn on the Dameware Internet Proxy component on computers that already have a web
server installed on them.
If you already use a third-party security certificate, the Dameware Internet Proxy does not create a
self-signed certificate and uses the preexisting certificate instead. See Removing the Security Error
for Internet Sessions for information on installing a third-party security certificate on the Dameware
Internet Proxy.
By design, most web servers only serve one application per port number. For example, if you already
serve an application out of port 443, you cannot use port 443 with the Dameware Internet Proxy. To
run the Dameware Internet Proxy on the same computer, you must use a different port number for
each application.
You can change the port number used by the Dameware Internet Proxy by changing the Internet
Session URL in the Configuration Wizard. For example, if you want to run the Dameware Internet
Proxy out of port 444 instead of port 443, change the Internet Session URL to
https://domainName.com:444.
Additionally, the Internet Session URL cannot already exist in your directory structure. The
Configuration Wizard creates the virtual directory from the Internet Session URL and cannot
successfully create the path if it already exists.
If you already use a third-party security certificate, the Dameware Internet Proxy does not create a
self-signed certificate and uses the preexisting certificate instead. See Removing the Security Error
for Internet Sessions for information on installing a third-party security certificate on the Dameware
Internet Proxy.
https://yourdomain.com:443/dwnl/?3285798686
This Internet Session URL can be an IP address or domain name. You can use an IP address or
domain name that you already have, or you can create a custom path. If you create a custom path,
this path cannot already exist in your Web directory. Dameware creates the virtual path using the
entry you provide in the Internet Session URL field. The Dameware Internet Proxy may not start if the
path already exists.
The Internet Session URL must be accessible from the Internet. If it is not accessible, users cannot
join an Internet Session. See Modify your firewall or router for more information about accessing the
Dameware Internet Proxy from the Internet.
All firewalls and routers operate differently. Please consult the manufacturers documentation for
specifics, and use the information in this topic as a general guide.
When you install the Dameware Internet Proxy, you can install it on a computer with or without a pre-
existing web server. See Install the Dameware Internet Proxy with another web server for more
information.
Use the Test Connection button in the Configuration Wizard to ensure that outside users can
communicate successfully through your firewall or router.
If you do not have a security certificate from a certificate authority installed, end users may
encounter security warnings if they download an Internet Session agent before joining an
Internet Session.
l By design Apache cannot serve multiple sites out of port 443. If you are currently using HTTPS
with Apache, you cannot co-locate the Dameware Internet Proxy on the same computer and use
the same port number. See Install the Dameware Internet Proxy with another web server for
more information.
l Do not use a URL for your Internet Session URL that is already in use.
l For the optional ports for specific Dameware features, see Dameware 12.2.2 centralized
installation system requirements.
The Dameware Internet Proxy uses port 443 (HTTPS) to communicate with Mini Remote Control and
Internet Session agents on the end users' computers. The Dameware Internet Proxy also includes a
web server, which allows end users to download the Mini Remote Control or Internet Session
agent. The port number used can be modified where you configure the Internet Session URL. When
you configure the Dameware Internet Proxy using this port, the Configuration Wizard generates a
self-signed certificate and installs it. If a certificate exists already, the Configuration Wizard uses that
certificate and does not generate a self-signed certificate.
Dameware agents listen on this port for incoming remote desktop connections.
The Mobile Gateway listens to this port to allow communication between the Mobile Client and the
agent on the remote computer. You can change this port number in the Configuration Wizard.
6132 (Dameware Central Server and Dameware Internet Proxy Communication Port)
Dameware Central Server and Dameware Internet Proxy listen to this port to allow communication
between the Mini Remote Control application and the remote agent. This is specific to Internet
Sessions. You can change this port number in the Configuration Wizard or the Administration
Console.
Dameware uses this port to communicate between Dameware Server components. Dameware
components listen to all communications inbound through this port. You can change this port
number in the Configuration Wizard.
If two or more websites are using port 443, non-Dameware products may not start. Change the port
number on the other products, use different IP addresses, or install each product on separate
computers.
If users cannot access the Internet Session URL or download agents, the ports may not be open.
Check that changes were applied correctly and to the correct appliance. The Internet Session
URL may also already exist on the computer.