Group for specific Terminal Servers, you now have the ability to create multiple groups that you can organize based on your own preferences - an example is shown below. In the Terminal Services Manager on Windows Server 2008. The Terminal Services Manager MMC snap-in may be used to perform the following tasks on local or remote Terminal Servers:ĭisplay information about server, sessions, users and processesįeature that was present in the Terminal Services Manager on Windows Server 2003 has been enhanced and renamed to Let's take a look at some of the different tools individually - beginning with the Terminal Services Manager: You would use the Terminal Services Configuration tool instead as it allows you to configure Terminal Services settings on a per-connection basis. In this case, Group Policy would not be the ideal method. Similarly there will be cases where two or more connections are present on the same computer, and where it is preferred to configure each connection separately. For example, you may configure your Windows Server 2008 Terminal Servers through Group Policies, and use the Terminal Services Configuration tool to configure servers that are running previous versions of Windows. In mixed Windows environments, it may be necessary to use a combination of tools. Terminal Services extension to Local Users and GroupsĪdditionally, connections settings that are not configured at the group, computer or user level can be set in the Remote Desktop Client application on a per-session basis. There are several tools and methods that can be used to configure Terminal Services configuration, user settings, connections and sessions - you may already be familiar with some of them: Today we will be continuing on with Terminal Services, specifically the Management and Administration components. There's only twelve more days until Launch Day. Welcome to Day Fifteen of our series on Windows Server 2008. First published on TECHNET on Feb 15, 2008

Terminal services manager server 2012