chapter 35 using terminal server - read.pudn.comread.pudn.com/downloads203/doc/954495/student...

154 Student Guide

35. Using Terminal Server _____________________________________

Chapter 35

Using Terminal Server

Copyright © 2001, Intellution, Inc. 35-1

Intellution Dynamics iFIX

35. Using Terminal Server ____________________________________ Section Objectives iFIX supports the use of Windows 2000 Terminal Services functionality. Terminal Services is a multi-session environment that provides remote computers access to Windows-based programs running on the server. In this section, the details of using iFIX with Terminal Services will be discussed.


154 Student Guide

35. Using Terminal Server ____________________________________

A. Overview

• iFIX supports the use of Windows 2000 Terminal Services functionality

• Terminal Services is a multi-session environment that provides remote computers access to Windows-based programs running on the server

• iFIX Terminal Server allows multiple clients to run individual instances of iFIX from one Server and one set of iFIX software

• Typically, an iFIX Terminal Server environment includes a Server, one or more iFIX SCADA nodes, and multiple clients

• Each thin client accesses applications on the Server by:

- connecting to the Terminal Server machine either through a locally installed .EXE (Full Client)

◊ OR

- through Internet Explorer v5.5 with Terminal Server Advanced Client.

◊ this allows very thin clients with minimal client-side resources to execute an individual instance of iFIX

B. Significant benefits of iFIX Terminal Server

• Reduced costs in installation and maintenance

- since iFIX Terminal Server serving up iClientTS software runs on one computer only, software needs to be installed just one time

- when upgrades are required, that is also done in that single location only

• Reduced implementation and management overhead

- manage projects and pictures from one location

• Reduced "size" and cost of client computers

- thin Clients can run a client session on smaller machines

• Multiple Platform support

- clients run on Windows 95, Windows 98, Windows Me, Windows NT, and Windows 2000




C. Methods to use Terminal Server

• Microsoft provides two connection methods for use with Terminal Server

- Terminal Services Advanced Client

- Full Client

• Terminal Services Advanced Client (TSAC)

- allows clients to log on to the Server through an Internet Explorer 5.0 browser

- The ActiveX Control (OCX) version

- no need to install any additional software, beyond the client requirements

• Full Client (TS – Terminal Server)

- requires the installation of an executable log on program directly onto the client machine to access iFIX from the Server

• Figure 35-1 compares these two methods

D. Design Considerations Prior to Implementation

• Before installing iFIX on a Windows 2000 Server machine, the Windows 2000 Terminal Server must be enabled and set up

• Consider iFIX Terminal Server limitations and software and licensing requirements

• Plan a sound network and security strategy, and user and machine naming conventions


154 Student Guide


Action

Standard iClient

Terminal Server with Internet Explorer 5

Requires software on client Yes No

iFIX Compatibility (Pictures/Schedules)

100% 100%

Picture Navigation Yes Yes

Tag Group Support Yes Yes

Write Access/Alarm ACK Yes Yes

Historical Charts Yes Yes

VBA Scripting Yes Yes

ActiveX Support Yes Yes

Configuration mode support Yes Yes

Color Support Unlimited 256

Client platforms supported Windows NT, 2000 Windows 95, 98, Me, NT, 2000

Runs in Browser No Yes, IE

iFIX Security Yes Yes

Environment Protection Yes No

Runs applications requiring NT Services

Yes No

Terminal Server platforms supported

N/A Windows 2000 Server

Number of clients talking to a SCADA node

Each client = 1 connection

Each client = 1 connection

Gets through firewalls Yes, 1 at a time, need to open up port 2010

Yes, need to open up port 3389

Figure 35-1: Comparison of iClient and iFIX Terminal Server




E. Software Requirements

• iFIX Terminal Server requires:

- Windows 2000 Server or Windows 2000 Advanced Server

- iFIX v2.5

• Full Clients require:

- Windows 95, Windows 98, Windows NT 4.0, Windows 2000, or Windows Me

- Terminal Server Client Software from Microsoft (Full Client)

• Terminal Services Advanced Clients (TSAC) require

- Windows 95, Windows 98, Windows NT 4.0, Windows 2000, or Windows Me

- Internet Explorer 5.0 or higher

- Terminal Server Advanced Client Software

- IIS Internet Information Server


154 Student Guide


F. Licensing Requirements for iFIX Terminal Server Client Machines

• Windows 2000 and Windows Me machines running as thin clients connecting to the Server already have a license built in to the machine

