Time to upgrade! NAM is scheduled for end of support. It's time to move to Dynatrace our all-in-one software intelligence platform.

Upgrading DC RUM 2017 with ADS

NAM 2017 May and earlier releases, contained two server components: Central Analysis Server (CAS) and Advanced Diagnostic Server (ADS).

Starting with Dynatrace NAM 2018 release, we moved the ADS component to CAS and we renamed the CAS 2018 release to NAM Server. As a result, Dynatrace NAM 2018 release provides the ADS functionality as an Advanced Diagnostics on Demand (ADoD) option within the NAM Server.

Renamed components after upgrade from NAM 2017 May release to Dynatrace NAM 2018 release:

DC RUM 2017 and older NAM 2018, NAM 2019
RUM Console NAM Console
Central Analysis Server (CAS) NAM Server
Advanced Diagnostic Server (ADS) Advanced Diagnostics on Demand feature of NAM Server
Agentless Monitoring Device (AMD) NAM Probe

There is no upgrade for the ADS component. Once you upgrade your CAS 2017 to NAM Server 2018, the ADoD starts to work automatically. It is enabled by default and no configuration is necessary.


Your ADS 2017 license is automatically considered your ADoD feature license. In NAM 2017 deployment that uses multiple ADS servers, one of the ADS server license would cover the NAM Server ADoD license and the remaining ADS license files will be converted to NAM Server licenses.

  • Consider using the remaining ADS licenses (now converted to NAM Server licenses), to install additional NAM Servers (old CAS) and create or expand a NAM Server cluster.

    Keep in mind that, there is no automated conversion or upgrade from ADS servers to CAS servers. If you choose to use converted ADS licenses, you will have to install NAM Server from scratch on the re-purposed ADS server and then add the new NAM Server to your cluster as a node.

  • Consider re-using disks from the old ADS server in your NAM Probes. With the ADoD feature enabled, the NAM Probe disk space requirements will increase.


Once you upgrade the CAS 2017 to NAM Server, most of the ADS-based reports will work in the same way. The exception are the reports that aggregate data across large data sets from the old CAS-ADS deployment. The ADoD feature extracts up to 1000 records per report and aggregates on these reports can only be calculated on such limited data sets.

Typically, ADS reports are focused on diagnostics. They present limited data sets filtered by specific dimensions for example, time, user name, URL and client IP address. ADoD supports such reports out of the box.

Built-in reports

All built-in NAM 2017 reports will work after the upgrade to NAM Server 2018. For example, all the user activity reports, waterfall charts and error detail reports will work out of the box on the NAM Server. Keep in mind these reports will use the ADoD feature data, not your old ADS 2017 server data.

Custom reports

Your custom ADS-based reports (with ADS data views) will not be converted automatically. There are two ways to convert your custom ADS reports to NAM Server 2018 :

  • Use diagnostic console command that converts the exiting reports to use ADoD data views.
    1. On the NAM Server go to Tools ► Admin console.
    2. In the Diagnostics column, click Commands console.
    3. Search for, and click the UPGRADE ADS REPORTS TO ON DEMAND command.
      A summary will list backup location of previous version reports and all converted reports.
  • Edit each of your custom ADS-based reports and change the DMI data view for each of them from ADS data views to ADoD data views.
Report errors

Until you convert your custom ADS-based reports, your existing ADS reports will continue to reference the old ADS servers within your deployment. If you decommission the old ADS servers before converting the reports, your custom ADS-based reports will display errors.

ADoD traits and limitations

  • Historical ADS 2017 data is NOT available in the ADoD feature.
  • The ADoD limitations are determined by the disk storage size on NAM Probes that host the ADoD data and the access speed to those disks.
  • The ADoD feature doesn't require a separate server machine, but it increases disk space requirements of the existing NAM Probes.
  • Because ADoD uses the NAM Probe disk to store the measurements, the only limit on the number of measurements stored is, the NAM Probe disk size.
  • The NAM Probe manages the disk space automatically and deletes the oldest data files when the disk is about to become full. As a result, the ADoD data storage period may vary depending the disk size of the NAM Probes and traffic levels you monitor.

