Terminal Services
an=2 width=10 nowrap>
« back to results for ""
Below is a cache of http://www.filemaker.com/downloads/pdf/terminal_services.pdf. It's a snapshot of the page taken as our search engine crawled the Web.
The web site itself may have changed. You can check the current page or check for previous versions at the Internet Archive.
Yahoo! is not affiliated with the authors of this page or responsible for its content.
Terminal Services
©2000 FileMaker, Inc. All Rights Reserved.
FileMaker, Inc.
5201 Patrick Henry Drive
Santa Clara, California 95054
www.filemaker.com
FileMaker is a trademark of FileMaker, Inc., registered in the U.S. and other countries, and the file folder logo is a trademark of
FileMaker, Inc. All other trademarks are the property of their respective owners.
All persons and companies listed in the examples are purely fictitious and any resemblance to existing persons and companies is
purely coincidental.
Mention of third party companies and products is for informational purposes only and does not constitute an endorsement. FileMaker
assumes no responsibility with regard to the selection, performance, or use of these products. All understandings, agreements, or
warranties, if any, take place directly between the vendor and prospective users.
Running FileMaker
®
Pro 5.0v3 on
Windows 2000 Terminal Services
This page intentionally left blank.
Contents
Chapter 1
Introduction to Windows 2000 Terminal Services
About Windows 2000 Terminal Services
1
-
1
Terminal Services server
1-1
Terminal Services client
1-1
Remote Desktop Protocol (RDP)
1-1
Benefits of using Windows 2000 Terminal Services
1
-
1
System requirements
1
-
2
Terminal Services server minimum requirements
1-2
Terminal Services client minimum requirements
1-2
Enabling Windows 2000 Terminal Services
1
-
2
Installing Windows 2000 Terminal Services client software
1
-
2
Chapter 2
Using FileMaker Pro 5.0v3 with Windows 2000 Terminal Services
Installing FileMaker Pro 5.0v3 on a Terminal Services server
2
-
1
Deployment recommendations
2
-
2
Connecting to FileMaker Server 5
2
-
2
FileMaker Pro 5.0v3 feature issues
2
-
3
Features not supported for Terminal Services clients
2-3
TechInfo database articles
2-3
Appendix A
License requirements
FileMaker, Inc. license requirements
A
-
1
Volume License Agreement (VLA)
A-1
Box Set license
A-1
Windows 2000 Server license requirements
A
-
1
Terminal Services license requirements
A
-
2
This page intentionally left blank.
Chapter 1
Introduction to Windows 2000
Terminal Services
About Windows 2000 Terminal Services
Terminal Services is a Windows 2000 component that lets you remotely access applications
installed on a Windows 2000 server from a wide range of machines over most types of network
connections.
Terminal Services has three components: the server, the client, and the protocol by which the server
communicates with the client.
Terminal Services server
When you are running Terminal Services in application server mode, all applications are run on the
server. The Terminal Services server sends only screen information to the client and receives input
only from the mouse and keyboard.
Terminal Services client
The Terminal Services client uses thin-client technology to provide the Windows 2000 Desktop to
users. The client only needs to make a connection with the server and display the visual information
that the server sends.
Remote Desktop Protocol (RDP)
The Remote Desktop Protocol (RDP) is automatically installed when you install Terminal Services.
RDP is the only connection you need to configure in order for clients to connect to the Terminal
Services server. You can configure only one RDP connection per network adapter.
Benefits of using Windows 2000 Terminal Services
1
Organizations can deploy Windows 2000 on older systems that may not have hardware supported
by Windows 2000.
1
Users can continue to use their current operating system and applications.
1
Organizations can deliver Windows-based applications to a variety of desktop environments and
over LANs and WANs.
1
Administrators only need to install and update one copy of an application on a server machine
instead of on all the computers in their network.
1
Networked applications will perform better over slow network connections.
1-2
Running FileMaker Pro 5.0v3 on Windows 2000 Terminal Services
System requirements
The hardware requirements for Windows 2000 Terminal Services depend mainly on how many
clients will be connecting at a time and the usage requirements of the clients.
Terminal Services server minimum requirements
1
133 MHz or higher Pentium processor
1
128 MB RAM; 256 MB RAM recommended
1
2 GB hard disk with a minimum of 1 GB free space
1
Additional 10 to 20 MB RAM per client connection
Terminal Services client minimum requirements
1
Windows-based terminal devices (embedded)
1
Intel and Alpha-based computers running Windows for Workgroups 3.11, Windows 95,
Windows 98, Windows 3.51, Windows NT 4, and Windows 2000
Windows 2000 Terminal Services shares executable resources among users, so memory
requirements for additional users running the same application are less than the requirements for
the first user to load the application.
For improved performance use:
1
High-performance bus architecture such as EISA, MCA, or PCI. The ISA (AT) bus cannot move
enough data to support the kind of traffic that is generated by a typical Terminal Services
installation.
1
A SCSI disk drive, preferably one that is compatible with Fast SCSI or SCSI-2. To increase disk-
access time, use a SCSI disk drive with RAID.
1
A high-performance network adapter. Consider having two network adapters in the server
machine and designate one for RDP traffic only.
Enabling Windows 2000 Terminal Services
Windows 2000 Terminal Services should be set to run in application server mode. For a step-by-
step procedure to enable Terminal Services, see:
1
http://windows.microsoft.com/windows2000/en/server/help/ts_set_h_020.htm
Installing Windows 2000 Terminal Services client software
Windows 2000 Terminal Services client software should be installed on every machine that needs
to use Terminal Services. There are two versions of the client:16-bit for older machines and 32-bit
for newer machines. For more information about installing the client software, see:
1
http://windows.microsoft.com/windows2000/en/server/help/ts_cli_h_010.htm
Chapter 2
Using FileMaker Pro 5.0v3 with
Windows 2000 Terminal Services
Installing FileMaker Pro 5.0v3 on a Terminal Services server
Note
This installation requires FileMaker Pro 5.0v3 Worldwide English.
To install FileMaker Pro 5.0v3 on a Windows 2000 Terminal Services server:
1.
Make sure Terminal Services has already been installed and configured on your Windows 2000
Server machine and you are logged on as administrator.
2.
In the Control Panel, double-click
Add/Remove Programs
.
Note
Do not directly access the
Setup
icon on your FileMaker Pro Volume License or Box Set CD.
3.
Click
Add New Programs
.
4.
Click
CD or Floppy
, then click
Next
.
5.
Click
Next
.
6.
Click
Yes
if you accept the terms of the license agreement.
7.
Click
Next
.
8.
Choose
Typical
.
If you want to install FileMaker Pro in another directory or drive on the Terminal Services server,
click the
Browse
button and select the desired directory.
9.
Click
Next
.
10.
Choose
TCP/IP
and click
Next
.
Local FileMaker Pro client
Terminal
Services
server
Terminal Serv
ices
client
Terminal Serv
ices
client
RDP
RDP
TCP/IP
TCP/IP
FileMaker
Server
2-2
Running FileMaker Pro 5.0v3 on Windows 2000 Terminal Services
11.
In the Personalization dialog box, enter your name, company information, and installation code.
A Volume License Agreement or Box Set license installation code is required.
12.
Click
Next
.
13.
Click
Yes
if the registration information is correct.
14.
Click Finish.
15.
If prompted to restart, click No, then Finish.
16.
Click Next.
17.
Click Finish when Add/Remove Programs has finished the installation.
18.
Restart the Terminal Services server.
Deployment recommendations
1
Terminal Services requires a minimum of 128 MB RAM (256 MB RAM recommended by
Microsoft). An additional 10-20 MB RAM is required for each subsequent Terminal Services client
running FileMaker Pro.
1
Estimate more RAM per client if your solution is memory-intensive or if you are serving multiple
applications in addition to FileMaker Pro.
1
Use a fast Pentium processor, preferably a Pentium II or Pentium III.
1
The recommended number of users per CPU is 10-15.
1
To improve overall performance, add processors to the Terminal