If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.
My goal was to have a thin client connect automatically to the terminal server when it was started without intervention, but I was stopped by a persistent request for Remote Desktop credentials, even though they were set to save and I could manually type in the password to successfully connect.
Investigation online revealed several solutions for similar issues, but the actual fix was simple and not mentioned elsewhere, which is why I wrote this article.
The thin clients are running Windows 7 embedded Standard addition. The terminal server is running Windows Server 2008 SP2 (32-bit). This is in a Workgroup environment.
The pop up error looks like this:
To resolve the issue, perform the following steps on the terminal server.
The Group Policy change is pictured here:
Making this simple change allowed the thin client to auto logon using saved credentials and I was able to place the saved .RDP file in the startup folder, so a connection is automatically made as soon as the thin client powers up.
With just this one change the thin client was able to logon to the terminal server without intervention, allowing reconnect anytime there is a power disruption stopping connection to the terminal server. The same saved .RDP file was left on the thin client’s desktop in case connection was lost by some other means. This solution provides an easy and secure method for thin clients to gain access to a terminal server.