Most of the Terminal Services Group Policies are found under the Computer Configuration. Whilst some settings are also available under User Configuration, my first piece of advice is just use the Computer Configuration Group Polices for Terminal Services. My reasoning is keep it simple, and keep all the settings in one place.
Next time you log in, the policy will not be able to overwrite the image or set it as wallpaper and hence it will default to a solid colour background. In my case I am still not able to choose a new image for the background because group policy disabled that option; I am however able to choose the Windows 7 default theme which set the background to default black.
Set Default Wallpaper on Terminal Server - Experts-Exchange Experts Exchange > Questions > Set Default Wallpaper on Terminal Server ...
Terminal Server Remote Desktop Connection Registry Settings (Compact 7) You can configure Remote Desktop Connection by using the Remote Desktop Connection registry settings.
Log in to RDS Server >>> Run >>> control system >>> Remote Settings >>> Remote tab >>> Select users >>> Delete any groups/users >>> Add security group for RDS users
I am in a situation where my wallpaper is locked to a specific image on my work computer via group policy. I can't change it via the Personalization settings since it is grayed out and says it has been set by the system administrator.
Users can still change the desktop background color in Windows Server 2012. Note that you need to have Desktop Experience installed. You also have to allow users to change their colors and desktop background in Group Policy.
On a Windows Server 2012 Remote Desktop Session Host with the Desktop Experience feature enabled and the desktop wallpaper disabled, users wish to configure own color schemes and define an own desktop background color. However, I seem unable to find an easy way to change the desktop color via the GUI.
However, this doesn't complete the picture. As you can see, when I set a solid background color, the taskbar changed but my window borders didn't change. I suspect this is a bug.
If you intend to be serious about Microsoft's Terminal Services then invest time to configure Group Policies. In fact, choosing your Terminal Server settings will be both fun and a labour of love. Perhaps you already use Windows Server 2003's Group Policy to control the XP experience? If so, then configuring the remote desktop will follow on naturally.
Many of these Group Policies can also be controlled via the , a classic case of Microsoft providing two (three) ways of doing everything. So, my suggestion is to have both the GPMC and the Terminal Services Configuration menus available.
I only wanted a black background in my case so I did not try to tinker around with the various read/write/modify permissions on the image itself. However, theoretically, you may be able to make your own image, name it the same as the default group policy background image, replace the default image with the new, change permissions on all groups, users to read only. This way the policy should fail to overwrite the image but succeed to set it as the default background. I have not tried this last bit.
About half of the Group Policies are only needed for special situations, such as Microsoft clustering or running Remote Desktop from PDAs. I have indicated where settings would not be needed if you have a standard configuration of Terminal Services. However, I have selected 5 Group Policies which you should consider for any Windows Server 2003 configuration.
You have access to the Windows 2003 Server, and you have opened the GPMC (Group Policy Management Console). From there you edit the Group Policy. See screen shot above showing Terminal Services Group Policy.