Forum Replies Created
-
Posts
-
So what your saying is I’m trying to fit a square peg through a round hole… I was wondering if the 3040 was underpowered to what I was trying to do. Appreciate you clarifying it for me. Shame we didn’t foresee the rapid adoption of Teams, we replaced all our thin clients less than 2 years ago and video meetings were not part of the design at the time.
Guess we’ll need to split our Citrix users into two groups now. Those that do video meetings and those that don’t.Thank you for your help.
From Dell Wyse Administrator and Release note Guides:
Citrix Unified Communications support on Wyse 3040 Thin Clients
Following features are not supported on Wyse 3040 Thin Clients due to client resource limitations:
● Video call or meeting
● Share screen
To avoid audio choppy issues during the audio call or meeting, users are recommended not to perform the following tasks:
● Move the application window frequently or quickly.
● Scroll down the Microsoft PowerPoint slide, Word document, Excel sheet, or a website page frequently or quickly.
● Play a video in an ICA session frequentlyDo you have pending jobs? If so, make sure to clear by either having outstanding devices check-in or force unregister the device that is outstanding.
Best practice it to perform upgrades incrementally, there are a few that you must have done prior to jumping to 3.5.1.
Brian,
Sorry for delay in responsing. Never enough time in a day.
We are using Wyse 3040 Thin Clients. My test environment is the only ones using a 9.1 firmware. The version is 9.1.1131, I’ve tried newer versions and ran into different issues.
With v9.1.3, it was going to screensaver and then was unable to log back into an existing session, even after a reboot of the thin client.
With the latest version 9.1.5 it crashes back to login the moment I open Teams. I can log back in but it crashes again when trying to connect to my hardware, audio/webcam.I did confirm that it is not showing HDX Webcam but rather the actual name of the webcam device.
I’ll have to check my settings for the browser content redirection, not sure if I enabled that.Just feels like ThinOS is becoming harder to manage and setup as time goes on. Updates haven’t exactly felt like they are making things better, but here’s hoping!
Check your application Security and make sure they are selected for access.
Do you have ThinOS 9.1.5067 Microsoft AVD package v1.5_1325 for Dell Wyse 3040, 5070, 5470, and 5470 All-in-One Thin Clients installed?
https://dl.dell.com/FOLDER08003895M/1/Microsoft_AVD_1.5_1325.zip
Download and extract. Then upload into WMS as a package for 9.1. Then go to your policy and under the Firmware section, select application, and select the AVD package to install on your device.
When I consult WMS users, I always recommend upgrading without skipping a version, even if the document states you can. Also, make sure that you have no Jobs pending.
– WMS_3.5.1.exe binary can be used if you are installing Wyse Management Suite for the first time or upgrading from previous versions 3.2/3.2.1/3.3/3.5.
– If you are using Wyse Management Suite 3.3.1, you must upgrade to 3.5 before upgrading to 3.5.1.
3.5.0.866, 3.5 15 Nov 2021
3.3.1.29, 3.3.1 16 Aug 2021
3.3.0.276, 3.3 05 Jul 2021
3.2.1.44, 3.2.1 17 May 2021
3.2.0.780, 3.2 26 Mar 2021
3.1.1.580, 3.1 HF1 25 Feb 2021
3.1.559, 3.1 04 Dec 2020What version are you using?
Did you just upgrade? If so, from what version?
Jim
Good afternoon, the file is available in Downloads/DHC. My link was in error.
Hey nstaab,
there any update on your preceding post? We are experiencing similar issues among users using Wyse 3040 and Wyse 5070 thin clients running on ThinOS 9.
We have the keyboards working with the following settings on USB redirection:
vUSB Force Redirect 0x11889535
vUSB Force Redirect 0x11889545
This was required to get the V4 keyboards to work.
But……
If the wyse device is set to lock then the keyboard appears to remain connected to the remote session so when a user comes to unlock it they are unable, and we had to plug in a standard keyboard to unlock the wyse and gain access to the running session. Therefore we have had to disable terminal lock in the wyse system prefrences.
For the new V5 keyboards they are working with out the addition of the redireciton policies,
VID 0X1188 PID 0XA101
