R10 upgrade to 8.3_109 – Boot issue.

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

    Hello,

    we got several R10 wyses and want to manage them with wms on premise.
    As we can’t add them to wms with 8.0_210 someone at Dell give us the 8.3_109.

    I’ve tried an upgrade from 8.0_210 to 8.3_109 everything seems to be ok and I can manage the wyse from our wms server but as soon as I shutdown the wyse it’s no longer possible to boot it.
    I’m stuck with a black screen instead of loading the OS.
    The only way is to plug an USB key to downgrade the OS to 8.0_210

    I’ve found nothing about it, anyone got an Idea ?

    edit : I also tried with the 8.3_109 image found in the donwload area (in cas of the other file was corrupted) but same issue …

    thanks and regards,

    Nicolas.

    #48577
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★
    #48581
    niccar
    Participant
    • Total Post: 10
    • Regular Joe
    • ★★

    Hello and thanks for the quick answer.
    I’ve already check the good practises to upgrade thinos and I have tried upgrading from 8.0_210 to 8.0_512 then to 8.3_109 and I got the same issue …

    Nicolas.

    #48585
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Can you post the ThinOS eventlog after the upgrade to 8.3_109?

    CG

    #48679
    niccar
    Participant
    • Total Post: 10
    • Regular Joe
    • ★★

    Hello,

    here is the eventlog :

    14:06:45 System Start Date: 2019/01/09 Wednesday
    14:06:45 Version du systeme : HF 8.3_109 (ROM : 1.0H_SPC)
    14:06:45 Characteristics: FilesystemSecurity
    14:06:45 Version UC : AMD Sempron(tm)
    14:06:45 PKG: extracting rom.pkg V1.01 …
    14:06:45 rom.pkg: 236 files extracted
    14:06:45 VGA: offscreen video ram = 86 MB
    14:06:45 B: registered, type 0x7, size 256 MB.
    14:06:45 PKG: base.i386.pkg V1.24, size 10271260, files 250
    14:06:45 CERT: built-in certificate GTECTGlobalRoot.crt expired.
    14:06:45 Initializing Certification Center …
    14:06:45 locale/French.msg: No such file or directory
    14:06:46 Ethernet device version: RTL8169sc/8110sc.
    14:06:46 ENET: Recherche de l’adresse IP via DHCP …
    14:06:46 AUDIO: Change record device to HD Audio
    14:06:46 AUDIO: Change playback device to HD Audio
    14:06:47 VUSB: Local Device(0x046d,0xc31c,0x03,0x01,0x01)
    14:06:47 USB: Found a new 1.5Mbps device “usbhid” on port 5
    14:06:47 USB: Found a new 1.5Mbps device “usbhid” on port 5
    14:06:48 VUSB: Local Device(0x413c,0x301a,0x03,0x01,0x02)
    14:06:48 USB: Found a new 1.5Mbps device “usbhid” on port 6
    14:06:53 Obtain IP[192.168.0.10] from DHCP server[192.168.0.1]
    14:06:53 DHCP lease time: 04:00:00
    14:06:53 Obtain WDM server [http://wdm:80] from DHCP server[192.168.0.1]
    14:06:53 ENET: set default gateway 192.168.0.2
    14:06:53 Set Name Servers: DNS DOMAIN=[dom.fr]
    14:06:53 Set Name Servers: DNS=[192.168.0.3; 192.168.0.4]
    14:06:53 Set Name Servers: WINS=[]
    14:06:53 Checking 1 Packages …
    14:06:53 IDE: reformat C: with encryption method AES …
    14:06:53 ide1: initializing …
    14:06:53 ide1: total 524288 sectors
    14:06:54 CCM agent: Looking up settings by DNS SRV record …
    14:06:54 Contacting CCM Server …
    14:06:54 CCM agent is retrieving full configurations.
    15:06:59 CCM agent received configurations
    15:06:59 CCM agent checked in …
    15:06:59 locale/French.msg: No such file or directory
    15:06:59 Received Full configuration from CCM.
    15:06:59 Connexion au serveur de fichiers …
    15:07:07 Cannot access system profile
    15:07:07 Skipping firmware check on ftp since already received upgrade/downgrade request from CCM.
    15:07:07 Contacting SNTP [sntp.dom.fr] …

    ______

    Thanks,

    Nicolas.

    #48787
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Try to add
    PlatformConfig=all EncryptFS=yes
    to your wnos.ini before you upgrade the client.
    Just a test.

    CG

    #49292
    niccar
    Participant
    • Total Post: 10
    • Regular Joe
    • ★★

    Hello,

    If someone got the same issue as me: after several tests and mails with dell I got some news.

    If you try to push some configuration to R10 from WMS it will brick the wyse.
    The only thing you can do with WMS and R10 with 8.3 is inventory.

    Thanks for your answers.

    Nicolas.

    #51800
    kingfisher678
    Participant
    • Total Post: 3
    • Newbie

    Does WMS allow you to actually see R10 winterms online? We have already upgraded all of ours to 8.3_014 but Dell does not think they will be visible. Our environment runs off of FTP so this is purely for inventory purposes and to validate firmware.

    #51802
    niccar
    Participant
    • Total Post: 10
    • Regular Joe
    • ★★

    Hello,

    We can’t see our R10 with WMS, as we only wants to inventory our R10 here’s what we have done :

    1- Dhcp provide  file server adress
    2- FTP pushes wnos.ini conf file wich enable SNMP of R10
    3- I uses a scheduled task to launch a script to scan SNMP and get R10 infos
    4- The script fill a XML doc with all R10 infos collected
    5- with a short php code we display the XML infos

    So we have a little inventory without using WMS.

    BR,

    Nicolas.

    #51811
    kingfisher678
    Participant
    • Total Post: 3
    • Newbie

    Thanks niccar. We are also using FTP to manage our devices and snmp for reboots. We are moving away from WDM 5.7.2 to WMS 1.4 and that our main concern was that visability. So far I have found the following and am testing it out. Would you mind including the script you are using if different?

    What do you use to remotely monitor Wyse Thin Clients?

    Here’s a modified snippet of code from one of our PowerShell scripts that uses SNMP to query info from WYSE thin clients:

    #– The below assumes you have a value set for $WYSEClientAddress and SNMPUTIL.EXE in c:tools
    #– Get the uptime remotely
    $WYSEUptimeTimeTicks = c:toolsSNMPUTIL.exe get $WYSEClientAddress SNMPWYSE .1.3.6.1.2.1.1.3.0 | Select-Object -Skip 1 |% {$(($_ -split ‘=’)[1] -replace (‘TimeTicks’,”)).Trim()}
    $WYSEUptimeDays = ([datetime]::Now – ([datetime]::Now).AddSeconds(-($WYSEUptimeTimeTicks[0]/100))).days
    $WYSEUptimeHours = ([datetime]::Now – ([datetime]::Now).AddSeconds(-($WYSEUptimeTimeTicks[0]/100))).hours
    $WYSEUptimeMins = ([datetime]::Now – ([datetime]::Now).AddSeconds(-($WYSEUptimeTimeTicks[0]/100))).minutes
    $WYSEUptimeSecs = ([datetime]::Now – ([datetime]::Now).AddSeconds(-($WYSEUptimeTimeTicks[0]/100))).seconds
    $WYSEUptime = “$WYSEUptimeDays” + ” days ” + “$WYSEUptimeHours” + ” hours ” + “$WYSEUptimeMins” + ” mins ” + “$WYSEUptimeSecs” + ” secs”

    #– Get the NIC speed remotely
    $WYSENICSpeed = c:toolsSNMPUTIL.exe get $WYSEClientAddress SNMPWYSE .1.3.6.1.4.1.714.1.2.6.2.4.0 | Select-Object -Skip 1 |% {$(($_ -split ‘=’)[1] -replace (‘String’,”)).Trim()}

    #– Get the firmware version remotely
    $WYSEfirmware = c:toolsSNMPUTIL.exe get $WYSEClientAddress SNMPWYSE .1.3.6.1.2.1.1.1.0 | Select-Object -Skip 1 |% {$(($_ -split ‘=’)[1] -replace (‘String’,”)).Trim()}

    #– Get the INI server details remotely
    $WYSEConfigServer = c:toolsSNMPUTIL.exe get $WYSEClientAddress SNMPWYSE .1.3.6.1.4.1.714.1.2.6.2.2.0 | Select-Object -Skip 1 |% {$(($_ -split ‘=’)[1] -replace (‘String’,”)).Trim()}
    $WYSEConfigServerPath = c:toolsSNMPUTIL.exe get $WYSEClientAddress SNMPWYSE .1.3.6.1.4.1.714.1.2.6.2.3.0 | Select-Object -Skip 1 |% {$(($_ -split ‘=’)[1] -replace (‘String’,”)).Trim()}

    #– Output the details
    $WYSEUptime
    $WYSENICSpeed
    $WYSEfirmware
    $WYSEConfigServer
    $WYSEConfigServerPath

    #51819
    kingfisher678
    Participant
    • Total Post: 3
    • Newbie

    I will give it a test. Thank you so much Niccar!

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