WDM – Which version?!

  • This topic is empty.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #7460
    timstone
    Member
    • Total Post: 19
    • Regular Joe
    • ★★

    We are currently looking at rolling out a new config to our Wyse terminals, and would like to look at WDM for this.

    Terminals are WTOS Wyse S10’s

    I’ve downloaded trials of 4.9 and 4.9.1 and after looking through the release notes, they require the terminals to have v7 firmware and above. We are currently running 6.1, and planning to upgrade to 6.5

    We have tested 7, and although it’s great, there is no flexibility to roll back to 6.x once you have upgraded.

    We’re happy to pay the appropriate license fees for the software, but I’m really struggling to find out which version of WDM we need to start with that is compatible with 6.1

    The earliest set of release notes that I have found are for WDM 4.8.5, which still requires the terminal firmware to be v7.

    Any ideas would be really appreciated.

    Cheers 🙂

    #22674
    timstone
    Member
    • Total Post: 19
    • Regular Joe
    • ★★

    Also, what is the HAGENT that all of the guides refer to? I can’t find any explanation as to what it is anywhere!!

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

    You can use any version of WDM from 4.7 onwards.
    The only requirement would be, as long as you using 6.x firmware, to use Windows 2003 server and not 2008 or 2008R2. This is because of incompatibilities with the newer IIS.
    But in my opinion no WDM is needed. You only need the wnos.ini file for Thin OS based clients.

    HAgent is the small agent on the client site that communicates with WDM. This is not upgradable on a Thin OS device as the HAgent is part of the OS. HAgent=HTTPAgent, as is uses http as the communication protocol.

    CG

    #22693
    timstone
    Member
    • Total Post: 19
    • Regular Joe
    • ★★

    Thanks for the response 🙂

    After a little more digging, I’ve discovered that I can remote control the terminals using VNC.

    After trying a could of clients, I’ve settled on UltraVNC. Although it’s a little sluggish, it’s perfect for what I need to do.

    I can connect to the unit, log in as admin, change the dhcp options, and let it reboot and collect the new firmware and settings from the new FTP server.

    Works perfectly!!

    #22694
    timstone
    Member
    • Total Post: 19
    • Regular Joe
    • ★★

    Also, interesting with not being able to use w2k8.

    You say it’s an issue with IIS. Is IIS 6 on w2k8 no good then?

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

    Use 2003. That I know for sure will work.

    CG

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