WTOS 9 WMS AGENT FAILED TO CHECK-IN

Question

I’m trying to test a WTOS 9 config from home. I’ve set my test policy as my production 8.6_206 policy and then change the firmware to 9.0.1136. The upgrade took and in WMS 2.0 my WTOS9 policy is configured and WMS validation key the same as the WTOS 8.6_206 validation key. After the WTOS9 upgrade it only received a base configuration like its OOB.

Here is what the event log is showing:

WMS: failed to check-in: URI does not contain a protocol:

https://imgur.com/a/xYaLBEk

I then performed a factory reset and walked through manually entering my group registration token and I get the same message. Anyone seen this yet? I was in the WTOS9 beta and had no problem setting up a working policy.

BigBJ · Answer

I tried that

us1.wysemanagementsuite.com

https://us1.wysemanagementsuite.com

https://us1.wysemanagementsuite.com:443

None of them work

I'm going to try rolling back to 8.6 manually and try again using WMS public cloud, but it doesn't give me a warm fuzzy feeling to do this to almost 3000 devices in WMS if I'm 0 for 1 out of the gate.

DELL-Scott H · Answer

Change the WMS Server on the WTOS9 client from being fqdn to https://fqdn

In other words if your WMS server is listed on the thin client as

wms.company.com or wms.company.com:443

change it to

https://wms.company.com

Fisk3r · Answer

I have the same issue on all our 3040 but it work on all our 5070 laptops, have you found a soluiton to this problem ? Best regards Frederik

BigBJ · Answer

Nothing yet, haven't opened a case with Dell yet and I don't have access to any other devices while WFH, all i have are some 3040's to play with.

So you're getting the same on all your 3040 devices?

Are you also using WMS public cloud?

BigBJ · Answer

I have a case open with Dell.

I've done this upgrade process several times now, rolling back to 8.6_206 manually and then upgrading again, double checking my policy settings every step of the way.

When upgrading from 8.6_206 to 9.0.1136, by default, before you even get to have WMS check-in, WTOS 9.0.1136 is Enabling the proxy, and the proxy is un-configured. You have to use the local Admin Policy Tools and disable the proxy setting manually before the device is allowed to check-in to WMS public cloud.

I found this by reviewing the wlogd.log file when you export the system logs, look for the log in the system_log_date_xxxxxx.zip\compat\linux\home\tmp\wlogd

About a fourth of the way down i notice this entry:

[20200519 15:20:44.608] N/WebUIProc/WebUIModule (1/1) Proxy: proxy enabled.
[20200519 15:20:44.729] D/WebUIProc/WebUIModule (1/1) Try to add event listener for "electron_open" ...
[20200519 15:20:44.737] D/WebUIProc/WebUIModule (1/1) Added event listener for "electron_open"
[20200519 15:20:44.750] D/WebUIProc/WebUIModule (1/1) Try to add event listener for "sigout" ...
[20200519 15:20:44.762] D/WebUIProc/WebUIModule (1/1) Added event listener for "sigout"
[20200519 15:20:44.792] D/WebUIProc/WebUIModule (1/1) Try to add event listener for "notify" ...
[20200519 15:20:44.800] D/WebUIProc/WebUIModule (1/1) Added event listener for "notify"

Nowhere in my policy is my proxy enabled and I checked the ThinOS 9 policy in WMS under proxy and made sure it is disabled. This is a manual step that needs to be done at the device level that essentially makes upgrading through WMS Public Cloud broken.

Guy201901001 · Answer

Thanks - this was driving me crazy as it also wouldn't connect to Citrix either!

Technodrom · Answer

Please try upgrade from 8.6_303 (Main Release 5) to 9.0.1136. Is the issue resolved?

You can find it here:

https://www.dell.com/support/home/en-us/product-support/product/wyse-3040-thin-client/drivers

Moose09876 · Answer

I have replicated this issue twice with an end user. He is using a private VPN for his entire network - that's the only difference we can find. We've upgraded probably 15 in the field so far with no other issues.

thellix · Answer

after upgrade, reset the thinclient over WMS console, after that, the os is able to make bios upgrade and then connects to storefront.

Moose09876 · Answer

@thellix - This did not resolve my issue. The thin isn't able to contact the WMS server. I sent a reset, but it cannot communicate. The thin is still unable to contact WMS cloud. I'm engaging our sales engineer now since we've had another person with this specific issue.

Wyse ThinOS

WTOS 9 WMS AGENT FAILED TO CHECK-IN

Was this post helpful?