localzuk Posted December 18, 2012 Posted December 18, 2012 I am attempting to set up some Windows FLP clients using the RDP7 client, and so far, I've got them working with NLA just fine. However, when prompted to log in, after opening the shortcut to the connection, they are asked to enter their username - which has to include the domain\ part. I can eliminate this by joining the client to the domain and using SSO, however there then comes the issue of having to log off twice - once from the RD server and once from the thin client. Is there either a way to make it so they don't have to type in the domain or to make it so that once the connection ends, the thin client session logs out?
localzuk Posted December 18, 2012 Author Posted December 18, 2012 I can get the domain\ to show with 'username:s:Blah\' in the connection file, but you know the kids are going to delete it and then get confused...
localzuk Posted December 18, 2012 Author Posted December 18, 2012 (edited) Unless someone can come up with a better solution, I now have a vbs script that runs and auto runs the rdp file, which contains the domain\ bit. If the kid gets confused or types the wrong thing, they can simply press cancel and it'll open again. EDIT: Problem though, as the VBS 'sleep' makes the window flash and it then selects the username box and selects all the text! Edited December 18, 2012 by localzuk
localzuk Posted January 14, 2013 Author Posted January 14, 2013 Ended up doing this instead: http://www.edugeek.net/forums/thin-client-virtual-machines/107013-hp-t5735-custom-debian-install-allow-nla-session-broker-work-rds.html
Chris_ Posted November 20, 2013 Posted November 20, 2013 I know this is an old thread. Do you have any details on how you enabled NLA? I can't seem to get it to work on WinFLP. I've followed guides for enabling it on XP but they don't seem to work. Thanks
localzuk Posted November 20, 2013 Author Posted November 20, 2013 After 10 months I'm afraid I can't remember - I abandoned the idea of using FLP and moved to Debian as it worked out being a better solution for us. I think it was to do with CredSSP - Description of the Credential Security Support Provider (CredSSP) in Windows XP Service Pack 3
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now