Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > User Device Tracker (UDT) > User Device Tracker 3.3 Hotfix 1

User Device Tracker 3.3 Hotfix 1


Updated: 10/31/17

Fixed issues

This hotfix addresses the following issues:

  • All Orion nodes were being monitoring by UDT without request.


  • UDT 3.3


  • This hotfix is located at SolarWinds Customer Portal.
  • This hotfix must be installed on the main Orion server, all additional UDT polling servers, and all standby servers with UDT installed.
  • Repeat the steps below for all your servers with UDT.
  • This hotfix modifies the following file on the Solarwinds User Device Tracker (UDT) Orion Server:


Installation instructions

The latest released version of Falcon will automatically install this hotfix.

  1. Do the following for ALL POLLING ENGINES with UDT installed:

    The latest released version of Falcon will automatically install this hotfix.

    • Use an Administrator account to log in to the server that hosts your SolarWinds Orion installation.
    • Run the Orion Service Manager, click Shutdown Everything, and close the Orion Service Manager.
    • Run the SolarWinds-UDT-v3.3.0-HotFix1.msp file ON ALL POLLING ENGINES with UDT installed.
  2. If the hotfix is applied after upgrade, then the customer should perform the following additional steps:
    1. Execute SQL query:

      DELETE FROM udt_nodecapability
      DELETE FROM udt_job


    2. Clean up Collector sdf data and JobEngine sdf data on each Poller.

      JobEngine data: C:\ProgramData\Solarwinds\JobEngine.v2\Data
      Collector data: C:\ProgramData\SolarWinds\Collector\Data
      For clean up data file please do the next steps:

      • all SolarWinds services should be stopped on all polling engines
      • Navigate to Data folder
      • Prepare a backup copy of JobEngine35.sdf or PollingController.sdf file
      • Delete JobEngine35.sdf or PollingController.sdf 
      • Copy JobEngine35 - Blank.sdf or PollingController-Blank.sdf to the same folder and rename it to JobEngine35.sdf or PollingController.sdf
      • Remove the Read-only attribute from that files
      • After cleaning up all UDT polling engines start all SolarWinds services for all engines

Install the hotfix with SolarWinds High Availability

If your product is using Orion Platform 2016.2 or later, use these instructions to install the Hotfix with SolarWinds HA.

Important: The HA pool must be disabled to begin installation. If you install prior to disabling, the pool is automatically disabled.

  1. In the Orion Web Console, click Settings > All Settings > High Availability Deployment Summary.
  2. Select the pool you want to disable.
  3. Toggle High Availability to Off.
  4. Install the hotfix on the primary server in the pool.
  5. Install the hotfix on the secondary server in the pool.
  6. In the Orion Web Console, click Settings > All Settings > High Availability Deployment Summary.
  7. Select the pool you want to enable and toggle High Availability to On.
  8. The Orion Web Console verifies all SolarWinds product versions match across the HA pair before enabling. If you receive errors, check your product versions.
  9. You may need to recreate the HA pool. For details, see Set up an HA pool.
Last modified