USB redirection Chromebooks

[Ryan Johnson]

Hi,

 

I am attempting to get USB redirection working on our Chromebooks via Xendesktop.

 

We are using G Suite to manage the Chromebooks, users connect through the Citrix Receiver App in Chrome kiosk mode, so I can use .cr file to change some configuration if needed. 

 

We don't use the connection bar when logging into our virtual environment.

 

 

 

Ryan

[Priyanka Karanth]

Hi Ryan,

 

Are you trying to access USB devices in KIOSK mode? If so, you need to enable the Toolbar for the session (by default, in KIOSK mode it's disabled). 

Please refer this article for enabling USB redirection inside Citrix Session: http://bit.do/c6r6X

 

If you have already tried this, can you please explain what is the issue you are facing?

 

Thanks

Priyanka Karanth

[ted assefa]

Hi,

I have also almost the same issue with our chromebook. I can connect to the printer locally but when I try to connect it in the citrix session I get the message "The device you are selected is not compatible with citrix receiver" error. I do this through connection center and Add devices.. I have Citrix Receiver for chrome v:2.5.1.302

[Shruthi Udayakumar]

HI Teddy,

 

Error says that the printer cannot be redirected through USB redirection.

 

You can use local PDF printing or Google Cloud printing instead.

[ted assefa]

Does anyone found an answer for this issue. we got the same situation. if I follow this instruction I get an error: The device you selected is not compatible with Citrix Receiver.

https://support.citrix.com/article/CTX200825

thx,

[Nick Fuchs]

@ted assefa - While there is more limited support of USB devices running on Chrome OS as there are with other client operating systems, I would double check to make sure you are whitelisting the device in the google console (chrome device management). I put together some more clear steps in this blog post: http://nickyfixit.com/2018/12/citrix-usb-redirection-on-cloudready-chrome-os/

[Greg Fox1709163042]

In case anyone comes across this, the fix for me was adding the VID and PID to the "Client USB device redirection rules" on our policies. After adding, the device redirected properly!