- This topic is empty.
-
AuthorPosts
-
December 14, 2007 at 3:20 pm #11046
I have now come to a solution that suits my customers reqs.
I learned during this week that not all the INI commands work and especially if you have an old OS version of the Wyse Thin OS.
I did not get the user.ini to work with 5.1 something version..but with 5.2 no problems at all.
I also learned that this MONKEY FORUM IS THE BEST EVER!
I have never come upon such expertise and speed in the answers here. No support forum or even paid support channels can even be measured with these “monkeys”. I thank you from the bottom of my CPU, TT and ConfGen ๐Now Iรยดll tell you my solution:
The specs/reqs where quite narrow…no actions from enduser, not even a click. And if possible no action from admins also…(this impossible)
The setup is as follows:
1) DHCP with 161 and 181
(The solution with reserved IP scope options is brilliant but the admin overhead is too heavy..if easier DHCP solution good solution)
2) One wnos.ini with settings for all and also PNAgent logon using variables
3) One %username.ini for each TC in INI folder where ICA connections configured with “autoconnect”.
This configuration made it possible for the “kiosks” to have an app launched in their face at startup (only one per TC).
The drawback is that there is two ICA icons on the desktop ๐ Have to see if something to be done with that…??
I had to do it this way because I could not find some command for autoconnect with PNAgent logon apps on the desktop (though it can be manually configured???)
So even with couple of Q marks the outcome is OK and is not so heavy on the admin side…Only need to rename the TCรยดs manually (no commands for this!) and create usernames in AD matching those settings in INI files.Once again I thank TT and CG.
BR
Patrick
December 14, 2007 at 8:24 pm #11050๐
Now with all those nice things you have said we will all get big heads!!!
Glad you found a solution!
-
AuthorPosts
- You must be logged in to reply to this topic.