Upgrading NAM 2017 deployment with ADS 2017 components:

Short version

This is a short version of the upgrade procedure. It covers major upgrade points. It does not include steps like database upgrade, upgrade paths and deployment backups. If you would like to follow the full upgrade procedure use the main upgrade topic.

Step 1. Get license

Contact your license management team and request license upgrade from NAM 2017 DLM licenses to Dynatrace NAM 2018 component licenses. The license management team will generate Dynatrace NAM 2018 component license files based on your old DLM licenses. These license files are stored in your eServices account and can be downloaded for Offline license management.

Step 2. Disable ADS servers

In your NAM 2017 deployment:

In the NAM Console, delete your existing ADS clusters.

Make sure no ADS server is listed as a Report data server in your primary CAS servers configuration.

For each main ADS server (primary ADS server in a cluster or standalone ADS server), delete all AMDs that are data sources for that ADS server.

Remove all ADS 2017 servers from the NAM Console device list.

Stop and disable the Dynatrace Advanced Diagnostics Server service on each ADS server machine.

Step 3. Upgrade components

Upgrade all components in the recommended order:

Upgrade the console (Upgrading the NAM Console).

Upgrade the report server (Upgrading NAM Server).

Skip ADS

Since Dynatrace NAM 2018 release doesn't include ADS as a component, the procedure doesn't contain the upgrade ADS step.

Apply component licenses (Skip if you have capacity licenses).

If you use capacity licenses, you can skip this step. Capacity licenses should be applied after the NAM Probe (old AMD) upgrade.

In the NAM Console, use either the Online license management or the Offline license management to upload and activate the component licenses:

Apply component licenses to every standalone NAM Server (old CAS) within your deployment.

Farm upgrade

If your deployment uses clusters, apply the component license to the primary NAM Server (old CAS) server of each cluster within your deployment.

Upgrade Linux (Updating Linux).
Make sure your NAM Probe is running Red Hat Enterprise Linux 7.x (64-bit), the Red Hat Enterprise Linux installation media and license, and access to additional packets required by NAM Probe.

Upgrade the probe (Upgrading the NAM Probe software).

Apply capacity licenses (Skip if you have component licenses).

If you use component licenses, you can skip this step. Component licenses should have been applied after the NAM Server (old CAS) upgrade.

In the NAM Console, use either the Online license management or the Offline license management to upload and activate the capacity licenses:

Apply capacity licenses to every NAM Probe (old AMD) within your deployment.

(if necessary) Upgrade TCAM. (TCAM upgrade via GUI).

(if necessary) Upgrade any other components that you have integrated with your deployment.
If you want your deployment integration perform well after the upgrade, make sure the integrated components are at their supported versions.

Step 4. Remove DLM

Remove or uninstall the DLM software responsible for license administration in NAM 2017 and earlier releases.

DLM can stay

While all Dynatrace NAM 2018 release components use eServices licensing platform, your deployment may contain legacy components that still require DLM. Make sure your deployment doesn't use such components before removing DLM.

If you choose to remove DLM, do as follows:

  1. In the Windows Registry Editor (regedit), navigate to:


  2. Edit this entry in the registry:

    C:\Program Files\Common Files\Compuware\libdlm64.dll

  3. Set Value data to 1.

  4. Open a Windows Command Prompt (cmd) in administrator mode (Run as administrator).

  5. In the Command Prompt, issue the command:

    msiexec /x {0305B5EC-97C0-4636-B3C0-38DC697AA920} /qn /l*v "C:\DLMuninstall.log"

    Adjust the uninstall log path (C:\DLMuninstall.log) as needed for your environment.

  6. Find Removal completed successfully in the DLMuninstall.log log file to verify that DLM was uninstalled.

Step 5. Remove ADS

Uninstall and remove any ADS 2017 components from your upgraded deployment and decommission the hardware.