Forum Replies Created
-
Posts
-
What version of Citrix VDA are you running on the VM?
We’ve had UDP audio working over EDT but the experience was poor so we disabled that Citrix policy. You can check this documentation here:
https://support.citrix.com/article/CTX220730
Keep in mind the Citrix receiver on ThinOS 8 is a Dell modified version of Citrix receiver from around 8 years ago or so. ThinOS 9 is now using a full Citrix Workspace App for Linux and will be subject to Linux’s limitations.
What is it you’re trying to get UDP audio working with?
I don’t use PCoIP or AWS so I’m not much help there. I am curious, though, since you’re saying the logs aren’t helpful; are you getting the logs from WMS using Request Log File or exporting logs locally to USB thumb drive? Typically the exported logs are more robust and could provide more information. You can also have any of the impacted associates run a network trace from the thin client and reproduce the issue and it will save locally to the thin client until you export log files from that thin client.
Anything stick out in the Windows event logs at the time of the disconnects?
Can Amazon provide any network packet captures from their side?
This appears to be fixed by enabling “HID Fingerprint Reader” under the Citrix session settings underneath all of the UC communication settings. Must be a specific virtual channel the Bloomberg keyboard tries using to pass the fingerprint portion.
Thought I’d check back on this.
Just tried the same thing in WMS Public Cloud, went from our implemented on-prem ADFS to try doing an Azure AD implementation not realizing exactly what @david.drum pointed out with the SAML claim. In WMS public cloud 3.2.1 44, everything we copied in seemed to pass the test when you test the SSO, but the sign on would fail after saving the configuration. We’re going to be retiring the on-prem ADFS solution for Azure AD so I’m looking for something other than the WMS built in two-factor email.
That’s great, thanks CG.
Hopeful for some new Zoom and WebEx plugin availability outside the regular quarterly releases.
I would also check the MS Teams network port requirements.
https://docs.microsoft.com/en-us/microsoftteams/prepare-network
Ports
UDP ports 3478 through 3481
IP addresses
13.107.64.0/18, 52.112.0.0/14, and 52.120.0.0/14Is this MS Teams 32-bit or 64-bit?
You have Teams Optimization turned ON for the thin client policy under WMS Session Settings >> Citrix Session Settings >> UC Virtual Channel Settings
Also Other Virtual Channel Settings >> USB Redirection ON
Then under WMS Settings >> Session Settings >> Global Session Settings >> USB Redirection Exclude Audio Devices ON and USB Redirection Exclude Video Devices ON
When the sound stops working does the Citrix Audio Service stop running on the Windows Machine? You can run services.msc and see what’s running. There would also be an event log entry usually for faulting application ctxaudio or something to that effect.
What version of the Citrix VDA are you running on the desktops? Are these VM’s or physical desktops or both?
I was also going to suggest you could add ‘HD audio-1’ without the ‘’ as the Playback Device in the WMS console under Peripheral Management >> Audio >> Playback Device.
Im a bit surprised your setting is working for you because the 5470 isn’t using USB audio it’s built in audio on the main board. You might run into an issue if you do plugin a USB audio source like headset or speakers if you still want the audio source to be the 5470 built in. Just be aware.
I haven’t seen this. After swapping topology do you also select a new primary monitor? Is this on 3040 and 5070 or specific to something like a 5470 AIO?
what happens if you swap DP ports on the back of the device instead of moving the topology in the monitor layout?
Is this a WD19 USB-C dock? I know there where some known issues in the past with audio on the dock. Are the speakers USB or 3.5mm output from the dock?
That’s a great find and helpful for me to look at root cause between our old server and the new one we built that got this working.
Also, I’d like to ask, this functionality was removed in WTOS 9 correct?
Ahhhhhh, it’s the captive portal WiFi self test so to speak.
Apple uses captive.apple.com to detect that you are on a captive network, and once it detects this, it does some very Apple-specific actions. Google and Microsoft use the same method, except with a different url.
If any application wants to detect it is on a captive network, it can connect to any of these websites (captive.apple.com or the Google or Microsft site), check the result, and that way detect a captive network. You absolutely don’t need to run on an Apple, Google or Microsoft device for this.
Correct.
That is the policy as shown in WMS Public Cloud. If I look in the admin policy tool on the thin client locally it has my local WiFi listed, so when connecting from home it appears to remember and add the local WiFi to the local admin policy tool. I couldn’t possibly add every home user WiFi to a WMS policy so I leave it empty.
