FTP to WMS Migration

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #105224
    Avatardjmoeller
    Participant
    • Total Post: 61
    • Back Stage Pass
    • ★★★★

    Our site uses Wyse thin clients in an industrial environment. The desire is to assign a policy (mostly resolution and RDP) based on the IP and/or name of the thin client. Basically if a thin client fails, it gets replaced by maintenance who assigns minimal settings (IP Address, DNS Servers) and the unit should start working like the thin client that failed.

    With FTP we were able to do this fairly successfully using two commands.

    Terminalname=$DNS Reboot=yes

    Include=$TN.ini

    Can I replicate this in WMS, I’m not seeing how to apply a policy based on the name of the thin client?

    Should I be using a combination of WMS and Central Configuration? Maybe I can combine what gets set via WMS Policy and what gets set via .INI files?

    #105275
    ConfGenConfGen
    Keymaster
    • Total Post: 11287
    • Jedi Master
    • ★★★★★★★

    This is not possible with WMS.
    You have to create either different groups with their own policies, or you have to modify the policy on the Devices tab per device.
    However, the latter will assign the policy to the device and if you replace the device, you would have to recreate it again.

    CG

    #105360
    Avatardjmoeller
    Participant
    • Total Post: 61
    • Back Stage Pass
    • ★★★★

    Are there any other strategies, I should consider or does WMS simply no longer meet our use case?

    For example, stuff like this was working as recently as 8.6 (per the 8.6 Reference Guide)?

    include=&Left($FIP,11).ini

    With WMS have we lost all ability to assign profiles dynamically? Are we now required to login to WMS to assign a non-default group token or have I missed something?

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