FileMaker. Running FileMaker Pro 9 on Windows Server 2003 Terminal Services

Transcription

1 FileMaker Running FileMaker Pro 9 on Windows Server 2003 Terminal Services

2 FileMaker, Inc. All Rights Reserved. FileMaker, Inc Patrick Henry Drive Santa Clara, California FileMaker is a trademark of FileMaker, Inc., registered in the U.S. And other countries, and ScriptMaker and the file folder logo are trademarks of FileMaker, Inc. All other trademarks are the property of their respective owners. FileMaker documentation is copyrighted. You are not authorized to make additional copies or distribute this documentation without written permission from FileMaker. You may use this documentation solely with a valid licensed copy of FileMaker software. All persons and companies listed in the examples are purely fictitious and any resemblance to existing persons and companies is purely coincidental. Credits are listed in the Acknowledgements document provided with this software. Mention of third-party products is for informational purposes only and constitutes neither an endorsement nor a recommendation. FileMaker, Inc. assumes no responsibility with regard to the performance of these products. For more information, visit our website at Edition: 01

3 Contents Chapter 1 Introduction to Windows Server 2003 Terminal Services About Windows Server 2003 Terminal Services 5 Terminal Services server 5 Terminal Services client (Remote Desktop Connection) 5 Remote Desktop Protocol (RDP) 5 Benefits of using Windows Server 2003 Terminal Services 5 System requirements 5 Installing Windows Server 2003 Terminal Services client software (Remote Desktop Connection) 6 Chapter 2 Using FileMaker Pro with Windows Server 2003 Terminal Services Installing FileMaker Pro on a Terminal Services server 7 Deployment recommendations 8 Environments for deploying FileMaker Pro files 8 Non-shared files 8 Connecting to FileMaker Server 8 FileMaker Pro feature issues 8 FileMaker Knowledge Base articles 8 Appendix A Standard requirements FileMaker, Inc. standard requirements 9 Volume License Agreement (VLA) 9 Site License Agreement (SLA) 9 Windows Server 2003 and Terminal Services license requirements 9

4 4 Running FileMaker Pro on Windows Server 2003 Terminal Services

5 Chapter 1 Introduction to Windows Server 2003 Terminal Services About Windows Server 2003 Terminal Services Terminal Services is a Windows Server 2003 component that lets you remotely access applications installed on a Windows Server 2003 machine 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 (Remote Desktop Connection) The Terminal Services client, called Remote Desktop Connection (RDC), uses thin-client technology to provide the Windows 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 Server 2003 Terminal Services 1 Organizations can deploy Windows-based applications on older systems that may have inadequate resources. 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. System requirements The hardware requirements for Windows Server 2003 Terminal Services depend mainly on how many clients will be connecting at a time and the usage requirements of the clients. For more information, see

6 6 Running FileMaker Pro on Windows Server 2003 Terminal Services The following clients are supported by FileMaker, Inc. at this time. Other clients may work as expected but have not been tested with FileMaker Pro and are not currently supported. 1 Windows: Terminal Services Client (Remote Desktop Connection) version running in Internet Explorer version Mac OS: Remote Desktop Connection version (040913) Windows Server 2003 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. Installing Windows Server 2003 Terminal Services client software (Remote Desktop Connection) Windows Server 2003 Terminal Services client software (Remote Desktop Connection) should be installed on every machine that needs to use Terminal Services. 1 Windows Server 2003 or Windows XP: the Remote Desktop Connection software is installed by default. You can also use Remote Desktop Web Connection. 1 Mac OS: you must download the Remote Desktop Connection software. See

7 Chapter 2 Using FileMaker Pro with Windows Server 2003 Terminal Services FileMaker Pro on Windows Server 2003 Terminal Services FileMaker Server Windows Server 2003 Terminal Services client Windows Server 2003 Terminal Services client Standard FileMaker Pro client Installing FileMaker Pro on a Terminal Services server Note This installation requires FileMaker Pro Worldwide English (Volume License or Site License is required). To install FileMaker Pro on a Windows Server 2003 Terminal Services server: 1. Make sure Terminal Services has already been installed and configured on your Windows Server 2003 SP1 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 Site License CD. 3. Click Add New Programs. 4. Click CD or Floppy, then click Next. The FileMaker Pro InstallShield Wizard appears. 5. When the License Agreement panel appears, read the Software License Agreement. If you accept the terms of the license agreement, click I Accept. 6. Install FileMaker Pro by following the on-screen instructions. For details about installation issues, see the Installation and New Features Guide for FileMaker Pro and FileMaker Pro Advanced. 7. Click Finish when Add/Remove Programs has finished the installation.

8 8 Running FileMaker Pro on Windows Server 2003 Terminal Services Deployment recommendations 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 III or Pentium 4. FileMaker supports deployment and development of FileMaker Pro solutions running on Windows Server 2003 Terminal Services. Some aspects of development may not function as expected when using Terminal Services clients as a FileMaker development environment. For more information on known technical issues when using Terminal Services clients as a FileMaker development environment, see Environments for deploying FileMaker Pro files Non-shared files Terminal Services clients can access FileMaker Pro files that are not shared over a network. Non-shared files can be developed and deployed by Terminal Services clients just like any non-shared FileMaker Pro file. Shared files and peer-to-peer hosting (FileMaker Network Sharing) are not supported on Terminal Services clients. Note To turn off sharing for a specific file, choose File menu > Sharing > FileMaker Network, select the file, then select No users. Connecting to FileMaker Server Use FileMaker Server (or FileMaker Server Advanced) to host files to the Terminal Services server. The Terminal Services server deploying FileMaker Pro will access FileMaker Server to host FileMaker Pro files to Terminal Services clients as well as local FileMaker Pro clients. When a user opens FileMaker Pro running on Terminal Services, accessing FileMaker Pro files hosted by FileMaker Server is done in the same way as accessing FileMaker Server under normal networking conditions. For more information, see Opening shared files as a client in chapter 5 of the FileMaker Pro User s Guide. Note FileMaker Server should not be installed on the same machine with Windows Server 2003 Terminal Services. FileMaker Pro feature issues Features not supported for Terminal Services clients: 1 FileMaker Network Sharing 1 Instant Web Publishing 1 ODBC/JDBC sharing 1 Third party plug-ins. Plug-in developers must test and certify their support for the plug-ins they supply to run under Terminal Services. FileMaker Knowledge Base articles Check the FileMaker Knowledge Base for articles regarding running FileMaker Pro on Windows Server 2003 Terminal Services. You can access the FileMaker Knowledge Base from

9 FileMaker, Inc. standard requirements Appendix A Standard requirements In order to use FileMaker Pro Worldwide English via Windows Server 2003 Terminal Services, you must purchase a Volume License Agreement (VLA) or a Site License (SLA). Retail packages of FileMaker Pro cannot be used with Terminal Services. Volume License Agreement (VLA) The FileMaker VLA is a transactional agreement that grants you the right to use the software on as many computers as are listed on your License Agreement. For information about the VLA, see Site License Agreement (SLA) The FileMaker SLA allows for any combination of FileMaker Pro, FileMaker Pro Advanced, FileMaker Server, FileMaker Server Advanced and FileMaker Mobile to be installed anywhere in your organization of 50 or more employees or computers. For more information on licenses, please call (weekends and holidays excluded). See for details. Windows Server 2003 and Terminal Services license requirements For information about licensing requirements for Windows Server 2003 and Terminal Services, see