Puertos terminal server windows 2008




















On the Terminal Server computer, open the Server Manager. In the Server Manager , click on the Roles node in the left pane of the console. Click the Add Roles link in the right pane of the console. We can select this option in our current scenario because we are using only Vista SP1 clients to connect to the Terminal Server through the TS Gateway. However, I have not yet confirmed this, so make sure to check the release notes on Windows XP SP3 when it is released later this year.

On the Specify Licensing Mode page, select the Configure later option. We could select an option now, but I decided that we should select Configure later so that I can show you where in the Terminal Services console you configure the licensing mode.

You can add or remove groups if you want finer tuned access control over the Terminal Server. However, if all of your users will be going through the Terminal Services Gateway, then you can control who can connect to the Terminal Server using the TS Gateway policy settings. Leave the default settings as they are and click Next. We select this option in this scenario because we only have a single domain.

If you have a multi-domain forest, you might consider selecting the The forest option. On the Confirm Installation Selections page, check the warning information indicating that you might have to reinstall applications that were already installed on this machine if you want them to work properly in a Terminal Services session environment. Click Install. On the Installation Results page, you will see a warning that you must restart the server to complete the installation.

Click Close. Click Yes in the Add Roles Wizard dialog box that asks if you want to restart the server. Log on as Administrator.

The installation will continue for a few minutes as the Installation Progress page appears after the Server Manager comes up. Click Close on the Installation Results page after you see the Installation succeeded message.

You may see a balloon telling you that Terminal Services licensing mode is not configured. You can dismiss that warning, as we will next configure Terminal Services Licensing and then configure the licensing mode on the Terminal Server. In the TS Licensing Manager console, right click the server name in the left pane of the console.

Most applications written for bit will continue to work as normal in WoW mode. Any new applications written for Windows 7 Remote Desktop Services should be developed and tested for deployment on bit platforms.

Remote Desktop IP Virtualization allows the user to assign IP addresses to remote desktop connections on a per-session or per-program basis:. Some programs require a unique IP address for each instance of the application. Prior to Windows Server R2, every session on a remote desktop server shared the same IP address, resulting in compatibility issues for these applications.

In Windows Server R2, you can install a program on the Remote Desktop Server just as you would install the program on a local desktop.

Ensure, however, that you install the program for all users and install all components of the program locally on the Remote Desktop Server. For applications that required per-user configurations, such as Microsoft Office Word, an administrator needed to pre-install the application, and application developers needed to test these applications on both the remote desktop client and the Remote Desktop Session Host. Remote Procedure Call.

Installation Bootstrap Service. Installation Bootstrap protocol server. Installation Bootstrap protocol client. Microsoft Operations Manager Microsoft SQL Server.

SQL Probe. Internet Authentication Service. Routing and Remote Access. Message Queuing. OLAP Services 7. MS Theater. DHCP Server. SMS Remote Control control. SMS Remote Control data. SMS Remote Chat. SQL Analysis Services. SQL Analysis Server. Universal Plug and Play Device Host.

SSDP event notification. Global Catalog Server. Cluster Services. Cluster Service. Terminal Services. NetMeeting Remote Desktop Sharing. Cola de mensajes. SSDP legacy event notification.

Distributed File System Replication. Information Store. Directory Referral. Net Session State.



0コメント

  • 1000 / 1000