Cisco Cisco Agent Desktop 8.5 Guia Da Instalação
Cisco CAD Installation Guide
44
February 21, 2013
Automated Package Installation vs. Manual Installation
Automated installations must use the same files and meet the same installation
criteria as manually-deployed installations.
criteria as manually-deployed installations.
CAD MSI packages are located in a specified location (the folder
C:\Program Files\Cisco\Desktop\Tomcat\webapps\TUP\CAD) on a
successfully-installed production server and are intended for both manual and
automated deployment. Alteration of these files or the use of other MSI files included
with the product at other locations is not supported.
C:\Program Files\Cisco\Desktop\Tomcat\webapps\TUP\CAD) on a
successfully-installed production server and are intended for both manual and
automated deployment. Alteration of these files or the use of other MSI files included
with the product at other locations is not supported.
Installation criteria such as supported operating systems, product deployment
configurations, installation order, and server/client version synchronization must be
met. Altering the supplied MSI packages to circumvent the installation criteria is not
supported.
configurations, installation order, and server/client version synchronization must be
met. Altering the supplied MSI packages to circumvent the installation criteria is not
supported.
Multiple Software Releases
Multiple software releases must not be combined into a single deployment package.
Each CAD software release is intended for distribution in its entirety as a distinct
deployment. Combining multiple releases (for example, a software package's base
release and a subsequent service release) into a single deployment package is not
supported.
Each CAD software release is intended for distribution in its entirety as a distinct
deployment. Combining multiple releases (for example, a software package's base
release and a subsequent service release) into a single deployment package is not
supported.
Reboots
Any reboots associated with CAD installations are required. If the installation’s default
reboot behavior is suppressed, the target machine must be rebooted before running
the installed applications to ensure expected functionality.
reboot behavior is suppressed, the target machine must be rebooted before running
the installed applications to ensure expected functionality.
Delaying a reboot is not known to be an issue at this time, as long as a reboot occurs
before launching the installed applications. If it is determined in the future that
delaying a reboot via command line suppression affects expected behavior, then that
delayed reboot will not be supported.
before launching the installed applications. If it is determined in the future that
delaying a reboot via command line suppression affects expected behavior, then that
delayed reboot will not be supported.
Best Practices
Best practices recommendations are listed below.
Windows Installer Logging
To ensure that any loggable issues are captured efficiently, enable Window Installer
logging using the following command line argument:
logging using the following command line argument:
/l*v <logfile path and name>