- This topic is empty.
2. February 2012 at 18:47 #7102
Hi there…first post so go easy on me!
We have about 100 S10 devices connecting to a XenApp 5 environment that all use the standard wnos.ini file for their config and that works fine.
I want to take a few of those devices and set them up to test a new XenApp 6.5 environment. Our issue is how to make it so that those select few terminals are set differently from the rest that all use the wnos.ini settings?
Are there wnos.ini parameters that can be used to achieve this? I have been reading about and have seen some slight references to a $MAC entry etc but can get no solid details….so if anyone here can advise how I can do this I would be most appreciative.
Thanks.2. February 2012 at 22:37 #21748GeetarboyMember
- Total Post: 8
You can create another ftp site with the new WNOS.ini and set the File Servers/Path to the new location on the machines you want to test. At least that is what I do on my V10s.3. February 2012 at 8:53 #21749
Cheers for that reply…this sounds like a plan so I will give it a go.
I figured this would not work as the device would get an IP from DHCP and so get the DHCP flag that send the Wyse to the defined FTP server there.
But I guess I can use static IP’s for these specific devices…I will return with results!3. February 2012 at 18:35 #21750GeetarboyMember
- Total Post: 8
yeah, that option 161 will override anything you physically type in to the central configuration, so you have to move those devices outside the scope somehow.6. February 2012 at 9:58 #21751
OK, I got this working handily enough.
First I assigned each device a static IP. That then opened up the ftp server selection option on the client. So I created a new FTP site with my new wnos.ini and manually pointed the clients to that.
This all works rand so long as the users don’t CTRL-G the device!
Cheers for the replies guys and it really helped me with this and allows me to get proper testing of a new XA6.5 environment with a move to moving all the devices to that new env next month.21. February 2012 at 18:28 #21817AmeristParticipant
- Total Post: 61
- Back Stage Pass
Fozz, there might be an easier way to do this. Use a $MAC.INI file for each device where you would like to do your testing, where $MAC is the MAC address of the NIC in the winterm. Put these files in the “inc” folder located in the “wnos” folder in your FTP server. The other devices without $MAC.INI files on your FTP server will continue to use the default configuration.
In our WNOS.INI the first line is
This bypasses the rest of the WNOS.INI contents and looks into the $mac.ini file where we essentially put a copy of everything that is in the WNOS.INI with whatever changes we want to appear on that specific device. At the end of each $mac.ini file we put this line.
This is SUPER important because without this, when the instructions in the $MAC.INI are finished being read, it then goes back to the WNOS.INI and finishes reading from the second line and we don’t want that.
Exit=all will tell the winterm to stop reading its config right there and not go back to the WNOS.INI. Provided you have all of your device configuration in the $MAC.INI this should not be a problem.
This is how we do parallel testing using the same FTP and DHCP settings for all devices. We use this method to set up locally attached printers on some terminals and we are using some terminals as kiosks which don’t require a username or password to connect to a Citrix published app for our HR department.
With this approach there is no need to visit each of the terminals, aside from collecting the MAC address of the device (assuming you are unable to get this remotely through SNMP or some other means) and no worries if someone presses CTRL-G to reset the terminal.
By the way you can also disable CTRL-G from WNOS.INI but I don’t recommend it because it’s a good field troubleshooting tool.22. February 2012 at 14:56 #21823ConfGenKeymaster
- Total Post: 11485
- Jedi Master
BTW, it is just “g” and not Ctrl+g or something else 😉
- You must be logged in to reply to this topic.