- This topic has 2 replies, 2 voices, and was last updated 6 years, 4 months ago by
.
-
Posts
-
Hello ConfGen,
I wasn’t sure if I should post here (on WDM forum), but my problem does involve WDM.
Background: I recently updated WDM from 4.9.1 to 5.7. Actually, I’ve created a new WDM server with 5.7 and started migrating thinclients updating firmware from 1.022 to 1.041.
My problem is that we need to accelerate things to disable old WDM 4.9.1. Simply pointing T50 to new WDM doesn’t work. WDM 5.7 can’t see T50 running 1.022 running Hagent 5.0.75-00.04.
Updating Hagent 5.0.75-00.04 to 5.0.300-00.00 works in part. WDM 5.7 sees the T50 but can’t send wlx.ini to them. No matter what, the thinclients won’t receive new wlx.ini files.
Any suggestions?
Thanks
WDM does not send a wlx.ini to a client.
How do you try to do that?
Or are you just using the webserver on the same server for that?
Is it ftp or http/https?
If http, have you set MIME types for .ini?
Have you imported any certificates for https?CG
Hi CG,
You are right, WDM doesn’t send wlx.ini to thinclients. Correct me if I’m wrong, IIS delivers these files upon request from thinclient.
About my server:
– WDM 5.7 (Workgroup)
– HTTPS / FTP.
– IIS has MIME configured ok (.ini files).
Before your post, I didn’t try importing certificates, since I didn’t have to do this in our other clients running firmware 1.041. I tried and nothing.
I did solve my problem. Not sure if you will agree with me, but it works (without importing certificate).
– Install from WDM new HAGENT
– Install import-certs_2.0.4-0.0_armel.deb
– Copy “/etc/addons.d/dispatcher.d/60.fetchIni” from a 1.041 to the box running 1.022. This file has two aditional lines about SSL checks.
And it works. Not the best solution, but it works. I haven’t made theses changes in production. Still testing.
Any comments?
- You must be logged in to reply to this topic.