Control user experience through GPO in Terminal Services.

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 also help prevent non business devices from consuming precious bandwidth.

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog