We have completed the bulk of the development effort and are now focused on testing the latest release of User Device Tracker (UDT). UDT 3.0 is going to reach Beta status soon. This is your chance to install the latest version and provide feedback on the new features and fixes. Providing feedback during the beta is the best way to ensure that your feedback will be incorporated in to the release. To participate, simply fill out and you will be sent the download links for the Beta. Remember, Betas cannot be installed in production and you cannot upgrade the Beta to any other future versions.
The following enhancement have been added to UDT:
You can define the set of rules that UDT uses to determine if a network device belongs on your white list. If so, the device appears in UDT resources as a safe device.
You can add
If there are devices connected to your network that are not on the white list, they will appear in a new 'Rogue Devices' resource and alerts will be generated:
You can also define the set of rules that determine if a network device should be ignored by UDT. If so, UDT discards all related data. This is handy e.g. for HSRP and VRRP MAC addresses.
Many network devices suppport sending trap notifications when an endpoint connects or disconnects. UDT is able to process these notifications now to update the endpoint connection information immediately (and not wait for the next poll).
Configuring your Domain Controllers properly, so that UDT is able to collect login information, is not an easy task and users find it difficult. That's why we have prepared a set of tests that help you diagnose whether UDT can access the information in the Domain Controller.
First you need to test the credentials; if there are errors, UDT helps you fix them.
When the port to which an endpoint is connected changes, an alert is generated:
If the device is configured with read-write SNMP credentials (and supports this operation), you can easily shut down a port. This functionality is also available via the API/SDK.
UDT now distinguishes between ports that are administratively down (icon with red cross) and operationally down:
There is a new report for wireless endpoints now:
If a network device is configured with VRFs, UDT will display the information: