Microsoft KB Archive/229774

= Running Windows NT Server 4.0, Terminal Server Edition with Small Business Server 4.5 =

Article ID: 229774

Article Last Modified on 4/17/2006

-

APPLIES TO


 * Microsoft BackOffice 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 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.



SUMMARY
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.



How to Set Up Terminal Server in the SBS Domain
Before you install Terminal Server in the SBS domain:
 * 1) Add the computer account to the SBS domain. To do this, click the Set Up a Computer wizard in the Manage Computers Tasks on the SBS console.
 * 2) 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.
 * 1) Type a name for the Terminal Server computer (for example, if your SBS computer name is Oxygen, choose the name Oxygents), and then click Next.
 * 2) Click Microsoft Windows NT 4.0 Workstation for the operating system.
 * 3) In the Application window, select all programs except Outlook 2000 or Microsoft Office 2000.

NOTE: You cannot install Outlook 2000 or Office 2000 until you configure them to run on the Terminal Server computer. Configuration and installation of Outlook 2000 on Terminal Server is discussed later in this article.
 * 1) Insert a blank disk into the disk drive when you are prompted to create the client Setup disk, and then click Next.

NOTE: Even though you are not going to 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.

Installing Terminal Server
If you are not familiar with the installation of Terminal Server, use the following guidelines to install Terminal Server:
 * In the Terminal Server Desktop License window, choose the appropriate number of Terminal Server desktops. This number is the same as the number of SBS Client Access Licenses (CALs) that you have.
 * Install Terminal Server as a stand-alone (member) server, as this is the most appropriate configuration.
 * It is not necessary to install Microsoft Internet Explorer 4.0 during Setup; Internet Explorer 5 is installed during SBS client Setup.
 * 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. If you are not using the 10.x.x.x range on your network, set the TCP/IP information accordingly.
 * After Terminal Server Setup is finished, install Windows NT Server 4.0, Terminal Server Edition, Service Pack 4 before you install SBS 4.5 client programs. Do not install Windows NT Server 4.0 Service Pack 4 or later that is included with SBS 4.5, as it may prevent your current Terminal Server installation from working properly.

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.  Create a folder on the root drive of the Terminal Server computer and name it Sbsfiles. You will use this folder later to store some of the necessary files used in configuring programs to run on Terminal Server. Find the logon script at the following location:

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

 Locate the following sections in the logon script:

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

\\ \Clients\Setup\%directory%\Startcli.exe /s: /u:Administrator /l:%>windir%\..\Startcli.log

 Copy the following text:

Pause

Change user /install

Change user /query

Pause

 Paste the text you copied in between the two sections (noted above) in the logon script. 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: Adding this text to the logon script 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 does 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 working correctly.

 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, go to an MS-DOS command prompt and type the following command:

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> When you log on as Administrator in the SBS domain, the administrator's logon script is run on the SBS server and begins installing the SBS client. Internet Explorer 5 is installed, and then the server restarts.</li> Log on as Administrator again. When the SBS Client Setup dialog box is displayed, click Next to continue.</li> The Microsoft Fax client is installed, and you are then prompted to insert the Terminal Server 4.0 CD-ROM into your CD-ROM drive. Setup then attempts to copy the Mswd6_32.wpc file from the CD-ROM to the hard disk. When you receive a prompt asking you if you want to overwrite the newer file that exists, click No To All.

The file that exists is installed from Windows NT Server 4.0, Terminal Server Edition, Service Pack 4 and is newer than the file that exists with the Fax client. Setup continues and Proxy Client and the Modem Sharing client are installed. When Setup is finished, 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 in this article.</li></ol>

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

c:\sbsfiles\startclie.exe /s:%logonserver% /u:%username%

</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> Start Registry Editor (Regedt32.exe).

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.

</li> Locate the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\

Terminalserver\Install\Software\Microsoft\Windows\CurrentVersion\

Runonce

</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> Delete the Internet Connection Wizard and Install Internet Information Server 2.0 shortcuts from the Administrator desktop on the Terminal Server computer.</li></ol>

