Forum Replies Created
-
Posts
-
My WMS public cloud (hosted by Dell) was upgraded to 3.2 over the weekend and I noticed the same thing in my public cloud session. I then launched an InPrivate window in Edge and logged in and the event messages cleared.
Thanks for the tips
To clarify, the is the local admin policy tool on the thin client. So that means if you factory reset a device you have to go in and turn the proxy OFF and save it on the device, then it should connect and get an IP and pickup DHCP option tags. Unless I’m miss understanding whats happening for you.
Check your policy under proxy and turn the proxy off if you don’t have one defined. That’s been around since 9.0 and I still don’t understand why the Proxy in WMS is on but undefined by default.
Remove the Citrix package and reinstall or just Delete All packages and reinstall. Had the same thing and that fixed it. Seems to crop up if you do an upgrade AND install packages at the same time.
When I upgrade from WTOS 8 to 9 I move devices to a global polic that first updates the OS. When complete I move it to a sub policy (regional for time zones and URL brokers and app installs/updates) where I push the packages. Seems to work smoother and also makes it easier to roll out firmware updates by region during off hours.
Doesn’t look like I can push anything from WMS Public Cloud until they upgrade to 3.2 this weekend, 4/2. I did download the linuxx64-21.3.0.38.tar.gz file from Citrix under the Citrix Workspace App for Linux Tarball package and it did sync with into my Apps & Data – Hybrid Client App Inventory from WMS Repo.
Is DHC 64-bit or should I get the 32-bit package? I’m making an assumption here.
I don’t think you’ll be able to test that. You’ll need to install the Citrix Virtual Desktop Agent on your server since that is what you want to connect to, but the VDA agent needs to register to be able to broker the connection between the server and endpoint.
https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/manage-deployment/vda-registration.html
Citrix HDX and ICA are proprietary technologies and they want their money. There is licensing involved etc. I would reach out to Citrix and begin a vendor engagement and see if they can offer you a trial for a proof of concept or something to that effect. I don’t believe there is any other way for you to test this.
Turn off local mapping and usb redirect for services you aren’t using. Also if you aren’t using unified communication plugins like Zoom VDI, Jabber VDI, Teams optimization, turn those off in the virtual channel unified communication settings.
I found an issue where I had printing and USB redirect working fine in my policy, then I began testing unified communication plugins like Zoom, WebEx, and Jabber. After turning on those UC Virtual channels my printing stopped redirecting, but it wasn’t something I noticed right away. I turned off USB redirect for serial, smart card and other things I wasn’t using and turned off the UC Virtual Channels I wasn’t using in production and printing started working.
There is a Citrix Workspace App for Linux virtual channel limitation of 32 virtual channels, 17 are reserved. As of release 21.3 CWA for Linux (released March 9) the number of virtual channels has been increased to 64 virtual channels which should hopefully address this issue. For now, ThinOS 9.1 is using CWA for Linux 20.12 from December 2020 so we are stuck with the VC limitation until Dell packages CWA 21.3 for ThinOS 9.1.x
Has this ever worked in the past?
If it’s worked before, what changed recently?
Is there anything on the Windows device that would be blocking USB storage devices by corporate policy like antivirus or Windows firewall?
Anything in the event logs on the Windows device at the time you connect indicating an issue with USB redirect?
I’m not sure I’m following how you want to connect. In my experience there’s always been something to broker the connection.
Are you a Citrix customer currently? You could reach out to Citrix and see if they could provide you with a Citrix cloud environment for testing.
There is nothing to install on the thin client. When you plug the printer into the thin client is it recognized on the thin client? You would see on the thin client in the Event Log if the printer is identified when plugged in. In the Peripheral management section of System Settings you should see the printer and have the option to print a test page.
If that is successful you would use USB redirection to the RDP session. On the Windows machine you are connecting to in RDP you would want to have the drivers installed for the printer if Windows doesn’t automatically detect and install them.
If its XenApp i would think there might be something in the event logs on the XenApp server.
Looks like the message occurs when you are connected, how are you connecting (Citrix, VMWare, RDP)?
Anything in the Windows system event logs on the machine at that timestamp when the panic heap occurs?
Glad you got it working. To be fair I did mention that in my February 22 post
”
For the record, this was the one that finally got it working
[HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Spark Native] “isVDIEnv” = “true”, datatype:REG_EXPAND_SZ
Also, for obvious reasons, make sure your turn on the Citrix Virtual Channels for the different unified communications in WMS for the policy under Citrix Session Settings… Zoom VDI, WebEx VDI, Teams VDI etc.
I now have both Zoom VDI and WebEx VDI working.”
We use WMS Public Cloud so it was updated last week I believe. Things are still working without issue.
Is there a reason you can’t move forward with a newer version of WebEx just for testing?
You have the “VDI” turned on in the WebEx admin console and the registry edits on the desktop install?
Try wiping the device in the Bios and then reimage from USB. I’ve had my 5070 and 5470 get in strange reboot loops when switching from WiFi disable on Enet up to Enet not detected WiFi enable would cause constant reboots even after resetting to factory. Resetting to factory and walking through the ThinOS 9.1 OOB setup if you would select WiFi for how your device connects to the internet as soon as you select the SSID and enter a password it would reboot, rinse and repeat.
The only fix I found was a complete device wipe from the Bios where they make you confirm 4-5 times, “Are you sure you want to wipe?” Re-enable boot from USB and turning off secure boot to image again to 8.6, upgrade to 9.1 and all problems and anomalies seem to go away for me after a full device wipe.
Now if Dell could just make the USB Imaging Tool work with a current version of Windows or make it work from Ubuntu to actually make USB imaging sticks without a headache I would appreciate that. My current home version of Windows 10 is as up-to-date as you can get and USB Imaging tool never seems to work to make new imaging sticks.
