Overview
Remote Install of Communications Suite V1.1

This help file describes how to remotely install Communications Suite V1.1 components using the Tivoli Software Distribution product, Courier.  Information and support for Courier is available on the Tivoli Web page (www.tivoli.com).  The product response files provided with this package can be used for Communications Suite V1.1 only.  The response files might not always work in your network environment.  You can use these response files or create your own.

Note:  If you already have a previous version of any of the Communications Suite components installed, you will need to generate a different response file.

The sample CDF files in the ecs11tivoli.exe package were created using Courier 3.0.

Netscape Navigator and plug-ins

Personal Communications

FTP Software

Lotus Notes Mail Client

Microsoft Internet Explorer

Debugging InstallShield Problems

Refer to Windows help if you are not familiar with creating folders (directories), subdirectories, or copying files.


Installing Netscape
Installing Netscape and Plug-ins

Before you begin

To perform a remote installation of Netscape Navigator and the plug-ins (this will perform a typical install):

1.	Copy the following Netscape and plug-in folders from the Communications Suite CD-ROM to a local or shared network drive:

\Netscape\nscape32
\Netscape\acrobt32
\Netscape\techex

2.	Copy the SETUPA.ISS file from the cs11tivoli.exe package to the netscape\acrobt32 folder and rename the file to SETUP.ISS.  This is the response file for Adobe Acrobat Reader.

3.	Copy the SETUPT.ISS file from the cs11tivoli package to the netscape\techex folder and rename the file to SETUP.ISS.  This is the response file for IBM techexplorer.

Steps

From the Tivoli Profile Manager:

1.	Create these profiles:

nscape32 - (Navigator)
acrobt32 - (Acrobat)
techex - (Techexplorer)

2.	Import the following files from the cs11tivoli.exe package into the appropriate Tivoli profile that you just created:  NSCAPE32.CDF, ACROBT32.CDF, and TECHEX.CDF.

3.	Edit the properties for each profile as necessary.

source host
source directory
destination directory path
destination directory path on after distribution command

4.	Distribute the nscape32 profile to the remote systems.  The nscape32 profile has acrobt32 and techex included in it so you do not need to run those profiles separately.  When the install is finished, remove the file package to free up space on the remote systems.


Installing Personal Communications

Before you begin

To perform a remote installation of Personal Communications (this will install Personal Communications only):

1.	Copy the PCOM folder from the Communications Suite CD-ROM to a local or shared network drive.

2.	Copy the MIN35.ISS file from the cs11tivoli.exe package to the PCOM folder.  This is the response file for Personal Communications.

Steps

From the Tivoli Profile Manager:

1.	Create a pcomm profile.

2.	Import the PCOMM.CDF file from the cs11tivoli.exe package into the pcomm profile.

3	Edit the properties for the pcomm profile as necessary.

source host
source directory
destination directory path
destination directory path on after distribution command

4	Distribute the pcomm profile to the remote systems.

5	When the install is finished, remove the file package to free up space on the remote systems.


Installing FTP Software

Note: The FTP Stack cannot  be installed on Windows NT systems.

To perform a remote install (this will perform a full install):

1.	Copy the FTP stack and application folders from the Communications Suite CD-ROM to a local or shared network drive.  The folders are \FTP\stack32 and \FTP\apps32.

2.	Copy the files STACK32.BAT and STACK.INF from the cs11tivoli package to the \FTP\stack32 directory.

3.	Copy the files FTP32.BAT and COMSUITE.INF from the cs11tivoli package to the \FTP\apps32 directory.

Steps

Note: The FTP Stack cannot be installed on Windows NT systems.

From the Tivoli Profile Manager:

1.	Create these profiles:

ftp-st  (FTP Stack)
ftp32  (FTP applications)

2.	Import the following files from the cs11tivoli.exe package into the appropriate Tivoli profile:  FTP-ST.CDF file and FTP32.CDF.

3.	Edit the properties for each profile as necessary:

source host
source directory
destination directory path
destination directory path on after distribution command

4.	Distribute the ftp-st profile to the remote systems to install the stack.  Have the Windows 95 CD ready.  The installation program on the remote system might require files from the CD.  When you install the stack, the applications are also installed.
To install the applications, distribute the ftp32 profile.  When the install is finished, remove the file package to free up space on the remote systems.

You must reboot the remote system after the FTP stack has been installed.


Installing Lotus Notes Mail

Before you begin

To perform a remote installation (this will perform a standard install):

1.	Copy the Notes32 folder from the Communications Suite CDROM to a local drive or shared network drive.

2.	Copy the files NOTES32.BAT and INSTNOT.RSP from the cs11tivoli package to the Notes32 folder.  INSTNOT.RSP is the response file for Lotus Notes Mail.

Steps

From the Tivoli Profile Manager

1.	Create a notes32 profile.

2.	Import the NOTES32.CDF file from the cs11tivoli.exe package into the notes32 profile.

3.	Edit the properties for the notes32 profile as necessary:

source host
source directory
destination directory path
destination directory path on after distribution command

4.	Distribute the notes32 profile to the remote systems.  When the installation is finished, remove the file package to free up space on the remote systems.


Installing Internet Explorer
Installing Microsoft Internet Explorer

To perform a remote installation:

1.	Copy the Internet Explorer folders from the Communications Suite CD-ROM to a local or shared network drive.  The directories are \IE4\winNT and \IE4\win95.

2.	Copy the file IE495.BAT from the cs11tivoli package to the \IE4\win95 folder.

3.	Copy the file IE4NT.BAT from the cs11tivli package to the \IE4\winNT folder.

Steps

From the Tivoli Profile Manager:

1.	Create these profiles:

ie495 - (Internet Explorer for Windows 95)
ie4NT - (Internet Explorer for Windows NT)

2	Import the following files from the cs11tivoli.exe package into the appropriate Tivoli profile:  IE495.CDF and IE4NT.CDF.

3	Edit the properties for each profile as necessary.

source host
source directory
destination directory path
destination directory path on after distribution command

Distribute the ie495 profile to the remote systems that have Windows 95 installed and the ie4NT profile to the remote systems that have Windows NT installed.  When the install is finished, remove the file package to free up space on the remote systems.


Troubleshooting

Debugging InstallShield Problems

This section describes how to debug problems which occur when silent installing or uninstalling Communications Suite.

If the silent install or uninstall fails, check for the file SETUP.LOG in the directory where you are installing/uninstalling the software from (the directory where SETUP.EXE resides).  The SETUP.LOG file should contain a ResultCode which indicates the reason why the silent installation/uninstallation failed.

The SETUP.LOG file contains three sections:

[InstallShield Silent]
Identifies the version of InstallShield Silent used in the silent installation/uninstallation.  It also identifies the file as a log file.

[Application]
Identifies the installed application's name and version, and the company name.

[ResponseResult]
Contains the result code indicating whether or not the silent installation/uninstallation succeeded.  An integer value is assigned to the ResultCode keyname in the [ResponseResult] section.  InstallShield3 places one of the following return values after the ResultCode keyname:

  0      Success

 -1      General error

 -3      Required data not found in the SETUP.ISS file

 -4      Not enough memory available

 -5      File does not exist

 -6      Cannot write to the response file

 -9      Not a valid list type (string or number)

-10     Data type is invalid

-11     Unknown error during setup

-12     Dialogs are out of order.  (You will get this ResultCode if the response file 	SETUP.ISS is not in the installation directory.)

Following is an example of the SETUP.LOG file for a successful silent installation:

[InstallShield Silent]
Version=v3.00.000
File=Log File
[ResponseResult]
ResultCode=0

Common InstallShield Problems

•	The SETUP.ISS file is not in the directory where the installation code resides, or is not in the directory specified with the -f1 parameter.

You changed the name or location of the SETUP.ISS file and did not specify the new name or location when you issued the SETUP.EXE command to install the code.

•	Not enough space on specified target drive to install the code.

You are installing/uninstalling Communications Suite and the user logged on the target machine does not have Administrator authority.

•	You cannot uninstall the code immediately after installing it without performing a
reboot.

You made a syntax error when you made a change to the syntax of the SETUP.EXE or UNINST.EXE commands.

Note:  there is currently an InstallShield bug when creating a response file which occurs when the length of the path and filename specified on the f1 parameter exceeds 43 characters.  You will get a "Setup Initialization Error" with Error code 105.  To get around this problem, create the response file in a directory path with a shorter name, and then copy it into the desired directory.