- This topic has 41 replies, 5 voices, and was last updated 4 years ago by
.
-
Posts
-
I hope this is fixed in the coming MR1 release scheduled 7/7.
CG
I’ve been working with Dell Engineering on this for some time. It would seem to me they have to update the version used to go from 8.6 to 9.x. If MR1 is an upgrade from the ThinOS 9.x configuration/policy settings in WMS under firmware I don’t think it will help, this needs to be the firmware from 8.6-9.x that you upgrade from in the regular Thin OS policy not the ThinOS 9.x policy
Fingers crossed.
My tests shows that the problems are still not solved.
1.: A new client cant get DHCP tags from DHCP server, so cant checkin on WMS.
2.: Client name with $MAC adresse has : in the name, which is not allowed on a DHCP server, so no name on the client in the DHCP scope.
@MHP:
1. not true. This works fine for me. How does your DHCP option tags look like?
2. correct. Please open a ticket with Dell supportCG
We have a v8.6 setup here tags are working just fine, here i have a port numer 449 in the tag, thats not possible in v9, then i have made a new WMS server where i use the default port 443, so i removed the port number in tags, but still it cant connect. Can you copy your tags in here so i can do then likewise or? – Ill make a support call on the other issue.
Make sure the WMS server option Tag includes either a leading https:// or a ending :443
CG
I think there are two separate issues that throughout the course of this thread have emerged.
- WTOS 9 WMS Agent Failed To Check-In – Proxy Enabled By Default -SR#1025297396 (if anyone wants to report and reference existing SR)
- WTOS 9 WMS Agent Failed To Check-In – DHCP option tags not working
- Is DHCP Option tagging not working because of the proxy?
I think its good we’ve worked to identify the issues, the DHCP option tagging issue might be better served in a separate thread labeled as such. Not a thread hijacking complaint just trying to better serve this community which i appreciate and to help others easily find what they’re looking for.
The issue with the Proxy enabled by default is still not fixed in WTOS 9.0.2081 under certain conditions.
Test 1 – Upgrade from 8.6_x – WTOS 9.0.1136
- After upgrade proxy is enabled by default, WMS cannot check-in and pull policy
- No proxy policy is ever set in WMS for 8.6 or for 9, this is never an issue in 8.6
- Even with proxy policy set to OFF in WMS for WTOS9 the upgrade from 8.6-9 still enables the proxy
- Manually disabling the proxy using (locally on thin client) System Setup>>Admin Policy Tool under Network Configuration>>Proxy Settings>>Enable Proxy toggle to off and Save & Publish will correct the issue
Test 2 – Upgrade from WTOS 9.0.1136 to WTOS 9.0.2081
- Upgrading from WTOS 9.0.1136 to WTOS 9.0.2081 after performing the above manual steps, the proxy remains off and the upgrade takes place without issue.
Test 3 – Factory Reset of WTOS 9.0.2081
- Performing a factory reset of WTOS 9.0.2081 the OOB setup has Proxy enabled
- Manually disabling the proxy using (locally on thin client) System Setup>>Admin Policy Tool under Network Configuration>>Proxy Settings>>Enable Proxy toggle to off and Save & Publish will correct the issue
These scenarios hold true for 3040, 5070, and 5470 mobile.
What Dell really needs to do is pull the upgrade package from 8.6-9, correct the proxy issues and re-issue the package. With the proxy enabled by default it makes updating a device remotely impossible without having to physically touch the device or walk someone through disabling the proxy locally on the device, this is not a scalable solution for organizations that rely on pushing updates remotely.
I can no longer find the 8.6_x to WTOS 9 A10Q or X10 packages on Dell’s download site.
I do see these two below, but no longer the upgrade, perhaps they pulled it for hotfixes which would be good news.
- ThinOS 9.0.1136 Base Image file for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients
- ThinOS 9.0.2081 Image file based on 9.0.1136 for Dell Wyse 3040, 5070, 5470 and 5470 All-in-One Thin Clients
Click on the 2081 details and select “Older Versions”. There you find the conversion image.
Really bad.CG
The proxy issue is finally resolved in 9.0.3030 when doing the OOB experience and the device is already installed with WTOS 9.0.3030.
I still need to check going from 8.6_206 (or newer) directly to WTOS 9.
Ok here is my clarified testing:
- Taking a working device with the proxy disabled from WTOS 9.0.2108 to WTOS 9.0.3030 – Working fine
- Factory resetting a device with WTOS 9.0.3030 installed and walking through the OOB setup – Working fine
- Taking a device on WTOS 8.6_206 to WTOS 9.0.1136 which is using A10Q_wnos-9.0_11.36 – Proxy is enabled and cannot continue on to upgrade to WTOS 9.0.3030.
The primary issue is getting the device from 8.6_x to WTOS9. My engineer confirmed that they wanted to make sure 9.0.3030 resolved the OOB experience and they will create a new upgrade package for example A10Q_wnos-9.0_30.30
- You must be logged in to reply to this topic.