Tools

Pre-install Dameware Remote Everywhere (DRE) agent on a Windows OS image

This article describes the limitation when installing the DRE agent.

First published date

8/20/2020 6:51 PM

Last published date

2/10/2025 4:37 PM

Overview

Installing the agent as part of the Windows OS image will not work as expected.
The reason for this is that upon installing the agent on a machine, it creates a unique machine ID for each installation to give the device an identity for remote connection.
Deployment using reimaging corrupts the installed unique machine ID. This causes some agents to be uninstalled automatically, and the device name changes as soon as it connects to the DRE Cloud.
Each DRE agent has a specific ID recorded on a .ini file, that ID is essential to each agent and serves as an identifier for the remote end when the remote sessions are initiated. If the administrator clones a device with a DRE agent already installed, the agents would all have the same ID, which would result in crossed connections, and the agents would not work correctly.

For DRE agent deployment, you can generate a single DRE Agent installer by configuring it as "No installation limit" and "no expiry".
However, this agent must be installed per machine.
 

Product section

Dameware Remote Everywhere

Resolution

We have some documents with regard to DRE Deployment:
Generate an MSI installer to deploy agents in DRE
Deploy DRE Agent with Group Policy and Active Directory