Wyse Xenith Firmware Upgrade Gives Invalid File Format Error

Wyse Xenith Firmware Upgrade Gives Invalid File Format Error

Viewing 15 posts – one through fifteen (of xv full)

  • Author

    Posts


  • #7645

    Hello once more,

    My company is currently using about 10 Wyse Xenith Pro units that are running firmware version one.7.130. I have been using the USB Firmware Tool to update individual terminals to exam the 2.0.015 firmware nonetheless nosotros ran into some issues with that version and had to roll back for the fourth dimension being.

    I come across what Wyse has released version 2.0.017 and I would like to test this to run across whether or non information technology volition resolve our issues still I am not sure near the all-time way to go about updating our clients for testing.

    With version 2.0.015 I was able to easily flash a USB drive with the bios.img, cmos.img, par1.img, and commandsXml.xml files that were downloaded from Wyse to create an image to manually button to the terminals. This time I merely have access to the C00_xen and R00_xen files for the new version. Unless I am mistaken, the USB tool us unable to create an image with just these files.

    I see that the proper method of widely updating these is through FTP/HTTP from the Xen file server however I want to limit this deployment to a single device for testing until it is adopted globally. Is in that location a way to do that using this method of upgrading or practice I need to button information technology manually using WDM?

    I am looking at the Scruptbuilder create a .rsp script to push button the update to a single client through WDM however I am not familiar with the script language and the documentation seems pretty slim at best. Which command would I use to update the device with the new firmware? I’m assuming information technology would exist Send File (SF) to copy information technology, however I am a flake confused about whether or not this command is used with the Xenith OS. Can someone provide a sample script that would be used to update a Xenith Pro in this way?

    Is there another method I’g overlooking to update a single device for testing?

    Thanks very much for whatever advice.

    -Joe


    #23224

    UPDATE:

    The USB Firmware Tool does back up .rsp scripts, I overlooked that ability previously. Knowing this now, and having read up a bit on creating .rsp scripts, I should be able to utilize this to push the R00_xen to the final via usb for testing however I’m nonetheless a bit hung up on creating the script itself.

    So now I demand to make sure that the script correctly pushes and installs the update. Will SF (Send File) just copy the R00_xen file or volition that also run it as well?

    I figured out the value for the source of the files I’m going to push but I don’t know what value I should be entering for the Device Filename value. Practise I need to specify a path or can that just be the file name?

    Practice I need to add together whatsoever other commands to update the image or will this do it?

    As a test I but tried to create a .rsp script with only a SF and RB command to push the R00_xen file to my terminal and reboot it. Afterwards saving the script I tried to use the USB Firmware Tool to flash a USB bulldoze with this update still it failed with the error “Invalid file type. Delight select a valid rsp or i2d file.”

    The script was created using the Wyse Scriptbuilder application and was saved with the following file structure:

    ii.0.017.rsp
    2.0.017R00_xen

    Hither is the content of the script itself:

    [Version] Number=two.0.017
    Description=Updates Wyse Xenith Pro to firmware version 2.0.017.
    OS=XEN
    Category=Amanuensis Update
    USE_REMOTE=Yes
    ; Date: 12/28/2012

    [Script] SF “R00_xen” “R00_xen”
    RB

    I feel like I’m missing something important hither. Any thoughts what that might be?

    Many cheers again equally always for any assistance!

    -Joe


    #23225





    ConfGen

    Keymaster

    • Full Post: 10692
    • Jedi Master

    • ★★★★★★★

    Don’t try any further. This will not piece of work.
    I estimate you are using ftp to configure and update all clients centrally.
    Why non using the same way to update merely one client?
    Create a folder /inc inside the wnos binder. Identify a mac.ini file in in that location, eg. 008064123456.ini and put Autoload=2 in information technology.
    Then put
    Include=$mac.ini in the xen.ini or wnos.ini, depending on what you are using. But brand sure you put that parameter AFTER the autoload=0 (has to be in in that location) parameter that is already in your xen.ini .
    Also make sure that the name of the mac.ini file corresponds to the correct mac accost of the ane client you want to upgrade.
    At present save the examination firmware in the default wnos folder and reboot your test car.
    Done.

    CG


    #23229

    ConfGen’southward method is probably easiest, just you could separate the client on the network level.

    The fashion I do all my testing is to take different VLANs which allows me to take unlike DHCP servers, and hence I have a testing environment ‘LAN’ and a production environment ‘LAN’. However, if your router+switches aren’t VLAN/Multi DHCP server capable, this option won’t piece of work for you.


    #23273



    @ConfGen

    wrote:

    Don’t attempt any further. This volition not work.
    I guess you lot are using ftp to configure and update all clients centrally.
    Why not using the same fashion to update only one client?
    Create a folder /inc inside the wnos folder. Identify a mac.ini file in there, eg. 008064123456.ini and put Autoload=2 in it.
    Then put
    Include=$mac.ini in the xen.ini or wnos.ini, depending on what you are using. Simply make sure you lot put that parameter Later the autoload=0 (has to be in there) parameter that is already in your xen.ini .
    Besides make sure that the proper noun of the mac.ini file corresponds to the correct mac address of the ane customer you desire to upgrade.
    Now save the exam firmware in the default wnos binder and reboot your test machine.
    Washed.

    CG

    im trying to do this method but no update is happening, heres a look at my xen.ini. i put the firmware in the root of wnos folder, and the mac.ini file in a folder called “inc” which resides on the root of the wnos folder.

    Autoload=0 Include=008064A81C8C.ini
    BootpDisable=yeah
    AdminMode=yes username=XXXXXX password=XXXXXX
    Privilege=None Lockdown=yes
    EnableGKey=yeah
    formurl=header_main_transp.bmp

    ;*************************************************************
    ;* General 2 *
    ;*************************************************************

    Locale=English language

    ;*************************************************************
    ;* Time *
    ;*************************************************************

    Timeserver=XXXXXXXXXXXXXXX Timeformat=”12-hr format” Dateformat=mm/dd/yyyy
    TimeZone=’GMT – 08:00′ ManualOverride=yes Daylight=yep Start=030507 End=100507 TimeZoneName=”Pacific Standard Time” DayLightName=”Pacific Daylight Time”

    ;*************************************************************
    ;* Network *
    ;*************************************************************

    SignOn=Yes
    ;Signon=NTLM DisableGuest=yes
    MaxVNCD=1
    VncPassword=”JHGCKIHKOGHFOB” Encrypt=yeah
    VncPrompt=Yes Have=10

    ;*************************************************************
    ;* General Session *
    ;*************************************************************

    SessionConfig=ALL MapDisks=yep DisableSound=No unmapprinters=yes

    ;*************************************************************
    ;* ICA *
    ;*************************************************************

    Seamless=yes FullScreenReserved=Yes
    PnliteServer=http://XXXXXXXXXXXXXXXXXXXXconnectAtLogon=2 ReconnectFromButton=two AutoConnectList=”Desktop”
    SessionConfig=ICA DesktopMode=Fullscreen SessionReliability=aye


    #23275

    also which file exactly should i be renaming to C00_xen as the firmware file. is it the nothing file?


    #23280





    ConfGen

    Keymaster

    • Total Post: 10692
    • Jedi Master

    • ★★★★★★★

    No demand to rename it. Leave it as it is.
    But you misunderstood my previous postal service.
    The include parameter has to be in a separate line after Autoload=0.
    Autoload=0
    Include=008064A81C8C.ini

    CG


    #23291

    thanks i got it all to piece of work, however information technology still worked for me when i put include include=$mac.ini


    #23599

    Ok, so I am revisiting this many weeks later, sorry for the huge delay. My boss’s priorities shifted significantly so this had to go to the very low finish of the to practise list for a while…

    I used the method you described to successfully update the terminal using the mac.ini file however information technology appears that this update is being applied to all terminals, not just the one mac specified.

    Hither’s a sample of my xen.ini:

    Autoload=0
    Include=008064A2D718.ini
    BootpDisable=yes
    Fileserver=*****.*****.***
    AdminMode=yep Admin-Username=******* Admin-Password=*******
    Privilege=None
    PasswordServer=

    I created the file …inc08064A2D718.ini which contains a unmarried line:
    Autoload=2

    Despite specifying the mac accost of that 1 unit in both .ini files, every device on the network manifestly is applying the firmware update when they boot regardless of their mac.

    Luckily none of these unintended updates have caused any problems however I’d like to brand certain that nosotros can successfully specify individual units equally intended in the futurity.

    Whatever thoughts on what I’yard doing wrong are profoundly appreciated.

    Thanks!


    #23610





    ConfGen

    Keymaster

    • Total Postal service: 10692
    • Jedi Master

    • ★★★★★★★

    Looks good to me.
    Tin can you lot start past adding some other stuff to your mac.ini file like a different groundwork image or privilege level and retest?

    CG


    #23644

    Ok, I added some random lines to the mac.ini such equally a “desktop=background.jpg” and “disabledomain=no” and confirmed that those options are also being applied to all of the terminals, not just the i specified in the mac.ini

    Whatsoever further thoughts on what I’1000 missing here?

    Thank you!


    #23649





    ConfGen

    Keymaster

    • Total Post: 10692
    • Jedi Principal

    • ★★★★★★★

    Of course, all clients will get those.
    Change Include=008064A2D718.ini to Include=$mac.ini

    CG


    #44466





    Stevie

    Participant

    • Full Post: vii
    • Newbie

    Trying to setup something like so nosotros tin can test firmware and wnos.ini settings on a unmarried device but I but keep running into an issue loading the FR bundle, evidently Autoload=0 ways no package loading?

    Wnos.ini:

    Autoload=0

    Include=$mac.ini

    AddPkg=”FR”

    0123456789.ini
    Autoload=101
    AddPkg=”FR”
    ……
    Exit=All


    #44471





    ConfGen

    Keymaster

    • Total Post: 10692
    • Jedi Main

    • ★★★★★★★

    Aye, autoload=0 means no update.
    Put both parameters on the same line in your mac.ini:
    autoload=101 AddPkg=”FR”

    CG


    #44479





    Stevie

    Participant

    • Total Post: 7
    • Newbie

    Oooooh blimey, I experience silly now, been staring at it and didn’t see it.
    That’ll teach me to stay away from ENTER…thanks a bundle!

Viewing 15 posts – 1 through fifteen (of fifteen full)

  • Yous must be logged in to answer to this topic.

Wyse Xenith Firmware Upgrade Gives Invalid File Format Error

Read:  Yamaha Rx-a3000 Firmware Update but No Display

Check Also

How to Update Firmware on a Samsung Hd204ui

How to Update Firmware on a Samsung Hd204ui

How to Update Firmware on a Samsung Hd204ui #i What the heck…I just got a …