Start a Conversation

Unsolved

A

15 Posts

11424

August 14th, 2019 02:00

Problem with a Wyse 5040 AIO Thin Client

Hi,

In the past we have supplied our customers with Samsung Wyse devices and they have had very few issues, but we are unable to get any more of them so we have supplied them with a Dell Wyse 5040 instead.

On the whole this looked to be working okay, but we have now come across a problem which I am hoping you can help with. How the customer worked with the Samsungs was they would work on their own desktop VDI but if a customer came in they would move into the meeting room and log in to their desktop again so they could share information with the customer. They are not at this point logging out of their VDI on the first Wyse just locking it, this works fine for the Samsungs, but when they try to do this with the Dell device they just get a black screen.

How do we get this to work on the Dell unit in the same way it does on the Samsung? I logged a call with Dell but they have told me I need to have software support rather than just basic support.

Can anyone help?

Thanks,

ARLamb200

3 Apprentice

 • 

724 Posts

August 14th, 2019 08:00

What firmware version are the 5040's on?

What are you managing them with? WMS or INI files?

What broker are you connecting to?  Horizon or Citrix?

My advice would be get them to the latest firmware from support.dell.com, 8.6_027

 

15 Posts

August 16th, 2019 01:00

Hi,

We only have one of these devices in use at the moment, so we are managing it with ini files.

I have tried to upgrade the firmware with WSM free but can't see how to do that, I have also tried to upgrade it from an ftp server but again we can't get this to work.

It was at this point I tried to get help from Dell, but they just told me to buy software support.

Are you able to advise on the firmware upgrade?

We are using a horizon solution.

The device is running version 8.5_020   PD10_wnos

3 Apprentice

 • 

724 Posts

August 16th, 2019 15:00

firmware is available at support.dell.com

Firmware update guides here

<ADMIN NOTE: Broken link has been removed from this post by Dell>

https://www.dell.com/support/manuals/us/en/04/wyse-3020/thinos_8.5_ag/firmware-upgrade-using-ftp-server?guid=guid-04277cab-23d1-4f93-b4fb-3ead1a4def95&lang=en-us

Ignore the part about downloading firmware from Dell Digital Locker

15 Posts

August 20th, 2019 06:00

Hi,

I have followed the instructions through but it is still not upgrading the firmware, is there any way to trace what is happening when it doesn't run?

My setup is a Windows ftp server which has the PD10_wnos file and an ini file which contains:

Autoload=2
loadpkg=1
Addpkg=TCX,FR,horizon

I know I am missing something but I am not familiar with these devices at all.

 

3 Apprentice

 • 

724 Posts

August 20th, 2019 09:00

Likely you dont have the files in the proper directory structure.  I find it much easier to work with a 3'rd party FTP server, like FileZilla Server, which has a running log to show you what your device is looking for.  

If you insist on using MS FTP, enabling  logging and post the logs from the time the device boots and communicates with the FTP server.

This article has some good notes, specific to IIS FTP

https://www.dell.com/support/manuals/us/en/04/wyse-3020/thinos_8.5_ag/firmware-upgrade-using-ftp-server?guid=guid-04277cab-23d1-4f93-b4fb-3ead1a4def95&lang=en-us

 

15 Posts

August 21st, 2019 05:00

I think I have made progress. I used the following video to help me set up a free WMS Server:

https://www.youtube.com/watch?reload=9&v=hIBCQl4ejJU&list=PLmbFlhPb2qyU04e3zV4Bdbs8xb-zl7cUK&index=16&t=0s

I can now see the details of the device and have gone through setting up a policy and tried to do a firmware upgrade from there, but I think I may have the wrong files.

The firmware I have in there is:

5010 PCoIP 8.6_024 which is a PD10 file

The other one I have found is:

5010 8.6-027 which is a ZD10 file

I was also looking at installing the Horizon and RTME packages but when the rebooty happens I get a message about invalid files.

Can you advise what files I should upload? At the moment I think I must have the wrong ones.

Thanks

3 Apprentice

 • 

724 Posts

August 21st, 2019 08:00

Those are the proper firmware.  

ZD10_WNOS is if the device does NOT have PCOIP

PD10_WNOS is if the device does have PCOIP.

