- This topic is empty.
-
Posts
-
Greetings,
I am relatively new to the thin client scene and have had the opportunity to play with only 2 clients – an HP & the Wyse V10l. The Wyse is the one I currently have in my possession and am duly impressed with the ease of setup in most respects. I do have one little thing that I’m trying to figure out.
I will be using the client/server equipment in a small portable field office environment with up to 30 users (but usually around 10-15). I have setup a Win2K3 server in a non-domain configuration with Terminal Services, FTP, DHCP, and File & Print Services. The issue I’m having is streamlining the login process.
What I’d like to see is 1 of either 2 things:
1) With Signon enabled, when I enter a username/password in the TC, those credentials are passed through to the RDP session for login, or
2) The TC have a login dialog box similar to the Signon that simply says “Authorized users may login” (accomplished with an image & logo) with an “OK” box to initiate a session with the server.
I think my preference would be #2. But would have thought I could at least accomplish #1, but every attempt has failed (and I get that annoying beep/chirp when I attempt to login).
I realize that I can make a desktop wallpaper image with the pertinent information, but I have an aesthetic issue with creating a connection document that sits in the upper left hand corner that must be double clicked. What I really want is a Signon box that doesn’t ask for a username/password (nor a sub-banner saying I can login as guest)
Is this possible with the current firmware and if not, do we know if that will be a feature in future releases?
Thanks for any info you may have.
Hi,
this should work fairly easy. As you are using FTP, I assume you have also played around with the wnos.ini file. If yes, a file like this should do the trick for you.
;*************************************************************
;* *
;* This wnos.ini file was generated with the *
;* Configuration File Generator *
;* Copyright by Thomas Moellerbernd *
;* *
;*************************************************************;*************************************************************
;* General 1 *
;*************************************************************Privilege=None Lockdown=yes
;*************************************************************
;* Network *
;*************************************************************SignOn=No
;*************************************************************
;* RDP *
;*************************************************************;
;- RDP Session 1 –
;- Each line but the last must end with a ‘ ‘ –
;
CONNECT=RDP
Host=servers ip address
Description=”RDP Desktop”
Icon=default
AutoConnect=yes
Reconnect=yes
Fullscreen=yes
Experience=0
LocalCopy=yesPrivilege=none Lockdown=yes means that the user does not have any local rights to change anything on the unit. By using “Lockdown” this will even work when the FTP server is not available.
Then the RDP session will be started automatically presenting the user the standard Windows logon dialog.
Is that what you want?
ConfGen
Yes & no.
Yes I have been playing with wnos.ini…a lot. This approach works up to a point and meets my needs except that when the RDP session times out without a user logging in, the device reverts to the Wyse desktop at which point it would be nice to have a “Press OK to Connect” versus “Login to Connect” dialog box.
Oh, just saw the reconnect line. I will play with that – I missed that setting. So now I have a second question: what is the processor load on idle sessions that are sitting there and reconnecting every few minutes?
It seems to the naive mind of mine that it would not be a best practice to have this thing toggling in and out of connecting with the server.
Side note, out of eternal curiosity, is it possible to get the login dialog box to work in the environment that I specced out above or is that only for ICA sessions?
Thanks.
-BT.
Hi BT,
If you want a CE style connection box them set the line connectionmanger=maximise and remove the icon=default statement. This gives you no icon on the desktop and the connection manger. Personally I like the icon.
You can use the reconnect= statement with a time value, then you see a countdown as it re-connects. It does use some memory on the server as the win socket is opened however its not a big deal. Normally most just let the user click the icon.
Finally you can use the signon=NTLM however you will have to allow you TS server to respond to NTLM authentication. In a AD environment this is not great but in your stand alone server setup I don’t believe its a big issue. The Microsoft site will have the reg setting to do this.
So you
may end up with this:Signon=NTLM
CONNECT=RDP
Host=servers ip address
Description=”RDP Desktop”
Icon=default
Username=$UN
Password=$PW
AutoConnect=yes
Reconnect=yes
Fullscreen=yes
Experience=0
LocalCopy=yesCheers,
-TT
- You must be logged in to reply to this topic.