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.
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.
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.
2 – Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections > enable the policy “Allow Users to connect remotely using Remote Desktop Services” Note: this used to be > Windows Components > Terminal Services > “Allow users to connect remotely using Terminal Services”
Most of the Terminal Services Group Policy settings are found under the Computer Configuration. Whilst some settings are also available under User Configuration, my 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.
Many of these GPOs can also be controlled via the Terminal Services Configuration Snap-in, a classic case of Microsoft providing three ways of configuring.