You can tell which you have by looking at the "OS Version" column in the device view. 

 

15 Posts

August 22nd, 2019 05:00

Just checked and mine definitely has PCoIP Wyse ThinOS PCoIP (8.6_024) So why won't the packages load? Or are they not relevant to this device? Thanks

3 Apprentice

 • 

724 Posts

August 22nd, 2019 08:00

Installing packages is different than firmware, and yes you should expect that you can install the packages. 

Did you upload the packages via the Apps & Data, OS Image Repository, ThinOS, Packages tab?

Did you upload the packages that correspond with the version of firmware you are on?  8.6_024?

Did you assign the packages via the firmware update portion of the policy?

Can you post the event log from the device showing the error you get?

15 Posts

August 23rd, 2019 07:00

Yes I uploaded the packages via the path you mentioned.

The packages I went for were the 8.6_027 ones I will look for an older version.

I tried what I think would be the correct version from the list of older downloads but I am still having the same issue.

How do I export the event logs? I only have the free version of WMS so can't access the desktop remotely.

Sorry to be such a pain with this.

3 Apprentice

 • 

724 Posts

August 23rd, 2019 10:00

Even with the free version of WMS you can enable VNC in a policy and use a VNC client to connect to the thin client and view logs.

You can also pull the event log from the device by going to the device page in WMS, and clicking on "Device Log".

 

15 Posts

September 2nd, 2019 05:00

Hi,

I am struggling to find the VNC setting but the event log is here:

