Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > User Device Tracker (UDT) > User Device Tracker (UDT) Documentation > Previous Versions > SolarWinds User Device Tracker 3.2.3 Hotfix 1

SolarWinds User Device Tracker 3.2.3 Hotfix 1

 

Updated June 13, 2017

Fixed issues

This hotfix addresses the following issues:

  • VLAN context polling for VLANs created through VTP is now supported.
  • The SWIS indication failure for UDT by subscribing to the changes on specific properties of the node are now eliminated.
  • Indirect connections in the port history resource are not displayed when the UDT.UI.ShowAlsoIndirectConnections setting is set to False.

This hotfix modifies the following files on the Orion server:

  • C:\Program Files (x86)\SolarWinds\Orion\UDT\SolarWinds.UDT.BusinessLayer.DLL.config
  • C:\Program Files (x86)\SolarWinds\Orion\UDT\SolarWinds.UDT.BusinessLayer.DLL
  • C:\Program Files (x86)\SolarWinds\Orion\UDT\SolarWinds.UDT.Common.DLL
  • C:\Program Files (x86)\SolarWinds\Orion\UDT\SolarWinds.UDT.Jobs.DLL 

Install this hotfix on both the primary Orion polling engine and any additional Orion polling engine.

Environment

UDT 3.2.3

Notes

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 the 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.

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.

Installation instructions

Note: SolarWinds strongly recommends that you only edit the files mentioned as instructed. Any additional modifications to the files may result to system performance issues or may create an error state.

  1. Go to C:\Program Files (x86)\Solarwinds\Orion\UDT\ and create a backup of the following files:
    • SolarWinds.UDT.BusinessLayer.dll.config
    • SolarWinds.UDT.BusinessLayer.dll
    • SolarWinds.UDT.Common.dll
    • SolarWinds.UDT.Jobs.dll
  2. Run the installer and extract the files to a temporary folder.
  3. Copy and paste the following files to the ModulePatches folder (%Program Files(x86)%\Solarwinds\Orion\ModulePatches\):
    • UDT-3.2.3-patch.zip
    • UDT-3.2.3-patch-sql
  4. Run the following query, and:
    update udt_setting set settingvalue=1 where settingname='UDT.PollAllActiveVLANs'
  5. Restart the Orion services
  6. Run the configuration wizard twice and make sure that the Database, Services, and Website options are selected.

 

For more information, contact Technical Support at www.solarwinds.net/support.

Last modified

Tags

Classifications

Public