username.ini equivalent in WMS ?

Tagged: , , , ,

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #49276
    Dpy
    Participant
    • Total Post: 9
    • Regular Joe
    • ★★

    Hello,

    I am preparing the migration from WDM to WMS 1.3
    I use username.ini files containing Privilege=High to give more rights to the support guys
    How to do the same with WMS ?

    Thanks
    Dpy

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

    There is no username.ini with WMS. The only option is to modify WMS to push INI files.
    You can find more on this in the WMS Troubleshooting Guide.

    CG

    #49279
    Dpy
    Participant
    • Total Post: 9
    • Regular Joe
    • ★★

    Thanks

    I followed the troubleshooting guide, I can see my ini file
    https://wms_server/wyse/wnos/username.ini or https://wms_server/wyse/wnos/ini/username.ini

    But when I connect in my 3040, the privileges haven’t changed
    In the Tomacat logs, I see the requests, but none of them concern the username.ini

    3040 IP – – [04/Mar/2019:14:14:10 +0100] “GET /ccm-web/device/getInProgressCommand?wyseId=wyse6900983740129874634 HTTP/1.1” 200 12
    3040 IP – – [04/Mar/2019:14:14:10 +0100] “POST /ccm-web/device/checkin HTTP/1.1” 200 796
    3040 IP – – [04/Mar/2019:14:14:11 +0100] “POST /ccm-web/device/fullConfig HTTP/1.1” 200 68023
    3040 IP – – [04/Mar/2019:14:14:11 +0100] “GET /wyse/wnos/bitmap/logon.jpg HTTP/1.1” 404 1112
    3040 IP – – [04/Mar/2019:14:14:11 +0100] “GET /wyse/wnos/locale/French.msg HTTP/1.1” 404 1113
    3040 IP – – [04/Mar/2019:14:14:11 +0100] “GET /wyse/wnos/pkg/RTME.i386.pkg HTTP/1.1” 404 1113
    3040 IP – – [04/Mar/2019:14:16:17 +0100] “POST /ccm-web/device/remoteUser HTTP/1.1” 200 2

    Did I forget something?

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

    Have you pointed the clients to that WMS server as their fileserver? There is a WMS policy setting for that.

    CG

    #49282
    Dpy
    Participant
    • Total Post: 9
    • Regular Joe
    • ★★

    This policy ?

    Configuring central configuration settings
    Use the Central Configuration page to specify a file server where the ThinOS thin clients checks for configuration and image updates.

    tested with https://wms_server/wyse or https://wms_server/wyse/wnos

    #49311
    elproducto
    Participant
    • Total Post: 94
    • Back Stage Pass
    • ★★★★

    CG,

    Glad I came across this thread. I guess I have to visit more areas of this website aside from just the forums. I was not aware of the wonderful WMS troubleshooting guide that was put together. I can confirm following the steps outlined in the guide. I was able to pull INI files from WMS server via HTTPS.

    Any concerns with this solution?
    Will this configuration survive a WMS upgrade?

    Currently I need to maintain a few IIS servers to provide files to clients that can not be hosted in WMS, but the files are still needed for client configuration. For example ThinOS devices INI file for selectgroup configuration, ThinLinux devices pulling zip files for third party app, proxy.js files, ThinLinux firewall text files, etc… With this method I can get rid of my IIS server and host these files on WMS and/or REPO servers.

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

    Hmmm, I personally expect issues after upgrading WMS as you modify files that possibly getting replaced then.
    I think I have a solution for that at home. However, currently I am lying at the beach 🙂 with no chance to look it up.
    Please remind me in two weeks to look it up for you.

    CG

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