Copy /etc/vmware/config on boot?

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #41528
    coiniman
    Participant
    • Total Post: 2
    • Newbie

    Hey guys,

    we are having 500 + linux suse thin clients, for our VDI environment.
    We are in the disaster recovery business which means clients are having master images in our netwerk, and we deploy them for the clients. however all images report to our clients domains, which means we cannot run policies. (since those are managed by the clients)

    the challenge we face are the bloomberg keyboards and especially the fingerprint readers. at first we solved this with windows embedded thin clients.
    But now with the D50D thin client we managed to get them working yaaayyy.

    the only thing we have to do is edit on the thin client the /etc/vmware/config file with these entries:

    VMWareViewIncludeUSBID=vid-1188_pid-03E9
    viewusb.AllowAutoDeviceSplitting=true
    

    the first rule can be pushed via the wlx.ini however the 2nd one doesn’t produce an entry in the /etc/vmware/config file.

    so we are now wondering is it possible to for example store the config file on the FTP server and when a thin client boots has a script running that copies that file?
    Also i preferably don’t manual make a script on all the thin clients 🙂

    #41529
    ConfGen
    Keymaster
    • Total Post: 11340
    • Jedi Master
    • ★★★★★★★

    Pretty sure the second is not known by the parser.
    You could create a script that sets these two values. Then build a WDM package that copies the script to all clients and executes it.
    Have you checked if this has to be added after each boot, so, that it is lost after a reboot?
    If so, create a custom connection which simply autostarts the script each time.

    CG

    #41678
    coiniman
    Participant
    • Total Post: 2
    • Newbie

    Hi CG,

    it is known, we have created a million different options to get this to work.
    and this is the only way to get it done.
    Only the first rule is not sufficient. the spilliting is needed.
    this was tested with:
    vmware_viewclient-2.3.0-1551379.00.00.sletc11sp2.rpm
    and
    vmware_viewclient-3.2.0-2331566.00.04.sletc11sp2.rpm

    and the config file is persistent after reboot, (however if you update the view client the file gets overwritten :))

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