Microsoft KB Archive/256931

= Running Windows 2000 Terminal Server with Small Business Server 4.5 =

Article ID: 256931

Article Last Modified on 4/17/2006

-

APPLIES TO


 * Microsoft BackOffice Small Business Server 4.5

-



This article was previously published under Q256931



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 Description of the Microsoft Windows Registry



SUMMARY
This article describes how to automate the Windows 2000 Terminal Server installation process in a supported Small Business Server (SBS) version 4.5 domain environment. This article also provides steps to install and configure Microsoft Outlook 2000 on the Terminal Server.

IMPORTANT: It is very important to perform the following procedures exactly as they are provided because of the unique installation process for Terminal Server programs. You should read this entire article and understand each section before you perform any of the following steps.



MORE INFORMATION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Before You Install Terminal Server in the SBS Domain
 Add the computer account to the SBS domain. View More Tasks in the SBS console, click Manage Computers, and then click Set Up A Computer to start the wizard. Choose administrator as the user that installs the SBS client programs, and then click Next.

NOTE: You must have administrative rights to install programs on the Terminal Server computer. Type a name for the Terminal Server computer, and then click Next. For example, if your SBS computer name is SBSCOMP, you could name it SBSCOMPTS. Choose Microsoft Windows NT 4.0 Workstation as the operating system. In the Application window, click only Microsoft Proxy Client 2.0.

NOTE: You cannot install Outlook 2000 or Microsoft Office 2000 until you configure them to run on the Terminal Server computer. Configuration and installation information for Outlook 2000 on Terminal Server is provided later in this article. SBS Fax and modem sharing on Windows 2000 require software updates available for download from the Small Business Server web site. For more information, please see the following Microsoft Web site:

http://www.microsoft.com/smallbusinessserver/productinfo/2000/Interop.htm

 When you are prompted to create the client Setup disk, insert a blank disk into the floppy disk drive, and then click Next.

NOTE: Although you do not use the disk to set up Terminal Server, you must let the wizard create the disk. If you quit the wizard, all previous selections are discarded.</li></ol>

Preparing the Windows 2000 Terminal Server
Use the following guidelines to install the Terminal Server:
 * Install Windows 2000 (with Terminal Services selected) as a stand-alone (member) server by using per-seat licensing.
 * When you configure networking, type a static TCP/IP address of 10.0.0.3, and a subnet mask of 255.255.255.0 . No gateway address is needed. If another server in the network is currently using 10.0.0.3, use the next available TCP/IP address in the range of 10.0.03 to 10.0.0.10. The primary and secondary Windows Internet Naming Service (WINS) server addresses should be set to 10.0.0.2. The previous instruction assumes that you are using the default IP scheme (10.0.0.x) for SBS. If you are not using the 10.0.0.x range on your network, set the TCP/IP information accordingly.
 * Do not join the SBS domain until the following steps have been completed.

Installing the SBS Client Programs
Because 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. Again, this must be done before you join the SBS domain. <ol> Create a folder in the root folder of the Terminal Server computer and name it SBSFILES. You will use this folder later to store some of the files that are needed to configure programs to run on Terminal Server.</li> Find the logon script at the following location, and then open it in a text editor such as Notepad:

C:\Winnt.sbs\System32\Repl\Imports\Scripts\SmallBusiness\Administrator.bat

</li> Locate the following entries in the logon script:

IF "%Directory%" == "" goto exit

\\ \Clients\Setup\%directory%\Startcli.exe

/s: /u:Administrator /l:%>windir%\..\Startcli.log

</li> Copy the following text:

Pause

Change user /install

Change user /query

Pause</li> Paste the text you copied into the logon script between the 2 sections that are noted above. For example:

IF "%Directory%" == "" goto exit

Pause

Change user /install

Change user /query

Pause

\\ \Clients\Setup\%directory%\Startcli.exe

/s: /u:Administrator /l:%>windir%\..\Startcli.log

NOTE: By adding this text to the logon script, it enables the Installation mode of Terminal Server. You must add this text because the SBS client program installation is run in the last part of the logon script and you cannot change modes on Terminal Server during the client program installation process.

If you do not add this text to the administrator logon script, the SBS client program is installed incorrectly and will not run for any users except the administrator. It is very important that the Terminal Server be in Installation mode before the programs are installed. Keep this text in the Administrator logon script until all SBS client programs are installed and are working correctly.</li> The logon script pauses and displays which mode Terminal Server is in. You must press ENTER to continue to run the logon script. If the Terminal Server computer does not switch to Installation mode when the logon script is running, type the following command at a command prompt:

change user /install

