Unsolved
1 Rookie
•
8 Posts
0
31
November 3rd, 2025 13:33
WMS 5.3 205 Issues after upgrading private cloud
Hi.
I'm having some issues after upgrading from 5.2 to 5.3.
If i reasign a client (Optiplex 3000 ThinOS 2505) to a different group, and move it back to the original group. It won't take the settings.
Client is connected to WMS, and i can reboot it via WMS.
If i send unregister command, the client receive it, and unregister.
Trying to reset the client to factory settings. It is discovered after reboot, and when i assign it to the correct group, the client prompts to reboot, as normal.
After reboot it "Tries to get full configuration" but nothing happens.
WMS status is connected
MQTT server is idle
Any ideas? Known issues?
No Events found!
DELL-Scott H
Moderator
•
914 Posts
0
November 5th, 2025 11:17
Thinos 9 2505 or ThinOS 10 2505?
If you look in Central configuration on the thin client does it have the proper WMS Server and group token?
If you manually trigger a check in does it work?
Can you share snippets at the log when it fails?
SkrettingMannen
1 Rookie
•
8 Posts
0
November 5th, 2025 11:52
@DELL-Scott H We have rolled back the server, and will contact support before we try again. ThinOS10 2505. This is our second attempt.
The log just says "Tries to get full configuration"
DELL-Scott H
Moderator
•
914 Posts
1
November 5th, 2025 13:11
I would definitely encourage you to have T10 2508 available to test at the same time.
SkrettingMannen
1 Rookie
•
8 Posts
0
November 5th, 2025 13:15
@DELL-Scott H Do you recommend upgrading the thin clients before upgrading WMS?
DELL-Scott H
Moderator
•
914 Posts
1
November 5th, 2025 13:23
In general staying on current builds helps stay on top of enhancements, bugs and security issues. While I am not aware of any specific issues with 2505 and WMS 5.3, if it is something you will need support and engineering feedback on they will want to know how current code (2508) behaves. I would suggest updating a few devices prior to the WMS update run it through your QA processes and see how it behaves compared to 2505 after the 5.3 update and be prepared to open a case and provide logs if needed to engineering.