Update the very old Version 8.3_011

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • March 24, 2021 at 4:04 pm #101583
    MFriedlein
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    Hello everyone,
    I have discovered a few Wyse T10 units in my inventory with a firmware version 8.3_011.

    I distribute the firmware via FTP/Fileserver. However, the clients do not accept the DOVE_boot file. All other clients can update. A downgrade does not work either.

    The autoload is set correctly – is there an error here with the version – or how can I update the clients differently?

    March 24, 2021 at 4:57 pm #101612
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Any hints in the local eventlog or the FTP log?
    Maybe the clients are looking for a different file or you have some permission issues.

    CG

    March 25, 2021 at 9:26 am #102081
    MFriedlein
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    Changes i make in the mac.ini for this client are accepted.

    In the local Event Log there is not really any information:

    ….
    07:45:10 Kontaktiere Datei-Server …
    07:45:10 Rufe Systemprofil auf…
    07:45:10 locale/German.msg: Keine solche(s) Datei oder Verzeichnis
    07:45:10 Ungültiger SESSIONCONFIG Parameter: WyseVDA
    07:45:10 Ungültiger VERBINDUNGS-Parameter: WyseVDA=no
    07:45:11 Kontaktiere Datei-Server …
    07:45:11 Kann das Systemprofil nicht aufrufen
    07:45:11 Prüfe Software ftp:/wnos/DOVE_boot …
    07:45:11 Prüfe Paket von ftp:/wnos/DOVE_boot …
    07:45:12 Kontaktiere SNTP [de.pool.ntp.org] …
    07:45:12 RDP: Start session to xxx.xxx.xxx.xxx
    07:45:12 RDP: Connect to xxx.xxx.xxx.xxx …
    07:45:12 RDP: NLA CredSSP Authentication
    07:45:12 RDP: NLA CredSSP Authentication failed (1)
    07:45:12 ERROR: Connection Failed!

    ….

     

    March 25, 2021 at 5:12 pm #102306
    Midas
    Participant
    • Total Post: 17
    • Jedi Master
    • ★★★★★★★

    Hello,

    “Kann das Systemprofil nicht aufrufen”

    Looks, they cannot reach wnos.ini file.

    Please be sure wnos.ini file is placed under right “wnos” folder.

    Please try to reset a related device and let us know the result.

    March 26, 2021 at 11:41 am #102818
    MFriedlein
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    Thanks for the answer,

    when i change the settings in the WNOS.INI they arrive at the client (e.g. changes to the RDP session). So the WNOS.INI should be reached.

    Is there no other way to update the clients, for example via USB?

    March 26, 2021 at 11:54 am #102841
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Again, do you see anything in the ftp log?
    T10 is ARM based and therefore cannot be updated via USB.

    CG

    March 26, 2021 at 3:00 pm #102936
    MFriedlein
    Participant
    • Total Post: 15
    • Regular Joe
    • ★★

    For your information, we log on to the FTP as anonymous.

    what irritates me is that the updates works with the 3020 and 3040 and not with the T10.

    Here is an excerpt from the log

    March 30, 2021 at 12:49 pm #104899
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    The error code 550 indicates that the file is either not there or not accessible.
    Maybe a hidden extension?

    CG

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