- when the client connects to the Server, the license from the client is used

- the first time the machine connects to the Server, that license is activated

• Machines with Windows 95, 98 or NT 4.0 need to have Windows 2000 Professional Licenses or TSCALs from Microsoft

- TSCAL - Terminal Services Client Access Licenses

• iFIX Terminal Server has a 90 day temporary license to run a maximum of ten client machines from the Server

- the first 10 Windows 9x and NT client machines connecting to the Server will reserve the licenses

• Important Notes:

- TSCAL are counted per machine and are not concurrent

- once a license is activates it is permanently associated with that machine

◊ rebooting the machine does not clear the license use




G. iFIX Terminal Server Limitations

• The Terminal Server machine must have Windows 2000 Server installed

- running iFIX on Windows NT 4.0 Terminal Server Edition is not supported

• SCADA nodes are not supported on the Terminal Server machine

• Terminal Server imposes a limit of 256 colors

• The iFIX node name must be the same as the SCU file name

• Terminal Server does not solve the iFIX limitation of 100 iClients connecting to a single SCADA node

• Running FIX32 and iFIX on the same machine is not supported within Terminal Server

• Advanced Historian collection is not supported in the Terminal Server environment

- use stand alone nodes networked to the Terminal Server environment for Advanced Historian Data Archiving

• Although Windows 2000 allows machine names of up to 15 characters, iFIX node names are limited to eight characters

• Running iFIX as an NT service under Terminal Server is not supported

• Running FIX Background Server as a service is not supported

• NETBIOS is not supported for connecting View (Terminal Server machine) to SCADA

- the Auto Alarm Manager is a NETBIOS application and is not available in the Terminal Server RDP TCP/IP environment.

• LAN Redundancy is not supported.

• Some keyboard shortcuts (such as Ctrl+ALT+DEL) are disabled or remapped

• Alarm printing at the client side is not supported

• User accounts must be created and accessed after installing iFIX


154 Student Guide


H. File Systems

• Windows 2000 Server provides three types of file systems for disk partitioning:

- NTFS, FAT, and FAT32

• Intellution recommends that you use NTFS with iFIX Terminal Server

- NTFS provides greater file-level security for users in a multi-session environment

I. Naming Conventions

• Intellution recommends that you follow a naming convention that provides a common naming scheme among the thin clients, the NT user, and the IP address

• Figure 35-2 shows examples of common naming schemes

• Benefits of Naming Conventions

- it is easier to locate and modify the correct SCU and user if they use the same name

◊ if the name includes the last octet of the IP address assigned to the SCU, networking and SCU issues are easier to locate and maintain

- using %username% in the launch command line

◊ this variable reduces the chance of errors in configuration

◊ the command line can be pasted into each user's start up properties, or a single desktop icon can be copied to All Users desktop

Location of client station

IP address for user on the Server

IP address for the Thin Client (if used)

User and Node name

Line 1 Station 1 10.0.0.150 10.0.0.250 L1S150

Line 1 Station 2 10.0.0.151 10.0.0.251 L1S151

Line 2 Station 1 10.0.0.152 10.0.0.252 L2S152

Figure 35-2: Common Naming Schemes




J. Implementing iFIX Terminal Server

• The Terminal Services functionality makes many configurations possible

- the architecture in Figure 35-3 shows a simple configuration

• Three machines are the minimum that would be required to demonstrate the delivery of an iFIX application using iFIX Terminal Server:

- SCADA Server node

◊ in this example it is iFIX on an NT Workstation

- Windows 2000 Server with Terminal Services enabled

- Client machine

◊ in this example we use a Windows 2000 Professional machine because it comes with a Terminal Server Client License

• The SCADA must be on a separate machine

- iFIX Terminal Server does not support SCADA functionality

• Must have special key for Terminal Server machine

• Setting up this environment can be grouped into these three general sets of tasks:

- Setting up Windows 2000 for Terminal Services

- Installing and Configuring iFIX on the Terminal Server machine

- Installing the Terminal Server Client on the Client machine


154 Student Guide


Figure 35-3: Sample Terminal Server Architecture



35.1. Setting up Windows 2000 for Terminal Services ______________

A. Enabling Windows 2000 Terminal Services

• To enable Terminal Services on a Windows 2000 Server machine:

- In the Control Panel, double-click the Add/Remove programs icon

- Click Add/Remove Windows Components

◊ The Windows Components Wizard opens

- Select the Terminal Services check box and click Next

