Unsolved
This post is more than 5 years old
4 Posts
0
69081
Changed IP address of WDM, now hagent.exe crashes on WES thinclients
Changed IP address of WDM, now hagent.exe crashes on WES thinclients
Hi -
I have WES thinclients on new Z90DW hardware, and they all have started exhibiting a problem where HAGENT.EXE crashes. This happens about 1-5 minutes after starting the thinclient. If I go in and restart the service, it crashes again after a few minutes. I think this corresponds to its attempt to check in and communicate with the WDM.
Why I'm posting this in the WDM board is because I think the issue started when I changed the IP address on my WDM server. When I changed the IP address I went in to the WDM and adjusted the "Software Repository" section of the Configuration Manager to reflect the new IP. I also modified my scope options on the DHCP server to point the thinclients to the new address.
Interestingly I have a few ThinOS Wyse systems and they don't seem to be affected at all. They all check in with my WDM. All the WES devices though, do not (because their HAGENT crashes).
There's no indication on the WES clients why HAGENT is crashing - no entries in the event log that point to a possible cause.
Does anyone have any ideas short of reinstalling the WDM software ore going back to the old IP?
--Aaron
jpropsner
67 Posts
0
June 15th, 2015 08:00
I am not sure that the Hagent crash is related to changing the IP of the WDM server, but there are a few steps you need to follow on the WDM server to get the IP changed. You addressed the software repository, but the database still has the old IP.
Check out "Solution 13321: Wyse Device Manager - How to Change the Server Name and IP Address". Use the tool to change the information in the database.
technothrakon
4 Posts
0
July 13th, 2015 07:00
Thank you for the KB article. You're right... that's not it - at least not exactly. Everything checks out now with RPTDIAG and I'm still having HAGENT crashes. Interesting development - if I boot a new Z90 up that I hadn't had on my server before the IP switch, it's fine. If I image it with images I made before the IP switch, it starts exhibiting the problem. Perhaps the thinclients are caching that old IP information somewhere even though I'm pushing the correct WDM IP using DHCP scope options?
technothrakon
4 Posts
0
July 13th, 2015 08:00
OK I found the setting on the WES clients where the WDM server address is and so far, the issue appears to be resolved in testing. DUH, I feel stupid now when there's an obvious WDM icon in the control panel!
I guess I would have assumed that the DHCP scope option would push that change, but I'm supposing that only works when the write-filter is turned off.
jpropsner
67 Posts
0
July 13th, 2015 08:00
The 186 tag should overwrite the WDM address in the control panel applet. You do need the 186 and 192 for this to work right. The 186 tag is for the address the 192 tag is to specify the port.
Solution 17015: DHCP - How to Set Up Option Tags to Discover Thin Clients Using WDM
What should happen when the unit pulls the 186 and 192 tags, the unit will checkin to the new WDM server address. The server will instruct the unit to turn off the WF, reboot, add the address to the registry, and then reboot again to turn the WF back on. This will all be automatic if the tags are correct.