Forum Replies Created
-
Posts
-
For your Citrix broker server are you doing the URL to the store? For example I have https://company.name.com/Citrix/NSWEBFAS as my broker.
Citrix Workspace mode turned on
NetScaler/ADC authentication method is Default
i have no issues with Microsoft 2FA SAML auth that way.
I have Azure AD SAML authentication working in WTOS9. I think your roadblock is going to be the approval of the authorization. I hit approve on the MFA app and it goes through launching the full workspace.
From a 2FA perspective doesn’t an auto logon defeat the purpose of a secure 2FA?
Am I misunderstanding your objective?
I’ve seen this on a few of our 3040’s which is a slight variation of your message at the end with “trap: deadlock detected”
Vanadium: TW Protocol error: Execution failed (Code -2147483626). Cmd = CMD_TW2_BITBLT_IMAGE_REGION_AVOIDCACHE.ICA trap: deadlock detected
On the machine the thin client is connecting to, is anything going on in the Windows event logs?
I’m seeing CitrixCseEngine ID 8 and 9 messages with Invalid handle instead of successful RSOP calculations.
Ok here is my clarified testing:
- Taking a working device with the proxy disabled from WTOS 9.0.2108 to WTOS 9.0.3030 – Working fine
- Factory resetting a device with WTOS 9.0.3030 installed and walking through the OOB setup – Working fine
- Taking a device on WTOS 8.6_206 to WTOS 9.0.1136 which is using A10Q_wnos-9.0_11.36 – Proxy is enabled and cannot continue on to upgrade to WTOS 9.0.3030.
The primary issue is getting the device from 8.6_x to WTOS9. My engineer confirmed that they wanted to make sure 9.0.3030 resolved the OOB experience and they will create a new upgrade package for example A10Q_wnos-9.0_30.30
Correct, its a custom build and its pretty old. If you look at the receiver for Windows release versions here https://support.citrix.com/article/CTX112613 it would put 14.0.x around 2013/2014, though I don’t know if the Windows versions would accurately apply in this case so I don’t want to misinform.
Most of the reason why WTOS 9 was created was so Dell could produce a version of WTOS that could separately upgrade the Citrix Workspace and JVDI and other agents outside the OS/firmware. They also need to compete with Igel and 10Zig in a faster changing VDI/Thin Client market.
The proxy issue is finally resolved in 9.0.3030 when doing the OOB experience and the device is already installed with WTOS 9.0.3030.
I still need to check going from 8.6_206 (or newer) directly to WTOS 9.
<p style=”text-align: left;”>Have you tested on a 5070? I believe the WTOS 9 documentation states the 3040 is too taxed for audio/video for Jabber and Teams and the 5070 is recommended.
</p>
How does the 3040 behave with only one monitor in use?Glad that worked.
I’ve had to fully delete devices from WMS in the past to get them to re-register and it sometimes fixes other oddities.
Another thing you can try is Wipe the device or Unregister the device. When you go to the Dashboard view of WMS click on the Device name like WT509a4c03f2c4 and when your looking at the device level info under More Options at the top righ the only drop down option is Delete, Delete the device from WMS and then re-register it and see if the behavior persists.
I’ve had random issues in the past where Deleting the device entry from WMS altogether has fixed thing when you register it again.
Couple things I would try, don’t know if it will fix anything but I’ve found oddities other areas where it has fixed stuff:
- Reset monitor back to factory. I know its the thin client freezing but I’ve had stranger things occur like monitors being set to DP1.2 for daisy chaining from one DP out, but then going back to a thin client with DP 1.2 enabled it doesn’t play nice, DP 1.2 also doesn’t like WD19 docks if enabled and on two separate ports
- Change your screensaver image. If its a PNG make it JPG, if its BMP make it JPG. If its JPG resize it and save it and re-upload it, you never know.
- What happens if you do Sleep=20 but no screensaver, does it wake from sleep?
- Since it sounds easily reproducible, enable a persistent log capture and see what comes back on the logs when you power cycle. I was never able to get a log capture because i couldn’t consistently reproduce it.
I use WMS Public Cloud so I can test the NA feature after July 10 when the cloud version upgrades to WMS 2.1.
I can no longer find the 8.6_x to WTOS 9 A10Q or X10 packages on Dell’s download site.
I do see these two below, but no longer the upgrade, perhaps they pulled it for hotfixes which would be good news.
- ThinOS 9.0.1136 Base Image file for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients
- ThinOS 9.0.2081 Image file based on 9.0.1136 for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients
I think there are two separate issues that throughout the course of this thread have emerged.
- WTOS 9 WMS Agent Failed To Check-In – Proxy Enabled By Default -SR#1025297396 (if anyone wants to report and reference existing SR)
- WTOS 9 WMS Agent Failed To Check-In – DHCP option tags not working
- Is DHCP Option tagging not working because of the proxy?
I think its good we’ve worked to identify the issues, the DHCP option tagging issue might be better served in a separate thread labeled as such. Not a thread hijacking complaint just trying to better serve this community which i appreciate and to help others easily find what they’re looking for.
The issue with the Proxy enabled by default is still not fixed in WTOS 9.0.2081 under certain conditions.
Test 1 – Upgrade from 8.6_x – WTOS 9.0.1136
- After upgrade proxy is enabled by default, WMS cannot check-in and pull policy
- No proxy policy is ever set in WMS for 8.6 or for 9, this is never an issue in 8.6
- Even with proxy policy set to OFF in WMS for WTOS9 the upgrade from 8.6-9 still enables the proxy
- Manually disabling the proxy using (locally on thin client) System Setup>>Admin Policy Tool under Network Configuration>>Proxy Settings>>Enable Proxy toggle to off and Save & Publish will correct the issue
Test 2 – Upgrade from WTOS 9.0.1136 to WTOS 9.0.2081
- Upgrading from WTOS 9.0.1136 to WTOS 9.0.2081 after performing the above manual steps, the proxy remains off and the upgrade takes place without issue.
Test 3 – Factory Reset of WTOS 9.0.2081
- Performing a factory reset of WTOS 9.0.2081 the OOB setup has Proxy enabled
- Manually disabling the proxy using (locally on thin client) System Setup>>Admin Policy Tool under Network Configuration>>Proxy Settings>>Enable Proxy toggle to off and Save & Publish will correct the issue
These scenarios hold true for 3040, 5070, and 5470 mobile.
What Dell really needs to do is pull the upgrade package from 8.6-9, correct the proxy issues and re-issue the package. With the proxy enabled by default it makes updating a device remotely impossible without having to physically touch the device or walk someone through disabling the proxy locally on the device, this is not a scalable solution for organizations that rely on pushing updates remotely.
It sounds like this setup is working for most users except for this one user?
Try changing the picture or image or leave it as default. Also try Sleep=0 and see if it freezes after a certain time frame.
Its been an intermittent issue with various firmware versions from my experience. 8.6_206 doesn’t seem to freeze, haven’t moved to 8.6_303.
