I have a Terminal Server running Windows Server 2008 Standard SP1. Domain controller is running Server 2008 SP2. We want our users to be able to save credentials on the desktops to log in automatically. On Windows XP, it works fine, on Windows 7 we get the error: Your credentials did not work: Your system administrator does not allow the use of saved credentials to log on to the remote computer x.y.com because its identity is not fully verified. Please enter new credentials. The server is not configured to require saved credentials: Remote Desktop Configuration is set to not require credentials. Domain Group Policy is set to not require credentials (Computer Config\Administrative templates\windows components\Terminal services\terminal server\security\Always prompt for password upon connection). I've tested it on RDP 6.0 and 6.1 on XP machines and they work fine. It doesn't work in Windows 7. I followed the instructions from here: http://alinconstantin.blogspot.com/2007/08/terminal-service-client-not-using-saved.html Which I got from this technet post: http://social.technet.microsoft.com/Forums/en-US/itprovistasetup/thread/894b2a64-68c9-4b57-a65f-14d377e3a295 But to no avail. Since the server name doesn't match the FQDN, I've also tried installing the cert in Trusted Root, Intermediate Root and Third Party Root, but still get the error. I've searched the internet but haven't been able to find anything. Please let me know how to fix this. Thanks

Hi, Thanks for the post! Try the following steps: 1. On your Windows 7 client, click Start, input gpedit.msc in search bar, press Enter. 2. Navigate to Computer Configuration\Administrative Templates\System\Credentials Delegation. 3. On the right pane, double click Allow Saved Credentials with NTLM-only Server Authentication. 4. Click Enable. In the Show contents dialog box, click Add, type the name of remote computer(server) in this format: TERMSRV\<computername>, then click OK. Now check if it works. Regards, MiyaThis posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I ran into something similar a while back and what I found in my situation was remote desktop would not work using machine name, authentication would fail. however it worked as it should if I used the ip address.

Yes, I've tried that and it doesn't work. I am part of a different domain, but I don't believe that group policy is set from the domain.

Sorry, let me be clear.... Miya, I did make that change but it did not resolve the issue. I also tried with the IP address and added the IP address to allowed servers, but it still prompts for my password.

Yes, I've tried that and it doesn't work. I am part of a different domain, but I don't believe that group policy is set from the domain. Do you mean you access the shared folder on Domain A from a domainB-joined client? What type of trust is create betweent the domains? You can refer to Best Practice for using security security groups accross forests in http://technet.microsoft.com/en-us/library/cc772808(WS.10).aspx Regards, Miya This posting is provided "AS IS" with no warranties, and confers no rights. | Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

The workstation I test from is on a completely different forest that's not connected in any way to the terminal server I'm connecting to. However, when I test this from a windows 7 machine not attached to any domain, it works just fine. There must be some GP setting I'm missing in the domain attached to my computer. I'm checking with the client to see if they're attached to a domain.

Hi! i have the same problem.... so what is the solution? Thank, Aviv Hassidim

i have change the deafult domin security policy and it works

For some reason when I connect to different domains at the same time I run across the same problems. Seems to be some issue of trust between domains. I do not use AD here, no need. I have read manuals galore on AD and I recall trust was mentioned when dealing with consolidation. Windows MVP, XP, Vista, 7. Expanding into Windows Server 2008 R2, SQL Server, SharePoint etc I feel badly for my American friends who have to endure the extremists in Washington who are bankrupting the nation over ideology. My page on Video Card Problems is now my most popular landing page. See my gaming site for game reviews etc. Developer | Windows IT | Chess | Economics | Hardcore Games | Vegan Advocate | PC R