Forum Replies Created
-
Posts
-
Do you have a Dell Sales contact? If so, ask them to speak with an SE. And, ask them to submit a Help A Customer request, give them your Service Request number, this will get someone engaged beyond normal support channels.
You might want to give Relative Mouse mode a try. Here is a link to how to enable it.https://docs.pikvm.org/mouse/#relative-mouse-on-v2-platform-otg-hid
You might be able to block the USB device with the policy from USB Redirection.
If you haven’t already done so, reimage the device. BTW, which device are you using?
There is a fix, you will have to contact Dell Support for the instructions and the files. I am no longer working for Dell and cannot share the information.
Jim
Give this a try, you will want to delete the app or image policy using the file. Then locate the file in your repository and delete it. Let WMS sync. then using the console upload the file and test.
There is a fix available with direct contact with Dell Support. Ask them for the KB article to fix WMS upgrade. You will need to have a personal Dell support account to access the article.
Activating ThinOS converted devices requires the purchase of Wyse Management Suite Pro AND ThinOS activation licenses. If you are using Wyse Management Suite Standard, you immediately think you must buy WMS licenses for all your devices. The best way to do this is to purchase WMS Pro and ThinOS Activation Licenses for the number of devices you want to activate, creating a WMS Pro Cloud tenant with the licenses ready to assign.
All you have to do now is to register the devices to WMS Cloud using your default Group Policy Token, this will automatically assign a TAL to your device if is does not have one.
You can check the assignment by referencing the Subscription section in Portal Administration, if the device is assigned, unregister it and place it back in your WMS standard console.
I had another SE report they changed the DB passwords to a stronger version and they were able to apply updates.
