Deploy Windows Server 2003 Terminal Server to Host User Desktop
Introduction to this page Overview Plan and Deploy Terminal Server Process Planning Server and Network Resource Planning Network Connection Server and Network Resource Planning Network Connection Server and Network Resource Planning Network Connection Permission Printer Select License Mode Configuration Terminal Server Create Administrator Account Creating a Computer Account and connect to Network Install Terminal Server License Redirects "My Document" Installing the Client Application Configuring Client Computers
Introduction
You can start Terminal Server by adding an additional server to your Microsoft Windows Small Business Server 2003 network. You can use Terminal Server to host your user desktop. By extending the service life of desktop hardware, you can save money for your company.
Note: You can also achieve centralized management of applications and data with Terminal Server hosting business applications. You need to know more about the Terminal Server hosting business application, click Start, click Help and Support, and search "Program Consideration", and in addition, please refer to the Microsoft Resource Site "through Terminal Server Hosting Application.
Overview
After you install Windows SMALL Business Server 2003 and complete the "List" (To Do List), you can access the attach server to the network and configure it as a terminal server.
What is Terminal Server?
Windows Server 2003 Terminal Server Components You can send Windows desktops, including Windows-based applications, sent from central servers to any desktop computing device, even those who cannot run Windows. Terminal Services only transmits the user interface of the program to the client computer. The client computer returns to the keyboard and the mouse click, and the server is processed. Terminal Server uses the Remote Desktop Protocol, RDP to communicate between clients and servers.
The client connected to the terminal server can run Windows (including Microsoft Windows CE operating systems) or other operating systems such as Apple Macintosh or even Unix (using a third party accessory). Each user can only see their own session, which is transparent by the server's operating system and is isolated from the session of other clients.
The process of planning and deploying Terminal Server in a Windows Small Business Server environment To manage your desktop in a small business, you can take the following steps to plan and deploy Terminal Server.
Note: If you are deploying Terminal Server to host business applications, you need to make sure your application is compatible with Terminal Server. Need to know more about Terminal Server hosting business applications, click Start, click Help and Support, and search "Program Consideration". Also, please refer to the "Terminal Server Hosting Application" on the Microsoft Resource Site.
Planning server resources
2. Select the license mode. 3. Configure the Terminal Server role on the server. 4. Create an administrator account. 5. Create a computer account and connect to the network. 6. Configure Terminal Server license. 7. Redirect "My Documents". 8. Install the client application. 9. Configure the client computer. Planning Server and Network Resources To achieve optimal performance and user experience, make sure your server and network hardware have been fully upgraded and configured. The primary task of planning servers and network resources is:
1. Plan the capacity of the attached server. 2. Plan a network connection performance. 3. Plan the printer.
Planning the capacity of additional servers
Terminal Server capacity can vary depending on various factors, such as user types, servers, and network configurations, and applications you manage. In order to achieve good performance, a terminal server requires at least 128 MB of memory, and adds additional memory to the server based on the user type to run the user's application.
Multiprocessor configurations maximizes CPU availability. In general, the demand for processors and memory is proportional. In the Pentium system of the multiprocessor, double the number of users can be supported by double the number of processors and memory. Therefore, it is best to purchase a system that supports multiple processors, even if you first purchase a processor, you can easily expand capacity according to the demand growth.
Determine the capacity required for your server as follows.
User needs: The RAM and CPUs required by Terminal Server users are based on the features of the application they use, and the frequency of use, and the workload completed within the unit time. Application Consider: Carefully check the system requirements for each application you intend to install to the server, and consider the growth of RAM and CPUs based on the number of users sessions that may be run simultaneously. Since the terminal server shares an executable resource between the individual users, the memory requirements of additional users running the same program are usually lower than the first user of the loaded application. TERMINAL Server license consideration: A disk space for approximately 1 MB is required to install Terminal Services Licensing (Terminal Service License). After the deployment is complete, the server load is monitored to ensure your server has sufficient capacity.
Planning Network Connection Performance Terminal Server is running very well on a narrow bandwidth connection and can use any IP connections you provide. However, by determining that the connection type is suitable for completed, you can optimize the performance of the application and the entire network. For example, a single user can connect on a narrow bandwidth modem line and achieve good performance, but this is not suitable to share 28.8 kb from a large office with 100 people.
Note: Printing, audio, redirecting drives, and user file transfer, are increased bandwidth requirements and may result in decline in performance to the user's consideration.
Planning the printer When the user logs in to the terminal server, the server detects the client's local printer and installs the appropriate printer driver on the remote computer. If there are multiple printers to connect to client computers, Terminal Services defaults to all print jobs to the default printer of the client computer. Only the printers available on Windows client computers are displayed in remote desktop sessions for redirected local printers (server-side printers are also available). If your printer driver is not included in the client operating system, you must be installed manually on the server.
Select License Mode To use Terminal Server in your organization, you need to get a Windows Server 2003 license for each terminal server deployed in your organization, and get the Terminal Server Customer Access License for those accessing the terminal server (CAL ). For terminal servers running Windows Server 2003, there are two Terminal Server Cal: Per De (each device) Per User Select which CAL set according to your Planning Terminal Server. By default, Terminal Server configures in Per Device mode, but you can also switch to each user Per User mode using the Terminal Services Configuration Tool (TSCC.MSC). You can support these two license types from the same license server. Need to know more about how to set up a license mode, see "Visit the Terminal Server Manager" on the Microsoft Resource Site.
Terminal Services CAL can manage Terminal Services Cal on your web. Permissions Server Stores all Terminal Server Cal tokens that have been installed to the terminal server and tracks the token that has been distributed to the client. Need to know more about Terminal Server licenses, click Start, click Help and Support, and then search the Terminal Server License Overview.
Note: The user must obtain the correct license from each service or application accessed from the terminal server. Typically, each device requires an application license and CAL associated with it, even if the application or device is indirectly accessed through the terminal server. For more information, see Product Documents, End User License Agreement, EULA or other documents that specify product use permissions.
Per Device Licensing Mode Per Device CAL Grants permissions per client computer access to the permission of the terminal server that is running Windows Server 2003. Per Device Cal is saved locally and submits to the terminal server each time the client computer is connected to the server.
The following is suitable for using Per Device license mode:
Manage the home desktop for all or controlled equipment. Connect to the terminal server or computer in most of the working day. This license is not a good choice if you don't control the device's device. For example, a computer in an internet cafe, or a business partner connected to your terminal server from an external network.
Per User License Mode In Per User Licensing Mode, you must grant each user to a license. With the Per User license, the user can access the terminal server from an unlimited device, and only one CAL is required, without having to acquire a CAL each device.
The following is suitable for using the Per User certification mode:
Provide access to roaming users. Access services are provided for those users who do not only use a computer (such as portable computer and desktop computers). Provide simple management capabilities for organizations access to the network to the user (rather than). In general, if your organization has more computers than the number of users, then Per User license may be a way to use cost to deploy Terminal Server, because you only need to pay for users who visit Terminal Server, without having to pass by users Visit each device for Terminal Server payment. See EULA for applications you intend to manage to determine whether they support Per User license. Configuring the Terminal Server role After adding an additional server, configure the server through the Terminal Server. To learn about adding additional servers, click Start, click Help and Support, and search for "Add Additional Server"
Important: Because Terminal Services supports multiple users, you highly recommend that you use the Windows Server 2003 version of the NTFS file system as the unique file system of the server, without the file allocation table, fat. FAT cannot provide user or directory security, however you can limit subdirectory for a specific user or user group via NTFS. This is important for the Terminal Services and other user systems. No NTFS provides security, any user has access to each directory and file of the terminal server. To learn more about the file system, please refer to the Design and Deployment File Server on the Microsoft Resource Site.
Install Terminal Server
1. Use the local administrator account to log in to the additional server. 2. Click Start, click Manage Your Server, and double-click Add or Remove Role, "Configure your Server Wizard" will start. 3. On the Server Role page, select the Terminal Server check box, then click Next. 4. On the Select Summary page, click Next to start configuring. After the configuration is complete, the computer will restart.
Create an administrator account Next, create a domain administrator account to manage your attach server.
Important: Use "Add User Wizard" to create a domain administrator account to manage your attach server. If you have created a domain administrator account using Add User Wizard, you can skip this step.
Create an administrator account for additional servers
1. Log in to the computer running Windows Small Business Server 2003 using the local administrator account. 2. Click Start, click Server Management. 3. Click User in the console tree. 4. In the Details pane, click Add User. 5. "Add User Wizard" started.
Click Administrator Template in the Template dialog box in the Template Selection page. On the Install Client Computer Page, click Do not install your computer. On the "Complete Add User Wizard" page, click Finish.
Create a computer account and connect to the next step, create an account for your attach server on the Windows Small Business Server network, and then connect the server to the network.
Create a computer account
1. Log in to the computer running Windows Small Business Server 2003 using the local administrator account. 2. Click Start, click Server Management. 3. In the console tree, click Server Computer. 4. In the Details pane, click Install Server Computers, and Install Server Wizard will start. 5. Create a server computer according to the instructions of the wizard.
Connect the terminal server to the network 1. On the newly created server, log in with the local administrator account. 2. In Internet Explorer, log in to http:// servername / connectionComputer, and then click "Connect to the Network".
Note: Internet Explorer is not limited by the Terminal Server by default. However, if you cannot log in to this site via Internet Explorer, you can click Internet Options on the Tools menu. On the Security tab, click "Trusted Site" and click Site. Add HTTP: // Server Name / ConnectComputer in the "trusted site" dialog box to the trusted site list. Make sure to "Require Server Verification (https :)" check box for all sites in this area.
3. Connect the computer to the network according to the instructions of the wizard. Use the administrator username and password you created when you run Add User Wizard.
Installing the Terminal Server License After adding the additional server to the network, configure the server through the Terminal Server. To learn more about adding additional servers, click "Start", click Help and Support, and then search "Terminal Server License".
Configure Terminal Server license
1. Click Start, click Control Panel, and then click Add or Remove Programs. 2. Click Add / Remove Windows Components. 3. In the Components dialog box, click Terminal Server License, click Next. 4. On the Terminal Server License Installation page, click Next to accept the default value of this page. 5. Provide a license server database to install the file system location on the Terminal Server permission server, click Next, click Finish. The default location of the license server database is SystemRoot / System32 / LServer.
Active License Server The Terminal Server license server is activated, it becomes a repository for the Terminal Server client license. The Terminal Server license server can divide a temporary license for the client, allowing its access to the terminal server within 120 days of the first login. After this evaluation period, the terminal server does not allow the client to connect unless it is positioned to distribute a Terminal Server license server to distribute client licenses. The license wizard attribute set during the activation process, such as activation method and company information, can be changed at any time.
Activate permission server
1. Click Start, click Control Panel, click Administrative Tool, and then click Terminal Server License. 2. In the console tree, right-click the Terminal Server license server you want to activate, and then click "Activate Server" to launch the Terminal Server License Server Activation Wizard. 3. In "Activation Method", select "Auto Connect" (Recommended), click Next, follow the instructions of the wizard.
Add a Client License to a Permissory Server To enable users to use the terminal server, you must purchase a client access license for each client connected to the Terminal Server and install it on the license server. To learn more about Terminal Server licenses, click Start, click Help and Support, and then search "Terminal Server License".
Note: Terminal Server license is set to Per Device mode by default. To change it to Per User mode, click Start, click Administrative Tool, and then click Terminal Services Configuration. In the console tree, click Server Settings to double-click "License" in the Detail Pane. In the drop-down list box of the License Mode dialog box, click Per User, and then click OK. Install customer license key package
1. On the Terminal Server, click Start, click Control Panel, click Administrative Tool, and then click Terminal Server License. 2. To verify that the installation method of the Terminal Server license server is set to "Auto", you can click "Properties" by right-click the TERMINAL Server license server that you want to install the key package. Multiple installation methods are changed as needed on the Installation Method tab. 3. In the console tree, right-click the Terminal Server permission server you want to install the key package, click Install License to launch the Terminal Server CAL Installation Wizard, and then click Next. .
If the Terminal Server Cal Installation Wizard has been started, there is no need to perform the above steps. 4. In Program and Customer License Information, provide the information you need to accept your license, and then click Next.
Microsoft Clearinghouse handles your request and installs an encrypted customer license key package on your Terminal Server license server. 5. Click Finish to complete the action.
The Terminal Server license server can now issue licenses for clients connected to the terminal server.
Redirect "My Document" recommends that you reordbound the user's "My Document" folder to the server running Windows Small Business Server 2003 and applies volume quotes for these folders. By default, the user's "My Document" is saved on the terminal server with user personal information. If you use My Document Redirects and SMALL Business Server 2003, your user data will back up with the other data of the server. To learn about the information about the user's "My Document" folder, realligating the Windows Small Business Server 2003, click Start, click Help and Support, then Search "Folder Heavy Direction ".
Note: Redirect "My Documents" to all users applied in the domain.
Installing the Client Application You can use the client application on the client running Windows Small Business Server 2003 and install it on the terminal server. You can also install other client applications on the Terminal Server. To learn more about installing and running applications through Terminal Server, click Start, click Help and Support, and search for Terminal Server.
Installing Outlook You can install Microsoft Office Outlook 2003 from the server running Small Business Server 2003.
Note: Make sure that Applauncher.exe has completed running before starting the step. To see the status of Applauncher.exe, press Ctrl Alt Delete, and then click Task Manager. Make sure Applauncher.exe does not appear in the Process tab.
1. On the additional server, log in with the domain administrator account. 2. Click Start, click Run, type // ServerName (Server Name). 3. Double-click "ClientApps" and double-click "Outlook2003". 4. Double-click "Setup.exe" and follow the instructions of the installer. 5. To close the Outlook installer after the installation is complete, and click Next, click Finish. Make sure you turn off the wizard that is started with the installer. Note: You don't need to configure Outlook for each Terminal Server user. When the user logs in for the first time, the client installer automatically configures Outlook.
Terminal Server users cannot use cached Exchange MODE.
Install Internet Explorer You do not need to install Internet Explorer on the Terminal Server, and Windows Server 2003 contains the correct Internet Explorer version. Favorites menu and connection settings are configured by the client installer. Some of the items pointed to the Favorites menu need to install the Microsoft ActiveX control or certificate. The Internet Explorer can be configured for these links based on the following steps.
Configuring a fax for Terminal Server You can configure the server running Windows Small Business Server 2003 as a fax server by installing a fax service on a server running Windows Small Business Server 2003. To learn more about the fax service over the additional server, click Start, click Help and Support, and search for "Use Fax".
To configure fax services for Terminal Server users, you need to configure the terminal server and each client that needs to use the service. Configure the Terminal Server by the following steps to use the fax function. When configuring a client computer to use Terminal Server, you also need to configure a client using a fax.
To configure fax function on the terminal server
1. On the Terminal Server, click Start, click Control Panel, click Add or Remove Programs. 2. Click Add / Remove Windows Components. 3. Select the Fax Services check box and click Next. 4. Click "Do not share this printer", then click Next.
Note: You may be prompted to insert the Windows Server 2003 operating system installation disc. 5. Click Finish.
Configuring a client computer To configure a client computer to access the terminal server, you must install a remote desktop connection on each client computer. Once you have installed the remote desktop connection, you can configure the fax service to the client computer.
Install a remote desktop connection on the client computer
Note: When you install Windows Server 2003, Windows XP, and most Windows CE versions, the Remote Desktop Connection Tool has been installed by default. In the earlier versions of Windows and Pocket PC, you must manually install the remote desktop.
1. Click Start on the client computer, click Run, then type
// ServerName / ClientApps 2. Click "Tsclient". 3. Double-click the Win32 folder and double-click "setup.exe". 4. Complete the Remote Desktop Connection - Installsheild Wizard.
Configure client computers to use fax services
Note: When the user logs in to the terminal server, the server then detects the local printer of the client and install the correct printer driver on the remote computer. 1. On each client, click Start, "Programs", "Accessories", "Communication", and Remote Desktop Connection, and then log in to the terminal server with the remote desktop. 2. Click Start, click Printer and Fax, then double-click Add Printer, and Add Printer Wizard. 3. Click Next. 4. Click Network Printer, or connect to another computer, and then click Next. 5. Click "Find printers in the directory" and click Next. 6. In the Find Printers dialog box, click "Find now".
In the list of search results, a printer named "fax" will appear. Select this printer named "fax" and click OK.
Note: You may prompt you to enter the client operating system media. 7. When you ask if you want to set the printer to the default printer, click No, then click Finish.