Internet Explorer 5
If 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: <ol> Start Registry Editor (Regedt32.exe).</li> Locate the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\

Terminalserver\Install\Software\Microsoft\Windows\CurrentVersion\

Runonce

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

Microsoft Fax Client 4.5
The 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: <ol> <li>Copy the following text:

REGEDIT4

[HKEY_CURRENT_USER\Printers]

"DeviceOld"="\\\\ \\Fax,winspool,Ne00:"

[HKEY_CURRENT_USER\Printers\Connections]

[HKEY_CURRENT_USER\Printers\Connections\,, ,Fax]

"Server"="\\\\ "

"Provider"="win32spl.dll"

[HKEY_CURRENT_USER\Software\Microsoft\Fax]

[HKEY_CURRENT_USER\Software\Microsoft\Fax\Devmode]

"\\\\ \\Fax"=hex:5c,00,5c,00,4a,00,45,00,46,00,46,00,42,00,52,00,59,\

00,53,00,42,00,53,00,34,00,35,00,5c,00,46,00,61,00,78,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,01,04,00,\

04,dc,00,58,01,03,27,01,00,01,00,01,00,ea,0a,6f,08,64,00,01,00,01,00,c8,00,\

01,00,01,00,c8,00,01,00,00,00,4c,00,65,00,74,00,74,00,65,00,72,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,44,61,78,00,00,00,00,01,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,41,00,64,00,6d,00,69,00,6e,\

00,69,00,73,00,74,00,72,00,61,00,74,00,6f,00,72,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\

00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

[HKEY_CURRENT_USER\Software\Microsoft\Fax\Setup]

"CoverPageDir"=hex(2):25,73,79,73,74,65,6d,72,6f,6f,74,25,5c,43,6f,76,65,72,50,\

67,00

"CoverPageEditor"=hex(2):25,73,79,73,74,65,6d,72,6f,6f,74,25,5c,73,79,73,74,65,]

6d,33,32,5c,66,61,78,63,6f,76,65,72,2e,65,78,65,00

"FaxProfileName"=""

[HKEY_CURRENT_USER\Software\Microsoft\Fax\UserInfo]

"Installed"=dword:00000001

"LastCountryID"=dword:0000ffff

"LastDialAsEntered"=dword:00000000

"AlwaysOnTop"=dword:00000000

"SoundNotification"=dword:00000000

"EnableManualAnswer"=dword:00000000

"OnTaskBar"=dword:00000001

"VisualNotification"=dword:00000001

"LastRecipientAreaCode"=""

"FullName"="Enter your name"

"FaxNumber"="Enter your fax number"

"Mailbox"="Enter your mailbox name"

"Company"="Enter Company Name"

"Title"="Enter your Position"

"Address"="Enter your address"

"Department"="Enter your department"

"Office"="Enter your office number"

"HomePhone"="Enter your home phone"

"OfficePhone"="Enter your office phone"

</li> <li>Paste the text you just copied into new text file, and then save the file as Faxsetup.reg.

NOTE: Replace all instances of  in the text you paste into the new file with the actual computer name of the SBS server in the domain (for example, if the name of your SBS server is Oxygen, replace   with the word Oxygen).</li> <li>Move the Faxsetup.reg file to the C:\Sbsfiles folder on the Terminal Server and place a backup copy in the C:\SmallBusiness folder on the SBS server.</li></ol>

The registry file above only configures the fax printer for each user. To set up each user's fax information (such as fax number and company name), you need to display the User Info window using a command that runs when the user first logs on to the Terminal Server computer. You can run this command from the RunOnce registry key along with the Faxsetup.reg file created above. To add this key: <ol> <li>Start Registry Editor (Regedt32.exe).</li> <li>Locate the following registry key:

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 registry value:

Value name: faxsetup

Data type: REG_SZ

Value: c:\sbsfiles\faxsetup.reg

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

Value name: faxinfo

Data type: REG_SZ

Value: rundll32.exe shell32.dll,Control_RunDLL faxcfg.cpl,@0,2

</li></ol>

