The Release Notes, as well as the SolarWinds products, take advantage of JavaScript. Please enable active scripting.

Congratulations on your purchase of SolarWinds User Device Tracker (SolarWinds UDT). SolarWinds UDT streamlines and automates port monitoring and managing.

This version provides these key features:

  • User Tracking: Monitor AD domains and see when and where users are and have been connected.

  • User Details: View all information Active Directory makes available on a specific user.

  • User Search: Search for a user and automatically navigate to User Device Tracker detail pages.

  • Targeted Search: Search for a specific device (IP, hostname, MAC) and automatically navigate to User Device Tracker Endpoint Details .

  • New Reports: Generate reports on UDT capacity, devices on a specific VLAN, active endpoints (per node), connected MAC and IP addresses, nodes with IPv6 addresses, unused ports, devices by OUI, user history.

  • Advanced Alerts: Find out when a new device (MAC) appears on your network.

  • Enhanced Topology Mapping: Enables UDT to provide more accurate information on the connections among your managed devices.

  • Ad Hoc Reporting: Provides information on the connections among your managed devices.

Fixes in this Release

Note: If you have applied Service Packs or Hotfixes to your product, they were delivered with readme.txt files. These files contain fixes that supersede the information found in the Release Notes.

This release of User Device Tracker includes the following fixes:

UDT Fixes

  • Addresses a limitation that no predefined report shows unused ports on monitored nodes.
  • Fixes an issue with deleting multiple nodes.
  • Fixes an issue with account limitations that erroneously prevents viewing node details.
  • Fixes an issue with a Watch List resource error on the UDT Summary view.

Orion Core Fixes

