Jason Yoder, MCT

While attempting to connect to a RemoteApp with a standard user account, you may receive this message:   This can be caused by not having the logged on user as a member of the Remote Desktop Users group on the Remote Desktop Server.  Another reason why you may experience this issue is if you are still on the 180 grace period for RDS licensing.  To clear up this problem, reboot the RDS server.   if this still does not work while you are in the grace period add the users, or preferably a group, to the allowed list of users who can log into the RDS server. On the RDS server, Click Start . Right click Computer and select Properties Click Remote Settings   Click Select Users   Click Add . Add in the User or groups that you want to be able to log in through Remote Desktop Services to this server. You should be able to access your RemoteApp now.

Windows Thin Client allows you to take legacy hardware and continue to utilize it using modern operating systems.  This is done through the usage of Remote Desktop Services in Windows Server 2008 R2. When booting the ISO file for Windows Thin Client, you will get the usual imagery. Select the language of your choice and click Next   Click Install Now   Check I accept the license terms and click Next   Select the drive that you want to install Windows Thin Client on. If this is an unformatted drive, click Drive options (advanced) .   Click New   Determine how much of the hard drive that you want to format and click Apply .   Click OK at the message below.   Click Next   The installation will now run. Provide a name for the first account on this system and a name for this PC.  Remember, this is a local administrator for this client.   Provide and confirm a password for this account. ...

In class, I performed a quick demonstration using Remote Desktop Services in Windows Server 2008 R2. I set up a Remote Desktop Server and applied a Group Policy that restricted the users that logged into this Remote Desktop Server to a single session. The policy was located at: Computer Configuration / Policies / Administrative Templates / Windows Components / Remote Desktop Services / Remote Desktop Sessions / Connections / Restrict Remote Desktop Services users to a single Remote Desktop Services Session Once this policy was enabled, users were restricted. To test what happens when they connect on two different clients, I use the Remote Desktop Connection on two separate Windows 7 clients. On the first connection, I created a folder on the desktop so we can confirm that a single session was being used. I connected on the second client, and we saw the desktop with the folder. I then went back to the first client and we were notified that the Remote Desktop Session was ...

Remember from class that there are scenarios when the Remote Desktop Gateway server needs to be a member of the Active Directory environment: · If you configure a TS Gateway authorization policy that requires that users be domain members to connect to the TS Gateway server. · If you configure a TS Gateway authorization policy that requires that client computers be domain members to connect to the TS Gateway server. · If you are deploying a load-balanced TS Gateway server farm. The article below gives detailed information on what DMZ sceneries will work with Active Directory and Remote Desktop Gateway. http://blogs.msdn.com/rds/archive/2009/07/31/rd-gateway-deployment-in-a-perimeter-network-firewall-rules.aspx

You can utilize the TSCON command to connect to a active or disconnected session. Reference: http://support.microsoft.com/kb/321703 I did find a warning about consoles being unlocked from this command so you may also want to look at this article: http://support.microsoft.com/kb/302801 I did notice that in testing, this transfers the connection to your console and ends the connection with the client that the user in logged in on.

The users experience in Remote Desktop is going to be controlled by one of three ways. 1) You can configure the options on the Remote Desktop Connection on each workstation. That is not ideal in any environment beyond one or two clients. You can control 2) You can open Terminal Services Configuration . Right click RDP and select Properties . Then under the Client Settings tab, you can control the color depth and device redirection for that Terminal Server. 3) You can utilize GPOs at Computer Configuration à Policies à Administrative Templates à Windows Components à Terminal Services à Terminal Server Remember to test your users experience across the slowest network connection that will be used. Latency will drive up cost due to lost productivity, not to mention your users tempers. Easy ways to decrease latency is to limit the maximum color depth. Many application will work well in 8 or 15 bit color. Restricting device redirection may a...

In lab 1, Exercise 1, Task 4, we were asked to set a GPO policy to Allow Delegating Default Credentials . We set this delegation to NYC-TS-01 which was our terminal server. The reason that we did this was to support the SSO (Single Sign On) capability in Windows Vista and Windows 7. You may notice that when credentials are required, the client goes into the secure desktop mode. Not even the client software knows what you have typed. This is a security enhancement for you Windows Vista, Win7 and Win2008 environments. Reference: http://technet.microsoft.com/en-us/library/cc749211(WS.10).aspx

Testing shows that the Session ID is and RDP Session and not console when launching a remote session with the command MSTSC /admin. The purpose behind this is to allow you to connect to a terminal server without consuming a TS CAL. Reference: http://windowsitpro.com/article/articleid/97716/what-is-the-admin-switch-in-microsoft-terminal-services-client-mstsc-for-windows-2008-and-vista.html