Forum Replies Created
-
Posts
-
If you previously changed the policy on the device level through create an exception then it will not inherit changes from the group. you would have to reset the policy on the device so that it picks up inherited changes.
We are very happy (and stable) with 9.1.2101. All 5070’s running 9.1.2101, citrix workspace 21.4.0.11 & Teams pkg. Seems to be very stable although we do have the occasional device that forgets to check-in to WMS, loses its settings and the validate key button needs to be pressed. I think this was addressed in 9.1.3 but due to the upgrade bug we only have a dozen or so running the latest version. We had seen a LOT of issues with 9.0 but by 9.1.2 most of them were addressed.
We have unlocked the Network Connections portion for our users since the change to allow granular control over certain sections of the System settings and we have yet to see any users mess with any of these settings aside from inputting and fixing their Wifi passwords when they input them incorrectly. For what its worth.
We’ve also noticed that if the user inputs the password incorrectly the very first time after each reboot it will ask you for the Wifi password. Entering the password correctly here will not update the password that was originally entered when connecting to wireless for the first time. Maybe if dell allows that screen to update the stored SSId password then that would fix your issue but i would just allow the network connections screen in the meant time.
Yes i’ve upgraded a handful of WYSE 5070 slim and extended chassis and can confirm the same behavior.
After upgrading i’ve seen a mixed bag of devices that have stopped checking in due to the WMS Advanced settings checkbox becoming unchecked and a validate key needing to be pressed. I’ve had a couple boot back up after the firmware was installed and after a reboot they have kicked off the rest of the package installations BUT were unresponsive in WMS prior to the reboot. This leads me to believe that there is an issue with the new firmware and reading the DHCP Option Tags we have in place.
As of right now this firmware cannot be deployed in any enterprise organization. I will do a few users who i need to test but i’m in a holding pattern until dell fixes this issue.
We’ve had a LOT of issues with users inputing their WIFI pwd wrong OR selecting the wrong ssid and its gotten hung up. With the older version of ThinOS and ThinOS lite we have just gone into the device level and changed the pwd to something easy for them. In cases where they do not have internet we’ve had to walk users through connecting to their hotspot OR hardwiting it to their router temporarily so that the settings push down to the device and they can blank out the pwd/enter the new one. Then change the pwd back after they are done and connected
We noticed the session locking up immediately after upgraded the MR1, i was able to get rid of this by disabling the Screen Saver. We have also noticed that when you lauch a session is enters window modewhich spans across both monitors and take approximately 15+ seconds to snap to full screen after the VM is launched. I also noticed that CTRL ALT Down arrow no longer works, its seems to work on the local WYSE side but no longer while in the VM.