NOTE: If the Terminal Server is not in Installation mode, you must perform this procedure before you can continue to run the logon script.</li> At this point, the Windows 2000 Server is ready to join the SBS domain: <ol style="list-style-type: lower-alpha;"> Right-click My Computer, and then click Properties.</li> Click the Network Identification tab.</li> Change "Member of" to Domain: and then type the name of the SBS domain.</li> Click OK.</li> You should receive a message that indicates you have successfully joined the domain. This requires restarting your computer.</li></ol> </li> Log on as administrator in the SBS domain, and the administrator's logon script runs on the SBS server and begins installing the SBS client. The server then restarts.</li> Log on as administrator again. When you receive the SBS Client Setup dialog box, click Next to continue.</li> The Microsoft Proxy Client 2.0 is installed. When Setup finishes, you must restart the Terminal Server computer to finalize the client program Setup configuration.</li> At this point, you should install Outlook 2000 and/or Office 2000. You must manually install these programs because they require special configuration to run with Terminal Server. For more information about how to install Outlook 2000 or Office 2000 on Terminal Server, refer to the "Installing Outlook 2000 on Terminal Server" section later in this article.</li></ol>

To Configure SBS User Desktops on the Terminal Server Computer
<ol> <li>Copy the Startcli.exe file from the C:\SmallBusiness\Clients\Setup\I386 folder to the C:\Sbsfiles folder on the Terminal Server computer.</li> <li>Create a new batch file named Foldersetup.bat.</li> <li>Copy the following text, and then paste it into the batch file:

c:\sbsfiles\startclie.exe /s:%logonserver% /u:%username%</li> <li>Move the Foldersetup.bat file into the C:\Sbsfiles folder on the Terminal Server computer, and then paste a copy of the file in the C:\Smallbusiness folder on the SBS computer as a backup copy.</li> <li>Start Registry Editor (Regedt32.exe) on the Terminal Server.</li> <li>Locate the following registry key:

<pre class="fixed_text">HKEY_LOCAL_MACHINE \Software \Microsoft \WindowsNT \CurrentVersion \Terminalserver \Install \Software \Microsoft \Windows \CurrentVersion

</li> <li>On the Edit menu, click Add Key, and then add the following value:

Value name: Runonce</li> <li>Click the new key.</li> <li>On the Edit menu, click Add Value, and then add the following value:

Value name: foldersetup

Data type: REG_SZ

Value: c:\sbsfiles\foldersetup.bat</li></ol>

The Internet Connection Wizard icon appears on the desktop for each new user and running the Internet Connection Wizard could lead to an incorrectly 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: <ol> <li>Start Registry Editor (Regedt32.exe), and then locate the following registry key:

<pre class="fixed_text">HKEY_LOCAL_MACHINE \Software \Microsoft \WindowsNT \CurrentVersion \Terminalserver \Install \Software \Microsoft

</li> <li>Click the Internet Connection Wizard key.</li> <li>On the Edit menu, click Delete.</li> <li>Quit Registry Editor.</li></ol>

Microsoft Proxy Client 2.0
Edit the System.ini file in the C:\Winnt folder on the Terminal Server computer and verify that the following text is located in the [Microsoft Proxy Service] section:

[Microsoft Proxy Service]

Ini File Path=C:\mspclnt\mspclnt.ini

StfPath=C:\mspclnt\setup.stf

Configuration Location=c:\mspclnt

Security32=security.dll

NOTE: If the [Microsoft Proxy Service] section does not exist, you must add the above information for the Winsock Proxy (WSP) Client tool in Control Panel to function correctly.

Installing Outlook 2000 on Terminal Server
Because 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 about installing Office 2000 on Terminal Server, please view the following Microsoft Web site:

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 or Outlook 2000.

How to Customize the Terminal Server Transform File

 * 1) Install the Microsoft Office 2000 Resource Kit on the Terminal Server computer. This action installs the motionless Stillogo Office Assistant, which is used automatically. Do not enable any of the other Office Assistants in the transform file.
 * 2) Start the Custom Installation Wizard from the Microsoft Office 2000 Resource Kit Tools program.
 * 3) Under Open the MSI File, click the Outlook MSI file (Data1.msi). This file is located in the root folder of the Outlook 2000 CD-ROM.
 * 4) Under Open the MSI File, click Open an existing MST file, and then type the file name and path to the Termsrvr.mst file. This file is located in the C:\Program Files\ORKTools\ToolBox\Tools\Terminal Server Tools folder.
 * 5) Under Select the MST File to Save, save the Termsrvr.mst file to the C:\Sbsfiles folder. Do not overwrite the existing Termsrvr.mst file in the C:\Program Files\ORKTools\ToolBox\Tools\Terminal Server Tools folder.
 * 6) Type your organization name, and then leave the default installation path set to <ProgramFiles>\Microsoft Office.
 * 7) Under Remove Previous Versions (6), click Default Setup Behavior.
 * 8) Skip the remaining panels, 7-13, and do not make any changes.
 * 9) Under Customize Outlook Installation Options (14), click Do not customize Outlook profile and account information. This information is configured by using a .prf file, and this is explained later in this article.
 * 10) Under Customize IE5 Installation Options (15), click Do not install Internet Explorer 5, and then click Yes to continue when you receive the prompt about the requirements for Internet Explorer 5.
 * 11) Skip Modify Setup Properties, and then click Finish to save the Termsrvr.mst file.