◊ Terminal Services setup prompts you to choose a mode

- Select Application Server mode and click Next

◊ Terminal Services Setup prompts you to choose default permissions for application compatibility

- Select Compatible with Terminal 4.0 Users and click Next

- NOTE:

◊ in the next screen of the Terminal Services Setup, you may see programs listed that will not work correctly when Terminal Services is enabled

◊ you need to reinstall these programs for multi-session access using Add/Remove Programs after Terminal Services is enabled

- As the Setup begins to configure the Server, you are prompted to insert the Windows 2000 Server CD-ROM

- Click Finish to close the Windows Components Wizard

- Restart Windows 2000 Server before continuing

• NOTE:

- if you have already installed Service Pack 1 for Windows 2000, follow Microsoft's recommendation and documentation regarding reapplication of the service pack


154 Student Guide

35.1. Setting up Windows 2000 for Terminal Services ____________

B. Enabling Terminal Server Licensing

• Windows 2000 Server provides the Terminal Services Licensing administrative tool

• This tool enables the following:

- activate license servers

- install key packs

- track client license use

• To enable Terminal Server Licensing:

- In the Control Panel, double-click the Add/Remove Programs icon

- Click Add/Remove Windows Components

◊ the Windows Components Wizard opens

- Select Terminal Services Licensing in the Windows Components and click Next

◊ the Terminal Services Licensing Setup dialog box appears

- If your network includes several domains, select Your Entire Enterprise

- If your network includes Windows NT 4.0 domains, or if you want to maintain a separate license server for each domain, select Your Domain or Workgroup

C. Activating a License Server Through the Internet

• A license server stores all client licenses installed on a Terminal Server

- this provides a secure way of tracking the licenses that have been issued to Terminal Server clients

• You need to install the license server, activate it through the Microsoft Clearinghouse, and install license key packs onto the license server before issuing Terminal Server client licenses




D. Logging on to a Terminal Server Using Remote Desktop Protocol (RDP)

• After adding users to Windows 2000, follow these instructions to specify user access to Terminal Server from the Windows 2000 Server's Computer Management Console:

- From the Start Menu, select Programs - Administrative Tools

- Open the Computer Management Console

- Expand the Local Users and Groups options and click the Users folder from the System Tools tree

- Double-click the user you want to enable to log on as a Windows NT Terminal Server client

- Ensure that the Allow logon to Terminal Server check box is checked on the Terminal Server Profile tab

- Click OK

- Close the Computer Management Console

- From the Start Menu, select Programs - Administrative Tools

- Click Terminal Services Configuration

- Open the Connections folder

- Double-click RDP-TCP

- Add the users or groups that you want to grant permissions to the Terminal Server on the Permissions tab

◊ if you want to add users from the Domain, on the Permissions tab, add the users or groups that you want to have permission to this Terminal Server.

- Click OK to close the RDP-TCP Properties dialog box.

- Close the Terminal Services Configuration Console.

• If you configured a user to automatically start a specific iClientTS session, you must prevent that user from starting a second TS session

- multiple sessions running the same node name or running multiple node names on the same network can cause connection not established errors


154 Student Guide


E. Setting IP Addresses for Each Client

• Perform the following steps to set IP addresses for each client:

- from the Start Menu, select Settings - Network and Dial-up Connection

- Right-click Local Area Connection

- Select Properties from the right-click menu

◊ the Local Area Connections Properties dialog box appears

- Click Internet Protocol TCP/IP

- Click Properties

◊ the Internet Protocol (TCP/IP) Properties dialog box appears

- Select to Use the Following IP Address

- Enter the IP address of the Administrator account

- Click Advanced

- Click Add in the IP Addresses section

- Add an IP address for each client you want to connect

- Click OK to close the Advanced window

- Click OK to close the Internet Protocol (TCP/IP) window

- Click OK to close the Local Area Connection window



35.2. iFIX on the Terminal Server Machine _______________________

A. Once you have set up your Terminal Server, perform the following steps in order:

• Install iFIX on the Server

• Create a launch command that starts a unique node to test iFIX

• Configure the SCU

• Set up user accounts

• Configure SCU user accounts for iFIX

• Determine the types of user accounts and directories that need to be unique to users

• Create SCU files for each user

• Create a shortcut to Launch.exe for each user

B. Install iFIX on the Server

• Windows 2000 Server prevents you from installing iFIX directly from the CD

• Perform the following steps to set up Windows 2000 to install iFIX:

