Microsoft Terminal Server on NT 4.0 by AMS Services - Technology Research Department,
Updated November 2000 to reflect Office 2000 information.
This paper discusses some
technologies that are not directly supported by AMS Services, Inc. This document
is intended for informational use only and reflects the results of
lab testing performed by our research department. There may be issues in using
Terminal Server that were not found in testing. This document does
not establish an endorsement or a commitment to certify the use of this
technology with the AfW product. All of our test results are included - please
do not call AMS Services Support or AMS Rating Support with additional questions
on this technology.
The first part of this
document is designed to give an overview of Terminal Server.
The second part has
some recommendations on how to set up and use Terminal Server. Keep these
suggestions in mind if you decide to configure a Terminal Server system.
As consolidation continues in the insurance agency market, more and more
agency employees are working remote from the main office. Certainly, technology
has been an important reason for the success of this revolution, but many of the
solutions offered for remote connectivity are difficult to use or have good
performance for some applications, and poor for others.
Client server type
applications, for example, do very well on a wide area network (WAN), but
traditional file server-based applications do not. Using a remote control
product like PCAnywhere can improve performance in remote operations
since only screen images are transmitted, but can be very expensive to implement
since you need a computer at each end of the connection. Many other solutions
are available that provide similar functionality, but one solution does not
usually provide all of the features and performance for the needs of today’s
agency.
A few years ago a company called Citrix solved the above-noted remote control
issue of having two computers for each user by creating an environment in which
"virtual sessions" for each incoming user are run on a
"big" server. In a way, it's like the old mainframe environment
(DEC or IBM or WANG), but with a graphical interface. Terminal Server brings the Microsoft Windows
NT Workstation experience to Windows desktops through terminal emulation.
Only
the user interface commands (key clicks, mouse movements and screen images) are passed to/from
the client.
The original Terminal Server product was based on
Microsoft’s Windows NT Server v3.51. Client workstations can
connect over modems, utilizing the RAS (Remote Access Service), a RAS-like
service (i.e. Shiva Dial-up) or via the Internet.
Shortly after the release of Windows NT Server v4.0 Microsoft and Citrix
announced a partnership where Microsoft would license the multi-user technology
from Citrix, and the two companies would cooperate on the development of
multi-user capabilities for Windows NT 4.0 and future products. As a result of
the partnership, Microsoft released a product called Microsoft Window NT, Terminal Server
Edition. This product uses a protocol that Microsoft developed
called RDP (Remote Display Protocol). Citrix will continue to sell and enhance
their WinFrame software, which is based on Windows NT 3.51. In addition, Citrix
will provide enhancements and value-add for Terminal Server, including a very
interesting product called Citrix MetaFrame. As part of the agreement with
Microsoft, Citrix maintains control of their extremely efficient, industry
standard protocol called ICA (Independent Control Architecture).
Terminal Server
– Overview of the base solution
Microsoft Windows NT 4.0, Terminal Server Edition is a specialized version of the Windows NT operating system with
multi-user capabilities built-in.
1.
Terminal Server
Terminal Server is the operating system based on NT capable of hosting
simultaneous NT Workstation sessions. All applications are installed on the
server. Clients make connections to the Terminal Server, and all application
processing for each client is performed on the server.
Each user should have their own home directory, which will store any user specific files.
Terminal Server requires that TCP/IP be
loaded on the server and clients. No other protocol solutions
are provided.
2.
Remote Display Protocol (RDP)
RDP is the protocol that the server
uses to communicate with the clients. This protocol is tuned for high-bandwidth
enterprise environments. The client will only receive the
user interface (screen images and mouse movements) on their system.
Windows NT 4.0 Terminal Server uses RDP
4.0. Terminal Services which is now included with
Windows 2000 Server uses RDP 5.0.
3.
Terminal Server Client
The Terminal Server
Client component displays the
Windows NT Workstation session to the client.
4.
Terminal Server Administration Tools
Terminal Server
provides a number
of administration tools to help you manage your client sessions, including
shadowing.
There are two basic ways for a client to access applications on a Terminal Server.
With Terminal Server administration
tools, an administrator can "publish" or make applications available by
defining a client connection. The connection is actually a windows
NT virtual session running on the server.
The second method is for the client to define connections for itself using the
client connection tools on the workstation.
Note: As of August 2000, Terminal Server on NT 4.0 is available only from OEM's and
World Wide Fulfillment. Terminal Services is now a feature of Windows 2000
Server and Windows 2000 Advanced Server (same as Windows 2000 Server, but with
ability to support up to 8 processors in a machine and clusters). If an agency needs to run TSE on
NT 4, they would exercise their downgrade rights by purchasing the following, but running
NT 4.0 Terminal Server:
Windows 2000 Server or Windows 2000 Advanced Server (includes integrated
Terminal Services)
Windows 2000 Server CALs
Windows 2000 Terminal Services CALs
Obviously, there would be no charge to upgrade to Windows 2000 Terminal
Services if Windows 2000 Terminal Services licensing is purchased. AMS
will be publishing a document on Windows 2000 and Terminal Services in the near
future.
Citrix MetaFrame – Enhances Terminal Server functionality and
management features
Citrix MetaFrame is an extension of Microsoft Terminal Server. Like Terminal Server, MetaFrame has a server component, a communication protocol, a client
component, and administration tools. MetaFrame uses Citrix’s industry standard
ICA (Independent Computing Architecture) protocol for communication. ICA is very
efficient even over low bandwidth connections. MetaFrame also provides features, above and beyond what the basic
Terminal Server product
provides. Please see the chart below for details.
MetaFrame also supports the
following networking protocols: TCP/IP, IPX/SPX, NetBIOS, SLIP/PPP and
asynchronous connections.
All these features do not come without a significant
cost, however. Currently, the Citrix MetaFrame (without "Subscription
Advantage" ) sells for $4,995 with 15 user licenses. Additional
MetaFrame user licenses can be added in increments of 5, 10, 20, or
50-concurrent users for $995, $1,995, $3,990, and $9.975, respectively.
For smaller agencies with a cap of 5 users, there is a product called
MetaFrame/Workgroups 1.8 for NT Server 4.0, Terminal Server Edition which is
available for $1,195.00.
Please note that prices in this document were current at the time this
white paper was written. For the
most current information on the licensing and pricing of MetaFrame, see the
Citrix web site at: http://www.citrix.com/
. AMS does not resell any Citrix products.
Does it Make Sense?
With all of the potentially positive features of this type of environment,
there are reasons a business may elect not to pursue such a
solution:
NT Workstation Shell: When you run the client software
and connect to the Terminal Server, the window that appears is actually
emulating Windows NT Workstation. This means thatany
software you wish to run while connected must operate on Windows NT
Workstation. It doesn’t matter if your workstation is running Windows
95/98 – when connected, the session running on the Terminal Server
system is emulating Windows NT Workstation and you are seeing the
screens from that session. In particular, there are a number of older
DOS type applications still in use within the insurance industry. While
some of these may work on Windows NT Workstation, many may not. In
particular, communication applications do not operate very well in this
environment since the emulated Windows NT Workstation does not have a
physical COM port or modem that many of these programs
require. This means that some very popular personal desktop
applications like WinFax Pro will not integrate with Terminal Server.
The old APT program that dialed out to IVANS will not work in a Terminal
Server environment. Nor will older download applications that use
a modem.
Server Memory :
Another important consideration with this environment is the server
hardware required. As you can imagine, in order to run multiple copies
of Windows NT Workstation there must be memory for each session. The
amount of memory required for each session depends greatly on the
applications being run, but even for programs like Microsoft Office a
minimum of 32Mb is needed. Some studies are even showing
that 64Mb is a better idea when you are running Office and a Server /
Client application like AfW. Each server needs to have enough
physical memory to ensure that the page file is almost never used.
Luckily memory is relatively inexpensive today.
Server CPU : The
speed of the system must be taken into account. Again, depending on the
applications being run, a server with a very powerful processor may only
support 10-20 users. It may be necessary to use multiple processor-based
servers (SMP) to give the system the performance boost it requires. If
dial-in functionality is needed, serial ports and/or modems will need to
be added to the server. Many options exist for this type of product.
Based on these issues, and depending on the size of the installation,
the server hardware could be quite expensive.
Licensing Expenses : In addition to the hardware expenses, there are
software expenses as noted above. You must purchase Windows 2000 Server, Windows 2000 Server CALs,
and Windows 2000 Terminal Services CALs. Then you need to obtain the
media for the Terminal Server version of
Windows NT Server software (assuming you plan to run with 4.0). For
details on the most current licensing information for Terminal Server see
the Microsoft web site at: http://www.microsoft.com/ntserver/terminalserver.
We also recommend Citrix MetaFrame for all but
the most basic use of Terminal Server as it provides a very robust
server and client configuration that includes the ability to print
locally.
This section of the white paper will discuss basic concepts for setting up
applications in a "shell" or "desktop" environment. In other
words, further discussions will describe an environment that emulates an
actual Windows NT Workstation session. We will not be addressing the
specifics of "publishing" an application in a MetaFrame
environment. Some of these concepts require a good understanding of
Windows NT Server.
Please note the following drive references:
"C: Drive" in a
vanilla Terminal Server environment refers to the Terminal Server's root
drive
"V: Drive" in a
vanilla Terminal Server environment refers to the client's root drive
(usually "C" on the client).
"M: Drive" in a
MetaFrame Server environment refers to the MetaFrame/Terminal Server's
root drive.
"C: Drive" in a MetaFrame environment refers to the
client's root drive (usually "C" on the client).
Installation
Installing Terminal Server is very similar to installing Windows NT Server.
The installation of the Terminal Server client software, as well as the
MetaFrame client software is intuitive.
MetaFrame Only: When installing MetaFrame Server
software, there is a point during the installation where you need to make a
choice about how the drives are mapped. You can have drives C: D:, E: , etc.
refer to the server’s hard drives or the client’s hard drives. To make
end-user support easier, AMS recommends
reassigning the server drives in a MetaFrame environment. This means that when a MetaFrame client is
connected to the server, drive C: will correspond to the local user's C:
drive. If you don't do this, the clients drive letters will be reassigned
starting with the letter V: and you will have an endless rush of confused
customers calling your technical support personnel. Remember, at the Server Drive Reassignment dialog box during
the MetaFrame installation, verify that there is a checkmark in the box next
to Remap the server drives.
Do not forget to apply any applicable service packs for Terminal Server and MetaFrame.
If you have installed Terminal Server, you will need to make connections
using RDP. If you have installed MetaFrame, connections can be made using
RDP or ICA.
General Guidelines on Application Loading
In a Terminal Server environment, applications that you want to be available
to all users are installed on the Terminal Server. There
are two ways of installing applications to ensure that the applications are
available to all users that connect to the server.
The first method is to use
the Add/Remove Programs applet in Control Panel. A dialog has been added to this
applet to allow you to choose whether you want to make the application that you
are installing to be available to all users or just the user who is installing
the application (choose All users begin with common application
settings). When you choose to make the
application available to all users, the system makes specific changes in
the registry to ensure multi-user capabilities. This ensures that when
each user connects, they will have their own user profile and the
ability to customize their user settings.
Alternately,
there is a command that you can issue at the command line (change user
/install). You use the change user /install command before installing
an application to create .ini files for the application in the Terminal Server system directory. These files are used as master copies for the user-specific
.ini files. After installing the application, use change user /execute to
revert to normal .ini file mapping. This command enables the ability the map
.ini files to the home directory. This is the default setting. For more
information on this command see
http://support.microsoft.com/support/kb/articles/q186/5/04.asp
Since not all applications in use today are written to be used in a
multi-user environment, some fine-tuning is required to get some applications to
function properly. Microsoft has supplied compatibility scripts that can be run
for most of its popular applications, such as Microsoft Office. Compatibility
scripts are stored in the %SystemRoot%\ApplicationComptibilityScripts\install
directory. The script makes specific changes to the registry, in order to make
the application function properly in a multi-user environment. Compatibility
scripts need to be run once after you install the application. In addition,
there is a logon directory, that contains a logon script (UsrLogon.cmd) which
runs each time a user logs on to the Terminal Server. One of the functions of
this logon script is to map the location of each user’s home directory. The
first time a compatibility script is run you are prompted to choose a letter to
map to each user’s home directory. W: is a popular choice. The logon script may
also contain application-specific commands.
Microsoft has stated that most standard
Windows-based applications should function properly on the Terminal Server
without modification. However, for some applications without a
compatibility script, the Terminal Server registry may need to be altered
for the application to function properly. As always, use extreme caution
when making changes to the registry.
Terminal Server – AMS Products
AMS has done some preliminary testing with the following products and
Microsoft Terminal Server (and Citrix MetaFrame):
AMS for Windows (4.033 or greater)
Basic AfW integration with Microsoft Office 2000 (Word and Excel)
AMS for Windows Imaging
Rating (Eastern)
PS4
Optus FACSys
Suggestions on how to set up and configure the above list of applications are
included here. Most steps need to be performed at the Windows NT Terminal Server, however, some steps are to be performed at each workstation, where
indicated.
Before you begin, you will need to decide on a few things.
Will these services be available to your CSR's
from home (the Internet, leased lines, or direct dial-in
access)?
What will each user's profile look like (home
directory?) ?
Determine the structure will you use for various applications.
(ie. Map an O: drive for Office, a "P" drive for AfW file
server information, a "Q Drive" for the AfW client, etc..,
NOTE:
Many of the suggestions and workarounds listed here involve making changes to
the Windows NT Server Registry. Only a Microsoft Windows NT expert should
make such changes -- mistakes can cause the server to malfunction and often
result in a complete re-install of the software.
First and foremost, the server portion of the AfW
installation is done exactly as noted in the THS. You may want to leave the Agena share (P: drive) on the SQL server for
simplicity's sake. We do not recommend putting any shares on a
Novell client in any Terminal Server configuration. It is possible, but has a rather
convoluted setup that we will not be discussing in this white paper.
The installation of AfW on a Terminal Server differs only slightly from a
typical installation. It is important that the installation is initiated from
the Add/Remove Programs utility located in Control Panel, and that the machine
is not rebooted until the Add/Remove Programs utility is complete. This ensures
that each user maintains their own set of configuration files. Follow these
instructions to install AfW on the Terminal Server.
Log on to the Windows Terminal Server console as Administrator.
Map drive
letter P: to AGENA on the Windows NT database server.
Click the Start button on the taskbar, point to Settings, and click
Control Panel.
Double-click Add/Remove Programs. Click Install.
The program prompts you for a floppy disk or CD-ROM. Click Next.
At the Run Installation Program dialog box, click Browse.
Click the arrow at the end of the Look in field to view the drop-down list
of drives.
Select the P: drive, then double-click the afwpgm directory,
Select afwsetup and click Open.
The following should appear in the Command line for installation
program field: p:\afwpgm\afwsetup.exe. Click Next.
At the Change User Option dialog box, select All users begin with
common application settings. Click Next.
At this point, follow the instructions for installing AfW found in the
Installation Technical Help Series guide until you get to the dialog box where
it asks you if you want to restart your computer. DO NOT let the program
restart the computer at this point.
Select No, I will restart my computer later. Click Finish.
A message displays indicating that AMS for Windows setup completed
successfully. Click OK.
Locate the After Installation dialog box and click Next. (You may need to
close the AfW and ODBC windows in order to find the dialog box.)
At the Finish Admin Install dialog box, click Finish. Close the Control
Panel window.
Click the Start button, point to Programs, and click Command Prompt. Type
shutdown /reboot and press Enter. Click OK when prompted. The machine
will reboot.
Microsoft Office 2000
Microsoft
Office 2000 is a completely different animal than Office 97. With Office
97, you simply did the install, ran a few scripts, then changed a few registry
settings. The Microsoft Office 2000
installation, on the other hand, must first be customized using the Custom
Installation Wizard. You will need to load the Office 2000 Resource Kit in
order to run the Custom Installation Wizard. You must
load all applications / features that users will need. Users will not be
able to add/remove
features from their Terminal Services window.
Install the Office Resource Kit (ORK) as follows:
Log on to the Windows Terminal Server console as Administrator.
Insert the Office 2000 Resource Kit CD
Go to Control Panel -> Add/Remove Programs
Install for only the current user.
Select the options for Custom Installation
Wizard and Internet Explorer, Excel tools, Terminal Server Tools, Office
Profile Wizard, Office Remove Wizard, Package Definition files, System
Policy Editor and Office Policy Templates, Unbind Office Binders
Utilities.
Once you have installed the ORK, you need to run
the Custom Installation Wizard and configure your Office parameters. Here
are some tips. The following instructions are merely and outline
and not an official installation document.
Launch the Custom Installation
Wizard
Open the data file you plan to use (usually a
copy of data.msi).
Open an existing transform (a copy of the
default *.mst unless you first decide to create a template based on a
current user installation). This can usually be found in
C:\Program Files\ORKTools\Toolbox\Tools\Terminal Server Tools.
When you are prompted for the installation
directory for Office, please be sure to indicate an 8.3 compliant name as
not all insurance agency applications are able to deal with long
names. (We used Office2K).
We only loaded Word for Windows and
Excel. Agencies may wish to run Access, Power Point,
Outlook, or other applications if they have purchased official licensing for
them. We recommend you closely follow the guidelines established in
our THS Guides. Be aware, however, that end users cannot install
With Terminal Services on Windows 2000, the
only Office Assistant that can be installed is the StillLogo. This is
a good idea as the paperclip, professor, cat, and other popular wizards
demand too many resources from the Terminal Server.
Follow the instructions indicating whether you
have any customized registry entries, shortcuts, or other programs to
install.
Once you have created and saved your new
transform, you will want to run it:
setup.exe Transforms ="location of
transform" /qn+
(You can look up information on these
options in the on-line help for the Resource Kit).
When the install begins, do not touch the
Terminal Server machine until a finish message pops up. (Warning: If you click on the "next" button in the "After
installation" box prior to completion of the install, you will have to
uninstall and begin again. )
At the After
Installation dialog box, click Next. Then click Finish.
Additional Tasks.
Navigate to the following directory: C:\wtsrv\application compatibility
scripts
Change user /install
Edit rootdrv2.cmd to reflect the correct root drive that you have used in
your profile information (usually W:)
Navigate to the following directory: c:\wtsrv\application compatibility
scripts\install
Run Office97.cmd. At the Run dialog, click OK.
(We found that these scripts needed to be run to get Office 2000 to
work correctly due to the way Terminal Server handles permissions on various
*.DLL files. We expect updated scripts in the near
future).
Notepad will open a document. Read the contents of the document. Modify
the last line of the file to read Set RootDrive = W: (if this is how you set
it above). Make
sure there are no spaces after the drive letter and colon.
Select Exit from the File menu. Choose Yes to save the changes.
A message displays indicating that tuning is complete. Press any key to
continue.
Close the Control Panel and remove the
Microsoft Office 2000 CD from the drive.
You may need to give the group EVERYONE permission to the following files
if you experience problems with the AfW application, especially after
running any ZAK (zero administration kit) utilities: ( msjet40.dll, mswstr10.dll, msjter40.dll,
msjint40.dll, odbccp32.dll, msjtes40.dll, and other ODBC drivers).
Tuning for AfW Form Letters and Schedules for Insurance.
There are some modifications that need to be made in order for AfW Form
Letters and Schedules of Insurance to work properly in a Terminal Server environment. This may also be done via Policy Manager if
preferred.
Form Letters
In order for AfW Form Letters to work, each user
must have access to the following templates: closemsg.dot, formltr.dot,
and normal.dot. They should be copied from the P:\agena\afwshare\formltrs
area to the "User Templates" area you designated when performing the
installation of Word/Office. Or, you may copy these
files to each user's home directory if you have set up your NT structure as
such.
Schedules of Insurance
In order for Schedules of Insurance to work, the Schedule of Insurance file
needs to be in an area that each CSR has access via the "Group
Templates" setting in Word or some other public area.
Afwofc32.dll must also be available in one of the pathed
directories.
Depending on how you have set up
your user's directories, you may need to add the following lines to each user's
AfW.ini file:
HomeDrive=%HomeDrive%
HomePath=%HomePath%
The following procedure needs to be performed once at each workstation. These
instructions assume that P: is mapped to the AfW shared directory and W: is
mapped to the user’s home directory.
Click the Start button, point to Programs, and then click Command Prompt.
Type copy p:\afwshare\agency1\schedule\schedi97.dot
w:\office97\templates\schedi97.dot.
Type exit and press Enter to close the Command Prompt
window.
Start AfW and open a customer for whom you want to generate Schedules of
Insurance.
Click Schedules on the AfW toolbar.
Change the path to the Word Template to the following:
w:\office2K\templates.
Proceed to generate the Schedules of Insurance.
AMS for Windows Imaging
Imaging on in a Terminal Server environment has some limitations. First
and foremost, your screen resolution will appear exactly as you set it in your Terminal Server
session configuration. We recommend at least an 800x600 screen
resolution.
Furthermore, the imaging application will not be able to directly access
scanners and cameras as it does in a standard AfW application environment.
Terminal Server environments are not able to directly access a client's local
COM port. As a result scanned images and photos will need to
be stored locally on each client and then be imported to AfW Imaging.
Log on to the Windows Terminal Server console as Administrator.
Insert the AMS for Windows Imaging CD-ROM.
Click the Start button on the taskbar, point to Settings, and click
Control Panel.
Double-click Add/Remove Programs. Click Install, then Next.
The Run Installation Program dialog box indicates the path to the
installation program (d:\afwsetup.exe, if d is the CD-ROM drive). Click Next.
At the Change User Option dialog box, select All users begin with
common application settings. Click Next.
At this point, follow the instructions for installing AfW Imaging found in
the Imaging guide until you get to the dialog box that indicates that AfW
Imaging setup is complete. Click OK at this dialog box and continue with the
next step.
At the After Installation dialog box, click Next, and then click Finish
Close the Control Panel and remove the AfW Imaging CD from the drive.
Click the Start button, point to Programs, and click Command Prompt. Type
shutdown /reboot and press Enter. Click OK when prompted. The machine
will reboot.
Rating (Eastern)
The installation of Rating software on a Terminal Server differs only
slightly from a typical installation. A special command must be issued at
the start and end of the process to ensure proper setup.
Log on to the Windows Terminal Server console as Administrator.
Click the Start button on the taskbar, point to Programs, and click
Command Prompt.
Type change user /install and press Enter.
Install and configure Rating and Rating Integration as you normally would
according to the Rating documentation. Note It is assumed that
Rating is installed on the AfW database server and each workstation will map
drive R: to the AMSR share on the database server.
When you are finished, click the Start button, point to Programs, and
click Command Prompt.
Type change user /execute and press Enter. Type exit and
press Enter to close the window.
Rating Integration
If you choose to run the actual rating program locally, rather than on the
Terminal Server, rating integration should also be set up locally on the
C: drive of the client. The Link button in the AfW application would need
to refer to the "V:" drive so that it could send information to the
client computer.
If you are going to run Rating on the Terminal Server,
you must install Rating Integration on the Terminal Server to the "C"
drive . Remember to do the classic change user /install before
installing.
Unlike Office and the AfW client, Rating
Integration does not seem to install cleanly to a mapped drive in the Terminal Server
environment. Always choose the root drive.
PS/4(These notes apply to Terminal Server
on NT4.0 only. PS/4 is NOT supported on Windows 2000).
There are several configuration changes that need to be made in order to get
PS/4 to run properly on the Terminal Server. One of the modifications involves
using the Terminal Server command flattemp. The purpose of using this command is
to ensure that each user has a unique place to store temporary files. For more
information on this command see: http://support.microsoft.com/support/kb/articles/q186/5/16.asp
Log on to the Windows Terminal Server console as Administrator.
Click the Start button, point to Programs, and click Command Prompt. Type
change user /install and press Enter.
Install PS/4 as you normally would, following the appropriate
documentation, except DO NOT reboot until these instructions tell you to.
( Hints: FIRST double click on the ws_ps4w.exe file to
invoke. If it asks you if you want to install Adobe reader, say no--you've
already got it. Secondly double click on ws_afw32.exe. If you do this
backwards, you will experience problems with the applications).
After installing PS/4, click the Start button, point to Programs, and
click Windows NT Explorer.
On the left side of the window, select the c: drive. Double-click
ps4, then double-click admin, and then select dll.
Select all files titled p4*.dll on the right side of the screen. (You can
select more than one file at a time if you hold down the Ctrl key while
selecting the files with the mouse.)
Right-click in the selected area and select Copy.
Select the C: drive, then double-click the wtsrv directory (if this
is the directory that Terminal Server is installed in).
Select the system directory. Right-click on the system directory and
select Paste.
Select the C: drive. Double-click ps4, then select admin.
Select p4prow97.dot, p4rsqw97.dot, p4abou32.dll, and
p4Inkd32.dll on the right side of the screen.
Right-click in the selected area and select Copy.
From the Tools menu, select Find and then select Files or Folders.
Type WrdStart in the Named field. At the Look in field, use the drop down
box to select (C:). Click Find Now.
All the user profile directories will be listed. Right-click each
directory and select Paste. Repeat for each directory. Close the Find
dialog.
Click the Start button, point to Programs, and click Command Prompt. Type
flattemp /enable. Type exit and press Enter to close the window.
When finished configuring PS/4, click the Start button, point to Programs,
and click Command Prompt. Type change user /execute and press
Enter. Type exit and press Enter to close the window.
Click the Start button, point to Programs, and click Command Prompt.
Type shutdown /reboot and press Enter. Click OK when prompted.
The machine will reboot.
Modifying the TEMP variable
The following steps need to be performed at each workstation in a Terminal Server
session.
Click the Start button, point to Settings, and click Control Panel.
Double-click the System icon.
Click the Environment tab. In the User Variables window, double-click the
line beginning with TEMP. Replace the contents of the Value field with the
following: %HomeDrive%%HomePath%\TEMP. Click Set.
In the User Variables window, double-click the line beginning with TMP.
Replace the contents of the Value field with the following:
%HomeDrive%%HomePath%\TEMP. Click Set.
Click Apply, then click OK.
Configuring PS/4 -AfW Integration
The following steps need to be performed at each workstation in the
Terminal Server session.
Start AfW and log in.
Follow the instructions in your PS/4 - AfW Integration manual to configure
the AfW Link button for PS/4 integration. Important: The Integration
directory that you specify should be C:\temp if integration is running
on the Terminal Server.
Optus FACSys
Optus Software has published a technical note on the Optus web site that
states that FACSys v4.x is supported on Microsoft Terminal Server. For details
follow this link: http://www.facsys.com/indexed/tsb/PS98-523.htm.
FACSys should be installed using the Add/Remove Programs utility, but requires
no other special instructions. Optus does recommend that the fax server software
be loaded on a separate server, likely due to performance concerns.
Log on to the Windows Terminal Server console as Administrator.
Insert the FACSys CD-ROM.
Click the Start button, point to Settings, and click Control Panel.
Double-click Add/Remove Programs.
Click Install, then Next.
Click Browse. Navigate to the following directory: D:\clients\win32\i386
(assuming D: is the CD-ROM drive).
Double-click setup, and then click Next.
At the Change User Option dialog box, select All users begin with common
application settings. Click Next.
At this point, follow the instructions for installing FACSys client
software in the FACSys Technical Help Series until you get to the dialog box
that indicates that the FACSys setup is complete.
Select No, I will restart my computer later and click Finish.
At the After Installation dialog box, click Next, and then Finish.
Close the Control Panel and remove the FACSys CD from the drive.
Click the Start button, point to Programs, and then click Command
Prompt. Type shutdown /reboot and press Enter. Click OK when
prompted. The machine will reboot.
Notes on Security
You need to disable anonymous File
Transfer Protocol (FTP) to prevent unsecured access to the file system.
Depending on what you use, you will
want to keep TCP, RDP, and ICA port numbers available to/from your
facility. You may want to choose a firewall that can
also set up security based on user ID's, not just a TCP/IP address which
can be spoofed.
Always beware when loading old DOS
applications as any ability to get to a DOS prompt from a public network
could be business-threatening.
You may want to implement Group
Policies and NTFS permissions to better lock down your server. Be
careful with this on Windows 2000 Pro stations as policies applied to TS
environments also apply to local user profiles.
Always encrypt your logon.
Always encrypt passwords
Limit the number of logon attempts
If you decide to deploy the Zero
Administration Kit, please be sure to carefully log all changes made as
various Citrix or Office files may be inadvertently protected from the
group "Everyone".
| back to previous page