Note: Besides UDT fixes, this release also includes the following fixes and updates to the Orion Core (Orion Core version 2011.2) components shared by all Orion products:

  • Errors arising when deleting orphaned objects during database maintenance have been resolved.
  • Values returned by selected date and time variables have been corrected.
  • Network Sonar Discovery and Node Management no longer truncate node names to 32 and 40 characters, respectively.
  • Orion Report Scheduler now correctly shows existing jobs as scheduled for the current Windows user, even when they are scheduled for other users. Changing the account name under which a job is scheduled no longer defines a completely new job under the new user account name.
  • An issue resulting in the display of incorrect text in exported PDFs has been fixed.
  • An issue causing errors when previewing reports in the web console has been traced to a failure to translate Wahr/Falsch, in German, as True/False boolean values. Report schemas have been updated accordingly.
  • Database Manager now allows Orion user accounts with dbo_owner and public permissions to access the SolarWinds database. Previously, sysadmin privileges were required.
  • It is now possible to use the Select All checkbox, without causing errors, to select more than 250 objects in Node Management.
  • The SolarWinds MIB database (MIBs.cfg) has been updated Alvarion OIDs.
  • The Seed Router selection method available in Network Sonar Discovery now properly handles seed routers requiring SNMPv3 credentials.
  • The correct NetObjectID property was added to trap templates that were not properly updated for a previous release.
  • An issue resulting in the requirement of an excessive period of time to add a single monitored object has been corrected.
  • With improvements to Network Discovery, the full name of nodes with names longer than 32 characters is now stored in the SolarWinds database.
  • An issue preventing the successful get of required security identifiers (SIDs) for group accounts has been resolved. SolarWinds no longer allows Active Directory authentication or account creation for groups that do not have non-empty SIDs.
  • The Export to PDF feature now functions correctly when the web console is assigned to a specific IP address and the PDF is exported from a remote machine accessing the web console by hostname and not by IP address.
  • An issue resulting in failures to poll volumes after performing database maintenance has been corrected.
  • The contact SolarWinds link provided on the Completing the Orion Configuration Wizard view has been corrected.
  • Negative values supplied by the VMware API for memory usage statistics are properly handled to provide correct results.
  • Learn more links on the Add New Account page have been fixed.
  • The acknowledge alert link in emails sent by triggered Orion APM application alerts now functions as designed.
  • The Unmanage Scheduling Utility now properly handles the case when default custom properties are deleted.
  • Schemas for selected Inventory reports have been updated to correctly report polling engines.
  • New Scheduled Report tasks can now be created without error for Active Directory users.
  • The web console now properly handles the maintenance of multiple Edit Object Properties views, each in different tabs in the same browser.
  • Updates to the SolarWinds poller have improved polling completion percentages.
  • A website script error that is thrown when managing groups containing large numbers of devices on the Manage Groups view has been fixed.
  • The Configuration Wizard no longer deletes existing https bindings on upgrade or repair.
  • An issue where domain names for DHCP nodes were truncated before insertion into the SolarWinds database has been corrected.
  • New Scheduled Report tasks can now be created without error when the Terminal Server Windows component is installed.
  • Network Atlas no longer fails to complete file synchronization with the Orion database. This failure had been linked to Network Atlas users who had insufficient permissions to access the Network Atlas synchronization folder.
  • Cisco Catalyst 2960-S Series Switches (Model WS-C2960S-48FPS-L) are now correctly identified by Network Sonar Discovery.90, 94
  • SolarWinds now polls the correct object identifiers (OIDs) for monitoring IBM AS/400 disks.
  • The web console now properly handles the maintenance of multiple list resources, each in different tabs in the same browser.
  • Updates to Network Atlas improve how Network Atlas handles groups and custom properties.
  • Spaces are no longer removed from messages supplied to the Modify Syslog Message action.
  • Updates to the SolarWinds Information Service (SWIS) enable the Configuration Wizard to more gracefully handle corrupt performance counters when validating the NetPerfMon service.
  • An error that left the To: field out of email messages sent as alert actions has been fixed.
  • The machine types for multiple American Power Conversion Corp. devices--including back-ups, matrix-ups, and smart-ups devices--are now correctly recognized.
  • Events for node name changes have been restored.
  • Clicking displayed results in the Nodes with High Memory Utilization resource now displays the correct Memory Utilization chart.
  • The web console now proparly handles resources assigned a ResourceID of 0. Previously, resources with a ResourceID=0 would cause web console errors.
  • Removing a VMware DataCenter from monitoring no longer generates an error in the VMware Assets resource. ESX hosts on the removed Datacenter are automatically reassigned to their new DataCenter for monitoring.
  • The Selected Node Properties resource now correctly provides all custom properties that are available for listing for a selected node.
  • A condition where objects in a scheduled unmanage period are not restored to a managed state as scheduled, if the DataProcessor service is restarted during the unmanaged period has been corrected.
  • Trap messages for email that include null characters (\0) in the values for listed variable bindings are no longer cut off at the null character.
  • A condition preventing secured WCF sommunication between polling engines in a multiple polling engine environment, resulting in website errors, has been corrected.
  • The Last XX Syslog Messages resource is now capable of displaying more than 25 messages at a time.
  • IOS version information is now reported correctly on the Node Details view for selected Cisco devices.
  • Grid lines have been restored to separate items listed in web console resources.
  • Resources on the Node Details view now properly handle virtual machines returning null as the Powered State.
  • SQL variables using the "@" prefix now function correctly when included in HTML-formatted email messages.
  • Failures of the SolarWinds Collector Job Engine v2 due to incorrectly handling an error resulting from attempts to poll an incorrect OID for interface MAC addresses have been corrected.
  • Updates to code in the Orion SNMP library enable the addition of SNMPv3 devices, as designed.
  • The machine type for Cisco ASA5580 devices is now correctly recognized.
  • URLs longer than 255 characters are no longer truncated when provided in the Orion Report Scheduler.
  • The machine type for IBM P595 PowerPC devices is now correctly recognized.
  • Node custom properties assigned floating point values, are now validated correctly in the web console.
  • The web console now uses the UTF character set. This corrects a number of issues with how reports appear in the web console.
  • Network Atlas running on Windows 7 now accepts Active Directory credentials, as designed.
  • Network Atlas map resources now display correctly on the Group Details veiw of the web console.
  • SolarWinds SSL certificates are now created using the SHA1 has algorithm, instead of the less-secure MD5 algorithm.
  • SolarWinds APM variables ${ComponentsWithStatusFormatted} and ${ComponentsWithProblemsFormatted} are now translated correctly for use in email actions.
  • The Send Syslog Message action now functions as designed when the Syslog Message Facility is set to local use - level 0.
  • It is now possible to edit the filenames of PDFs exported by the Orion Report Scheduler.
  • The compressed archive created for the SolarWinds Diagnostic Utility has been updated to enable extraction on Windows Server 2003.
  • Network objects selected in Network Sonar Discovery to be ignored no longer display on the Devices to Import tab.
  • The Send New Syslog Message alert action can now send messages to custom ports.
  • An issue preventing the correct display of node states in the web console has been corrected.
  • An error that regularly corrupts the collector SDF has been fixed, allowing the Collector Data Processor and Collector Polling Controller to start, as required.
  • Job Engine v2 credentials are now correctly synchronized, allowing effective communication between polling engines.
  • An issue resulting in errors in Syslog resources on the Network Summary page, has been traced to an incorrect translation of a localized date, using "." instead of ":", and it has been fixed.
  • A security issue preventing valid user access to selected reports and views in the web console has been corrected.
  • Failures in vCenter polling due to undetermined validity of provided credentials have been fixed.
  • An issue resulting in stopped polling and 'VMware Guests with Problems" errors has been resolved.
  • The titles of object properties, including custom properties, are now stored correctly, with spaces, in the database, preventing the collapse of Custom Property List resources into a single line.
  • The correct timestamp is now displayed for syslog messages both in the Node Related X Syslog Messages resource and in the Last X Syslog Messages resource.
  • The SolarWinds MIB database (MIBs.cfg) has been updated with the correct value for the cExtSnmpTargetAuthInetAddr OID.
  • An issue that forced links to the Admin Settings view to instead open the Network Summary view has been corrected.
  • A change in the format of forwarded Syslog messages has been corrected.
  • Monitored objects with Chinese names are now correctly displayed with Chinese names in the web console.
  • Cisco Catalyst 2960, 3560, and 3760 Series Switches are now correctly identified by Network Sonar Discovery.
  • The alignment of labels in Network Atlas has been improved to better indicate object status.
  • Network Sonar Discovery can now accept community strings of up to 250 characters in length.
  • Virtualization monitoring now better handles credentials for wireless ESX hosts that regularly lose connection (drift in and out of range).
  • Documentation has been updated to direct the installation of Additional Polling Engines and Additional Web Servers.
  • An issue that has caused both the trap service and the SolarWinds Information Service to restart repeatedly when upgrading multiple poller environments has been fixed.
  • An issue related to dependencies that resulted in polling delays has been fixed.
  • An issue preventing the display of variables in triggered alerts has been fixed.
  • An issue preventing the trigger of basic alerts from additional polling engines has been fixed.
  • An issue with trap filters that prevented trap alerts from triggering has been fixed.
  • The SolarWinds installer now deletes orphaned job scheduler results before completing an upgrade to the current version of SolarWinds NPM.
  • Groups defined on a dynamic basis now update as required.
  • A condition resulting in the display of negative polling completion rates has been corrected.
  • An update to the SolarWinds Information Service corrects an error with serialized query results seen when the NCM web console integration is installed.

