VMware THINAPP 4.6 - MIGRATING APPLICATIONS TECHNICAL NOTE Manual do Utilizador Página 11

  • Descarregar
  • Adicionar aos meus manuais
  • Imprimir
  • Página
    / 23
  • Índice
  • MARCADORES
  • Avaliado. / 5. Com base em avaliações de clientes
Vista de página 10
VMware ThinApp
R E V I E W E R S G U I D E / 1 1
To utilize ThinApp Converter, you must specify the parameters used for the automation in the
ThinAppConverter.ini file and then reference the appropriate fileshares. This diagram represents the
components and process used for the packaging operation.
Deploying ThinApp Packages
The process for deploying ThinApp application containers is very simple as there is no actual installation of
the application and interoperation with the local operating system is minimal. Deployment involves making a
decision for a centralized or de-centralized model for application delivery and then integrating the virtualized
applications into the desktop for end user accessibility.
ThinApp Deployment with VMware View 4.5
The following sections discuss both deployment and application registration with processes that can be utilized
on physical and virtual desktops. With the release of VMware View 4.5, ThinApp packages can be deployed
from within the View Administrator console and automatically registered. This turnkey integration of View
desktops and virtualized applications oer tremendous eciency and operational savings for VMware View
environments. For VMware View environments we suggest you read through the concepts of execution mode
and application registration to understand what happens automatically when you assign ThinApp packages
through the View Administrator console. The specific steps to deploy ThinApp packages in VMware View
environments are covered in the section Using ThinApp Assignments with VMware View.
Centralized and De-Centralized Deployment
The determination of centralized versus de-centralized depends on the execution mode of the package. The
same package can be executed using either method but delivers dierent benefits and administration models.
Execution Mode describes the two options for providing virtualized applications to end users.
Streamed execution mode allows the application to be centrally stored and accessed by multiple users.
Streamed execution mode is a one-to-many model which provides centralized deployment and update of an
application package to multiple end users for execution via a Windows desktop shortcut.
Vista de página 10
1 2 ... 6 7 8 9 10 11 12 13 14 15 16 ... 22 23

Comentários a estes Manuais

Sem comentários