- This topic is empty.
-
Posts
-
Hello,
I need the most basic of basic assistance in setting up my thin clients.I only have 10. They are going to be used for remote desktop to a Windows 2012 R2 server running RDS services. I have 15 licences.
Currently, out of the box, my C10LE units can connect to the server. They get their IP address, and I just have to configure the Default RDP settings with server, domain and the users can log on. I also take care of the display settings. As I mentioned, there are only 10, so full deployment should be a breeze.
I would like to “clean up” the startup and “optimize” the connection as best as possible. I notice during startup the unit is looking for Looking for WDM server, looking for DNS/WINS, looking for file server, none of which it apparently needs because once it’s booted up, I can click on RDP and connect.
I also read in the manual about other INI file entries that can optimize the connection, and just make things run better. I’d like to use them, but I don’t know how to get the configuration on these units. I don’t have an FTP server. I don’t have access to the DHCP server.
I can create a service account in AD and share a folder on a server for the INI file if that would help.
Any assistance would be helpful.
Thanks in Advance.
Miles
INI files are only pulled from the clients via ftp, http or https.
Most tuning options are only available via INI file. Therefore, I would highly recommend setting up a webserver and do a central config via wnos.ini.
That makes it even easy when you have to setup unit 11-20 sometime.Find more info on setting this up under
Products – ThinOS – First StepsCG
Well that is disappointing.
Is there any way to bypass the initial DHCP portion. I do not have access to the DHCP server. We are part of a large enterprise and while I can put an FTP server on an Application server we have, if I can’t manually tell the clients where to get their configuration, I may have just wasted money on an RDS server, licenses and clients. 🙁 Not feeling the love at the moment.
If you have access to the DNS server, you can add an alias there.
If not, you can add the webserver (called Fileserver in ThinOS) manually, of course.CG
Well I’m on my way… almost….
I don’t have access to DNS either.
I did create an FTP server, and I can hit it from my workstation and see the .ini file I created with the generator.
However, using the same credentials (anonymous) on the C10LE when it gets to File Server on the starup is errors.. cannot open data socket ?
I used the same credentials in Central Configuration as I do when I try to FTP from my workstation so I’m not sure what’s happening here.
Any thoughts
Ok… I resolved my own issue, sortof. I needed to set a firewall setting to allow inbound connections. So now there’s no error, but it’s not loading my wnos.ini file either.
LOL… don’t mind me… apparently I just need to keep posting my questions and answering them 🙂 There is a wealth of info here !!!!
FWIW.. because I’m not using DNS, I needed to set the Default FTP folder as the WYSE folder so that the Thin Client would look into the wnos subfolder.
It read the file, but there are a few things NOT happening. so I will trudge on.
Miles,
I would highly recommend you seek out the individual responsible for creating and maintaining the DHCP for your office where these thin clients are deployed and ask them to add a couple of option tags for your DHCP scope. This only takes a couple of minutes for a qualified administrator. Once these are set up you do all the configuration from your FTP server.
If your department has already spent the money on servers and licenses, its clear to me that the business deems this a necessary project, so if you need some help really don’t be shy about asking for two minutes of admin time to get the project complete the right way. DNS entry or the DHCP option tags are necessary for zero-touch deployment.
Secondly, I see you are struggling with the wnos.ini file. I started with thin OS devices knowing nothing about how to configure them and when I started I wish someone had offered me this advice. Start with the Configuration Generator software and make your first INI file using that tool. Don’t select too many options at first, just the bare minimum to show you that the configuration is loading. Move on from there to add settings that are critical to delivering what you need. Once you have a working INI file then go in and make another one that’s more advanced. (the nice-to-haves)
I would strongly encourage the use of MAC.INI files for testing. The way I have mine set up is the very first line of the WNOS.INI file is:
Include=$MAC.ini
Then at the end of my 008064XXXXXX.ini file I have this as the last line:
Exit=All
What this is going to do for you is that your users (production environment) can continue using your WNOS.INI file while you experiment with settings on your own terminal using your own “copy” of the WNOS.INI that’s actually called 008064XXXXXX.ini where the XXes are the rest of your MAC address on your test terminal.
Finally, I would recommend you download a copy of the Wyse ThinOS INI Files Reference Guide as it will explain most of the settings that appear in your WNOS.INI file. It seems from your questions that you’ve asked (particularly about disabling the search for the WDM server) that you haven’t read this guide yet. FWIW, I use these settings:
RapportDisable=yes
Service=WDM disable=yes😉
Thanks Amerist,
Unfortunately it’s not a matter of seeking out the individual. Without divulging too much, we are an entity who is on another organizations network where they get to pick and choose how much support if any they will provide. I can’t really say any more than that.
I did get the FTP server configured, and while I read much of the guide, I found the configuration generator to be much more useful to find out what all of the settings do. Now all I have to do is enter an IP address under Central Configuration and reboot. We have only 10 units to deploy so this works just fine.Again, thanks
- You must be logged in to reply to this topic.