Can I update S10 firmare using USB?

  • This topic is empty.
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #6901
    CtnTech654
    Member
    • Total Post: 5
    • Newbie

    I tried using Wyse’s USB firmware tool to pull the firmware image from an updated unit to a USB drive. It acts like it is going to work, but then I get an error saying “Error encountered during pull operation, copy image to USB failed”. I noticed in the documentation that the S10 model is not listed among the supported devices, so maybe that’s why it won’t work?

    Regardless, I don’t necessarily have to copy the firmware from an existing unit. I do have the firmware files from Wyse, but I don’t know how to incorporate them into the update procedure on the USB drive.

    Anyone have suggestions?

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

    Which files did you get from Wyse? You will need Merlin images and not the normal FTP files.

    CG

    #21245
    CtnTech654
    Member
    • Total Post: 5
    • Newbie

    I received RCA_boot and RCA_wnos from Wyse. I am not familiar with Merlin images (well, to be honest I’m not extremely familiar with any of this, but I’m learning as I go).

    I would still prefer to do the updates via USB if possible, but I also tried setting it up on a local ftp server per Wyse’s instructions (I included the two files listed above as well as a basic wnos.ini file. My wnos.ini file included Autoload=2, and Signon=0, but those are my only two lines. It seems even when I changed the File/Servers path on my thin clients to point to my local ftp server, my thin clients are still logging on to our company’s corporate server (which is in another location a few states away).

    Please forgive my ignorance in all of this. I do appreciate any advice.

    #21246
    Wyse_Egor
    Member
    • Total Post: 14
    • Regular Joe
    • ★★

    @CtnTech654 wrote:

    It seems even when I changed the File/Servers path on my thin clients to point to my local ftp server, my thin clients are still logging on to our company’s corporate server (which is in another location a few states away).

    Do you have DHCP option 161 specified on your network?

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

    What exact path are you entering and where exactly do you have your firmware/wnos.ini files stored?

    CG

    #21257
    CtnTech654
    Member
    • Total Post: 5
    • Newbie

    I do have 161 specified as the File Server option under DHCP settings.

    As for the firmware & wnos.ini files, they are on my ftp server under c:inetpubftprootwysewnos. On my thin client, I am specifying the FileServer/Path as 10.x.x.x/wyse (with the IP address of my local ftp server in place of the x)

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

    But if you are using OT 161, you should not be able to alter the Fileserver address locally at all. Something is wrong in your environment.

    Can you ftp your Fileserver from a PC?

    CG

    #21264
    CtnTech654
    Member
    • Total Post: 5
    • Newbie

    @ConfGen wrote:

    But if you are using OT 161, you should not be able to alter the Fileserver address locally at all. Something is wrong in your environment.

    Can you ftp your Fileserver from a PC?

    CG

    Yes, I can open the ftp folder and view the files from my local desktop.

    I don’t really understand OT 161. That is just the variable that was already in the field but I didn’t change it. Concerning altering the fileserver address, I have to disconnect from the network and restart the thin client to make the change (otherwise it is grayed out and shows the IP/servername from our corporate office). But after disconnecting and then typing in my local ftp address, I then shut down, plug the ethernet cable back in and then reboot.

    These complications are why I really preferred to do the firmware update via USB if possible. And I’ve got approximately 25 s10 units that I would like to update.

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

    OT 161 is sending out the fileserver IP or Name to the client. If you are connected to your LAN, you will get this info and cannot change it locally on the client.
    If you are disconnected from the LAN you do not get OT 161 and can change it temporarily.
    So, if you want to upgrade your units, just put the new firmware files on your corporate fileserver and reboot the 25 units. It will take maybe 1 minute and all clients are updated.

    CG

    #21304
    CtnTech654
    Member
    • Total Post: 5
    • Newbie

    Thanks again for all of the tips. The only issue with putting the firmware files on the corporate server is that I don’t have write access to that one. I am the tech at my local branch, but not an admin for the entire company. Yes, I could try to work with the corporate techs on this, but I was hoping to do the firmware updates without getting them involved. Not that it’s a bad working relationship, but sometimes us field techs feel like the stepchildren of the I.T. department. Thus another reason I was hoping to do this via USB and not FTP.

    I’ll keep trying some things, but if I can’t get it, I may break down and call our corp guys. I just don’t know if they would want to bother, or if they would have the time to work with me on this.

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