- This topic is empty.
20. November 2007 at 15:07 #753SecurusMember
- Total Post: 7
Good Morning everyone, Great site you got here, without it I wouldn’t have been able to get anywhere near the point I’m at now. But I do have a questions:
How do I (Can I?) create different configurations and then implement those different configurations on different terminals?
What I want is a currently deployed configuration (which I have and which is running great) and a test configuration that I want to push out to only one terminal in my lab.
I’m competly new to thin computing but already amazed by what it’s capable of.
I’m running 7 S10’s and here is my wnos.ini:
DeskColor=”0 78 152″
#Begin setting Citrix Application Settings
There are more applications but all have the same configuration. Feel free to point out and glairing mistakes and point and laugh at me, it is my first wnos.ini.
Any Information you guys can provide me with would be appreciated.20. November 2007 at 17:14 #10826lukeMember
- Total Post: 10
- Regular Joe
I’m just starting out with Wyse OS and found myself in a similar scenario. This is how I did it.
Create two additional ini files, one for the main configuration and one for your test configuration. Name them main.ini and test.ini. You would place these in the INI subfolder in the WNOS folder.
Add these two lines to your wnos.ini
Your other users will get a login screen when they boot up but they will only have to hit enter to login because the username will be auto-filled and no password has been designated.
When you would like to load the test configuration just change the username from “main” to “test” and login.
There’s a good chance that there is a better way to do this but this has worked for me.22. November 2007 at 14:46 #10837EBHMember
- Total Post: 43
- Frequent Flyer
if you are just using traditional FTP share to make your wnos.ini available and are NOT using DHCP option tags to automatically point the terminals to it, you could setup separate folders and manually point terminals to one or the other folder depending on which INI you want them to get. i.e.–for the ftp server path you could specify server ip/config1/wyse on one terminal and server ip/config2/wyse on another terminal.
If you have a large enterprise and don’t mind investing in WDM enterprise, you could do Default Device Configuration. This is perhaps one of the most powerful tools wyse offers which i have been using successfully with the help of others on this site. [/i]27. November 2007 at 19:14 #10889SecurusMember
- Total Post: 7
Thanks for you responses.
I tried the alternate ini files, main and test, but didn’t have any luck it wanted a password that hadn’t been set, it wouldn’t take a blank password nor could I change the password to something usable.
I am using the DHCP option tags to point to the ftp server so unfortunately that rules out your option EBH, I do appreciate the input however.
We are not a large enterprise and also nonprofit so WDM enterprise is not something we are looking at purchase at this moment. Depending on our needs is may be needed later.
While I was working with the terminal I noted you could specify on the terminal which option tags for it to use.
Can I create new option tags that specify a folder rooted in the FTP server that has a different wnos.ini file and point only my selected test terminal to those option tags to utilize the test configuration?
I plan on trying this soon but was hoping to get input from someone that might have already tried this, less I break DHCP or the interwebz 😀 .
Thanks agian for your help.
- You must be logged in to reply to this topic.