Forum Replies Created
-
Posts
-
This is so frustrating. The WYSE units are decent, but the support is terrible. I have a load of 5470 AIO units with PCoIP. I’m trying to connect direct to host, which does work with a little hack, but is not ‘supported’ and doesn’t work i’m told. The VM’s are in GCP and i keep on getting directed to use AWS settings or some other nonsensical idea and am told that the issue is with GCP, even when it’s not and this has been proved.
If these units had a minor tweak to fix this bug and decent support to fix all of our bugs, then they’d be awesome units
Is there any way to escalate this? This should not be a hard UI change to fix and i’m not getting a great response from Dell.
Still getting a slow response from Dell support. It’s clear that PCoIP works with software agents. How hard can it be to roll this feature out in v9.1, making direct to host connections a breeze for setups without a broker?
I bet you they’ve plugged in their phone to charge via the device off the USB. Then Apple is trying to call home.
I’ve tried that too, but still no luck. I get the message “The network connection has been lost (UDP)”.
To be clear, i’m trying to connected to Teradici software agents, not host cards. These are machines i spin up in Google Cloud with either the standard or graphics agents installed. I’ve confirmed the 5470AIO machines will connect via this method, but it was tricky to get working and took some testing from Dell Japan. Also, this method locks you to only 1 connection and not a range. Being able to connect to multiple VM’s via PCoIP software agents would be a big win for these units. They can already do it, it’s just not configured properly IMO.
Instructions for v8.6 ThinOS were;
You need to set up Teradici Cloud Access on WTOS Connection broker configuration UI.
And then please input the computer name to connect VM to Sign-on Domain of General options tab.
If you want to setup by WMS, you need to setup parameters in [Advanced Device Configuration – Advanced] for Teradici Cloud Access.
SignOn=Yes EnableMessage=No (No display security warning message)
ConnectionBroker=TeradiciCloudAccess Host=aaa.bbb.ccc.ddd (Connect VM’s IP address or FQDN)
DefaultUser=xxxx (if you necessary)
Domainlist=xxxxxxx (Connect VM’s Windows Computer name)
I have the silver PCoIP Teradici sticker on the back of the unit and the service tag confirms PCoIP in the product specs. The about menu looks like this.
[url=https://ibb.co/9TC0SnM][img]https://i.ibb.co/J7MTgnh/E2-E05-EEB-5080-40-D9-901-E-83-FD505017-A2.jpg[/img][/url]
There are no Broker Settings in this “About” menu though. In the Cloud WMS, i can see;
Broker Settings > Global Broker Settings >Default Broker Type
Citrix Virtual Apps and Desktops
VMware Horizon
Windows Virtual Desktop
Microsoft Remote Desktop Services
Amazon WorkSpaces
Teradici Cloud AccessIf i plug in a USB to RJ45 dongle, will that NIC interface work with some 3rd party devices and set the protocols up to the cloud VM?
I have this working now. You need to put the IP of your machine into the Broker connection IP. Reboot. Then enter the username and in the domain path, put the hostname of the machine, then you should be able to connect. Far more complicated (and incorrect!) than it needs to be.
To confirm, Dell Wyse 5470 AIO works via PCoIP with Teradici standard and graphic software agents in gcp.
So, my vendor sent me a new unit with build 8.6_511 installed. But the BIOS is still v1.0.0?!
I’ve tried connecting to my Teradici agent (software) in the cloud, but again, no luck. I go to Remote Connections > Broker Setup and select “Teradici Cloud Access”, but after reboot, that setting is back at “None”. Has that stuck? Is this a bug? This is where you set the certificate level for PCoIP.
Has ANYONE got this Wyse 5470 AIO unit working with PCoIP to a Teradici software cloud agent, not a hardware card?
