Unsolved
6 Posts
0
6952
Thin clients stop checking into the wdm server
I have a new 5.7.2 wdm server on Windows 2012 R2 and about 1000 thin clients which have all been freshly imaged. All 5010 models. They all successfully registered in wdm, but now after several days, about half of them have stopped checking in and are showing as offline in wdm. Spot checking shows that some simply cannot register after reboot and some are showing registered, but are still offline in wdm and some are legitimately offline. There are no apparent connectivity issues from the clients to the wdm server. wdm server health is all green.
I've googled it to death and can't find anything which might be causing this. Any ideas?
DELL-Scott H
3 Apprentice
3 Apprentice
•
740 Posts
0
September 29th, 2018 05:00
What operating system are the thin clients?
Are you able to issue and receive messages/reboot commands from WDM to the thin client when it shows as offline?
Have you looked through the troubleshooting guide?
https://docplayer.net/19771177-Wyse-device-manager-quick-reference-troubleshooting-guide.html
mjs66
6 Posts
0
October 4th, 2018 09:00
Windows 7 Embedded. The clients will not accept any commands or package updates.
I don't get a response when going to http://localhost/hserver.dll?&V99. But I don't see any messages when starting wdm about hserver not running.
Right now it's almost exactly half checking in, half not.
mjs66
6 Posts
0
October 4th, 2018 09:00
Actually https://localhost/hserver.dll?&V99 responds. "2018|10|4|11|48|16|-300|"
We have http disabled.
DELL-Scott H
3 Apprentice
3 Apprentice
•
740 Posts
0
October 4th, 2018 11:00
That would explain it. That service is responsible for communication with WDM, and would explain why some do and some do not report in. I would check the version of Hagent on the device and compare to the one that is on the version of WDM you are running and make sure they match. Standard behavior is to update Boot agent, and Hagent (now known as WDA) to the one that is packaged with the WDM version you are running, when you upgrade WDM.,
Setting the service to restart on failure is fine.
mjs66
6 Posts
0
October 4th, 2018 11:00
I'm pretty sure I found out what's causing it. The hagent service is stopped on the clients which aren't checking in. Starting it brings them on line again.
Now to figure out why thats randomly happening.
Would it be ok to set this service to auto start and auto recover?
mjs66
6 Posts
0
October 4th, 2018 12:00
The version that is available in the agent update section in WDM already matches whats on the thin clients.
Is it normal for this service to be set to manual? It was set like that in the fresh image from dell.
DELL-Scott H
3 Apprentice
3 Apprentice
•
740 Posts
0
October 4th, 2018 12:00
WDM install disabled HTTP automatically at a certain build level (Which caused other issues with people who had their discovery DNS/DHCPOT using HTTP. You just had to enable it in IIS bindings to get back in business, but it should be HTTPS anyway.