Forum Replies Created
-
AuthorPosts
-
Just coming back to this one. I have upgraded to Pro license and disabled the Front and rear USB ports via the policy settings. However I can still access the USB storage devices on the TC. I have tried re-registering the device but no luck. Is there anything else I need to do here to enable the functionality?
Thanks,
CL
Looks like it might be a license constraint. Looking at the feature matrix. I am using only standard version.
Is there any other way to lockdown the USB ports when using Standard version of WMS
Cormac
Hey CG,
Thanks again for the response. I missed the reply until just now. I cant find that setting anywhere. Is it in WMS or locally on the device? Here is what i see in WMS policies under WES settings.
Cormac
I re-registered the device using the hostname and i am having a lot more success now.
Does anybody know if the hagent service is required for WMS or if it is for the older WDM version? I enabled this also but not sure if it is required. Service was set to manual on the thin client before i changed it.
Is it possible to configure the easy setup kiosk mode with this method you mentioned. For example, single group with common setting and easy setup kiosk mode enabled. Then have per device exception for the rdp connection? Thus having every device in kiosk mode with independent rdp connection config.
Cormac
April 9, 2021 at 2:31 pm in reply to: WMS 3.1 and Wyse 5070 Device compliance status “pending” #104993Hey CG, you are right i actually noticed all the devices became compliant after a period of time. However when i run the app policies they still timeout after 15 mins mins and never get past “pending” state.
I am not sure any of my commands from the WMS server are working. I have confirmed telnet from TC to WMS on port 1883 is good so i think MQTT is working. Should it be working both ways? Telnet is failing on port 1883 from WMS to TC but when i check on the TC with netstat it is not listening on that port.
Thanks for the help.
Hey Midas,
thanks for replying. I was able to get this working by upgrading the WDA version to 14.5. I am running WMS 3.1 and I guess it needs this newer version.
-
AuthorPosts