Silent Install - iTivity User Guide

iTivity™ User Guide

Appendix A: Using Silent Install for Automated Installation

The iTivity software components, iManager, iServer and iAgents are provided by Tridia as standard MSI installers. You can use the MSI command line parameters and public properties to create a customized, silent installation. With silent install, you do not need to monitor the installation process and provide input through dialog boxes. Instead, all of the input data is passed to the installer via the command line. The easiest way to take advantage of the custom, silent installation is to create a custom installer on the Tridia support web site. See Appendix B, Creating Custom Installers for more information.

The rest of this appendix describes how you can manually build installer command lines to meet the deployment needs of your organization.

You can customize the installation for the following iTivity components on Windows platforms:

· iServer

· iTivity iManager

· Attended iAgent

· Unattended iAgent.

Command Line Options (Parameters) for msiexec

The following command line options or parameters apply to all MSI installers when invoked by "msiexec". For this reason, you can use these options with all of the iTivity installers.

/i <package.msi>	Install the MSI package.
/passive	Unattended mode. Installer only displays a progress bar.
/qn	Silent installation of the package with no user interface presented.
/qf	Provides a full user interface for the installation.
<PROPERTY>=<value>	Provides a value or setting for the indicated public PROPERTY.

Using these command line options or parameters in conjunction with the public properties for the individual installers, you can create custom, automated installations for your organization. Here are some examples of automating the iTivity software deployment using the msiexec.exe command line.

1. Install the Unattended iAgent with only the progress bar displayed and selecting Active Directory authentication and the iServer.

msiexec.exe /I iTivityUnattendediAgent.msi /passive AUTHENTICATION=ntlm CGRP1NAME="AcmeSoft iServer" CGRP1NAME=iserver.acmesoft.com CGRP1PORTS=23800

2. Install the iManager into a custom installation directory.

msiexec.exe /I iTivityiManager.msi /passive INSTALLDIR="C:\Program Files\AcmeSoft\" AUTOISERVER="iserver.acmesoft.com:25800"

3. Install the Attended iAgent with full user interface interaction and public certificate URL.

msiexec.exe /I iTivityAttendediAgent.msi /qf AUTHENTICATION=none PROMPTNAME=1 CONFIRMCONN=1 PUBCERTURL="http://iserver.acmesoft.com/4c6eac17.0" CGRP1NAME="AcmeSoft iServer" CGRP1NAME=iserver.acmesoft.com CGRP1PORTS=23800

iServer Public MSI Properties

The following public properties are recognized by the iServer MSI installer from Tridia.

Note: You should specify the IAGENTPORT and IMANAGERPORT for any silent installation of the iServer. The PERMISSIONGROUP will default to "iTivityServerUsers" unless you specify a different value.

AUTHENTICATION=<ntlm/none>	Authentication method for access to the iServer.
HOSTNAME=<computer-name>	Name of the iServer system to display in the iManager.
HOSTDESC=<computer-description>	Description of the iServer system.
IAGENTPORT=<iagent-port>	The iServer port number for iAgent connections.
IMANAGERPORT=<imanager-port>	The iServer port number for iManager connections.
INSTALLDIR=<install-directory>	Target installation directory for the iServer software.
LAUNCHISERVER=<0/1>	Flag indicating whether to launch the iServer at the end of the installation.
PERMISSIONGROUP=<ad-ntlm-group>	AD/ntlm security group granting access permission to the iServer.
REGURL=<registry-file>	URL of a valid registry file to apply with iServer settings.

iManager Public MSI Properties

The following public properties are recognized by the iManager MSI installer from Tridia.

Note: All of these settings have reasonable defaults. If you do not want the iManager to automatically connect to any specific iServer, then do not specify AUTOISERVER.

AUTOISERVER=<iservername:port>	Automatically connect to the iServer at iservername:port when the iManager starts.
HOSTNAME=<computer-name>	Name of the iManager system.
HOSTDESC=<computer-description>	Description of the iManager system.
INSTALLDIR=<install-directory>	Target installation directory for the iManager software.
PROMPTFORREASON=<0/1>	Flag indicating whether to prompt the iManager user for a connect reason.
REGURL=<registry-file>	URL of a valid registry file to apply with iServer settings.
SUPPORTDOMAIN=<support-domain-list>	Support domain(s), if any, where the iManager user is authorized for access. Separate multiple entries with a comma.
VERIFYCERTS=<0/1>	Flag indicating whether the iManager should verify encryption certificates.

Unattended iAgent Public MSI Properties

The following public properties are recognized by the Unattended iAgent MSI installer from Tridia.

Note: You should specify a hostname and port number for connection group one. Connection groups two and three are optional and should only be used for access from different iServers. Please note that the connection group one settings override the legacy ISERVER and PORT settings.

AUTHENTICATION=<ntlm/none>	Authentication method for access to the Unattended iAgent. This authentication stage is applied in addition to the authentication configured at the iServer. In some environments, it may make sense to disable the iAgent stage authentication ("none")and rely on the iServer authentication.
CGRP1NAME=<group-one-name>	Display name for connection group one.
CGRP1HOSTS=<group-one-hosts>	One or more iServer hostnames (or IPs) for connection group one (comma separated)..
CGRP1PORTS=<group-one-ports>	One or more iServer port numbers for connection group one (comma separated).
CGRP2NAME=<group-two-name>	Display name for connection group two.
CGRP2HOSTS=<group-two-hosts>	One or more iServer hostnames (or IPs) for connection group two (comma separated)..
CGRP2PORTS=<group-two-ports>	One or more iServer port numbers for connection group two (comma separated).
CGRP3NAME=<group-three-name>	Display name for connection group three.
CGRP3HOSTS=<group-three-hosts>	One or more iServer hostnames (or IPs) for connection group three (comma separated)..
CGRP3PORTS=<group-three-ports>	One or more iServer port numbers for connection group three (comma separated).
HOSTNAME=<computer-name>	Name of the iAgent system to display in the iManager.
HOSTDESC=<computer-description>	Description of the iAgent system.
ICONURL=<icon-file>	URL of a valid icon file (*.ico).
ISERVER=<iserver-hostname>	The hostname or IP address for the iServer.
INSTALLDIR=<install-directory>	Target installation directory for the Unattended iAgent software.
PERMISSIONGROUP=<ad-ntlm-group>	AD/ntlm security group granting access permission to the iAgent.
PORT=<iserver-port>	The iServer port number for iAgent connections.
PUBCERTURL=<public-certificate>	URL of the iServer public key certificate, renamed to the fingerprint hash value (1234abcd.0).
REGURL=<registry-file>	URL of a valid registry file to apply with iAgent settings.
SUPPORTDOMAIN=<support-domain-list>	Support domain(s), if any, where the iAgent system should be visible and accessible. Separate multiple entries with a comma.
VERIFYCERTS=<0/1>	Flag indicating whether the iAgent should verify encryption certificates.

Attended iAgent Public MSI Properties

The following public properties are recognized by the Attended iAgent MSI installer from Tridia.

AUTHENTICATION=<ntlm/none>	Authentication method for access to the Attended iAgent. This authentication stage is applied in addition to the authentication configured at the iServer. In some environments, it may make sense to disable the iAgent stage authentication ("none")and rely on the iServer authentication.
CGRP1NAME=<group-one-name>	Display name for connection group one.
CGRP1HOSTS=<group-one-hosts>	One or more iServer hostnames (or IPs) for connection group one (comma separated)..
CGRP1PORTS=<group-one-ports>	One or more iServer port numbers for connection group one (comma separated).
CGRP2NAME=<group-two-name>	Display name for connection group two.
CGRP2HOSTS=<group-two-hosts>	One or more iServer hostnames (or IPs) for connection group two (comma separated)..
CGRP2PORTS=<group-two-ports>	One or more iServer port numbers for connection group two (comma separated).
CGRP3NAME=<group-three-name>	Display name for connection group three.
CGRP3HOSTS=<group-three-hosts>	One or more iServer hostnames (or IPs) for connection group three (comma separated)..
CGRP3PORTS=<group-three-ports>	One or more iServer port numbers for connection group three (comma separated).
HOSTNAME=<computer-name>	Name of the iAgent system to display in the iManager.
HOSTDESC=<computer-description>	Description of the iAgent system.
ICONURL=<icon-file>	URL of a valid icon file (*.ico).
ISERVER=<iserver-hostname>	The hostname or IP address for the iServer.
INSTALLDIR=<install-directory>	Target installation directory for the Attended iAgent software.
PERMISSIONGROUP=<ad-ntlm-group>	AD/ntlm security group granting access permission to the iAgent.
PORT=<iserver-port>	The iServer port number for iAgent connections.
PUBCERTURL=<public-certificate>	URL of the iServer public key certificate, renamed to the fingerprint hash value (1234abcd.0).
REGURL=<registry-file>	URL of a valid registry file to apply with iAgent settings.
SUPPORTDOMAIN=<support-domain-list>	Support domain(s), if any, where the iAgent system should be visible and accessible. Separate multiple entries with a comma.
VERIFYCERTS=<0/1>	Flag indicating whether the iAgent should verify encryption certificates.

Table of Contents

webmaster@tridia.com
sales@tridia.com
Technical Support