Installation Guide
Installation Guide
Version 7.6
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Installation Guide
© Copyright Schneider Automation SAS 2005.
All rights reserved. This document may not be reproduced or copied in whole or in
part, in any form or by any means, either graphic, electronic, or mechanical, including
photocopying, recording, or storage in a retrieval system.
Apart from the creation of a back-up copy for the exclusive use of the purchaser, this
software may not be duplicated, reproduced, or copied in any form or by any means
whatsoever. Modification or adaptation of the software is forbidden.
This guide provides the installation requirements and step-by-step instructions for
installing Monitor Pro 7.6 on Microsoft Windows XP and Windows 2000 platforms.
The material in this guide is presented in the preferred installation order.
S YSTEM R EQUIREMENTS
The following minimum hardware and software requirements are recommended for
Monitor Pro 7.6. While the Monitor Pro software will run on the minimum hardware
requirements, for some larger, more complex systems, these requirements may not be
adequate for satisfactory performance.
Hardware Software
Pentium III 500 MHz CPU Supported Microsoft platforms:
(1 GHz recommended) • Windows 2000 Professional SP4
256 MB RAM
• Windows XP Professional SP2
(512 MB recommended)
• Windows 2000 Server SP4
2 GB Hard Drive or larger
(20 GB recommended) • Windows Server 2003 SP1
(If using SQL Server and storing large Note: Windows XP or 2000
quantities of historical data, a larger hard Professional (supports up to 5 clients)
drive is recommended.)
Windows 2000 Server or Server 2003
(for more than 5 clients)
1 GB Hard Drive or larger TCP/IP network protocol
(for a Monitor Pro client)
(10 GB recommended)
CD-ROM drive Internet Explorer 6 SP1
Monitor (1024 x 768 resolution) Adobe Reader 5.0 or higher
Keyboard and Mouse
Because it is impossible to define the exact requirements for each system due to the
flexibility and scalability of Monitor Pro and other layered software involved, use the
following guidelines to help you determine the best estimate of system requirements.
Your exact requirements may be somewhat less or more than what is stated in the
following tables.
The general hardware recommendations for a Monitor Pro client are as follows:
If you are installing SQL Server on the same machine as the Monitor Pro server for
production systems, use a dual processor Pentium and increase the memory by at least
64 MB RAM. For additional information on SQL Server 2000 requirements, search
the Microsoft online MSDN Library at http://msdn.microsoft.com/library.
I NSTALLATION CD S
The Monitor Pro shipping package includes Exhibit A, which contains your serial
number and configuration sequence, and the following CDs:
CD Description
Monitor Pro 7.6 Contents:
• Monitor Pro Installation (server and client)
• OPC Factory Server (OFS)
Contains the OFS product, which is a multi-controller
data server capable of communicating with PLCs of the
TSX Compact, TSX Micro, TSX Momentum,
TSX/PCX/PMX Premium, TSX Quantum, TSX Series
7, and TSX S1000 families in order to supply OPC
clients with data. OFS provides Monitor Pro
applications with a group of services (methods) for
access to control systems variables.
• Documentation and Release Notes
• Adobe Reader
Microsoft SQL Server 2000 If is recommended that you install SQL Server 2000 before
• Standard Edition installing Monitor Pro. Choose a SQL Server version, based
on the following guidelines:
• Personal Edition
• If you are running Monitor Pro on Windows 2000
Server or Server 2003, install Microsoft SQL Server
2000 Standard Edition.
• If you are running Microsoft Windows XP Professional
or 2000 Professional, install Microsoft SQL Server
2000 Personal Edition.
The SQL Server Personal Edition differs from the Standard
Edition in the following ways:
• Cannot use more than 256 MB of system memory
• Limited in the number of processors it can support
• Limited in the number of users that can connect. The
Personal Edition supports only 5 connections; more
connections are allowed, but performance is severely
degraded.
• Limited to 2 GB database size
CD Description
Microsoft SQL Server 2000 Contains Microsoft SQL Server 2000 SP4. Install this
SP4 service pack after you install Microsoft SQL Server 2000.
XWAY Drivers Contains the XWAY communication drivers documentation.
TECHNICAL S UPPORT
If you have any questions about the use or application of the Monitor Pro product,
contact your local country Schneider Electric representative.
It is recommended that you use Microsoft SQL Server 2000 as the primary database.
You also need SQL Server if you want to use it as the database for the Examples
Application that you can install with the Monitor Pro software. It is recommended that
you install SQL Server 2000 before installing Monitor Pro. SQL Server is not required
on the same computer as Monitor Pro.
1 For the Standard Edition only, contact your system administrator for the appropriate
licensing mode information (either per seat or per processor). You will need this
information during the installation.
2 Insert the Microsoft SQL Server 2000 CD into the CD-ROM drive. If the Installation
wizard does not automatically start, navigate to the root of the appropriate SQL Server
2000 CD and double-click setup.bat.
3 When the opening screen appears, select SQL Server 2000 Components, and then select
Install Database Server.
4 When the Welcome screen appears, click Next and follow the instructions on the
screen to install the database server.
Important Notes
• Your license key is in Exhibit A, included with the Monitor Pro shipping package.
• Use the SQL Server 2000 Standard Edition CD for running Monitor Pro on
Windows 2000 Server or Server 2003. Use the Personal Edition CD for running
Windows XP Professional or 2000 Professional.
• Throughout the wizard, accept the default settings. The screens requiring
different settings are as follows:
Services Account screen – Select Use the same account for each service. Then, select
Use the Local System account.
Authentication Mode screen – Select Mixed Mode (Windows Authentication and SQL
Server Authentication) and select Blank Password. (If you want to enter a password,
you will need to configure the Examples Application to use a password.
Currently, the Examples Application has a blank password.)
• After the Start Copying Files screen, the installation automatically begins
installing SQL Server 2000 for the Personal Edition.
For the Standard Edition, the Choose Licensing Mode screen appears. When
using the Per Seat license provided by Schneider Electric, select Per Seat and enter
the number of Monitor Pro CALs in the Seat Count field to begin installing SQL
Server 2000. (The total number of SQL CALs installed = Monitor Pro
Development CALS + Monitor Pro Run-time CALs.)
5 Insert the Microsoft SQL Server 2000 SP4 CD into the CD-ROM drive and follow the
instructions on the screen. After you install both SQL Server and SP4, restart your
computer. When your computer restarts, an instance of SQL Server starts.
After you install Microsoft SQL Server 2000, you need to set a maximum memory
limit to prevent SQL Server from consuming all the memory available to it and to
ensure the operation and speed of Monitor Pro tasks. For reporting functions, you
need to set the user language selection to match the language of the operating system.
1 Click Start > Programs > Microsoft SQL Server > Enterprise Manager.
2 In the Console Root window, navigate to SQL Server Group folder. Right-click your host
server name and select Properties.
3 In the SQL Server Properties (Configure) dialog box, click Memory tab. Click Use a
fixed memory size (MB) and use the slider to set the Microsoft recommended memory
size in the range of 40 to 80 MB, depending on your system’s RAM and virtual
memory size. Click OK.
4 To set the SQL Server user language to match the language of the operating system,
expand “your SQL Server” to the Security folder. Click Logins. Right-click the user and
select Properties. On the General tab, click the Language arrow and select the language
for the operating system. Click OK.
2 Ensure that you have administrator rights on the computer where you are installing
and close all running applications.
3 If using Microsoft SQL Server 2000 for your default database, ensure it is installed
before you install Monitor Pro. See “Installing Microsoft SQL Server 2000” on page 9
for SQL Server installation instructions.
4 Ensure that Microsoft Networking Services for TCP/IP is installed and running
properly.
Monitor Pro requires that a network adapter and Microsoft networking services be
installed and running even if you do not plan to connect your Monitor Pro system to a
network. If the computer has a network card, go to step 5. If not, install the Microsoft
Loopback Adapter:
Windows XP
a Click Start > Control Panel. Click Add Hardware and click Next.
b Select Yes, I have already connected the hardware and click Next.
c From the Installed hardware list, select Add a new hardware device and click Next.
d Select Install the hardware that I manually select from a list and click Next.
e From the Common hardware types list, select Network Adapters and click Next.
f From the Manufacturer list, select Microsoft. From the Network Adapter list, select
Microsoft Loopback Adapter. Click Next.
Windows 2000
a Select Start > Settings > Control Panel. Double-click Add/Remove Hardware and click
Next.
d Select No, I want to select the hardware from a list and click Next.
e From the Hardware types list, select Network adapters and click Next.
f From the Manufacturer list, select Microsoft. From the Network Adapter list, select
Microsoft Loopback Adapter. Click Next.
5 Ensure Media Sense is disabled to prevent the disabling of your network services
when you are not connected to a network.
You can disable Media Sense automatically using the NetWiz.exe utility, located on the
Monitor Pro CD.
If you are fully qualified to edit the Windows operating system registry, you can
disable Media Sense manually using the Registry Editor:
a Use the Registry Editor (regedt32.exe) to view the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\P
arameters
b Add this Registry value:
b On each Monitor Pro client, add the IP address and computer name of all the
Monitor Pro servers to its Windows hosts file.
If you experience Monitor Pro client connection problems and you have a DNS server,
it is recommended that you put the Monitor Pro server(s) IP address and computer
name in the Windows hosts file on each Monitor Pro client computer. If all your
Monitor Pro computers have static IP address, perform the steps above.
7 Uninstall any older version of Monitor Pro in the destination where you plan to install
the software. During the installation, if Monitor Pro detects a previously installed
version in the destination folder, you will receive a prompt to remove that version.
8 If you are in a workgroup (not a domain) and installing Monitor Pro on Windows XP
Professional, disable “simple file sharing” to avoid network access problems:
a Double-click My Computer on your desktop.
c When the Folder Options dialog box opens, click the View tab.
Under Advanced Settings, you will see a check mark in the Use simple file sharing
(Recommended) check box, which indicates that simple file sharing is enabled.
d Clear the check box and click OK to disable the simple file sharing feature.
9 Close the Settings > Control Panel > Administrative Tools > Services dialog box before
beginning the installation to prevent interference with the installation process.
10 Ensure that you have Exhibit A from your shipping package.
I NSTALLING M ONITOR P RO
After performing the preparation on page 11, you are ready to install Monitor Pro.
Note: To install Monitor Pro on a Terminal Server, click Start > Settings >
Control Panel > Add/Remove Programs to run the installation program.
Note: If the installation does not begin automatically, go to the CD’s Install
folder and run setup.exe. Select the desired setup language, English (default),
French, or German, and then click OK. Continue with step 2.
a When the Monitor Pro 7.6 screen appears, select the desired setup language:
English (default), French, or German.
b Click Release Notes to view last-minute instructions that might affect the
installation procedure and for other general information.
c Click Installation. (The installation program installs the Windows Installer if it is not
already installed on the machine.)
2 When the Welcome screen appears, click Next. Read the license agreement and click
Yes to accept the agreement terms.
3 On the Setup Type screen, choose what you want to install and where to install it:
Monitor Pro System Select this option to install the client and server on the
same machine.
By default, the Install OFS with Monitor Pro System check box
is selected. Clear this check box if OFS is already installed.
Monitor Pro Client Select this option to install the client only.
OPC Factory Server Select this option to install the OFS components (OFS,
Standalone (OFS) OFS Remote, Configuration Tool) only.
To select another destination drive rather than the default folder C:\Program
Files\Telemecanique, use the Browse button. Be sure the drive has at least 100 MB of
space for backup files.
4 Click Next. Depending on the option selected in step 3, do the following action:
Monitor Pro System Continue with the following procedure for this option.
Monitor Pro Client Go to page 19.
OPC Factory Server Go to page 19.
Standalone (OFS)
Note: To use a database other than these options (such as Oracle), select
dBase4 to install the default dBase4 Examples Application. You will need to
use the Configuration Explorer to configure the appropriate tables to modify
the default Examples Application for your database.
• If you select SQL Server, continue with step 4.
• If you select dBase4, go to step 5 to start copying files.
4 On the Create Database for SQL Server screen, enter the requested SQL Server
connection information and click Next.
5 On the Start Copying Files screen, review the settings. To change any settings, click
Back. If you are satisfied with the settings, click Next. General information about the
progress of the installation displays.
Note: If you selected the check box to install OFS and OFS is already
installed, you will receive a message stating the component is already
installed and that it will not be reinstalled. Click OK to continue.
6 When the installation finishes, the License Wizard opens with Enter Serial Number and
Configuration Sequence selected. Click Next.
7 Enter the serial number and configuration sequence provided in Exhibit A of your
Monitor Pro shipping package.
Tip: Any incomplete or inaccurate information displays in red.
8 If you need to designate the hardware device where you want the license assigned,
click Advanced. (For example, if using a Redundant Array of Independent Disks
(RAID) configuration, you would assign the license to a network card.) When the
Hardware Selection dialog box opens, select either Hard Drive (default) or Network Card
and then click OK.
9 When the license information is entered correctly, click Next.
10 Make a note of the automatically generated registration code, which you will need
later to authorize your Monitor Pro system. Click Later.
11 Click OK when the grace period notification message appears.
Note: The grace period is 10 days. You must authorize the software before
the grace period ends to continue using Monitor Pro.
12 Click Yes to start the DCOMWiz utility that sets the domain and account under which
the Monitor Pro DCOM components will run.
This utility assures proper communication between the Monitor Pro server and its
clients. It is recommended that you run the utility. You must run the DCOMWiz
utility if your Monitor Pro server is running on Windows XP as a web server.
13 Read the DCOMWiz message and then do one of these actions:
• Click Cancel if your network security requires you to manually configure the
DCOM settings. Then, use DCOMCnfg to set the permissions for the DCOM
components. (To see the DCOMCnfg properties, click Start > Run. Type dcomcnfg in
the Open field and click OK.)
14 On the Account Info screen, enter the account information that will be used to start the
server. Use the following examples and notes to help you set this information. (The
user name needs to have local Administrator or Power User rights on the computer.)
After you finish entering the information, click OK.
In a Domain
Domain for the company
In a Workgroup
Must leave blank for workgroups
Important Notes
• A typical configuration uses one account on the server and various accounts on
client machines. This is the account that the DCOM components will run under.
• If using various accounts to start the Monitor Pro server, you can start the
application by using the Configuration Explorer or the FLAutoStart service.
Using FLRUN while logged in as a different user will not allow most DCOM
connections (such as OPC used by the Client Builder) to work properly.
• If using workgroups with multiple accounts, select the Advanced check box and
enter the name of an account group in the Group field to allow access by
members of that group to the Monitor Pro DCOM components. However,
nothing is added to the group; the system administrator must add members to the
group. Note, the Administrator/Power User specified in the Username field must
be a member of that group.
• If using workgroups instead of domains in your network, leave the Domain field
blank. When you click OK, a message displays, “By not specifying a domain,
workgroup-mode is assumed. In this case, you must use the same account and
password on all clients and servers.” Click OK.
• By default, Windows XP and later systems do not allow the use of non-domain
accounts with blank passwords for network access. If you are running in a
workgroup configuration on Windows XP or later, the account specified in
DCOMWiz must have a non-blank password.
• When the Advanced check box is selected, the Group field appears with the name
of the group that is granted DCOM access rights. In domain mode, the default is
domain\domain user. In workgroup mode, the default is a blank field, meaning
only the specified user is granted access. You can change the default value to
allow DCOMWiz to grant access to any group, thus allowing flexibility in
configuring accounts and access. Note, the Administrator/Power User specified
in the Username field must be a member of that group.
• For cross-domain access, consult your systems administrator.
For clients and servers to exist in different domains, the network administrator
must establish a mutual trust relationship between them. A trust relationship is a
link between two domains that allows a user with an account in one domain to
have access to the resources of another domain.
For more information, refer to your Microsoft Windows user manual or search
the Microsoft online MSDN Library at http://msdn.microsoft.com/library.
15 After seeing the “DCOM permissions have now been set” message, click OK and then
click Finish.
16 Before removing the Monitor Pro CD, if you do not already have Adobe Reader
installed, run the file appropriate for your language (English, French, or German) from
the Adobe folder on the CD. (You need a PDF reader to view the documentation.)
OFS Installation
1 On the Start Copying Files screen, review the settings. To change any settings, click
Back. If you are satisfied with the settings, click Next. General information about the
progress of the installation displays.
2 When the installation finishes, click Finish.
A UTHORIZING M ONITOR P RO
During the installation, you entered the serial number and configuration sequence
provided in Exhibit A of your Monitor Pro shipping package. At that time, Monitor
Pro automatically generated a registration number that you need to obtain an
authorization code for your system.
Look at the Exhibit A and enter the Web address provided. Submit the appropriate
registration information to obtain your authorization code. You will receive your
authorization code at the e-mail address you provide.
1 Click Start > Programs > Monitor Pro > License Wizard. (The Monitor Pro License Wizard
opens with Authorize Your System selected.) Click Next.
2 Enter your authorization code and the licensed company name. (This information
must match the registered information provided in the e-mail message you received.)
Note: Any incomplete or inaccurate information displays in red.
3 When the information is entered correctly, the Finish button is enabled. Click Finish.
4 After the Your system is licensed and authorized message appears, click OK.
2 Select Telemecanique, Monitor Pro Version 7.6 from the currently installed programs list
and click Change/Remove.
3 When the installation wizard opens, select Modify and click Next.
4 Select only the desired option you want to install. Click Next and follow the
instructions on the screen.
Note: When the installation program states it cannot find a file, insert the
Monitor Pro CD.
1 If Microsoft Access or the Access RunTime Viewer is not installed, use Windows
Explorer to browse to the Installs shared folder on your Monitor Pro server. Open the
Microsoft Access 2003 Runtime folder and double-click ACCESSRT.MSI. When the wizard
appears, click Next. Then, follow the instructions on the screen.
2 In Windows Explorer, browse to the Applications shared folder on your Monitor Pro
server. Open the Historical Reports folder and double-click Historical Reports.adp.
1 If Microsoft Access or the Access RunTime Viewer is not installed, use Windows
Explorer to browse to the Installs shared folder on the machine where Monitor Pro is
installed. Open the Microsoft Access 2003 Runtime folder and double-click ACCESSRT.MSI.
When the wizard appears, click Next. Then, follow the instructions on the screen.
2 In Windows Explorer, browse to the Applications shared folder on the machine where
Monitor Pro is installed. Open the Historical Reports folder and double-click Historical
Reports.adp.
U NINSTALLING C OMPONENTS
1 From the Windows Control Panel, open the Add or Remove Programs component.
2 In the currently installed programs list, select the desired program, and click
Change/Remove.
3 When the installation wizard opens, select Remove and click Next. At the confirmation
message, click OK.
4 After the program is uninstalled, click Finish.
One-Click Client provides the capability to install a client on a remote system on the
LAN, WAN, or VPN to access Monitor Pro information.
Notes:
• One-Click Client is for run-time only. You cannot create or edit projects
and mimics in a run-time system.
• If an ActiveX control is used in a mimic that is not one of the Monitor
Pro-supplied ActiveX controls, you must install the control on each client
where you want to use it.
The One-Click Client utility has two primary modes of operation. The first mode is a
manual install method that guides a user on a client machine step-by-step through the
installation and application deployment process. The second mode, which uses the
Advanced button of the utility, is designed primarily for automating the steps of the
manual method into a custom install script that can then be used in conjunction with
the utility to completely automate the deployment process. In this mode, a user on a
remote machine only needs to click a single link, received in an e-mail for example, to
initiate the automated deployment process.
3 In the Remote Project Directory field, either enter the path or use the browse button to
select the shared folder on the server where the Client Builder project is located.
(Using a base folder allows for the selection of multiple projects.) Then, click Next.
4 In the Local Cache Directory field, either enter the path or use the browse button to select
the directory where you want to store the project files locally. (This directory is the
root directory for local copies of all project files. All project-related files will be
placed in a subdirectory of this directory.) Then, click Next.
5 In the Remote Projects list, select the remote projects you want copied to the client
machines. Use the arrow buttons to move items between the lists. (The single arrow
moves only the selected item, and the double arrow moves all items.) Then, click Next.
6 Click Install to begin installing the software and projects.
After the installation completes, a Client Builder icon and a shortcut icon for each
project you selected is placed on the desktop. The related project files are cached to
the local folder you specified in the wizard.
7 After the software and projects are installed, the License Utility automatically starts.
Add the name or IP address of you license server(s). For instructions about using the
license utility, see the Utilities Guide.
8 Click Finish.
C USTOM I NSTALLATION
The custom installation can be started from a client computer to allow the user more
control over the install process by clicking the Advanced button in the One-Click
wizard. Using the advanced mode on the server provides a more powerful tool. The
developer can create an install script that can be used to completely automate the
client and project deployment process.
2 When the wizard appears, click Advanced. The Client Builder Project Installation
window appears.
3 In the Remote Project Directory field, enter the shared folder on the server where the
Client Builder project is located as a UNC path, such as \\MyServerName\SharedFolder.
Using a base folder, such as \\MyServerName\Applications, allows for the selection of
multiple projects.
4 In the Local Cache Directory field, enter the directory where you want project files
locally stored on the client computer. This directory is the root directory for local
copies of the projects. Each cached project will be placed in a subdirectory of this
directory.
Note: This parent directory will be created on each client computer at
installation time; therefore, the drive letter specified must be one that exists
on all clients. For example, specifying Z:\MyAppCache is not a good choice if
the Z drive is not available to all clients.
5 In the Remote Projects list, select the remote projects you want copied to the client
computers and move them to the Local Projects list. Use the Add and Remove buttons
to move the projects between the lists.
Note: If projects do not appear in the Remote Projects list, click Refresh.
Directory where
the project files
are stored locally
on each client
Used from the Defines the actions Used from the client
client computer the installer performs Used to configure computer to install or
to copy or update when creating an the license servers reinstall the light weight
existing project files install script
Client Builder program files
a Select the Create Installation File on Exit check box and type a name for the install
script you want to build.
Note: The install script must be saved in the same folder with the
OneClick.exe and CBSetup.msi files.
b Leave the default check boxes selected. Then, click OK.
By default, Copy all project files is not selected. Only the .fvp file is copied to the
cache; the remaining files are copied as they are requested at run time. Selecting
this check box copies all project files and increases the client installation time.
7 Click License Setup. The License Client/Server Settings dialog box appears for you to
define the list of license servers that the clients will use. See the Utilities Guide for
instructions to configure the license server to use redundancy.
8 Click Done to create the custom install.
9 When the exit install procedure message appears, click Yes. The install script file is
created.
You can now install a client simply by using a link to the OneClick.exe file and
specifying the /i“install script” parameter. Clicking this link begins the installation.
Using a Link
1 From the remote computer, the operator or developer can click a link (like the
following example) to install the client. Note, this link can be sent in an e-mail
message.
\\MyServerName\Installs\OneClick.exe /iMyInstallScript.txt
After the link is clicked, the client is installed to the local computer. The installation
provides a progress bar. After the installation finishes, a Client Builder icon and a
shortcut icon for each of the selected projects appear on the desktop.
1 Create a shortcut to your one-click client by right-clicking the OneClick.exe file and
selecting Create Shortcut. Rename the shortcut to an appropriate name, such as
MyOneClickInstall (actual filename is MyOneClickInstall.lnk).
2 Right-click the shortcut you created and select Properties. In the Target field, add a
space and /i“install script filename” at the end of the path to the OneClick.exe. Then,
click OK.
Example: (Target field)
C:\Program Files\Telemecanique\FactoryLink\Installs\OneClick.exe /iMyInstallScript.txt
3 The Monitor Pro developer or manager sends an e-mail message that contains a link to
the one-click client shortcut to the operator.
\\MyServerName\Installs\MyOneClickInstall.lnk
4 The operator clicks the install shortcut, which installs the client to the local computer.
The installation provides a progress bar. After the installation finishes, a Client
Builder icon and a shortcut icon for each of the selected projects appear on the
desktop.
The following table describes each parameter and its possible values.
Note: The default values noted in the table are the settings generated the first
time you run the utility. Any values you change are retained in the install
script. The new defaults are those read from the last install script created.
Possible
Name Values Description
Possible
Name Values Description
remote UNC Path or The shared folder on the server where the Client
Builder application project is located. Entering a base
Mapped
folder where multiple projects reside allows you to
network drive
enter multiple project parameter/value pairs in this
script. See the “project” parameter description.
cache Local The cache directory is used to store project files
directory locally. The directory you specify becomes the root
directory for local copies of the projects. Each cached
project is placed in a subdirectory of this directory.
copyall 0 or 1 The utility inserts one “copyall” parameter before the
first project. However, the user can edit the file and
insert multiple “copyall” parameters. This parameter
remains in effect for any following projects up to the
next “copyall” specification. When “copyall” is set to
zero, only the project file is copied. When set to
non-zero, all files in the project are copied.
1 = Copy all
0 = Copy only the project file (default)
expandlib 0 or 1 Extracts the graphic objects used in the project from
the local library during install. This parameter is global
and must be set before any “project” statements.
1 = Extract (default)
0 = Do not Extract
autolic TRUE or Client automatically selects an alternate license server
FALSE when the primary server is unavailable when multiple
license servers are defined.
TRUE = Automatically choose (default when multiple
license servers are defined)
FALSE = Do not automatically choose (default when a
single license server is defined)
Possible
Name Values Description
licservers hostname/port The server host name and the port number that the
[,...] license server is listening for license requests by the
client. Multiple hostname/port values can be specified
using a comma separator.
project Remote A project parameter contains the path and name of the
parameter project file to be deployed to the remote client. The
relative path specified is relative to the value given in the
application “remote” parameter.
path
Note: Multiple projects can be specified but must
all be located underneath the directory indicated in
the remote parameter line.
S OFTWARE U PDATES
When a major upgrade is made to the server, you can run the OneClick.exe file again or
the custom script to automatically update the clients installed on the remote systems to
the latest version.