Terminal services manager tool windows server 2008




















In the case of Per Device mode, this allows a specified number of devices to connect to the service at any one time regardless of who the users are. On the other hand, Per user restricts access to specified uses, regardless of the device from which they are connecting. Finally, the users and groups allowed to access the terminal server need to be specified, although users may be added and removed at any time by changing the members of the Remote Desktop Users Group.

Click on Add Clicking Next proceeds to the Confirmation screen. Read carefully any warnings that are displayed. Typically the wizard will recommend any currently installed applications should be re-installed before remote access is provided to users steps to achieve this are outlined below. Click Install to begin the installation process. Partway through the installation it will be necessary to restart the Windows Server system. Once rebooted, be sure to log in as the same administrative user to complete the Terminal Services configuration process.

The default configuration for Remote Desktop Users Group is to allow all members of the Administration group to connect remotely. Active Directory also contains a Remote Desktop Users group to which users may be added to provide Remote Desktop access privileges. Note that users with administrative privileges do not need to be added to this list, by default they already have Remote Desktop access.

To add additional users click on the Add Enter the name of the user in the text box entitled Enter object names to select and click on Check names to list names that match the name entered. Select the appropriate name from the list. The following example shows user Bill on server winserver-2 :. Click on OK to apply the change. The new user will now appear in the list of users with Remote Desktop access on the Remote Users screen.

The specified user will now have remote Terminal Services access to the system. With Terminal Services installed and configured on the server, the next step is to ensure the services can be accessed from a remote client. Terminal services provides both remote desktop and remote application access. Under remote desktop access an entire desktop session running on the server is displayed on the client.

The user then interacts with the desktop to launch and interact with applications details on installing applications for use with Terminal Services is covered in the chapter entitled Installing Applications for Windows Server Terminal Services.

In the case of remote applications, the remote application running on the server appears in its own window on the client desktop, to all intends and purposes looking like a local application to the user. With the appropriate configuration tasks completed on the remote system the next step is to launch the Remote Desktop Client on the local system. In case you need this to be placed on some other location, select the Browse option and choose a folder.

Review the option that you selected, read about the information and warning messages on the Confirm Installation Selections window and click install.

After installation is done a warning will pop up to reboot the system to finish the installation. While the installation is done but the TS licensing configuration is not yet done which we will do now. On the next page a drop down menu option will appear. Choose Automatic Connection recommended and Click Next. Provide the company information details information such as First name, Last name, Company, region on next configuration page and click next.

On next License program window select the type of License program. For this tutorial we will choose other agreement. PS: For Corporate Environment, choose the appropriate license program to proceed for further steps. In addition to managing Terminal Servers, users, processes, and sessions, you can also connect to a specific session on the target Terminal Server. For example, suppose you've performed a few management tasks on a server, but now you need to leave an application running while you work on something else on a different server.

You disconnect the session, which leaves the applications running. Later, you decide to check the status of the applications, so you connect to that session again. In a way, this capability is like Fast User Switching in Windows XP, which enables you to log on with a different account without logging off from the current account.

You can switch between sessions on any available Terminal Server. Terminal Services Manager also gives you the capability to remotely control another user's session, which makes it possible to monitor the user or provide assistance with software or other issues. The Terminal Services Manager provides several other capabilities, as well. There are also several command-line tools that can be used to perform administrative functions. The table below lists the various command-line tools:. When shutting down or restarting a Windows Server Terminal Server, any logged-on users will see a dialog indicating that a shutdown is in process and that they will be logged off from their Terminal Server session.



0コメント

  • 1000 / 1000