Thin Client and Virtual Machines Thread, Remote Desktop 7 client - either default domain or log off on disconnect in Technical; I am attempting to set up some Windows FLP clients using the RDP7 client, and so far, I've got them ...
18th December 2012, 09:26 AM #1
Remote Desktop 7 client - either default domain or log off on disconnect
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?
IDG Tech News
18th December 2012, 09:52 AM #2
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...
18th December 2012, 10:10 AM #3
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!
Last edited by localzuk; 18th December 2012 at 10:15 AM.
14th January 2013, 10:32 PM #4
20th November 2013, 10:41 AM #5
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.
20th November 2013, 10:50 AM #6
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
By Byford-Rew in forum Thin Client and Virtual Machines
Last Post: 23rd June 2012, 09:03 AM
By tosca925 in forum Windows
Last Post: 31st January 2012, 09:26 PM
By reggiep in forum Windows Server 2008
Last Post: 1st March 2011, 11:14 PM
Last Post: 8th November 2007, 03:53 PM
By Zoom7000 in forum Wireless Networks
Last Post: 20th September 2007, 10:24 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)