Unsolved

This post is more than 5 years old

1 Message

945

October 10th, 2019 06:00

New to WYSE, need help with USB passthrough to new 2016 VM environment

Hello,

I recently started at a manufacturing company that utilizes a large WYSE terminal/VMWare environment.  I have never dealt with WYSE terminals before, but have already learned a lot about them.  I have been tasked with a project to get roughly 80 of our Server 2008 VM's upgraded and replaced with Server 2016.  Most of these have gone without a hitch, but I have been struggling with one of our departments in particular: shipping. 

Our current shipping department uses FedEx Worldship.  We have a main FedEx host server, and 7 scanning stations using Wyse terminals connecting to individual Server 2008 VM's.  In general, they work OK.  Need to reboot things here and there, but overall they work well enough.  I recently built a new FedEx host server on 2016, and 7 new scanning stations.  The server and FedEx software itself seems to work fine. 

My issue has been the USB peripherals we need to pass through from the Wyse terminals to the 2016 servers.  I built the new 2016 servers exactly the same as our 2008 environment, but I cannot get our USB peripherals to reliably connect to the new 2016 servers.  Our 2008 servers had TCX 6.0.0.6 installed on them for USB devices, so I installed that same version on the 2016 boxes.  

Is there a newer version of TCX that I should be using on the newer 2016 servers?  If TCX is no longer supported, how do I get USB devices to pass through the WYSE terminal reliably to the new 2016 servers?

Each of our scan stations have 3 USB peripherals that need to interface with our remote desktop environment.  We have USB barcode scanners, which for some reason work fine most of the time.  We have USB fairbanks scales, which are plug and play with windows, and we have USB Zebra shipping label printers.  

In our 2008 environment, with all 3 peripherals plugged into the WYSE terminal, all devices are recognized quickly and work fine for the most part.  When I connected one of our WYSE terminals to the new 2016 servers, I had to reboot the WYSE box itself, or the 2016 vm multiple times to get all 3 peripherals to show up and function.  Even then, I needed to reboot multiple times per hour to keep the scanner, scale, and printer functioning for our shipping team members to process orders.  This lack of reliability made me put them back on the 2008 environment, as we do not have enough IT staff to reboot 7 stations constantly throughout the day.  

If anyone has any expert experience or advice on what I need to do to get our 2016 server environment to play nicely with our WYSE terminals and USB devices that work fine in server 2008, please let me know.  I was hoping to have this department upgraded to 2016 and finished over a month ago, and it has been a struggle ever since. 

Thank you all,
Mike J

 

No Responses!
No Events found!

Top