- This topic is empty.
-
Posts
-
Hi!
I am very new at this thinclient stuff and now I have to configure an environment to use these clients.
I would like to accomplish the following:
Several thinclients are situated at sites and they are to be treated as kiosks. Site 1 has tc001, tc002 and users can use these tc`s randomly…that is user Pete will use the tc001 today but tc002 tomorrow. Pete will just startup the tc and does not want to log on ..this must be automated.
The tc should use pnagent sites only..all apps are from one farm/WI site.So I have read the manuals and now I think I come up with the plan.
I have to configure wtos.ini and also configure the %usrname%.ini files for every username for each device…that is ic the t is tc002 the username could be user1_tc002 and the ini user1_tc002.ini
Is this correct way to approach this scenario?Do I need to configure what in the wtos.ini?
Do I need any Citrix related stuff here?How do i do the autologin for these users?
BR
Patrick
Hi Patrick,
Yes, you are correct!
You can use either a short cut to a Desktop or app with the user ID and Password in the connect string or PNagent with an autologin.
Example 1:
signon=0Connect=ica
Icon=ica.bmp
Description=kiosk
Application=”Kiosk App”
Browserip=ctxdc1,ctxdc2
Username=$TN
Password=$MAC
Domain=mydomain
autoconnect=yesSee the variables in the example above? Name the terminal name to the user to login to AD with. This way every terminal has a unique login, really import as you do not want lots of connections with the same user ID.
Example 2
signon=1
PNliteserver=ctxdc1,ctxdc2
DefaltUser=$TN
Password=$MAC
Domainlist=mydomain
seamless=yesThis example is similar to the first with apps published.
Check out confgen and the parameters guide for more – also I just made the two examples up off the top of my head so make sure I have the syntax correct 🙂
Post back with your results,
Cheers,
-TTThank you very much TT for your help
The DefaultUser=$TN is good BUT can you use a predefined name?
Can you change the name remotely? via ini?
This because of the process of sending out terminals to the site does not include changing the terminal names….Patrick
Hi Patrick,
Yes you can use a predefined name however try not to do this as having all the kiosks log in as the same user name is bad.
All the terminals have a unique name made up of WT so if you can use this for your user names in Citrix. You can also use $MAC or $SN if you like. These details are on the box so just bar code scan the box to get the details.
It is also possible to use the include=$MAC to remotely change the terminal name but this means creating extra files.
One last idea is just use the free WDM version to remotely rename the devices,
Cheers,
-TTthanks for the quick respone….
The problem I am having is that I am trying to have the terminals log on to a pnagent site automatically with their own user ID´s as stated before.
The solution you gave me is good but is all the lines for wnos.ini?
I tried to do a “username”.ini with those settings but it asks me to log on…and I want it to be automatic
Here are my ini files:
WNOS.INI;*************************************************************
;* General 1 *
;*************************************************************autoload=1
Privilege=Low;*************************************************************
;* Network *
;*************************************************************Device=Ethernet Speed=”Auto”
SignOn=1
MaxVNCD=1
VncPassword=XXXX
VncPrompt=No Accept=AND THEN THE USERNAME.INI:
*************************************************************
;* ICA *
;*************************************************************
;signon=1
;PNliteserver=ctxdc1,ctxdc2 (not needed because in DHCP)
DefaltUser=tc1
Password=
;Domainlist=mydomain (not needed because in DHCP)
seamless=yesHi Patrick,
in the moment you start using a username.ini you’d need SignOn=yes and the user has to enter some sort of credentials.
So in your place, I’d go TTs way.
Use just one wnos.ini and no username.ini.
Personally I would use this scenario:
One wnos.ini with these settings:signon=0
Connect=ica
Icon=ica.bmp
Description=kiosk
Application=”Kiosk App”
Browserip=ctxdc1,ctxdc2
Username=$TN
Password=”password”
Domain=mydomain
autoconnect=yesNow the only thing you’ll have to do is to create AD users named like the Thinclients name or rename each client.
If you want to autorename each client then you have to use one .ini file for each client. Create a subfolder under /ftproot/wnos called /inc/ and put files in there that are named like the MAC address of the clients, eg. 008064123456.ini.
In these files you put just one parameter:
TerminalName=tc0001
This will rename the client with the MAC address 008064123456 to “tc0001”
Then you have to create users in your AD with names like tc0001, etc.Hope this helps
ConfGenThank you ConfGen for your input..
However the inc folder-rename thingy does not work…do I need to call the function in some way or…?
Maybe does not work with s10? version HF 5.1.028BR
Patrick
Yes, you are correct Patrick. It requires a recent 5.2 build 🙁
How old are the units? If they are new you can get the latest build or else you will need to buy the upgrade,
Cheers,
-TTStill working to get the newer OS version…
Still confused about the %username%.ini
The scenario is that we want to have one TC001 at site connecting directly to IE, other TC002 to connect to SAP directly and automatically. We do not want the users to do anything else than to turn on the TC and IE pops up.
If I use the wnos.ini only this is not possible because I need two different settings, one for IE and one for SAP.
If I use %username%.ini I need to have Signon=Yes which brings up the logon screen.
Also I am having trouble to get the %username%.ini to work at all…..it seems that the TC does not compute those settings at all??? very strange…could this be the version of OS?Am I right about these things?
Or can I do some magic somehow..that I have overlooked…?Thank you in advance for your patience…I have only one brain and because I am in Finland it could be in deep ice 🙂
Hi Iceman,
what about create two subfolders under /ftproot/?
/ftproot/TC1/wnos/
/ftproot/TC2/wnos/Now place one wnos.ini file in each wnos folder. One file has a IE connection and one SAP connection predefined. Both as autoconnect with privilege=none.
At the client use as a fileserver/path either ip_address/TC1 or ip_address/TC2.
Cheers
ConfGenHow do I config the client side ftproottc1 and ftproottc2 centralized? I use DHCP to point to a FTProot. Unfortanetly I have under same scope different usage….under same scope one IE user and one SAP user
Looks like you’ll have to configure something manually or use WDM Enterprise with DDC(Default Device Configuration) but this would be chargeable.
Hi Patrick,
I live in Australia, the land down under so my brain is upside down 😉
OK, if you only have a few units then make a DHCP reservation for the devices and this will allow you to use a different 162 tag for each device. That way you can do it like ConfGEN suggested.
/ftproot/TC1/wnos/
/ftproot/TC2/wnos/How many devices do you need to create? Also the include= should work if you have new firmware.
Cheers,
-TTHi Mr. Frozen,
I think I have a solution for you. A friend of mine developed his own Connection Broker. This is exactly what you need. Go to http://www.technicalhelp.de and look for the DDClite Toolset from Guido.
This is brilliant and free.Cheers
ConfGen
- You must be logged in to reply to this topic.