- Log on to the Terminal Server as a member of the machine's Admin group

- Double-click the Add/Remove Programs icon from the Control Panel

- Select Add New Programs

- Choose to add the new program from a CD or Floppy

- Insert the iFIX installation CD

- Click Next in the Install Program from the Floppy Disk or CD-ROM dialog

- Use the Browse button to find Setup.exe on the iFIX installation CD

- Double-click Setup.exe

- Click Next

◊ the Product Install dialog box prompts you to choose which product to install

- Click Install iFIX

- Continue through the installation and choose to restart the machine later

- Click Finish in the Add/Remove Programs dialog box

- Restart Windows 2000 Server.


154 Student Guide


C. Create a launch command that starts a unique node to test iFIX.

• Note: This same information will be used to perform this same step for all users later

• Creating a Shortcut to Launch.exe for Each User

- Launch.exe allows you to create a shortcut that brings up a specific SCU file from iFIX

• To save each user's shortcut in their LOCAL directory:

- Right-click the shortcut to open the Startup Properties dialog box

- Select the Shortcut tab

- In the Target edit field, enter the path and file name of the Launch program

◊ Example: C:\Dynamics\Launch.exe

- Append to this the command line parameters for the SCU file and the node name to use for the user's Terminal Server session

◊ The command line parameters /s<SCUpath> for SCU and /n<Nodename> for the node name

- For example:

◊ launch.exe /nView1 /s\Dynamics\View1\local\View1.SCU

- To use Launch with environment variables:

◊ launch.exe /s\Dynamics\%username%\local\%username%.SCU /n%username%

◊ If you use environment variables with the Launch shortcut, you only need to create one desktop icon for all users

◊ Place the shortcut with the environment variables in all users' desktop profiles

- Place the shortcut on the user's desktop

◊ do this by placing the shortcut in the user's LOCAL directory and then dragging it to the desktop

◊ the user can access it when logging onto the Terminal Server




D. Set up User Accounts

• Before setting up individual user configurations, save a copy of the following directories and their contents, if any, to a backup directory

- Dynamics\LOCAL

- Dynamics\ALM

- Dynamics\HTR

• These will serve as template directories when setting up individual users who require separate directories for their particular application of iFIX

• Before creating your user accounts, determine what types of users you need

- Which of your users will:

◊ Share the same preferences?

◊ Be able to configure their own HTA?

◊ Work with recipes?

◊ Develop pictures?

◊ Have development rights?

◊ Have run-time rights?

• Anticipating the needs of your users allows you to successfully determine the configuration of your user accounts

E. Configure SCU User Accounts for iFIX

• Configuring the paths for specific SCUs to provide enhanced or unique functionality per user, thin client, or group, should be well planned

• The design scheme for this type of implementation is similar to implementing the same scenario in a traditional environment (non TS) where SCU paths are using a mapped network drive on a file server

• Careful planning is needed to prevent multiple users from performing conflicting actions, such as downloading recipes or modifying database values

• Incorporating iFIX security to limit applications and area access in the Terminal Server environment is highly recommend


154 Student Guide


F. Determine the Types of User Accounts and Directories Unique to Users

• Intellution recommends that the following types of user accounts and directories be unique to users:

- Run Time Only

◊ share all directories except local

- Run Time with Historical Collection

◊ share all directories except LOCAL, and HTR

- Special Alarming Run Time

◊ share all directories except LOCAL and ALM.

- Development

◊ developers should have all unique directories except for NLS and the base path, which should always be shared

• If a user is allowed to configure HTA, you should configure a separate set of HTR and HTRDATA directories to prevent work in the HTA from being overwritten




G. Creating SCU Files for Each User

• To simplify the task of creating SCU files for each user, you can create a master SCU file that contains settings that most users or a group of users will use

- once this file is created, it can be edited and saved as a unique file for each user

• To create the master SCU file:

- Start the SCU on the Terminal Server machine

◊ a Terminal Server dialog box appears notifying you that the Local Startup dialog box in not available and that the node name and the SCU file name must be the same

- Click OK to close the dialog box

- The iFIX System Information dialog box appears, allowing you to select which SCU file you want to configure:

- Browse to locate the path of the appropriate SCU file

- Open the Network Configuration dialog box from the Configure menu.

- Select TCP/IP

- Click OK

◊ although the SCADA dialog box is accessible, SCADA is not supported under Terminal Server


154 Student Guide


G. Creating SCU Files for Each User (continued)

• To create the master SCU file (continued):

- Open the Task Configuration dialog box from the Configure menu

- In the Filename Edit field browse to the file \\...\Dynamics\Workspace.exe, select it, and click Open

- Click Add in the Task Configuration dialog box

- Verify that the Start Up Mode is set to Normal

- Click OK

- Select Save As from the File menu to save the master SCU

- Browse to find the appropriate save location of the SCU file

- Give the SCU file the same name as the iClient's node name

◊ IMPORTANT: The name of the SCU file must match the node name

- Click Save

- When prompted to use the newly saved SCU file when iFIX is re-started, click No




H. Setting up User Accounts For iFIX

• When setting up user accounts for iFIX, note the following distinctions in NT user types

- Desktop users can access the desktop and are allowed to run multiple applications

- Single Application users cannot access the desktop, have access only to a single application, and end their Terminal Server session when exiting the application

• To set up user accounts in iFIX:

- Create a directory for each user.

◊ Intellution recommends that these directories be set up under the Dynamics directory, though this is not a requirement

◊ For example, the directory for a user named VIEW1 can be set up as C:\Dynamics\View1, while a directory for a user named View2 can be C:\Dynamics\View2

◊ When naming these directories, keep in mind there is a 64-character limit for the path and names of the directories entered in the Path Configuration dialog in the SCU

- Copy the template directory LOCAL and any other required directories for the user to the user's directory.

◊ If the user's node will collect historical data, copy the HTR and HTRDATA directories to the user's directory

◊ If the user will exclusively use other directories, they should be set up in the user's directory at this time


154 Student Guide


I. Setting up a User's SCU File

• Follow the instructions below to set up a user's SCU file:

- Start the iFIX SCU on the Terminal Server machine

- Locate the Master.SCU file from the iFIX System Information dialog box

- Click OK

- Select Save As from the File Menu

- Give the SCU file the same name as the node name

◊ example: iRT101.SCU

- Save the SCU file to the user's LOCAL directory

- For user iRT101 the directory is C:\Dynamics\iRT101\Local

- Click Save

- When prompted to use the newly saved SCU file when iFIX is re-started, click No

J. Editing a User's SCU File

• Follow the steps below to edit a user's SCU file:

- Open the SCU Path Configuration from the Configure menu of the SCU

◊ If modifying the Alarm ODBC settings of the SCU, make sure that iFIX has started before opening the Security Configuration Utility

- Enter the appropriate path for the LOCAL and ALM directories created in the Setting up a User's SCU File section in the Path Configuration dialog

- For example, the paths for View1 would be entered as:

◊ Local: C:\Dynamics\View1\LOCAL

◊ ALM: C:\Dynamics\View1\ALM

- Repeat for any other user-specific directories

- Click OK




J. Editing a User's SCU File (continued)

• Follow the steps below to edit a user's SCU file (continued):

- Open the Network Configuration from the Configure menu

- Verify that TCP/IP is selected under Network

- Verify that the remote node name in the Remote Node Name edit field is correct

◊ If the remote node name is not correct, enter it in the Remote Node Name edit field and click Add

- Click the Advanced button

◊ the SCU cautions you not to modify these values unless you are familiar with the system

- Click Yes to continue

- Enable the path (IP address) under LAN Redundancy that this user will use and disable all other paths

- Do not select the Enable LAN Redundancy check box

- The IP addresses displayed in this list box are those that were set up previously by the Terminal Server Administrator. Verify that only the user's assigned unique IP address is enabled

- When finished, click OK to close the Advanced Network Configuration dialog

- Click OK to close the Network Configuration dialog

- Save the SCU file by selecting Save As from the File menu


154 Student Guide

35.3. Installing the Terminal Server Client________________________

A. There are 2 options available for iClient Access to Terminal Server:

• The Full Client, TS – Terminal Services

- this option requires you to install an executable logon program directly onto the client machine to access iFIX from the Server

• The ActiveX Control (OCX) version, TSAC– Terminal Services Advanced Client

- this allows your clients to log onto the Server through an Internet Explorer 5.0 browser

- you do not need to install any additional software beyond the client requirements.

B. Terminal Services Full Client:

• Notes

- Microsoft Windows 2000 Server provides a Client Creator program that allows you to create floppy disks for installing and distributing thin client software to each client machine

• Creating the Terminal Services Full Client Install Disk

- Log on to the Terminal Server machine

- Open Terminal Server Client Creator from the Administrative Tools folder in the Start Menu

