Problems configuring Firmware upgrade over Http(s) instead of FTP

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #43168
    Miorky
    Participant
    • Total Post: 10
    • Regular Joe
    • ★★

    To upgrade the firmware of our thinclients (T10 R10 D10) we now use FTP. The clients will pickup the WNOS.ini from the FTP location and the upgrade will start.
    No we want to stop with the FTP protocol and switch to http (s). We are therefore working on upgrading of 4.9 to 5.7 (workgroup). Only we can’t get this working with Http(s). The WNOS.ini isn’t can’t be found.
    I have a site created in IIS and this referred to the WNOS FTP directory as indicated in the manual. This location is accessible.

    Upgrade the firmware with FTP with the new version is without any problems. The clients are also checking into Wyse device manager.
    With the use of Http(s) we have set the DHCP attributes as follows:

    186 Wyse WDM (IP adres server)
    190 WDM Server Secure port 443
    192 WDM Server Port 80
    194 WDM FQDN Name FQDN name

    Only the WNOS.ini will not be found

    The software Repository is set to port 80. Secure HTTPS is disabled. At test of the connection I get the message that the http connection test fails:
    [Error: Not Available] [WebDAV error: Failed to upload buffer. HTTP Response Code: 403Remote File Path: {BD6AF38E-7057-4599-AFBF-2B82E448D2B2} .tmp Error Code: 403]
    Is this a WEBDAV configuration error? If so can anyone tell me how to configure WEBDAV the right way, I can’t find anyhing in the installation manual.

    Do you guys have any idea how I can fix this so that I can upgrade the clients over http (s)

    #43174
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    Have you installed the WebDAV yourself or was it installed by WDM setup?

    CG

    #43176
    Miorky
    Participant
    • Total Post: 10
    • Regular Joe
    • ★★

    Webdav is installed by WDM Setup.

    #43177
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    How did you upgrade to WDM 5.7?
    There are several upgrades needed to go the whole way from 4.9.
    Why don’t you simply reistall WDM 5.7 on a new machine with same name and IP?

    CG

    #43178
    Miorky
    Participant
    • Total Post: 10
    • Regular Joe
    • ★★

    Hi CG

    I installed 5.7 on a new Windows 2012 server. So no upgrade. The old server is offline now. And all the DHCP entry’s are pointing to the new WDM server

    When I do a complete new install after I remove WDM 5.7, SQL and IIS. I still get this error.

    #43185
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    Could it be any Group Policies affecting the install?

    CG

    #43191
    Miorky
    Participant
    • Total Post: 10
    • Regular Joe
    • ★★

    Hi CG,

    No this is not a policy issue. To be sure I created a new OU with a policy block. After a new install on that server (win2012), the same error.

    After that I tried the install on a other server (win2008). Almost the same error. Failed to upload buffer
    [Error:Not Available] [WebDAV error:Failed to upload buffer. HTTP Response Code: 500Remote File Path: {8E811E5A-609E-497E-B357-C642D659CAE9}.tmp Error Code: 500]

    #43201
    Miorky
    Participant
    • Total Post: 10
    • Regular Joe
    • ★★

    Hi CG,

    I am a step further. I installed a complete new Windows 2012 server with a WDM 5.7 and now I get no error anymore at the repositorie.
    The thinclients are signing in to WDM. The onlu problem is now, that the cann’t find the .INI file.

    The structure is as follows C:\inetpub\ftproot\2016-01\wyse\wnos\
    MyWDM refers to the ftproot directory.

    Is this correct for use with HTTPS?

    #43203
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    As long as your clients are now looking in the folder /2016-01/wyse/ everything looks fine.
    Check locally at the client under System Setup – Central Configuration – Fileserver

    CG

    #43208
    Miorky
    Participant
    • Total Post: 10
    • Regular Joe
    • ★★

    Hi CG,

    Thanks for your quick reaction. I’ve checked the location locally and it is pointing to: https://ipadreswdm:443/MYWDM/rapport/WTOSCONFIG

    #43215
    ConfGen
    Keymaster
    • Total Post: 11485
    • Jedi Master
    • ★★★★★★★

    Then it is obvious that it could not work.
    Wrong directory.

    CG

Viewing 11 posts - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.