When you run the faxinfo command, the Fax tool in Control Panel starts and the User Info tab is automatically selected so users can type and save their fax information. This happens only once when each user logs on. If users need to change their information later, you must start the Fax tool in Control Panel and manually change that user's information.

Microsoft Proxy Client 2.0
Edit 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 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.

Microsoft Modem Sharing Client 4.5
The modem on the SBS server needs to be detected and installed on the Terminal Server computer before you can enable Modem Sharing:
 * 1) On the Terminal Server computer, click Start, point to Settings, click Control Panel, and then double-click Modems.
 * 2) Click Next, and let the wizard detect the modem.

If you have two COM ports on your computer, the remote modem should be detected and installed on COM3. If your modem is not detected properly when you set up SBS 4.5, or if the modem is not detected because it is not on the Windows NT Hardware Compatibility List, you must manually configure the modem for use with Terminal Server.
 * 1) If the modem is not detected, in the Install New Modem window, click have disk and then type the location to the Modem.inf file.

NOTE: It is possible to add additional modems for sharing on the Terminal Server computer. You must add additional remote ports on the Terminal Server using the Ports tool in Control Panel. After you add the ports, you can add additional modems using the previous steps.

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 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

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 File
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) On the Open the MSI File panel, click the Outlook MSI file (Data1.msi). This file is located on the root of the Outlook 2000 CD-ROM.
 * 4) On the Open the MST File panel, click Open an existing MST file, and then type the file name and path of the TermSrvr.mst file. This file is located in the C:\Program Files\ORKTools\ToolBox\Tools\Terminal Server Tools folder.
 * 5) On the Select the MST File to Save panel, 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 leave the default installation path set to  \Microsoft Office.
 * 7) On the Remove Previous Versions panel (6), click Default Setup Behavior.
 * 8) Skip the remainder of the panels (7 through 13). Do not make any changes.
 * 9) On the Customize Outlook Installation Options panel (14), click Do not customize Outlook profile and account information. This information is configured using a .prf file, which is explained below.
 * 10) On the Customize IE5 Installation Options panel (15), click Do not install Internet Explorer 5. Click Yes to continue when prompted about the requirements for Internet Explorer 5.
 * 11) Skip the Modify Setup Properties panel.
 * 12) Click Finish to save the Termsrvr.mst file.

How to Install Outlook 2000 on the Terminal Server Computer
To 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: <ol> <li>On the Terminal Server, click Start, point to Settings, click Control Panel, and then double-click Add/Remove Programs.</li> <li>Click Install, and then click Next.</li> <li>Click Browse.</li> <li>In the root folder of the Outlook 2000 CD-ROM, click Setup.exe, and then click OK.</li> <li>On the command line, add the following command after Setup.exe, separated by a space:

TRANSFORMS=path\TermSrvr.mst /qb+

NOTE: This command identifies the Terminal Server transform file for Setup to use during installation. You must specify the correct path to the MST file. The following example shows the full command:

d:\setup.exe TRANSFORMS=c:\Sbsfiles\TermSrvr.mst /qb+

</li> <li>Click Next.</li> <li>Using the Add/Remove Programs tool, click All users begin with common application settings, and then click Next, to run Outlook 2000 Setup. Outlook 2000 displays a message when the installation is finished.</li> <li>Restart the computer.</li></ol>

Configuring Outlook 2000
After 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. <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 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: <ul> <li>Change the HomeServer variable from %SBSServer% to %logonserver%. For example:

HomeServer=%logonserver%

</li> <li>Change the MailboxName variable from  to

MailboxName=%username%

</li></ul>

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  is the name of the SBS computer and   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. To create those keys: <ol style="list-style-type: lower-alpha;"> <li>Start Registry Editor (Regedt32.exe).</li> <li>Locate the following registry key:

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:

HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\

TerminalServer\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></ol> </li> <li>Copy the Offer.msg file from the C:\Smallbusiness\Template folder to the C:\Wtsrv 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:\Wtsrv\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 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 (such as Microsoft Windows for Workgroups 3.11). 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 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 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 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.

Additional query words: smallbiz

Keywords: kbenv kbhowto kbinfo KB229774

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.