Fixes in Previous Releases

These issues were fixed in previous releases:

UDT Version 1.0.1

  • Managing job timeout settings and enabling/disabling monitored port types are no longer dependent on a config file. These settings are availabe on a new UDT Advanced Settings page (DEVICES > UDT Settings > Advanced Settings). When this release is installed, the software uses a new set of default settings (stored in the database) to prevent job timeouts that were initially corrected, in release 1.0, by manually modifying the UDT.BL.dll.config file. Also, following installation, if you opt to delete a port type from the list of port monitored port types, the software prompts and accepts an affirmative response as a trigger for removing associated port entries currently being stored in the Orion database.
  • Guest accounts no longer have access to UDT port discovery and settings pages.
  • Adjustments in polling settings no longer result in a device unintentionally being removed from the list of devices managed in UDT.
  • SNMP bulk requests are now throttled to prevent CPU over-utilization.
  • UDT Reports now appear in a report group (HOME > Reports)
  • Port Discovery no longer freezes when ports are being discovered on Layer 3 switches.

Known Issues in this Release

The following issues have been identified in version 2.0:

No Endpoint Information is Shown

When using SNMPv3 credentials to poll devices (any vendor, any model) UDT does not show any endpoint information.

For a workaround, see this Knowledge Base article

UDT Obscures Data for Switch Ports with Multiple MAC Addresses

A switch port with multiple associated MAC addresses (for example, the swithc port itself, a VOIP phone connected to it, and a laptop connected via the VOIP phone) UDT sees only the layer 2 swith port.

No User Data Retrieved Via WMI (Windows Server 2003)

If you are running UDT on Windows Server 2003, and setup WMI retrieval of user data from a Active Directory domain controller outside of the local UDT server's domain, UDT is able to connect to the remote AD controller but does not retrieve user data. Data retrieval is blocked by an implementation of the Custom Security Descriptor (CustomSD). There is a workaround currently being tested. These notes will be updated with the workaround as soon as it is verified.

For a workaround, see this Knowledge Base article

Avaya 8600: Layer 2 and Layer 3 Information Not Being Pulled

When the user monitors the Avaya 8600 in UDT, polling cycles are not retrieving appropriate information for Layer 2 and Layer 3.

Legal