Running Windows NT Server 4.0, Terminal Server Edition with Small Business Server 4.5
This article was previously published under Q229774 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 (http://support.microsoft.com/kb/256986/EN-US/) Description of the Microsoft Windows Registry
NOTE: Microsoft Product Support Services only supports running BackOffice Small Business Server (SBS) 4.5 or later client programs on computers running Windows NT Server 4.0, Terminal Server Edition. SBS 4.0 client programs are not supported on Windows NT Server 4.0, Terminal Server Edition. On This PageSUMMARY
This article describes the steps necessary to automate the Terminal Server installation process in a supported SBS domain environment. This article also describes steps to install and configure Microsoft Outlook 2000 Microsoft Internet Explorer 5.
It is very important to perform the following procedures exactly as written because of the unique installation process of Terminal Server programs. You should read this entire article and understand each section before you perform any of the following steps. NOTE: Before you can install any SBS 4.5 client programs on the Terminal Server computer, you must apply Windows NT Server 4.0, Terminal Server Edition, Service Pack 4. MORE INFORMATIONHow to Set Up Terminal Server in the SBS DomainBefore you install Terminal Server in the SBS domain:
Installing Terminal ServerIf you are not familiar with the installation of Terminal Server, use the following guidelines to install Terminal Server:
Installing the SBS Client ProgramsBecause SBS 4.5 client programs are not designed for multi-user operating systems like Terminal Server, you must modify some of the programs before they can run properly with Terminal Server.
Configuring Terminal Server After You Install Client ProgramsSBS User DesktopsTo configure SBS user desktops on the Terminal Server computer:
Internet Explorer 5If you chose to install Internet Explorer 4.0 during the Terminal Server installation process, you must give the Administrator and System account full control permissions to the C:\Wtsvr folder, subfolders, and files. When you upgrade from Internet Explorer 4.0 to Internet Explorer 5, these permissions are removed and you must reapply them for additional users to run Internet Explorer 5 properly.The Internet Connection Wizard icon also appears on the desktop for each new user and running the Internet Connection Wizard could lead to a mis-configured Internet Explorer program. You should delete the SetupICWDesktop key from the registry so that the Internet Connection Wizard icon does not appear for new users that log on to Terminal Server. To remove the SetupICWDesktop key:
Microsoft Fax Client 4.5The Fax client is not a Terminal Server-aware program, so you need to configure fax information and set up the fax printer for each user. By default, the administrator's information is propagated to each user who logs on.You can use a .reg file and the RunOnce registry key to set up the Fax client for each new user so they have their own settings. To do this, use the following steps:
Microsoft Proxy Client 2.0Edit the System.ini file in the C:\Wtsvr folder on the Terminal Server computer and verify that the following text is located in the [Microsoft Proxy Service] section:Microsoft Modem Sharing Client 4.5The modem on the SBS server needs to be detected and installed on the Terminal Server computer before you can enable Modem Sharing:
Installing Outlook 2000 on Terminal ServerBecause of the special requirements for running Outlook 2000 in a Terminal Server environment, you must use the transform file provided in the Microsoft Office 2000 Resource Kit to install Outlook 2000 on the Terminal Server computer. Outlook Setup does not install Outlook 2000 on the Terminal Server computer without this transform file. For information on installing Office 2000 on Terminal Server, please refer to the following Microsoft Web site:
http://www.microsoft.com/office/ork/2000/two/30t3_2.htm (http://www.microsoft.com/office/ork/2000/two/30t3_2.htm)
In most situations, you can use the following steps to customize the transform file for installing Office 2000 as well as Outlook 2000.
How to Customize the Terminal Server Transform FileTo customize the Terminal Server transform file:
How to Install Outlook 2000 on the Terminal Server ComputerTo install Outlook 2000, you must use the Add/Remove Programs tool in Control Panel with the All users begin with common application settings option selected. This setting runs Setup in Install mode, which installs Outlook for all Terminal Server client users who connect to the Terminal Server computer. If you run Setup directly from the Outlook CD-ROM, Setup runs in Execute mode, which installs Outlook only for the user running Setup.To install Outlook 2000:
Configuring Outlook 2000After you install Outlook 2000 on Terminal Server using the transforms file, you must first log on to the Terminal Server computer and then run Outlook 2000 before any other users. Outlook 2000 must complete installation tasks during this time before other users can use Outlook 2000.You can easily configure normal SBS client installations of Outlook 2000 to connect to the Microsoft Exchange Server computer running on SBS when the user logs on to the network for the first time. However, this does not occur with Terminal Server, and you must either manually configure Outlook 2000 to do so, or use the following automation process. You can automatically configure Outlook 2000 using a .prf file, which is detected and parsed the first time Outlook 2000 runs. There is an Sbs.prf file in the C:\Smallbusiness\Template folder, which is a template file used when you add Outlook 2000 to normal SBS client installations. You can modify this file and use it on Terminal Server.
Configuring Client Workstations to Connect to Terminal ServerYou must install the Terminal Server client program on all workstations that connect to the Terminal Server computer.
Adding SBS Users to the Terminal Server ComputerExisting user accounts that you added to the SBS 4.5 computer before the Terminal Server 4.0 computer was installed in the SBS domain can log on to the Terminal Server computer without any additional configuration.When you add new users to the SBS 4.5 computer using the User Account Wizard in the SBS console, skip the third part of the wizard (Setup a user's computer) by clicking Cancel after the second part of the wizard (Give access to network resources) is finished. The third part of the wizard enables you to set up a user's computer, however, because the Terminal Server computer has already been configured by the Administrator for all existing and new users, you should not select a computer for the new user being added. If the user you are adding has his or her own computer (in addition to the Terminal Server computer), you should complete the third part of the wizard and set up that user's personal computer. NOTE: Do not add users to the Terminal Server computer in the third part of the wizard. Doing so may generate a number or error messages on the Terminal Server computer. If you must complete the third part of the wizard, either choose to set up a new computer for that user, or add the user to an existing computer that is not the Terminal Server computer. Known IssuesEach time a user logs on to the Terminal Server computer, a connection is made to the SBS computer and an SBS license is used. If you disconnect instead of logging off from the Terminal Server client program, you continue to use the SBS license. Eventually, this can lead to error messages stating that there are no more licenses available and you may not be able to log on to the Terminal Server computer. These errors occur because all of the SBS licenses are used and a disconnected session on Terminal Server has not released the SBS license.To work around this problem, set a time limit on how long a user can be disconnected. You can set this limit for all user connections in the Terminal Server Connection Configuration tool (click Start, point to Administrative Tools, and then click Terminal Server Connection Configuration) or on a per-user basis in User Manager on the Terminal Server computer.
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Help and Support
Back to the top
|
