Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

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.

Environment

  • UDT 3.3

Notes

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 hotfix is used to fix the issue with all nodes are being monitored by UDT after upgrade then customer should perform the following additional steps:
    1. Execute SQL query:

      DELETE FROM udt_nodecapability
      DELETE FROM udt_job

      THIS QUERIES UNMONITOR ALL UDT NODES (REMOVE ALL NODES FROM UDT MONITORING).

    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.

In the Orion Web Console, click Settings > All Settings > High Availability Deployment Summary.

Select the pool you want to disable.

Toggle High Availability to Off.

Install the hotfix on the primary server in the pool.

Install the hotfix on the secondary server in the pool.

In the Orion Web Console, click Settings > All Settings > High Availability Deployment Summary.

Select the pool you want to enable and toggle High Availability to On.

The Orion Web Console verifies all SolarWinds product versions match across the HA pair before enabling. If you receive errors, check your product versions.

You may need to recreate the HA pool. For details, see Set up an HA pool.

 

Last modified

Tags

Classifications

Public