VMware ThinApp 4.7：提升应用移植性、管理与兼容性的快速指南

VMware

ThinApp

需积分: 10 192 浏览量更新于2024-07-18 收藏 8.13MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

VMware ThinApp 4.7 Essentials 是一本专注于教授如何利用VMware ThinApp技术的实用指南，该技术旨在提升应用程序的可移植性、管理和兼容性。在4.7版本中，作者Peter Björk以专业经验为基础，提供了详尽的教程，帮助读者快速高效地实现应用虚拟化。通过将应用程序封装在底层操作系统之外， ThinApp 技术确保了在不同环境中的无缝运行，无论是Windows还是其他操作系统。本书的核心内容包括以下关键知识点： 1. **基础概念**：解释了什么是应用虚拟化，以及它如何通过封装技术隔离应用程序与底层OS的依赖关系，从而实现跨平台的部署和管理。 2. **安装与配置**：介绍了如何在VMware环境中设置和配置ThinApp服务器，包括必要的软件许可、环境配置以及搭建基础架构。 3. **创建模板**：详细阐述了如何创建和优化 ThinApp 包，包括捕获原始应用程序、处理系统依赖、调整设置以优化性能，并确保兼容性。 4. **部署与分发**：教授如何将 ThinApp 包部署到终端用户，包括自动化部署流程和管理工具的使用，以确保快速、简便的部署体验。 5. **管理与维护**：涵盖了 ThinApp 的日常运维，如更新管理、性能监控、故障排查以及用户权限和安全设置。 6. **案例研究与实战示例**：书中包含实际项目中的应用场景和最佳实践，帮助读者理解和掌握在实际工作场景中如何运用 ThinApp 4.7。 7. **版权与免责声明**：强调了版权法律，指出未经出版商书面许可，不得复制或传播书中的任何部分，同时也提到了出版商对信息准确性的承诺，但不担保书中信息无误，并声明不对因使用本书信息造成的任何损失负责。 VMware ThinApp 4.7 Essentials 是一本适合IT专业人士和技术管理人员阅读的书籍，无论你是希望提高应用程序管理效率，还是寻求新技术解决方案来解决兼容性和迁移问题，这本书都将为你提供宝贵的知识和指导。

资源详情

资源推荐

Application Virtualization

In this chapter we will cover a general overview of application virtualization

and ThinApp. We will start by exploring what application virtualization is and

why it is superior to local installations. We will then cover the architecture behind

ThinApp and how we can manipulate and customize ThinApp packages to suit

our specic requirements.

By the end of this chapter, you will have learned about:

• Application virtualization

• Why you should use application virtualization

• ThinApp architecture

• Common ThinApp vocabulary

• The sandbox

• Isolation modes

• Application linking with the help of AppLink

Application virtualization

Application virtualization encapsulates an application and all of its components

into a package that is easy to deploy and manage. Using virtualization allows you

to execute the application as if it was locally installed when it is not. Normally when

you install an application it will register DLL les, create registry keys, and copy

les into your operating system. This modies your operating system and you will

always run the risk of overwriting something already installed and breaking an

existing application. By virtualizing the application, you will never install anything

on the client, you will simply execute the application. There is also a virtualization

layer hooking into the APIs of the application. When hooking the API for, let's say

Open File, it is possible for the virtualization layer to present a virtual environment

for the application, thus fooling the application into thinking it is already locally

installed and therefore allowing it to execute.

Application Virtualization

[ 6 ]

The benets of using application virtualization are many. Your operating system

stays clean. By having clean machines, your clients will be more stable. A virtualized

application is much easier to deploy, maintain, and retire than a natively installed

one. With application virtualization, it is often possible to run two otherwise

conicting applications simultaneously on the same machine. Not using application

virtualization makes it pretty much impossible to have Microsoft Ofce 2003 and

Microsoft Ofce 2010 installed on the same client and run both at the same time.

ThinApp overview

VMware ThinApp is a packaging format. Like MSI and other packaging formats,

ThinApp simplies application deployment. ThinApp uses virtualization to package

your application, which lets you execute the packaged application without having

to install it. When using ThinApp, you simply need to have access to your package

in order to use the application, as compared to the legacy MSI format in which you

need to install and register your application on the local machine. As a side effect of

using virtualization, you can isolate the lesystem and registry components from

the locally installed applications as well as from other virtualized applications.

This allows you to run conicting applications on the same machine. Since you will

never install anything locally, the use of an application will not alter your operating

system. Your client will be much cleaner, more stable, and will operate faster for a

longer time. ThinApp minimizes the constant reinstallation of the operating system

due to repetitive application installs, which leave residue and often create conicts

that eventually leave the operating system in a degraded state necessitating a

complete system rebuild.

ThinApp has one very obvious advantage over other solutions out there. It is

agentless, meaning you need nothing locally installed in order to execute an

application packaged with the help of ThinApp. Being agentless greatly reduces

the administration overhead. When a new ThinApp version is released, you don't

have to touch any existing packages already deployed. Start using the new version

to capture new applications. You can happily deploy these next to an old ThinApp

package since there is no conict between ThinApp versions running side-by-side.

