Cisco Cisco Agent Desktop 8.5 Guia Da Instalação

Página de 148
Using Automated Package Distribution Tools
March 31, 2014
99
Using Automated Package Distribution Tools
CAD’s MSI-based desktop application installations can be deployed (“pushed”) via 
automated package distribution tools that make use of the Microsoft Windows 
Installer service.
If you need to create MSIs before the CAD services are installed, se
Requirements
CAD support for automated package distribution depends on compliance with the 
requirements listed below.
Execution
Installations must be executed on the target machine. Deployment methods that 
capture a snapshot of an installation and redistribute that image are not supported.
Per-Machine vs. Per-User Installation
Installations must be deployed on a per-machine basis. Per-user installations are not 
supported.
It might be necessary to ensure per-machine installation via command line. 
Privileges
By default, Windows Installer installations run in the context of the logged-on user. 
CAD installations, which use Windows Installer, require either administrative or 
elevated (system) privileges. If the CAD installation is run in the context of an 
administrative account, no additional privileges are required.
If the CAD installation is run in the context of an account with reduced privileges, the 
Windows policy “Always Install with Elevated Privileges” must be enabled to deploy the 
installation with elevated privileges.
When this policy is enabled, Windows Installer installations will run in a context with 
elevated privileges, thus allowing the installation to successfully complete complex 
tasks that require a privilege level beyond that of the logged-on user. 
To direct Windows Installer to use elevated privileges, launch the Microsoft 
Management Console (MMC) Local Computer Policy snap-in on the target machine. 
Enable the Windows policy “Always Install with Elevated Privileges” for both the 
Computer Configuration and the User Configuration nodes.
For more information about enabling this policy, see “Always install with elevated 
privileges” at: