Cisco Cisco Computer Telephony Integration Option 9.0 Installation Guide
WebView Removal and Silent Install of 8.5(1)
Silent install is not supported on machines that have WebView installed; one of the WebView
Third Party Tools (Sybase) requires a live response in order to be removed.
Third Party Tools (Sybase) requires a live response in order to be removed.
Recovering from Installer Failures
There are situations where the installer might fail for reasons that cannot be anticipated or
controlled. This could include:
controlled. This could include:
•
A power outage
•
System lockup due another process failing
•
A virtual machine hanging or shut down accidentally
•
An incorrect or incomplete silent install response file
•
The installer completes successfully, but for some reason you are unable to un-install using
Windows Add/Remove Programs
Windows Add/Remove Programs
Under "normal" conditions, when a failure in an InstallShield program occurs, the installer can
be aborted. An abort event is processed by InstallShield and the setup program attempts to undo
the changes it has made. Changes include file deployments, registry modifications, and other
modifications to Windows shell objects.
be aborted. An abort event is processed by InstallShield and the setup program attempts to undo
the changes it has made. Changes include file deployments, registry modifications, and other
modifications to Windows shell objects.
The InstallShield engine does not include native capabilities for either file backup during install
or file return during uninstallation. These additional tasks are scripted enhancements made to
the Windows based installer. If there is a catastrophic failure during the installation (or any
other state that blocks the uninstall program from running) the file return needs to be performed
manually.
or file return during uninstallation. These additional tasks are scripted enhancements made to
the Windows based installer. If there is a catastrophic failure during the installation (or any
other state that blocks the uninstall program from running) the file return needs to be performed
manually.
Warning: Do not attempt to repair a system by modifying the Windows registry and
running the installation a second time. You will lose the ability to return the system to its
pre-installation state. If the installer is run a second time, it backs up the recently installed
versions of files, overwriting the original backup files.
running the installation a second time. You will lose the ability to return the system to its
pre-installation state. If the installer is run a second time, it backs up the recently installed
versions of files, overwriting the original backup files.
Backup files are stored in child directories of the original files. The child directory name is the
minor release version number with each numerical component separated by an underscore. For
example, files patched in the C:\icm\bin directory are copied to a directory name like:
C:\icm\bin\_ICM_8_5_1_0_0_0_44.
minor release version number with each numerical component separated by an underscore. For
example, files patched in the C:\icm\bin directory are copied to a directory name like:
C:\icm\bin\_ICM_8_5_1_0_0_0_44.
A list is kept in a text file for every backup directory created. This file is written to the product
root directory (example: C:\icm\_ICM_8_5_1_0_0_0_44\Return_ICM_8_5_1_0_0_0_44.txt).
root directory (example: C:\icm\_ICM_8_5_1_0_0_0_44\Return_ICM_8_5_1_0_0_0_44.txt).
Upgrade Guide for ICM and CTI OS for Cisco Unified Contact Center Enterprise Release 8.5(1)
31
Chapter 5: Silent Installation and Recovery from Installer Failures
Recovering from Installer Failures