New image forcing other TC’s to update

  • This topic is empty.
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #1084
    Avatarrmlounsbury
    Member
    • Total Post: 9
    • Regular Joe
    • ★★

    I did some searching here and over on the Wyse help desk page to figure out this odd problem I have. I recently downloaded and updated a new thin client with the V90 4.02 Build 550.

    I took it to the warehouse to test the wireless connection and configure the device when all the other thin clients started to update themselves and reboot. Ran up stairs to check my laptop and make sure I didn’t start something on WDM. They continued to loop with the update until I shut down the new thin client.

    I haven’t seen anything from Wyse so far that would indicate this sort of behavior. Something I’m not aware of going on?

    #12390
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    On your laptop did you have a new installation of WDM? When a device is discovered in WDM it will cause the device to re-boot as it disables the write filter and adds the new IP and security key.

    I think it may have been something on your notebook not the new V90 client, can you check it out?

    Cheers,
    -TT

    #12396
    ConfGenConfGen
    Keymaster
    • Total Post: 11116
    • Jedi Master
    • ★★★★★★★

    Do the units just reboot or do you also see a message like “Your administrator is doing something on your unit….”?

    CG

    #12416
    Avatarrmlounsbury
    Member
    • Total Post: 9
    • Regular Joe
    • ★★

    I did a new install of WDM on my laptop back on Monday. It did go through and update everything which I was expecting. However, when I put the new TC onto the wireless network my laptop (which has WDM) had no Ethernet connection and the wireless card was disabled.

    So I know it wasn’t my laptop. Additionally the only thin client that did not attempt to update was the new thin client. I shut it down and pulled the wireless card and all the other thin clients stopped. attempting to update.

    I never did get the blue “your administrator is doing something” message. I only get the 5-minute warning screen.

    I’m staying late tonight so I’m going to do some experiments with the new TC to see if it is in fact the source of the disruption.

    #12418
    ConfGenConfGen
    Keymaster
    • Total Post: 11116
    • Jedi Master
    • ★★★★★★★

    Keep us updated.
    Have you answered the 5-Minute warning somehow?

    #12420
    Avatarrmlounsbury
    Member
    • Total Post: 9
    • Regular Joe
    • ★★

    I have used both the “delay” and “update now” buttons with a near by terminal. Nothing unusual on that part.

    #12425
    Avatarkaraziel
    Member
    • Total Post: 74
    • Back Stage Pass
    • ★★★★

    I think they meant when the devices started rebooting, was there a message that popped up regarding an update, or did they just start rebooting.

    The update messages means its triggered by a WDM server somewhere…no message seems more like malware, possibly virus causing reboots.

    -k

    #12426
    Avatarrmlounsbury
    Member
    • Total Post: 9
    • Regular Joe
    • ★★

    Okay, I have confirmed that it is infact the thin client (same model as all the other TC’s) with the new image flashed onto it.

    This the V4.02Build550_WRF downloaded from Wyse. No modifications have been made to the image with the exception of adding Linksys drivers for a WPC54G card.

    All the other thin clients in the warehouse go into a continuous update loop. I’m going to experiment with the Rapport Agent settings and image a second TC to see if devices with the new firmware have the same problem.

    #12427
    Avatarrmlounsbury
    Member
    • Total Post: 9
    • Regular Joe
    • ★★

    Figured it out. Can you say administrator error?

    I checked the Rapport Agent properties to see what IP address it had set for the server (192.168.140.25) and went back to check the IP address of the new thin client. Surprise, DHCP assigned it 192.168.140.25. Once I moved thin clients afflicted with this issue to a 192.168.0.1 they stopped attempting to update.

    Doh! 😆

    #12433
    Avatarthinkthin
    Member
    • Total Post: 1707
    • Jacked into The Matrix
    • ★★★★★★

    8)

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