Unsolved
This post is more than 5 years old
1 Message
0
36428
July 16th, 2015 17:00
Default WNOS.INI with additional configuration later
Hi, we have just purchased a bunch of T10 wyse thin-clients running ThinOS 8.0_505. Currently we do not have any sort of cloud configuration software setup (hopefully in the future we can get it approved and use it..). We are going to be sending out a few thousand units to over 2200 remote locations. All thin-clients will utilize RDP, but the RDP connection is based on location. Is there anyway to configure a default wnos.ini with stuff like admin password, access level, visual experience and a few other minor items, and then once the devices arrive at the location we can walk the end-user through configuring an RDP connection specific to them?
Currently, when I do this, I've set the wnos.ini to cache locally otherwise once I disconnect from my FTP server, it drops the config. The problem is that when I disconnect from the FTP, manually create my RDP connection and reboot, the RDP connection disappears, which isn't surprising since the basic default one is cached. Is there another way to go about this that I'm missing? We do NOT want to send units unconfigured because there is very little configuration possible in the UI, we can't setup an FTP at each location, and depending on location we could be configuring 5-10 different usernames/passwords, and these have to be automatic logons, we don't want the users manually typing name/password.