How to Install Outlook 2000 on the Terminal Server Computer

 * 1) Verify that the Outlook 2000 CD-ROM is in the CD-ROM drive. In Control Panel, double-click Add/Remove Programs, click Add New Programs, and then click CD-ROM or Floppy.
 * 2) Click Next, and then click Browse.
 * 3) In the root folder of the Office CD-ROM Disk 1, click Setup.exe, and then click Open. Setup.exe is added to the command line for installation program box.
 * 4) On the command line, append the following command after Setup.exe, separated by a space:

TRANSFORMS=c:\Sbsfiles\TermSrvr.mst
 * 1) Click Next, type your customer information, and then click Next.
 * 2) Accept the End User License Agreement, and then click Next.
 * 3) Click Install Now.
 * 4) When you receive the prompt that indicates that the installation completed successfully, click OK, click Next, and then click Finish.

Configuring Outlook 2000
After you install Outlook 2000 on Terminal Server by using the transforms file, you must first log on to the Terminal Server computer and then run Outlook 2000 before any other users do so. 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 by using a .prf file. This file is detected and parsed the first time you run Outlook 2000. There is an Sbs.prf file in the C:\Smallbusiness\Template folder that is a template file that is used when you add Outlook 2000 to normal SBS client installations. You can modify this file, and then use it on Terminal Server. <ol> <li>Make a copy of the Sbs.prf file, rename it to Outlook.prf, and then place it in the C:\Sbsfiles folder on the Terminal Server computer.</li> <li>Start Notepad, and then modify the Outlook.prf file in the c:\Sbsfiles folder on the Terminal Server computer.</li> <li>Open the Outlook.prf file. In the [Service2] section, make the following changes:

Change the HomeServer variable from %SBSServer% to %logonserver%. For example:

HomeServer=%logonserver%

Change the MailboxName variable from %SBSUser% to %username%. For example:

MailboxName=%username%

NOTE: By using system variables, you can use one file for all users. When Outlook 2000 parses the file, the system variables are replaced with the actual values (where %logonserver% is the name of the SBS computer and %username% is the name of the user who is logged on and running Outlook 2000).</li> <li>Place a backup copy of the modified Outlook.prf file in the C:\Smallbusiness folder on the SBS computer.</li> <li>Create a new batch file named Outlook.bat.</li> <li>Copy the following text into the batch file:

copy c:\sbsfiles\outlook.prf %systemroot%\profiles\%username%\windows

</li> <li>Place the Outlook.bat file into the C:\Sbsfiles folder on the Terminal Server computer, and then place a copy of the file in the C:\Smallbusiness folder on the SBS computer as a backup copy.</li> <li>Create registry keys for Outlook 2000 so that it copies, detects, and parses the user's Outlook.prf file the first time they log on. Start Registry Editor (Regedt32.exe).</li> <li>Locate the following registry key:

<pre class="fixed_text">HKEY_LOCAL_MACHINE \Software \Microsoft \WindowsNT \CurrentVersion \Terminalserver \Install \Software \Microsoft \Windows \CurrentVersion \Runonce

</li> <li>On the Edit menu, click Add Value, and then add the following value name:

Value name: OutlookSetup

Data type: REG_SZ

Value: c:\sbsfiles\outlook.bat</li> <li>Locate the following registry key:

<pre class="fixed_text">HKEY_LOCAL_MACHINE \Software \Microsoft \WindowsNT \CurrentVersion \TerminalSer ver \Install \Software

</li> <li>On the Edit menu, click Add Value, and then add the following value name:

Value name: Office

Data type: REG_SZ

Value: 1</li> <li>Quit Registry Editor.</li> <li>Copy the Offer.msg file from the C:\Smallbusiness\Template folder to the C:\Winnt folder on the Terminal Server computer.

NOTE: The Offer.msg file appears in the user's inbox the first time they run Outlook 2000 and describes the new features found in SBS 4.5.</li></ol>

Configuring Client Workstations to Connect to Terminal Server
You must install the Terminal Server client program on all workstations that connect to the Terminal Server computer.
 * 1) On the Terminal Server computer, create a share to the C:\Winnt\System32\Tsclient\Net folder and grant Everyone read access permissions.
 * 2) On the client, connect to the net share on the Terminal Server computer, and then install the client over the network. Run Setup.exe in the Win32 folder for 32-bit clients or Setup.exe in the Win16 folder for 16-bit clients. The Win32a folder is for clients running an Alpha processor. You can also use the Terminal Server Client Creator in Administrative Tools to create disks with the Setup files for each Windows platform.

NOTE: When you run the client from a workstation, you can move between a sizable window and full screen by pressing CTRL+ALT+BREAK.

Adding SBS Users to the Terminal Server Computer
Existing 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 by 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 allows 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 that is 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 Issues
Each 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 that indicate there are no more licenses available and you may not be able to log on to the Terminal Server computer. This occurs when 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 for 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.

Terminal Services Licensing
Each computer that connects to the Terminal Server must have a Small Business Server license, as well as a Windows 2000 Terminal Services license.

NOTE: Windows 2000 Professional includes a Terminal Services license.

Windows 2000 Terminal Services Licensing Service must be implemented within 90 days after you activate Terminal Services.

<div class="references_section">