Unsolved
10 Posts
0
6264
USB redirection broken in BLAST Linux VDI
I can not get USB redirection working with the BLAST protocol for Horizon 7.7 using Ubuntu 18.04 and Windows 10 images on WTOS 8.6_013.
PCOIP works on both the 4.10 client and WTOS 8.6_013 on a 5040.
BLAST USB redirection works for both Windows and Linux when used via the 4.10 Windows x64 client.
It appears something is broken with Blast for Horizon in this WTOS version.
Anyone else confirm BLAST USB redirection working in WTOS 8.6_013 with Horizon?
UPDATE: Windows 10 CDR works in the latest 8.6_206 WTOS image. Linux (Ubuntu 18.04 still does not). PCOIP is not an option for Linux VDI in Horizon 7.
blhx
10 Posts
0
March 1st, 2019 12:00
I confirmed USB redirection does not work on WTOS 8.6_013 on a Wyse 5040. I put in a support call but have not received a response yet.
montefusco
1 Message
0
March 2nd, 2019 02:00
Same problem with:
I'm waiting answer from DELL support.
smith_ll
4 Posts
0
April 11th, 2019 05:00
Did Dell come back to you on this?
Troubleshooting almost the exact same issue. PCOIP working fine, Blast fails to pull through for no reason?
vincent.huang
1 Message
0
April 22nd, 2019 00:00
smith_ll
4 Posts
0
April 24th, 2019 06:00
I've just upgraded to 8.6.019 today.
Running BLAST sessions connecting to VmWare View RDSH 2016. USB redirection working fine outside of ThinOS, it detects the USB device is redirectable and it lists it in Device Manager but doesn't allow access.
The same device connecting from Windows client works fine. The same device on the same terminal but connecting via PCOIP works fine.
CyberTron123
3 Posts
0
June 13th, 2019 04:00
blhx
10 Posts
0
November 13th, 2019 09:00
I tried WTOS 8.6_028 Wyse 5040 and Ubuntu 18.04 using Horizon 7.7. I can confirm that USB redirection still does not work. Dell has no solution for us yet. I am going to try Horizon 7.10 next to see if that helps.
Using Horizon client 5.2.0 build-14570289 USB redirection works using PCOIP or Blast for Windows 10 and also works using Blast for Ubuntu 18.04 (still no PCOIP agent for Ubuntu). This leads me to believe the WTOS implementation of the Blast USB redirection feature is broken or needs a special setting that I have not found yet.
CyberTron123
3 Posts
0
December 3rd, 2019 00:00
I just upgraded to the latest ThinOS 8.6.206 and horizon 7.10
still doesn't work with Blast and USB. DELL must fix this! It is insane that they can't get it to work!
blhx
10 Posts
0
February 13th, 2020 08:00
Still broken in 7.11 with 8.6_204 and 8.6_206. This missing feature is forcing us to look at WTOS alternatives like ThinLinux, Win10Iot and 10zig Linux. I have tried Ubuntu 18.04.0 and 18.04.3. However, I am most certain this is a WTOS flaw with how it communicates with Linux VDI. When using clients like Horizon client 5.2 for windows, the linux vdi os detects and mounts the USB drives just fine using the TSCLIENT automount. When using WTOS I see no syslog entries for any device being detected when inserting or removing USB drives. I am thinking it may be a problem with drive redirection as both windows 10 and linux VDI seem to use a mechanism for mounting all shared drives but the WTOS interface does not allow you to specify which drives you want to share like the windows client does.
Here is the output from syslog when enabling drive sharing in the windows client:
Feb 13 10:51:15 lic01001 dbus-daemon[28470]: [session uid=1000 pid=28470] Activating via systemd: service name='org.gtk.vfs.Metadata' unit='gvfs-metadata.service' requested by ':1.57' (uid=1000 pid=28855 comm="nautilus-desktop --force " label="unconfined")
Feb 13 10:51:15 lic01001 systemd[28377]: Starting Virtual filesystem metadata service...
Feb 13 10:51:15 lic01001 dbus-daemon[28470]: [session uid=1000 pid=28470] Successfully activated service 'org.gtk.vfs.Metadata'
Feb 13 10:51:15 lic01001 systemd[28377]: Started Virtual filesystem metadata service.
Feb 13 10:51:15 lic01001 gvfsd-metadata[29376]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Feb 13 10:51:15 lic01001 gvfsd-metadata[29376]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Feb 13 10:51:15 lic01001 dbus-daemon[28470]: [session uid=1000 pid=28470] Activating service name='org.freedesktop.FileManager1' requested by ':1.57' (uid=1000 pid=28855 comm="nautilus-desktop --force " label="unconfined")
Feb 13 10:51:15 lic01001 dbus-daemon[28470]: [session uid=1000 pid=28470] Successfully activated service 'org.freedesktop.FileManager1'
Feb 13 10:51:15 lic01001 gvfsd-metadata[29376]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Feb 13 10:51:15 lic01001 gvfsd-metadata[29376]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Feb 13 10:51:15 lic01001 dbus-daemon[836]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.9355' (uid=1000 pid=29380 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
Feb 13 10:51:15 lic01001 systemd[1]: Starting Hostname Service...
Feb 13 10:51:15 lic01001 dbus-daemon[836]: [system] Successfully activated service 'org.freedesktop.hostname1'
Feb 13 10:51:15 lic01001 systemd[1]: Started Hostname Service.
Feb 13 10:51:15 lic01001 gvfsd-metadata[29376]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Feb 13 10:51:15 lic01001 gvfsd-metadata[29376]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
Feb 13 10:51:16 lic01001 nautilus[29380]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory)
Feb 13 10:51:54 lic01001 gvfsd-metadata[29376]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed