Forum Replies Created
-
Posts
-
In addition to this critical error, did anyone else experience issues with multi-display setups? 9.1.6108 seems to treat the secondary displays as primary so when VDI is launched the layout is jacked. For example, the VMware login screen shows up on the monitor that’s NOT set as primary.
Trust me, you’re not alone. We’re a VMware shop as well and we have to keep all of our WYSE 5070s at ThinOS 9.1.1131 with Horizon 2006 because Dell has yet to deliver a solid ThinOS build that we can upgrade to. Pretty sure they don’t have a QA team. Everything released in the past year has been crap.
We’re also seeing this with our PILOT testing for ThinOS 9.1.5067. Most of users are only seeing this at startup. We have 2 users so far that are receiving the msg throughout the day and both are on mesh networks at home.
I’m so frustrated, all of our devices in the org are still on ThinOS 9.1.1131. Dell has yet to deliver a solid upgrade without issues.
Has Dell offered a solution to this or provided a workaround?
Thanks,
For us, upgrading to ThinOS 9.1.5067 fixed the issue. No changes needed on our backend infrastructure.
no, i believe this time out issue is with ThinOS 9.x. No events are recorded until successful sign-in to the broker.
I heard from my Dell rep the other day. The new ThinOS firmware that should be released around July 15th has this fix.
Anyone have any luck with this yet? Dell engineering suggested I change the session timout on our connection servers and auth timeout on our UAGs but having no luck. Still unable to login with 9.1.2101. Just spins at “Starting broker sign-on”.
We’re having this same exact issue. Having to downgrade to 9.1.1131. Has anyone heard from Dell if there’s a fix coming soon?
Thanks everyone for the replies! I continue to work with Dell Support on this one. They are saying that they can’t reproduce it and the only difference is their AD servers are on OS version Windows 2012 and ours on on 2016.
confgen, I did make the switch from modern to classic but I’m still not receiving a prompt to change my password. Just receiving login failed. Thanks for suggestion!
Thanks for the reply! I also have an SR open with Dell to look at my logs. I doubt my token is locked since I can get in successfully using a laptop.
Just curious, what version is your UAG appliance? We are at v3.2.1 which is making me wonder if we need to upgrade, maybe? Also, did you upgrade from ThinOS 8.6 to 9.1 or is it a new build?
Spent all morning today with Dell Support. We upgraded the agent version to 3.4.6-05 and the platform utility to 2.4.6-05 using WMS and WMS File Repository. No issues, the updates applied successfully. However, receiving the same Error 105 when trying to push the ThinLinux 2.2.0.1 merlin image. The merlin version number is 4.0.2 if that matters.
Any ideas? Dell has escalated to L3.
We’re getting the same error when trying to apply ThinLinux OS updates to our WYSE 5070s. Our WMS file repository is operation as we can push other updates, i.e. VMware Horizon successfully.
NOTE: We tried to push ThinLinux 2.0, 2.1, and 2.2, no luck. We are using Dell’s USB Imaging Tool for the interim but now have 300 thin clients.
Has anyone discovered a fix for this? Dell Support isn’t helpful.
We’re getting the same error when trying to apply ThinLinux OS updates to our WYSE 5070s. Our WMS file repository is operation as we can push other updates, i.e. Horizon successfully.
NOTE: We tried to push ThinLinux 2.0, 2.1, and 2.2, no luck. We are using Dell’s USB Imaging Tool for the interim but now have 300 thin clients.
Has anyone discovered a fix for this? Dell Support isn’t helpful.
