Relative vs. Absolute mouse orientation on the F1DN104K

On the F1DN104K, we ran into an issue early on in which the mouse cursor would sporadically jump across the screen when the KM was connected to zero or thin clients with the older Teradici firmware.  This issue was caused by the fact that Teradici's virtual environment was looking for a standard relative mouse signal, whereas the KM uses an absolute mouse signal (a cross between standard mouse and touchscreen).  Upon identification and duplication of this issue, a fix was put in place on F1DN104K to address this issue, creating a V2 version of F1DN104K.  If the version number of the F1DN104K is V111111, it does not have the fix.  If the version number is V211111, it has the fix in place.

NOTE:  The version number is located on the bottom of the KM.  If you need help finding your version number, click 
here.


This fix was put in place for the F1DN104K-3, F1DN108K-3 and F1DN104K-3 units under V111111 during the development stage of these products.  The F1DN108K was the only KM SKU that did not receive this fix. 

While we have made changes on our side to address this issue, Teradici has released a firmware build on their side that addresses the Absolute vs Relative mouse issue, regardless of KM version number.  In short, if the Teradici firmware build is 4.8 or greater, the version of Belkin Secure KM will no longer matter.

Was this support article useful?

Additional Support Questions?
Search Again