- This topic is empty.
-
AuthorPosts
-
May 8, 2007 at 3:46 pm #425
Now the FTP is working and default settings are working via the wnos.ini file I wondered is there a way of specifying unique usernames so users don’t have to type their username at the terminal server login screen?
I hoped I could create a default rdp session on the terminal then lock it down via the wnos file. But it appears everytime the wnos runs it clears any settings found on the terminal and only runs the wnos. I saw mention of using a username.ini file alongside the wnos but it mentions it only works with ica connections, unless I read it wrong?
Any ideas would be much appreciated.
Regards.
May 8, 2007 at 10:25 pm #9576Hi,
Yep, user.ini files work with RDP but if you want users not to log in just set the signon=0 in wnos.ini
Or are you after different users having different icons to different servers?
Can you tell me a bit more about how you would like the setup to look like?
Cheers,
-TTMay 9, 2007 at 8:14 am #9579@thinkthin wrote:
Hi,
Yep, user.ini files work with RDP but if you want users not to log in just set the signon=0 in wnos.ini
Or are you after different users having different icons to different servers?
Can you tell me a bit more about how you would like the setup to look like?
Cheers,
-TTThanks for responding.
All I want is for users to have their username showing in the user name field on the terminal server screen once the wnos has been processed. At the moment I can apply a specific username in wnos but that would appear for all users when they get to the terminal server login screen. I want each user’s username to appear for each terminal server login screen.
Regards.
May 9, 2007 at 11:09 am #9580Hi,
There are a few ways to do this:
Create a user.ini, for example fred.ini. The create a connect statment that has the line username=$UN. Finally ensure signon=1 is set, see the passthrough example on this site
You could so the same thing with Signon=NTLM adn the $UN statment is you want to use domain ID’s and not user.ini’s. The downside is you will need to allow NTLM authentication on the server.
I am assuming that you do not want users to enter a username or password, just pass through into a session? Most RDP setup simply set signon=0 and make the users enter the username and password when prompted,
Cheers,
-TTMay 9, 2007 at 11:35 am #9581@thinkthin wrote:
Hi,
There are a few ways to do this:
Create a user.ini, for example fred.ini. The create a connect statment that has the line username=$UN. Finally ensure signon=1 is set, see the passthrough example on this site
You could so the same thing with Signon=NTLM adn the $UN statment is you want to use domain ID’s and not user.ini’s. The downside is you will need to allow NTLM authentication on the server.
I am assuming that you do not want users to enter a username or password, just pass through into a session? Most RDP setup simply set signon=0 and make the users enter the username and password when prompted,
Cheers,
-TTThank you for your response. I’m not sure if I follow though. And I can’t see the passthrough example as there is no link to the site you mention.
Could you show me what I would need to put in the wnos file and then the user.ini files. I’m confused how the running of the wnos knows which user.ini would need to be used.
If for example we have three users with the following usernames:-
usera
userb
usercAnd I wanted each of them to have their username displayed when they reach their terminal server login screen.
Many thanks in advance.
May 9, 2007 at 12:42 pm #9582May 9, 2007 at 12:58 pm #9583So if we modified the ICA sample above usera would login, click the RDP icon and have the username pass into the session. I am not sure if this is a good setup and the user still has to enter the username at some stage.
Pass-thorough is normally used to pass the username and password directly into the session so you are not prompted again.
Some users use the terminal name and mac/serial as the pass through credentials to the user does not enter anything at all.
Sorry but I still am not sure why you dont want users to simply enter these details at login and want just the username filed in? My brain must be slowing 🙁
May 9, 2007 at 1:16 pm #9584@thinkthin wrote:
So if we modified the ICA sample above usera would login, click the RDP icon and have the username pass into the session. I am not sure if this is a good setup and the user still has to enter the username at some stage.
Pass-thorough is normally used to pass the username and password directly into the session so you are not prompted again.
Some users use the terminal name and mac/serial as the pass through credentials to the user does not enter anything at all.
Sorry but I still am not sure why you dont want users to simply enter these details at login and want just the username filed in? My brain must be slowing 🙁
Oh I see what you are saying now. I don’t think I will be able to do what I wanted. The only reason I wanted the username automatically added to the TS login screen is that the users were used to this when they had their normal PCs. It is not end of the world but it would have been nice if I could have done it with minimal user ineraction. I may try out what you have suggested and see if they can cope with it but it may be easier just to leave it as is.
Many thanks again for your help, it is very much appreciated.
-
AuthorPosts
- You must be logged in to reply to this topic.