Can you force and RDP sessions Experience Level?

Remote Desktop has allowed network administrators to remotely manage servers for years. While studying Remote Desktop settings this past week, we were looking at the possible experience settings below.

From these settings, you can control how much visual data is set from the target server to your remote session on your computer. The question was is there a way to set the experience level on the target server and override what the user wants? Using group policy, you can. Take a look at the settings below that can be found at Computer Configuration \ Policies \ Administrative Templates \ Windows Components \ Remote Desktop Services \ Remote Desktop Session Host \ Remote Session Environment

To demo the target override, I set the GPO to Enforce Removal of Remote Desktop Wallpaper. Here is a very annoying desktop background that I put on my server while logged in locally.

Below is the same view while logged in using RDP.

My RDP settings were set to Allow Desktop, but the GPO enforced on the target was set to Enforce Removal of Remote Desktop Wallpaper.

Comments

Anonymous said…

Hi, I am actually looking into the other direction. All RDP clients have by default the background not shown. But I want to enforce the Background to display regardless of what the RDP client has set. I don't find a way to do this centrally. Is there any way?

October 29, 2013 at 1:29 PM

Jason Yoder, MCT said…

This is a good one. I just spent an hour with the 2012 GPO data and could not find an avenue for success. I'm working on finding a method using GPO Preferences to try and set a registry value to have this flag set by default. Still working on it.

October 29, 2013 at 3:14 PM

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

This was an interesting observation from one of my Windows Server 2012 classes. While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted. When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places. First off in the Active Directory Administrative Center. This is what caused the initial confusion. Take a look. This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3. Test3 is a valid, functioning user account. Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...

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