◊ the Make Installation Disk dialog box appears

- Select the Terminal Services for 32-bit x86 Windows option from the Network client or service field

- Click OK

- Insert a blank, formatted disk and click OK

◊ this copies the Terminal Server Client installation software onto the floppy disk

- Click OK when the copy completes

- Close the Create Installation Disk dialog box

- Use the disk to directly install the files onto each client machine, or to share the installation files from the server




B. Terminal Services Full Client (continued):

• Follow the instructions below to install the Terminal Services Full Client software:

- Enter drive:setup at the Command Prompt and press enter

◊ Drive is the drive containing the Terminal Services Client disk or path

◊ the Terminal Services Client Setup dialog box appears

◊ NOTE: if you are installing the client on Windows 2000, use Add/Remove Programs to run the client within a client session

- Ensure that all other applications are closed and click OK

- Click Continue to begin setup

- Enter your full name in the Name field

- Enter the name of your organization in the Organization field

- Click OK

- Proceed through the license agreement

- Begin installation in the Terminal Services Client Setup dialog box

- Ensure that the installation path is correct

- Click the large setup button

- The Terminal Services Client Setup asks if you want all Terminal Services users of this computer to have the same initial settings:

◊ Click Yes to install the client software for all users of the computer.

◊ Click No to install the client software for only the current user.

- Select a Program Group from the list in the Choose Program Group dialog box or enter the name of a new Program Group

◊ NOTE: if you are installing the Full Client on a Windows 2000 machine, you may not see this dialog box

- Click Continue

- Click OK in the Terminal Services Client Setup dialog box to complete the installation


154 Student Guide


C. Terminal Services Advanced Client (TSAC):

• TSAC provides an ActiveX Client Control that allows thin clients to log onto the Terminal Server through an Internet Explorer 5.0 or higher browser

• To run TSAC, you must download the ActiveX Client Control from the Microsoft Website onto a Windows 2000 Server with IIS enabled

- IIS - Internet Information Server - http://www.microsoft.com/windows2000/downloads/recommended/TSAC/default.asp

• The download provides a set of sample default and connection pages that enable you to create a Terminal Server web connection

- preserve the sample files for troubleshooting TSAC issues

• To install the ActiveX Client Control with sample web pages on the client:

- Download the files onto the Server from the Microsoft web site

- Select Web Package from the drop-down menu and click Next

- Select the appropriate Language version and click Next

- Proceed through the license agreement

- Run the self-extracting executable file Tcwebsetup.exe

- Click Yes when prompted to install the Web Client Package

- Accept the defaults for the sample web pages directory

- The ActiveX control, sample web pages, and the associated documentation are installed to the TSWeb folder in the Inetpub\www root directory




C. Terminal Services Advanced Client (continued):

• To connect to the iFIX Terminal Server machine using the OCX client:

- Start Internet Explorer 5.0.

- Enter the URL, http://machinename/tsweb.

◊ For example, http://View1/tsweb

◊ NOTE: You can use either the machine name or the machine IP address when connecting to the Terminal Server.

◊ If you use the IP address, you may not be able to open the session in Full Screen

- Enter the IP address or the Server Name in the Server Name field

- Choose a screen size

- Choose to Send Logon information

- Enter the username you want to connect as

◊ NOTE: Multiple users cannot log on using the same account.

- Enter the Server machine name in the domain field.

- Click connect.

◊ The Windows 2000 log on screen appears

◊ If you have set up user accounts and passwords, enter them here


154 Student Guide


C. Terminal Services Advanced Client (continued):

• Additional Notes

- If you configured the user account with the application startup command, iFIX starts automatically

◊ if you did not configure the user account to auto launch, use the Launch icon to start iFIX

◊ do not use the iFIX Startup icon

- When attempting to connect through IIS and the TSAC OCX, if the ActiveX Client Control is not found on the client computer, or if an older version of the control is found, it will be installed at this time

◊ a dialog box may appear that asks if you want to install the control. If prompted, click Yes.

- If the Full Screen option is not available at connect time due to security limitations, you can access it after connection by pressing Ctl+Alt+Pause

- When the log on screen opens, you can create a shortcut to this page by making it a Favorite in Internet Explorer

◊ adding it to your Favorites list allows you to initiate future connections by clicking on the shortcut




this page intentionally contains no data


chapter 35 using terminal server - read.pudn.comread.pudn.com/downloads203/doc/954495/student...

Documents