System Start Date: 2019/08/23 Friday
System Version: MR 8.6_024 (ROM: 3.0U)
Characteristics: FilesystemSecurity
CPU Version: AMD G-T48E Processor
12:50:04.310 PKG: extracting rom.pkg V1.1 ...
12:50:04.324 SMP: cpu #2 starts up
12:50:04.571 rom.pkg: 306 files extracted
12:50:04.841 VGA: offscreen video ram = 158 MB
12:50:04.841 VGA: stolen video ram = 128 MB
12:50:05.171 B: registered, type 0x7, size 512 MB, AES.
12:50:05.173 PKG: base.i386.pkg V6.0, size 20185088, files 340
12:50:05.174 PKG: pcoip.i386.pkg V2.9, size 4591616, files 39
12:50:05.251 Initializing Certification Center ...
12:50:05.388 Screen1: [0xac10, 0x0] Dell Wyse AIO Week(8) Year(2014) S/N: 000000000000
12:50:05.698 Ethernet device version: RTL8168E-VL/8111E-VL.
12:50:05.713 Checking 2 Packages ...
12:50:05.750 AUDIO: Change record device to HD Audio
12:50:05.750 AUDIO: Change playback device to HD Audio
12:50:05.756 WLAN: iwlmvm driver probe failed.
12:50:06.663 USB: USB 2.0 Webcam Device connected
12:50:06.663 VUSB: Local Device(0x064e,0x920c,0xef,0x02,0x01)
12:50:06.672 USB: Found a new 480Mbps device "uvcvideo" on port 11
12:50:06.722 Waiting for network link ...
12:50:07.408 ENET0: Looking up IP address from DHCP ...
12:50:07.856 USB: Lenovo Traditional USB Keyboard connected
12:50:07.856 VUSB: Local Device(0x17ef,0x6099,0x03,0x01,0x01)
12:50:07.884 USB: Found a new 1.5Mbps device "usbhid" on port 12
12:50:07.912 USB: Found a new 1.5Mbps device "usbhid" on port 12
12:50:08.602 USB: Lenovo USB Optical Mouse connected
12:50:08.602 VUSB: Local Device(0x17ef,0x608d,0x03,0x01,0x02)
12:50:08.627 USB: Found a new 1.5Mbps device "usbhid" on port 7
12:50:12.807 Obtain IP[192.168.254.51] from DHCP server[192.168.254.12]
12:50:12.807 DHCP lease time: 8 day 00:00:00
12:50:12.822 ENET0: set default gateway 192.168.254.248
12:50:12.822 Set Name Servers: DNS DOMAIN=[pnsl.local]
12:50:12.822 Set Name Servers: DNS=[192.168.254.12]
12:50:12.827 Checking 2 Packages ...
12:50:12.829 Contacting WMS Server ...
12:50:13.001 WMS agent is retrieving full configurations.
12:50:19.175 WMS agent failed to open HTTP server:
https://WSMServer:443, errno:110
12:50:19.175 WMS agent execute http request error(cannot connect)!
12:50:19.175 WMS agent failed to update App (can't download or invalid file).
12:50:25.238 WMS agent failed to open HTTP server:
https://WSMServer:443, errno:110
12:50:25.238 WMS agent execute http request error(cannot connect)!
12:50:25.238 WMS agent failed to update App (can't download or invalid file).
12:50:25.314 WMS agent received configurations
12:50:31.378 WMS agent failed to switch to MQTT:WSMServer:1883
12:50:43.588 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
12:50:43.785 WMS agent failed to switch to https://WSMServer:443
12:50:44.838 WMS agent failed to connect to MQTT server(MQTT unreachable).
12:50:44.838 WMS agent checked in ...
12:50:46.002 Received Full configuration from WMS.
12:50:46.003 Contacting File Server ...
12:50:46.039 Contacting reserved file server wyseftpfbc4tc ...
12:50:51.558 Cannot access system profile
12:50:51.558 Skipping firmware check on ftp since already received upgrade/downgrade request from WMS.
12:50:51.565 Contacting SNTP [pool.ntp.org] ...
20:50:49.211 WMS agent failed to switch to MQTT:WSMServer:1883
20:51:01.214 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
20:51:01.305 WMS agent failed to switch to https://WSMServer:443
04:51:05.048 WMS agent failed to switch to MQTT:WSMServer:1883
04:51:17.419 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
04:51:17.481 WMS agent failed to switch to https://WSMServer:443
12:51:20.859 WMS agent failed to switch to MQTT:WSMServer:1883
12:51:32.944 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
12:51:33.004 WMS agent failed to switch to https://WSMServer:443
20:51:37.581 WMS agent failed to switch to MQTT:WSMServer:1883
20:51:49.241 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
20:51:49.323 WMS agent failed to switch to https://WSMServer:443
04:52:10.982 WMS agent failed to switch to MQTT:WSMServer:1883
04:52:22.638 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
04:52:22.699 WMS agent failed to switch to https://WSMServer:443
12:52:27.039 WMS agent failed to switch to MQTT:WSMServer:1883
12:52:39.487 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
12:52:39.557 WMS agent failed to switch to https://WSMServer:443
20:52:42.807 WMS agent failed to switch to MQTT:WSMServer:1883
20:52:55.232 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
20:52:55.294 WMS agent failed to switch to https://WSMServer:443
04:52:59.708 WMS agent failed to switch to MQTT:WSMServer:1883
04:53:11.739 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
04:53:11.807 WMS agent failed to switch to https://WSMServer:443
12:53:15.219 WMS agent failed to switch to MQTT:WSMServer:1883
12:53:26.848 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
12:53:26.932 WMS agent failed to switch to https://WSMServer:443
20:53:31.104 WMS agent failed to switch to MQTT:WSMServer:1883
20:53:43.107 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
20:53:43.170 WMS agent failed to switch to https://WSMServer:443
04:53:46.400 WMS agent failed to switch to MQTT:WSMServer:1883
04:53:58.047 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
04:53:58.103 WMS agent failed to switch to https://WSMServer:443
12:54:02.258 WMS agent failed to switch to MQTT:WSMServer:1883
12:54:14.427 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
12:54:14.567 WMS agent failed to switch to https://WSMServer:443
20:54:20.419 WMS agent failed to switch to MQTT:WSMServer:1883
20:54:32.243 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
20:54:32.302 WMS agent failed to switch to https://WSMServer:443
04:54:35.393 WMS agent failed to switch to MQTT:WSMServer:1883
04:54:47.397 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
04:54:47.459 WMS agent failed to switch to https://WSMServer:443
12:54:51.760 WMS agent failed to switch to MQTT:WSMServer:1883
12:55:03.989 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
12:55:04.073 WMS agent failed to switch to https://WSMServer:443
20:55:07.381 WMS agent failed to switch to MQTT:WSMServer:1883
20:55:19.193 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
20:55:19.252 WMS agent failed to switch to https://WSMServer:443
04:55:23.885 WMS agent failed to switch to MQTT:WSMServer:1883
04:55:35.915 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
04:55:35.977 WMS agent failed to switch to https://WSMServer:443
12:55:39.297 WMS agent failed to switch to MQTT:WSMServer:1883
12:55:51.126 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
12:55:51.191 WMS agent failed to switch to https://WSMServer:443
20:55:55.421 WMS agent failed to switch to MQTT:WSMServer:1883
20:56:07.424 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
20:56:07.483 WMS agent failed to switch to https://WSMServer:443
04:56:11.589 WMS agent failed to switch to MQTT:WSMServer:1883
04:56:23.604 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
04:56:23.664 WMS agent failed to switch to https://WSMServer:443
12:56:27.250 WMS agent failed to switch to MQTT:WSMServer:1883
12:56:39.277 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
12:56:39.337 WMS agent failed to switch to https://WSMServer:443
20:56:43.636 WMS agent failed to switch to MQTT:WSMServer:1883
20:56:55.640 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
20:56:55.702 WMS agent failed to switch to https://WSMServer:443
04:56:58.960 WMS agent failed to switch to MQTT:WSMServer:1883
04:57:10.964 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
04:57:11.023 WMS agent failed to switch to https://WSMServer:443
12:57:15.548 WMS agent failed to switch to MQTT:WSMServer:1883
12:57:27.593 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
12:57:27.656 WMS agent failed to switch to https://WSMServer:443
20:57:31.058 WMS agent failed to switch to MQTT:WSMServer:1883
20:57:43.617 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
20:57:43.676 WMS agent failed to switch to https://WSMServer:443
04:57:46.958 WMS agent failed to switch to MQTT:WSMServer:1883
04:57:58.722 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
04:57:58.783 WMS agent failed to switch to https://WSMServer:443
12:58:02.868 WMS agent failed to switch to MQTT:WSMServer:1883
12:58:14.078 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
12:58:14.137 WMS agent failed to switch to https://WSMServer:443
20:58:17.399 WMS agent failed to switch to MQTT:WSMServer:1883
20:58:29.404 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
20:58:29.464 WMS agent failed to switch to https://WSMServer:443
04:58:33.603 WMS agent failed to switch to MQTT:WSMServer:1883
04:58:45.419 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
04:58:45.479 WMS agent failed to switch to https://WSMServer:443
10:58:44.087 WMS agent: Query is received.
10:58:50.250 WMS agent failed to switch to MQTT:WSMServer:1883
10:59:02.025 WMS agent failed to open HTTP server:
https://WSMServer:443/ccm-web, errno:110
10:59:02.167 WMS agent failed to switch to https://WSMServer:443

I know there are a lot of very simple errors displayed but it is fixing them that I struggle with.

Regards,

Anthony

3 Apprentice

 • 

724 Posts

September 3rd, 2019 03:00

Anthony,

Looking at your log it looks as though your device is not able to communicate with your WMS server, which would explain why it isnt able to get the policy for the packages. 

  • According to the log it is trying to talk to WSMserver in domain pnsl.local
    • Confirm that is the proper name, and domain name of the WMS Server
    • On the thin client go to diagnostics and confirm you can ping the server at both wsmserver and wsmserver.pnsl.local
    • Confirm that "CA Validation" is not checked on
      • the System Settings, Central Configuration, WDA, WMS/CCM tab

VNC is enabled in the "Security" section of a WMS, ThinOS policy.

 

15 Posts

September 3rd, 2019 05:00

I have done some checking and I have added a manual DNS server pointing to our domain DNS server. I can ping the IP address of the server but not by name, interestingly the setting in the WDA tab is using the IP address, so it must be resolving the name from somewhere? Enable CA Validation is not checked. Thanks for the help with VNC, this is now working. I have just tried uploading a hosts file to get it to see the server and I can now ping the server. So far I seem to have the same issue, I have tried to request the log file but it is not showing up as yet.

15 Posts

September 5th, 2019 06:00

I am still unable to get the packages onto the device, so I can only think that the packages I have tried are the wrong ones. The firmware I am using is PD10_wnos-8.6_024 so what packages can I actually install onto the device? All the ones I have tried subsequently have failed to upload.
No Events found!

Top