Thanks for your feedback Ashish.
To address your points...
1. The USB key firmware is version 3.25. The "USB 1.02" refers to the server detecting the USB key/dongle as a USB 1.x device.
2a. Yes, I am able to see the key in Admin Control Center on the Windows 2008 R2 server. See attached screenshot.
2b. Yes, there are (3+) entries in device manager on the Windows 2008 R2 server. See attached screenshot.
3. The attached screenshot shows the additional information when the mouse is hovered over the key icon.
4. Ran haspdinst.exe -purge on the Windows 2016 server (Operation successfully completed).
5. Ran haspdinst.exe -i on the Windows 2016 server (Operation successfully completed).
After un-installing/re-installing using command line approach, the issue still persists. The USB is detected in device manager (with the exception of the "HASP Key" entry), however, the License Manager is unable to detect the USB key or vice-versa.
To address your points...
1. The USB key firmware is version 3.25. The "USB 1.02" refers to the server detecting the USB key/dongle as a USB 1.x device.
2a. Yes, I am able to see the key in Admin Control Center on the Windows 2008 R2 server. See attached screenshot.
2b. Yes, there are (3+) entries in device manager on the Windows 2008 R2 server. See attached screenshot.
3. The attached screenshot shows the additional information when the mouse is hovered over the key icon.
4. Ran haspdinst.exe -purge on the Windows 2016 server (Operation successfully completed).
5. Ran haspdinst.exe -i on the Windows 2016 server (Operation successfully completed).
After un-installing/re-installing using command line approach, the issue still persists. The USB is detected in device manager (with the exception of the "HASP Key" entry), however, the License Manager is unable to detect the USB key or vice-versa.