Being agentless also lets you offer an application to a user bringing his or her own

device without the need to ever touch the device. You don't run the risk of being

accused of altering the user's machine.

Chapter 1

[ 7 ]

Out of the box, ThinApp is capable of virtualizing 60 – 80 percent of your

applications. Having more ThinApp knowledge and experience might allow you to

virtualize up to 85 – 90 percent. You will, most of the time, never achieve 100 percent

virtualization. This means you will, most of the time, have two packaging formats in

place – native installation (often MSI) and ThinApp. ThinApp supports virtualizing

Services, COM, and DCOM objects. ThinApp does not support virtualizing device

drivers, Network visible DCOM, Global Hook DLLs, and COM+. There might

be workarounds to these limitations. One of these could be to load what is not

supported outside the virtual environment. One of the main reasons to virtualize

an application is to keep your operating system clean. This is why ThinApp does

not make many changes to the operating system when registering a ThinApp

package. Registering a package will give you a certain level of shell integration,

such as shortcuts, le type registrations, and a few more, but not all. Context menus

are a typical example. This changed user experience might be a reason not to

virtualize an application, even though ThinApp can package it. For instance, 7-Zip

adds a context menu item so that when you right-click on a ZIP le in Windows

Explorer, you can perform zip/unzip operations without having to open the

application directly. A 7-Zip ThinApp package will happily perform zip/unzip

operations when launched directly, but the users will not have access to the

right-click context menu. Most of the times you can create context menus pointing

to a virtualized application but it is not something ThinApp creates automatically

for you when registering the package.

Even though you will probably not be able to reach 100 percent application

virtualization, ThinApp adds signicant value to your application's deployment

and management infrastructure. Every application you manage to virtualize will

be easier to maintain and cheaper to support.

ThinApp architecture

Since it cannot be mentioned too many times, ThinApp is agentless. Nothing needs

to be installed on the client in order to run and use a ThinApped application. The

ThinApp runtime is built into each one of the ThinApp packages you create. ThinApp

does not create conicts between different versions of ThinApp runtimes, so you can

run packages built using different ThinApp versions on one single machine.

Chapter 1

[ 9 ]

The view of the environment of a package is a merge between the physical and the

virtualized. In the previous screenshot, Mozilla Firefox sees the content of native

C:\Program Files as well as the virtualized folder called Mozilla Firefox. The

Mozilla Firefox folder is not available to the operating system (Explorer window).

When the virtualized application is launched, the virtual environment is initiated

by the ThinApp runtime and presented to the executing process. The application

believes it is locally installed on the machine. The packaging process of ThinApp

does not alter the application's les in any way. The ThinApp runtime loads the

processes and by launching it, the ThinApp runtime can hook into the API calls

made by the processes and present the virtual environment.

Common ThinApp vocabulary

In order to have a meaningful discussion about ThinApp, we need to agree on

some common vocabulary. I prefer to give you this vocabulary earlier in the book

rather than later. If you have already used ThinApp, most of this will already be

known. If you are new to ThinApp, don't worry, as we will cover all of it in more

detail as the book progresses.

The capturing process

This is the whole process of capturing an application. You can run Setup Capture,

install your application, and save the capture into a project folder. The capture

process analyzes all changes made to your capture machine and stores those into

a project folder. These changes are what will become the virtual environment and

make the captured application believe it is locally installed on the target machine.

The capture machine

This is the machine on which you run the capture process. Most of the time it's

a virtual machine since that allows easy reversion to different machine states

(snapshots). After successfully capturing an application, you will revert to a

clean state before you capture a new application.

The project folder

This is the outcome of your capturing process. Now the real work as a packager

begins. It's the project folder that contains the virtualized environment such as

les and registry keys recorded during your capturing process.

www.allitebooks.com

剩余255页未读，继续阅读

qdl2000

粉丝: 0
资源: 9

VMware ThinApp 4.7：提升应用移植性、管理与兼容性的快速指南

Thinapp 4.7.1 含注册机及序列号

VMware ThinApp

vmware thinapp 5.0 with keygen

turbo studio vmware thinapp boxedapp

vmware thin aop

VMware可移动设备选项

什么工具可以预先加载应用

powerbuilder11.5 免安装

advanced installer14中文

河北金融学院在广东2021-2024各专业最低录取分数及位次表.pdf

非常好的通俗易懂的开关电源原理与维修6.zip

2米输送线_机械3D图Solidworks设计图.zip

分布式电源优化配置与选址定容MATLAB程序基于遗传算法 （1）该程序为基于遗传算法的分布式电源优化配置与选址定容程序，硕士学位

基于ssm图书馆借阅管理系统设计与实现.docx

WordPress优化插件，WPOPT v2.1.0

输送粉末涂层炉_机械3D图Solidworks设计图.zip

Unet 改进：加入SAM的bbox分割代码

链板输送机（链板给料机）_机械3D图Solidworks设计图.zip

宁夏医科大学在广东2021-2024各专业最低录取分数及位次表.pdf

最新资源

分布式电源优化配置与选址定容MATLAB程序基于遗传算法（1）该程序为基于遗传算法的分布式电源优化配置与选址定容程序，硕士学位