Skip to main content

Can you force and RDP sessions Experience Level?

By

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.

image

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

image

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.

image

Below is the same view while logged in using RDP.

image

 

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

Labels:

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
Post a Comment

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

By
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.
Post a Comment
Read more

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
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...
18 comments
Read more