- This topic is empty.
24. October 2008 at 23:54 #1546
I am new to the world of THIN so I appreciate some help pointing me in the right direction. This forum and all its resources appears to be exactly what I was after.
I have been tasked with familiarizing myself with a WYSE V10L. Eventually, it will be replacing sever older Bosanova units. Here’s what I know so far . . .
I have set up a successful ica session and the client is being served up a particular application. This was pretty easy. I had Bosanova screens to draw from. So the situation so far is that the V10L is connecting fine to Citrix.
1. But how do I access administrative functions??? When I right clcick on the desktop, I see that “Administrative Mode” is greyed out. You have a great resource here for configuring the inf file so I just need to know how to access admin functions. This is the first thing I need to overcome. I know the bios password (default) but I don;t even know what I need to do to get into admin mode!!
2. WTOS is running version 6.02. I see there is a 6.20 available. Do I need to setup Network:Server with ftp server info so I can download update?
3. Point me to a good configuration primer please – – -I have NO manuals.
Since I am new to thin, please also verify this for me. I want to be able to take one of these out of the box, plug in the minimal amount of information needed, plug them into a network connection (formerly bosonova boxes) and just have them suck full configuration down from a server and go, go, go . . . .
Thank you so much for the assistance25. October 2008 at 0:33 #14213
I watched the powerpoint presentation on deployment. I understand that deployment using ftp server and ini information stored on server will override local config. If my admin options are not available on this unit do I simply need to restore to factory defaults to get local config options back????25. October 2008 at 13:38 #14214
and welcome to the world of Thin OS (which is the best OS I know).
The video is a very good starting point. I have one quick start guide on my website ( http://www.technicalhelp.de) which could be of help also.
This guide describes how to set up a client and all needed netwrok resources.
Each terminal is in “admin mode” by default. As you were able to configure all parameters there is nothing more an admin could do – except via the wnos.ini configuration file on a FTP server.
In such a wnos.ini file you can set the privilege level to something like “none” or “low”. Then you are no longer able to configure everything locally and you need an admin mode. This is configured also via wnos.ini and as soon as you have configured both, privilege level and admin mode, the option is no longer greyed out.
Use my ConfGen tool to create the needed wnos.ini but only configure the parameters you need as I do see it more and more often that user configure everything ConfGen can do although they don’t need it.
Keep it simple like WTOS is.
CG25. October 2008 at 21:22 #14220
I see, The admin functions are not available because they are not yet configured, And the only way to configure is via the ini file in the ftp download -or the WYSE management tool, I suppose. I was a bit familiar with BOSanova products, and I always configured them via their management tool. But I guess I was never doing thin client deployment the way it was meant to be done.
I understand all about DHCP tags so that makes sense to me. There is only one problem . . .and it’s only a problem because I don;t know enough yet. This batch of thin clinets will be sitting behind a CISCO PIX router. As long as that router will allow me to set up the 161 and 162 tags, I should be good to go.
Then, once I have set up the FTP and configured options with admin functions via ini, the administrative mode will become available on the device?? Your a great help. And I spent quite a while at your website. Your ftp tutorial is great!
Cool!26. October 2008 at 16:40 #14221
Thanks for visiting my website.
As long as you do not have configured any wnos.ini file you are always in admin mode.
Only if you are using a wnos.ini AND privilege parameter inside the ini file then (and only then) you could need an admin mode to gain local admin access again without altering the ini file.
CG30. October 2008 at 21:16 #14248
And again, just for confirmation – – – -there is no way to configure the .ini file except by the ftp setup ot the management tool. So there’s no way from the local machine only I can do this?
This is only so I could tinker with it before we set up the whole network. The management tool costs and is only good for 30 days trial, correct?31. October 2008 at 7:17 #14249
The only way to alter the wnos.ini file is to do this via some Editor (notepad, Ultraedit, etc. or ConfGen).
But for testing I would not distribute the DHCP option tag to every client but enter the Fileserver IP locally only on the test machine. After finishing your testing you can distribute to all units via DHCP.
WDM Workgroup is free of charge. You just have to activate it once. Go to Configration Manager-Preferences-Licensing and double click the license. Then follow the steps to activate. WDM Enterprise would cost.
CG31. October 2008 at 19:22 #14251
Right. I wouldn’t use the switch globally. But you misunderstand my question.
To rephrase my question , is there any way I can modify the ini with ONLY direct access to local machine? I am not ready for ftp yet and I just want to play around with client locally for now.
As it was sent to me, there are two icons on desktop. One for Default RDP and one for Default ICA. I also see networ config, general properties and a few other things. But I see no way to access the wnos.ini fole locally or have any access to a file explorer of any kind.
MY Assumption was that this was DEFAULT setup and the box had not been messed around with by someone else. If so, then I see no way to locally edit a wnos.ini file. Is this by design . . . . or am I possibly not looking at a factory default setup. I have NO documentation
Thanks so much3. November 2008 at 10:11 #14255
I think you still have not understand the WTOS concept.
Here are some facts to clarify a few things:
– local config is always possible as long as the privilege level is high
– wnos.ini is a remote central config file which can (should) be used to configure the devices
– there is no local wnos.ini file. Local changes are directly written in the OS
– there is no file explorer as it is of no need and only a security risk
CG3. November 2008 at 20:42 #14271
Thanks so much. Yes. I think I think I see the light. You need to understand the evolution of this for me. I was familiar with BOSanova terminal configuration which is a bit less restrictive. (and less secure, as a result – I realize that) and I wanted to make sure of a few things.
You have been helpful and I think we can put this one to reset now.4. November 2008 at 7:07 #14273
I am glad I could help.
Don’t misunderstand me, you are always welcome here to ask (even simple) questions.
- You must be logged in to reply to this topic.