Module2-Application Virtualization VendorsAVS4
Module2-Application Virtualization VendorsAVS4
Smackdown
Author(s):
Ruben Spruijt
Version:
4.0
Date:
February 2013
Version 4.0
February 2013
Page 1/53
DOCUMENT OVERVIEW
HISTORY
Version
1.0
1.41
1.9
2.0
2.1
2.2
Date
April 2007
October 2007
November 2008
December 2008
January 2009
July 2009
2.25
July 2009
Author(s)
Ruben Spruijt
Ruben Spruijt
Ruben Spruijt
Ruben Spruijt
Ruben Spruijt
Ruben Spruijt,
Jurjen van Leeuwen
Ruben Spruijt
2.50
3.0
July 2010
August 2010
Sven Huisman
Ruben Spruijt
3.0
3.1
September 2010
October 2011
Ruben Spruijt
Ruben Spruijt
4.0
February 2013
Ruben Spruijt
Date
December 2008
July 2009
August 2010
September 2011
January 2013
Reviewer
Jurjen van Leeuwen
Jurjen van Leeuwen
Community review
Jurjen van Leeuwen
Jurjen van Leeuwen
Rory Monaghan
Remarks
Release The Matrix
REVIEWERS
Version
2.0
2.2
3.0
3.1
4.0
Version 4.0
February 2013
Remarks
Page 2/53
CONTENT
1.
Introduction ............................................................................................................. 5
1.1
1.2
1.3
1.4
1.5
2.
Objectives................................................................................................................ 5
Intended audience .................................................................................................... 5
Vendor involvement................................................................................................... 5
Feedback ................................................................................................................. 5
Contact.................................................................................................................... 5
About ...................................................................................................................... 7
2.1
2.2
3.
3.1
3.2
3.3
3.4
4.
Strategy................................................................................................................... 9
The essence of application and desktop delivery .......................................................... 10
Overview of application and desktop delivery solutions ................................................. 11
Vendor matrix, who delivers what.............................................................................. 15
Application Virtualization .......................................................................................... 17
4.1
4.2
4.3
4.4
4.5
4.6
4.7
5.
Virtualization .......................................................................................................... 17
Why application virtualization? .................................................................................. 17
Application virtualization strategy .............................................................................. 18
From niche to mainstream........................................................................................ 20
Whats in a name?................................................................................................... 21
Find the balance ..................................................................................................... 23
Workspace Aggregation ........................................................................................... 23
Application Compatibility and Readiness ..................................................................... 25
5.1
6.
Migration ............................................................................................................... 25
Application virtualization and VDI .............................................................................. 27
6.1
6.2
6.3
6.4
7.
Stateless desktops................................................................................................... 27
Stateful desktop...................................................................................................... 27
Overhead and storage impact ................................................................................... 28
Application virtualization impact on VDI, Project VRC .................................................... 28
Vendors and their Virtualization solutions.................................................................... 30
7.1
7.2
7.3
7.4
7.5
7.6
7.7
7.8
7.9
7.10
7.11
7.12
8.
Version 4.0
Introduction ........................................................................................................... 30
Cameyo ................................................................................................................. 30
Citrix application streaming....................................................................................... 30
Evalaze.................................................................................................................. 31
Installfree .............................................................................................................. 32
Numecent application jukebox................................................................................... 32
Novell ZENworks application virtualization (ZAV) .......................................................... 34
Microsoft App-V ...................................................................................................... 35
Roozz cloud platform ............................................................................................... 38
Spoon.................................................................................................................... 39
Symantec endpoint virtualization ............................................................................... 41
VMware ThinApp..................................................................................................... 44
Application virtualization Comparison ......................................................................... 45
February 2013
Page 3/53
8.1
8.2
8.3
8.4
Product version....................................................................................................... 45
Scope.................................................................................................................... 45
Feature compare matrix ........................................................................................... 45
Future additions...................................................................................................... 53
9.
Change Log............................................................................................................ 52
10.
Conclusion ............................................................................................................. 54
Version 4.0
February 2013
Page 4/53
1.
INTRODUCTION
Are you looking for an independent overview of application virtualization solutions and curious
about the different features and functions each application virtualization vendor is offering!?
This is the whitepaper you definitely must read!
In the current market there is an increasing demand for unbiased information about application
virtualization solutions. This white paper is focused on solutions that are anticipated to have an
important role in application virtualization deployments. An overview of available features of
each solution has been created to allow an understanding and comparison of capabilities..
1.1
OBJECTIVES
The goals of this whitepaper are to:
1.2
INTENDED AUDIENCE
This document is intended for IT Managers, architects, analysts, system administrators and ITPros in general who are responsible for and/or interested in designing, implementing and
maintaining application virtualization Infrastructures.
1.3
VENDOR INVOLVEMENT
All major vendors whose products are covered in the whitepaper, such as Citrix, Endeavors,
InstallFree, Microsoft, Roozz, Spoon, Symantec and VMware have been approached in advance
to create awareness of this whitepaper and discuss their solutions functionality and features.
1.4
FEEDBACK
We try to provide accurate, clear, complete and usable information. We appreciate your
feedback. If you have any comments, corrections or suggestions for improvements of this
document we want to hear from you! Please send an e-mail to Ruben Spruijt ([email protected])
Include the product name, version number and the title of the document in your message.
1.5
CONTACT
PQR; Tel: +31 (0)30 6629729
E-mail: [email protected] ; www.pqr.com
Twitter: http://www.twitter.com/pqrnl
Version 4.0
February 2013
Page 5/53
Version 4.0
February 2013
Page 6/53
2.
ABOUT
2.1
ABOUT PQR
PQR is a professional ICT infrastructure company focusing on the availability of data,
applications and work spaces with optimized user experience in a secure and manageable way.
PQR provides its customers innovative ICT solutions, from on-premise to cloud management,
without processes getting complex. Simplicity in ICT, thats what PQR stands for.
PQR has traceable references and a wide range of expertise in the field, proven by many of our
high partner statuses and certifications. PQR is a Citrix Platinum Solution Advisor, HDS Tier 1
Platinum Partner, HP GOLD Preferred Partner, Microsoft Gold Partner, NetApp Star Partner, RES
Platinum Reseller, VMware Premier Partner en VMware Gold Authorized Consultant Partner.
PQRs approach is based on four main pillars:
PQR, founded in 1990, is headquartered in De Meern and has over 107 employees. In fiscal
year 2011/2012 posted sales of 94.9 million and a net after tax profit of 4.6 million have
been recorded.
2.2
ACKNOWLEDGMENTS
Ruben Spruijt, CTO @ PQR
Ruben Spruijt (1975) is CTO and focuses primarily on Enterprise Mobility,
Virtualization and Cloud Management. He is actively involved in
determining PQRs vision and strategy. Ruben is a Microsoft Most Valuable
Professional (MVP), Citrix Technology Professional (CTP) and VMware
vExpert and is the only European with these three virtualization awards.
He gives customers advice and has them benefit from his expertise; he
motivates his colleagues and writes blogs, articles and opinion pieces on a regular basis. During
presentations in several national and international congresses, Ruben shares his thoughts and
knowledge on application and desktop delivery, and on virtualization solutions. To contact
Ruben directly send an email to [email protected]. Follow Ruben on twitter: @rspruijt
Version 4.0
February 2013
Page 7/53
A-Team - its only through the effort and persistence of the application virtualization
smackdown team that we achieved the goals, a big thanks to them!
Name
Position
Contact
Role
Jurjen van
Leeuwen
Sr. Consultant
Leodesk
Writer
@Leodesk_IT
Rob Beekmans
Consultant PQR
Writer
@robbeekmans
Sven Huisman
Consultant PQR
Writer
@svenh
Rory Monaghan
Desktop Analyst
Writer
@Rorymon
Peter Sterk
Solutions Architect
Writer
@PeterSterk
Special thanks: to Alistair Gillespie for reviewing the document and provide great feedback.
He is based in the UK and works in the End User Computing" space covering Client Virtualisation, Application Virtualisation and Enterprise Mobility. To contact Alistair directly email or follow
Alistair on twitter
Jurjen van Leeuwen: With a solid base as an infrastructure consultant in the Netherlands,
Jurjen van Leeuwen moved to Norway and started as a freelance consultant. With his company
Leodesk.com, Jurjen continues to practice his enthusiasm for products in the application and
desktop delivery area with a strong focus on Application virtualization solutions from multiple
vendors. Besides his work on the Application virtualization Feature Overview and Compare
Matrix, Jurjen also is active in the community as a moderator on AppVirtGuru.com and is a
Microsoft MVP on App-V. Contact Jurjen by email at [email protected]
Rory Monaghan, Is an Irishman who is currently based in Phoenix, Arizona. Rory has been
working with App-V for six years now. He gained his experience working with clients in multiple
different Industries of varying sizes. Rory contributes to the online App-V community which is
ever growing and made up of some sharp minds and very helpful people and he enjoys learning
about new tech and sharing knowledge via the website www.rorymon.com
Personal note from Ruben: I would give a special thanks to Jurjen van Leeuwen and Rory
Monaghan who simply did an incredible job in investigating and reviewing various solutions.
The amount of effort and private time spend is extraordinary Thanks !
Community effort
A BIG thanks to the application virtualization community members, especially: Andreas Welsch
Version 4.0
February 2013
Page 8/53
3.
3.1
STRATEGY
Enterprise Mobility, BYO, Consumerization of IT, BigData, Cloud Computing , Cloud
Management Solutions, Dynamic Datacenter and Software Defined Datacenter are the main
trends in the IT industry. Virtualization is incorporated in various of these trends.
Virtualization is nothing more than the decoupling of IT resources. The forms of virtualization
that are most frequently applied include network, storage, hardware/server, application and
desktop virtualization. Application and Desktop Delivery is a process which has the goal of
offering applications independent of location and device, so users can work onsite, online,
offsite, offline, anywhere, with any (own) device and at any time. The dynamic delivery of
applications is an essential functionality and part of a broader strategy of an optimized Desktop.
When studying and determining which Application and Desktop Delivery solution suits with
the users and your organization, it is essential to ask three questions:
1. What is the execution platform for the applications?
Within the execution platform, system resources such as the CPU, memory, disk and network
are used in order to execute the windows, web-architected, rich mobile and mobile webapplications. The most frequently used execution platforms include the following: Desktop,
Laptop, Tablet, Smartphone, Virtual Desktop Infrastructure and Server Based Computing (also
known as Session Virtualization). The choice of an execution platform is the most fundamental
decision made! Applications are either executed locally on a device or centrally in a datacenter.
Each execution platform has its own characteristics. In practice, every organization possesses a
mixture of device access scenarios. The theories: Less is more , Cut out the exceptions and
Manage diversity should always be in mind!
2. How will applications be made available on the execution platform?
An execution platform is great; but if there are no applications available on the platform, the
platform is of no real value to the end-user. The second question is this: How will applications
get onto the execution platform?! A number of solutions exist for making Windows, webarchitected, rich internet and mobile web applications available on the platform. The forms
most frequently used with windows applications include installation or application
virtualization.
With installation, applications are delivered to a windows machine and (typically) installed in
an unattended manner. The execution platform is altered (e.g. writes to the file system /
registry) as a result of the install. Installing applications as core components in a base image
is also one of the possibilities available.
When applications are made available by means of application virtualization, they are available
on demand on the execution platform. No adjustments are made to the platform, the
applications are isolated from the core operating system.
3. How are the execution platform and the applications managed from an IT-Pro
and from an end-user perspective?
Version 4.0
February 2013
Page 9/53
An execution platform with a variety of windows, web and mobile applications can be created
but how do you manage and maintain this environment?
Important points to keep in mind!
-
3.2
In essence desktop virtualization is the de-coupling of the desktop, operating system and
the applications from the underlying endpoint or device. This kind of virtualization can be
subdivided into two types:
With the first type applications are executed remotely, server hosted, and
presented at the endpoint via a Remote Display Protocol.
With the second type applications are executed at the endpoint, client-side and
presented locally.
The above description outlines the first question: What is the execution platform for the
applications?
In most enterprise infrastructures the majority of applications are either web-architected or
Windows-based. The ratio of Web vs. Windows applications depends on the vertical,
customer, history, legacy, innovation and control of application development. Windows
applications are either installed (manually, automatically or integrated in to the base-image)
or virtualized (using application virtualization or virtual disk layering solutions)
Enterprise Mobility Smackdown
Mobile applications delivery through a consumer or corporate application store, management
from both a device (MDM) and application (MAM) perspective, Data Access, Security,
Networking and App-ification are key components in an Enterprise Mobility strategy. In a (near)
future whitepaper Enterprise Mobility Smackdown we will smackdown this hot trend and
various solutions in the MDM and MAM arena.
Version 4.0
February 2013
Page 10/53
3.3
3.3.1
Version 4.0
February 2013
Page 11/53
Secure access
Secure Access solutions provide secure access for (untrusted) devices to corporate IT. The two
parts of the symbol stand for secure (the shield) and access (the traffic light). Depending on
the chosen solution, secure access can also be fine-grained. A Secure Access solution could be
be a full (SSL) VPN solution or a Gateway Services which is targeted for Server Hosted Desktops. Solutions that can be used to realize secure access scenarios include Cisco ASA, Citrix Access Gateway, Juniper SSL VPN, Microsoft Unified Access Gateway (UAG) and VMware View Security Server. A complete overview of Secure Access and Secure Networking solutions has been
created and can be downloaded here. A nice Gartner magic quadrant of SSL VPNs can be found
here.
3.3.3
3.3.4
Connection broker
A connection broker determines which server-hosted remote desktop will be made available to
a user. When using a server-hosted virtual desktop infrastructure for this, its possible to either
designate dedicated desktops or a pool of remote desktops. The desktop broker can automatically create, remove or pause remote desktops. There are a number of connection broker suppliers. Citrix - XenDesktop, Microsoft - Remote Desktop Services, Dell/Quest - vWorkspace
and VMware - View are the best known VDI solutions. Depending on the supplier, the connection broker may have additional functions, such as a web interface that can create secure (SSL)
connections to remote desktops, Directory Services integration, Full USB support, support for
various display protocols and integration with Remote Desktop Services Session Host (former ly
RDSH). Depending on the rules, it is possible to execute applications centrally on a serverhosted VDI or on a terminal server.
3.3.5
Version 4.0
February 2013
Page 12/53
work place. In other words; the application can be executed as if it had been installed locally
and can save data and print without the need of any modifications to the local client. Resources
such as the CPU, memory, hard disk and network card take care of the execution of these applications.
Application streaming and virtualization can make applications available to desktops, laptops,
server-hosted VDIs and Remote Desktop Services Session Host (TS) platforms. The applications
are executed on a client platform, without needing to modify the platform.
The advantages of application virtualization include: installation, upgrade, roll-back, delivery
speed and the ease of application support and management). Installation of applications is no
longer necessary, eliminating the possibility of conflicts. The result is a dynamic application delivery infrastructure. Application streaming and virtualization solutions include: Cameyo, Citrix
(XenApp) application streaming, Microsoft App-V, Symantec Workspace Virtualization, Spoon
and VMware ThinApp.
3.3.6
OS provisioning
OS Provisioning, or Machine Based Imaging, allows workstations to boot up and run from a central image. A single image can be used simultaneously by multiple workstations. The advantage
of this is that complete operating systems, including applications and agents, can be made
available quickly and securely. It is possible to make a single image available to multiple VDIs,
RDS and physical desktop environments without causing conflicts. As a result, it is possible to
upgrade or roll-back an OS quickly, simply, and without significant risks. When virtual desktops
use OS streaming, (valuable) storage is saved and the management of virtual desktops becomes relatively simple. This means that virtual or physical machines using OS Provisioning can
become - stateless devices. Citrix Provisioning Services and Machine Creation Services, part of
the XenDesktop family, Doubletake Flex, VMware Mirage, Dell/Wyse Streaming Manager
(WSM), Unidesk and the VMware View Composer are solutions that facilitate OS Provisioning .
3.3.7
Version 4.0
February 2013
Page 13/53
3.3.8
3.3.9
Remote Desktop Services Session Host (formerly known as Terminal Services) is also known as
Session Virtualization. With session virtualization every user has his or her unique terminal
server session. Session Virtualization is a solution for the remote access to desktops and applications that are run on a terminal server in a data center. Access to the desktop or application
is not tied to a location or end-user machine, and programs are executed centrally on the terminal server.
The data appears on the client screen through a remote display protocol such as Microsoft
RDP/RemoteFX or Citrix ICA/HDX. Remote Desktop Services consists of various infrastructure
components for management, load balancing, session control and support. It has the advantage that applications are made available quickly and securely, the TCO is low, and applications can be accessed irrespective of location or work place. Suppliers of Remote Desktop Services Session Host (TS) include Citrix, Ericom, Microsoft and Dell/Quest.
3.3.10
3.3.11
Client management
Any self-respecting professional IT organization is bound to use a Client Management solution,
as it is needed to facilitate things such as OS deployment, patch management, application and
client deployment, asset management, service desk integration, and remote control. Examples
Version 4.0
February 2013
Page 14/53
of client management systems are Altiris/Symantec Deployment Solution, IBM BigFix, LANdesk
Client Management , Microsoft System Center Configuration Manager (ConfigMgr/SCCM) and
Novell ZENworks Configuration Management (ZCM). A nice Gartner Magic Quadrant of Client
Management tools can be downloaded here.
3.4
Solution
Citrix
Citrix
Microsoft
RedHat
Dell/Quest
Virtual Bridges
VMware
XenDesktop
VDI in a box
VDI with RemoteFX
Enterprise Desktop Virtualization
vWorkspace
VERDE
View
SH-VDI
SH-VDI
SH-VDI
SH-VDI
SH-VDI
SH-VDI
SH-VDI
Ericom
Citrix
HP
Microsoft
Dell/Quest
Oracle
Virtual Bridges
VMware/Teradici
RDP/Blaze
HDX-ICA
RGS
RemoteFX/RDP
EOP/RDP
ALP
SPICE
PCoverIP
Teradici
HP
Citrix
VMware
PC over IP
Remote Graphics Software
XenDesktop HDX3D Pro
View
Citrix
Citrix
Microsoft
Virtual Bridges
Microsoft
VMware
XenClient
XenClient Enterprise
Windows 8 Client Hyper-V
LEAF
MED-V (MDOP)
Player/Fusion/Workstation/View
CS-DV, baremetal
CS-DV, baremetal
CS-DV, baremetal
CS-DV, baremetal
CS-DV
CS-DV
Double Take
Citrix
Citrix
Flex
Provisioning Services / MCS
Personal vDisk (former
RingCube)
HyperDeploy
View Composer
Mirage
Unidesk
OS Provisioning
OS Provisioning
OS Provisioning++
Quest/Dell
VMware
VMware
Unidesk
Version 4.0
Product
February 2013
OS Provisioning
OS Provisioning
OS Provisioning++
OS Provisioning++
Page 15/53
Vendor
Virtual Bridges
Dell/Wyse
Product
Dynamic Gold Imaging
Streaming Manager (WSM)
Solution
OS Provisioning
OS Provisioning
Microsoft
Citrix
Dell/Quest
Session Virtualization
Session Virtualization
Session Virtualization
Cisco
Citrix
Microsoft
Juniper
VMware
ASA
Access Gateway
Unified Access Gateway
SA
View
Secure Access
Secure Access
Secure Access
Secure Access
Secure Access
Citrix
Cameyo
Microsoft
Symantec
Spoon
VMware
Application Streaming
App-V
Workspace Virtualization
Spoon
ThinApp
Application virtualization
Application virtualization
Application virtualization
Application virtualization
Application virtualization
Application virtualization
IBM
LANDesk
Microsoft
Novell
RES
BigFix
Client Management Suite
System Center Config Manager
ZenWorks Configuration Mgr
Automation Manager
Client Management
Client Management
Client Management
Client Management
RunBook Automation
Citrix
VMware
Centrix
Framehawk
Cloud Gateway
Horizon Suite
Workspace Universal
Framehawk
Workspace Aggregator
Workspace Aggregator
Workspace Aggregator
Workspace Aggregator
Table 1, Application and Desk top Deliv ery ov er v iew of solution area, products and v endors.
Version 4.0
February 2013
Page 16/53
4.
APPLICATION VIRTUALIZATION
The previous chapter gave an overview of Application and Desktop Delivery solutions. This
chapter describes application virtualization in more detail.
4.1
VIRTUALIZATION
virtualization is the act of isolating or unbinding one computing resource from others. Or put another way - the process of decoupling layers of IT functions so that configurations of the
layers become more independent of each other. As a result, virtualization masks the specific
nature of IT resources from users. A user sees the function not the resource that delivers the
function. Application virtualization is an essential and critical component for all desktop delivery
solutions. The term Application Streaming and Virtualization is often used by customers
and IT-Pros, although its rarely understood fully. To understand the true meaning its best to
break down into constituent parts:
Application: These are the end-user focused windows and web programs, executed on a
Windows Operating System Platform.
Streaming is the process of transporting the application specific data/content as quickly as
possible to the end-point. The application is quick-up-and-running where ultimately the required
resources to run and use the application is being delivered to the user while the remaining data
is transferred in the background.
Virtualization is a software layer that improves portability, manageability and compatibility of
applications by encapsulating them from the underlying operating system on which they are
executed. A virtualized application is not installed in the traditional sense, although its still
executed and behaves as if it were. Virtualization isnt emulation.
4.2
Version 4.0
February 2013
Page 17/53
4.3
Version 4.0
What do you want to achieve, a business enabler, overall cost of ownership (TCO)
and cost reducer?
What are the use-cases? and does the use-case require application virtualization?
What is the business-case?
Are you investigating a tactical (point)-or strategic solution? What do you want to
solve?
Whats your Desktop delivery and migration strategy for Windows 7/Windows 8?
What endpoints do you support and facilitate and what is the role of these devices in
the optimized desktop?
Are the endpoints managed?
What is the strategy around Client Management, PC life Cycle Management, solution
and how does application virtualization fit?
Is a Bring Your Own Device (BYOD) concept one of the key access scenarios?
What is your application delivery model? Is delivery of applications focused on SaaS,
Enterprise, SMB or the Consumer space?
February 2013
Page 18/53
Version 4.0
February 2013
Page 19/53
4.4
Version 4.0
February 2013
Page 20/53
4.5
WHATS IN A NAME?
It seems that almost every vendor has a different name for the same technology. Is the
technology really the same, is the functionality different?
In the haze of messaging and marketing around application virtualization, different names can
blur the application virtualization arena; therefore its good to have definitions of streaming,
virtualization, isolation, integration and re-direction.
The name client or end-point can be a desktop, laptop, virtual desktop, terminal server or
remote desktop server. Managing expectations is always hard; a good starting point is to make
sure everyone speaks the same (IT) language. It is important to note that not all vendor
implementations support all aspects of the definitions provided below. For specific capabilities
offered by specific vendors please refer to chapter 7.
4.5.1
Streaming
The delivery process of transporting the application specific data/resources to the end-point
at the time the application is executed is called streaming. The application is quick-up-andrunning and only the minimum amount of data (commonly between 10-30% of the total
application) is delivered to a client before the application is launched. Not only does this result
in a quicker first time application launch for the user, it also results in significantly reduced load
on the network (compared with full application distribution pre-caching) and makes it possible
to keep end-user images stateless. Additional features of an application are delivered on
demand, or in the background without user intervention. Application packages are stored on a
(centralized) server, which can be a dedicated or shared infrastructure component. The
streaming protocol transports the data over the network in an optimized, efficient and
secure way.
Streaming can operate at a file-level (whole files are copied when they are needed) or blocklevel (file chunks are copied when they are needed) and cache resources locally on the
endpoint for offline execution or faster subsequent startups. Streaming is particularly effective
in well-connected environments where applications should be executed on-demand from a
network resource and end-user images should be kept stateless e.g. VDI and SBC.
4.5.2
Virtualization
The process where applications are encapsulated or isolated from other applications and the
underlying Windows Operating System on which they are executed is called Virtualization. This
improves portability, manageability and compatibility and reduce conflicts of windows end-user
applications. Virtualized applications run in their own discrete, or virtual, environments.
Application virtualization requires a virtualization layer that replaces part of the runtime
environment normally provided by the operating system. The layer intercepts all function calls
to the Windows Operating System such as File, Registry and objects such as COM and DCOM.
The application is executed inside the Virtual Environment, (sometimes called bubble or
sandbox) and behaves as if it is running alone in the Operating System. So the underlying
Operating System is protected, since the application virtualization prevents changes to system
components. Applications can use the hardware- and software components that are installed
and available inside the Operating System. While most application virtualization technologies
Version 4.0
February 2013
Page 21/53
today provide an adequate level of isolation between applications, thus preventing app-to-app
conflicts, very few provide full OS isolation and are able to prevent app-to-OS conflicts.
A quick summary of what application virtualization must provide:
1. All resources required by the virtual application are included in the package
2. The virtual application is completely separated (virtualized/isolated) from the operating
system and other applications
3. The virtual application cannot write to the OS file system or registry, or modify the
native OS in any way. The application virtualization solution is of course able to write to
specific locations to save documents etc.
4. The virtual application must operate the same way as a natively installed application
and provide full OS shell integration, inter-process communications, etc.
Application virtualization decouples the application from OS. Thereby minimizing application
conflicts.
4.5.3
Integrated
Application installation is the process where Windows Applications are installed on the
Windows Operating System. Installed applications are fully integrated with the system and are
able to communicate with other installed applications and the Operating System itself.
The Windows Installer (MSI) is the standard used for the installation, maintenance, and
removal of applications. The installation information, and often the files themselves, are
packaged in installation packages known as "MSI files". Applications that are installed and
integrated dont run in a sandbox environment.
4.5.4
Agent-less
Client-less, or agent-less, application virtualization involves the use of an embedded virtual OS
that is deployed as part of the virtualized application. While creating the virtual application
package the application and client components are compiled and stored in one single container,
mostly a single executable. These virtualized applications are fully encapsulated and able to run
as a standalone executable from multiple locations such as a network drive, local drive, or USB
removable storage device. Every virtualized application contains a built-in agent. So no agent,
or client-component, is installed in the Operating System but every application has an agent
which is used at runtime. VMware ThinApp and spoon are examples of agent-less application
virtualization solutions.
4.5.5
Agent-based
Client-based, or agent-based, application virtualization involves the use of a locally installed
agent or client on the endpoint. This agent, virtualization engine, contains functionality to setup
and maintain the Virtual Environment for each application. The agent takes care of
management tasks such as Shortcut creation, File Type Associates (FTA) registration and is a
key component in the streaming behavior. This behavior is a key functionality for agent-based
application virtualization solutions such as Microsoft App-V
Version 4.0
February 2013
Page 22/53
4.5.6
4.5.7
Portable apps
Portable applications are software programs that are able to run independently without the
need to install files to the system they are run upon and irrespective of the version of Windows
installed on the system. They are commonly used on a removable storage device such as a
DVD, USB flash drive, flash card, or floppy disk. Agent-less application virtualization may
convert even complex application into portable apps.
4.5.8
U3
U3 is a proprietary method of launching windows applications from U3 compatible USB drives.
Applications that comply with U3 specifications are allowed to write files or registry
information to the host computer, but they must remove this information when the USB flash
drive is ejected. Customizations and settings are redirected and stored with the application on
the flash drive. This isnt a virtualization technology, but has its use-cases though.
4.6
4.7
WORKSPACE AGGREGATION
The term Workspace Aggregator is used to describe software that unifies the delivery of
multiple application or desktop types such as:
Version 4.0
February 2013
Page 23/53
Desktops, local, server Hosted Virtual Desktops (VDI) or published Desktops in SBC
A workspace aggregator also evaluates the users device to determine which applications are
available for this user on this particular device and at this particular time (context-aware
access). Next to application delivery, workspace aggregators provide secure file data access
from a broad range of devices. A workspace aggregator simplifies the deployment and life cycle
management of applications. As the single point of access, (de)provisioning, auditing and
monitoring is easily accomplished through security rules and policy enforcement. Workspace
aggregators that are available at the market today also provide Single Sign On capabilities to
applications. The main vendors who deliver workspace aggregation functionality today are:
Version 4.0
February 2013
Page 24/53
5.
5.1
MIGRATION
The use of Application virtualization, Windows 7, Windows 8 and Virtual Desktop Infrastructure
(VDI) brings much new functionality and drives upcoming use-cases such as Bring Your Own
Device (BYOD). Today, users expect greater flexibility, freedom and functionality on their endpoint devices, whereas the IT organization is focused on cost reductions, manageability and
compliancy. The migration of applications to a new Operating System platform, such as
Windows 7 or Windows 8, has a huge impact on the planning, design build and migration to the
optimized desktop especially when x64 Operating System and application virtualization is
involved. The main questions in such a migration are:
There are various solutions on the market designed to address these questions. Some are free,
and limited but in some cases useful; others are more expensive and valuable. Solutions like
Microsoft Application Compatibility Tool Kit (ACT), Dell/Quest Changebase and Citrix AppDNA
play an important role in application compatibility, readiness and remediation. Solutions such as
Changebase and AppDNA examines application compatibility and gives insights in remediation
which results in a simpler, less risky and more controlled migration to a new or updated
platform.
The decision flow chart for application compatibility projects is useful to determine the steps
and solutions to solve application compatibility issues. Technology to alternate provisioning
strategies are VDI, Remote Desktop Servers Session Host, SBC or client-side Desktop
Virtualization.
Version 4.0
February 2013
Page 25/53
Version 4.0
February 2013
Page 26/53
6.
6.1
STATELESS DESKTOPS
A number of different terms are used for stateless desktops - pooled, non-persistent or
standard desktops are frequently-used terms. The essence is the same, the virtualized
desktop is and will always remain clean and pristine; therefore stateless'. All machine -related
modifications, for example applications that are installed by a user, are removed when the user
logs off. User-specific settings that are recorded in the user profile can be stored and re-used.
In addition to the benefits of Desktop Virtualization, stateless desktops also offer the following:
6.2
STATEFUL DESKTOP
A number of different terms are used for stateful desktops - assigned, persistent or private
desktops are terms that are frequently used. The essence is the same - the user is and will
always remain connected to a Virtual Desktop (vDesktop) on a 1:1 basis. If the user has right to
install software, the machine-related adjustments continue to be maintained within this
desktop, which is where the term stateful is derived from. In addition to the benefits of
Desktop Virtualization, a stateful desktop has a specific property, namely:
An important point of special interest with regard to stateful desktops is the fact that the rollout phase, update, upgrade and security of the operating system and the applications is less
simple to manage than with the stateless desktops. The impact on (central) storage is also
greater than with stateless desktops. Because of the ease of management and the flexibility of
stateless desktops; this type is mostly used in a VDI scenario. One of the challenges with
stateless desktops is to figure out how to get the right applications to each user on the stateless
desktop. Since a user is not dedicated to a virtual desktop and the desktop can be reverted to a
clean state, it is not an option to install on a per user or per desktop basis. It is also not an
option to install all the applications that are used within the company in the golden image,
because you would have to update the golden image and redeploy the entire image each time
an application needs an update. Thats not practical and flexible when you have to maintain
more than a small number of applications.
The best option is to use application virtualization to stream or publish applications to the
stateless desktops on a per user basis.
Version 4.0
February 2013
Page 27/53
6.3
CPU/Memory
The virtualized applications might use more CPU cycles and/or memory than locally installed
applications. This might affect other users on the same server in a Remote Desktop
Services Session Host, or SBC, environment or users on the same host in a hosted VDI
environment.
Network
Virtualized applications are often streamed to the users desktop or session. Depending on
the size of the virtualized application and the distribution method the application
virtualization solution is using, this might have an impact on the network.
Disk/Storage
Firstly - the size of the virtualized applications can be important for the disk sizing of the
physical desktop or laptops or Virtual Machines. The application virtualization solution can
use a caching method where the virtualized application is cached on disk. When hosting a
large number of virtual desktops, the caching of the virtualized applications takes place in
these entirely virtualized desktops - this can take up a lot of disk space. Whenever possible,
a shared caching method should be considered or use application virtualization solutions
which dont use a local cache at all.
Secondly, impact on IOs on the storage cannot be taken lightly. On a physical desktop the
number of IOPS is the last thing to worry about, but with shared storage this is one of the
biggest challenges in a VDI project.
Example tools to inventory and analyze the behavior of applications are Liquidware Labs
Stratusphere FIT and Lakeside Software SysTrack. These collect metrics to determine
help determine suitability for application virtualization.
6.4
Version 4.0
February 2013
Page 28/53
Both Microsoft App-V and VMware ThinApp are very close in overall performance overhead,
resulting in very similar VSImax scores. However, Citrix Application Streaming overhead
was considerably higher: the overhead is currently more than App-V and ThinApp. The
highest VSImax score was achieved with ThinApp 4.6, where the ThinApp packages were
locally stored in the VM image. From a disk I/O perspective VMware ThinApp showed the
least overhead throughout the test.
Interestingly, the response time of the file-open dialogue is much higher with Citrix
Streaming, this clearly impacts VSImax results. Also, it is interesting to see how Application
virtualization is maturing, for instance ThinApp 4.6 clearly outperforms ThinApp 4.5 in our
tests.
The storage impact on read and write IO was also investigated and the general conclusion
is that streaming applications will decrease the read IOs by 20% to 44% and increase the
write IOs by 20% to 44%. From a management point of view, choosing on demand
application streaming as the delivery method brings considerable management benefits and
will offload read I/Os. However, the impact on write I/Os should not be neglected.
Project VRC highly recommends validating the data in this document carefully. Project VRC
realizes that there are always valid reasons not to use specific settings as mentioned in this
paper. Real world VDI environments will always be different from the test-setup in the
Project VRC labs. More importantly, Project VRC must emphasize that it is crucial to test
and validate these optimizations in your own VDI deployment. Read the full whitepaper at
www.virtualrealitycheck.net
Version 4.0
February 2013
Page 29/53
7.
7.1
INTRODUCTION
To get an overview of the major players in the application virtualization space, a number of
solutions are explained in this chapter (sorted alphabetically by vendor). The goal of this
chapter is to have a better understanding of the application virtualization space from a vendor
perspective in their own words.
Note: The vendor solution descriptions are provided by the vendors. However, we have
attempted to remove the marketing fluff wherever possible.
7.2
CAMEYO
Cameyo is a free, open-architecture application virtualization product. It combines best-ofbreed application virtualization technology with simplicity. Cameyo allows you to package entire
applications into a single standalone executable, eliminating the need to install and providing
you with great portability.
Whether you are a home user or an enterprise IT administrator, with Cameyo you can take
your applications with you or deploy them very easily. Source:
http://www.cameyo.com/products.aspx
Cameyo have a website containing already packaged applications available to download for
free. They even have a feature in which you as user, can use an Online packager. Which will do
the packaging for you without any need for you to use your own environment for performing
the capture. Cameyo has also bravely attempted to work on a solution for 'virtualizing' drivers,
for now this is a 'secret feature' that has not been fully fleshed
(http://cameyoco.blogspot.co.il/2012/04/latest-cameyo-2.html) out but it's a start and
seemingly more than any other application virtualization vendor has provided, thus far. With
such ambitious offerings already and an eagerness for user feedback, we look forward to the
progression of this already exciting solution.
7.3
Version 4.0
February 2013
Page 30/53
7.4
EVALAZE
German software vendor Dgel IT-Management built an application virtualization product called
Evalaze of which version 1.0 shipped March 2011. Evalaze is an application virtualization
solution that converts Windows applications to single executables. Because it is a user mode
solution we see a lot of similarities with the other user mode solutions on the market. For
example Evalaze doesnt require a client, driver or admin rights on the target systems.
Evalazed, as the vendor calls it, applications can be run from USB storage devices also.
In contrast to the competition Evalaze also offers a free version of its product to create .exe
files. Another difference with the current market is that the vendor offers a virtualization service
for customers. When dealing with many or complex applications, the customer can upload their
software and download a virtualized version later. www.evalaze.de for more information.
Version 4.0
February 2013
Page 31/53
7.5
INSTALLFREE
WatchDox acquired InstallFree to provide secure document viewing, editing on Any platform
Note from the author: InstallFree was one of the application virtualization solutions and now
has been removed from this whitepaper because their focus isnt application virtualization
anymore.
7.6
Version 4.0
Layer 1 Installed Permanent this copies the file to the specified location on the
users system when the application is first virtualized and the file is left behind even
once the application is removed. We generally use this for the data files that might
come with an application, like an .mdb file or personalization registry settings. It is also
used for things that you would want to be persistent should the application be
virtualized again in future as the files are not overwritten if already present.
Layer 2 Installed Temporary this copies the file to specified location on the users
system when the application is first virtualized but the file is then deleted when the
application is removed from the player. This might be used for files that you want to
have on the machine but put outside of the control of Jukebox, but then remove them
when the app is removed in order to leave a clean state.
Layer 3 Virtual Integrated this is a virtualized file or key that can be seen by the
rest of the system and is visible in the file system and registry, as if locally installed but
its use is restricted by Application Jukebox
February 2013
Page 32/53
Layer 4 Virtual Isolated this is a virtualized file or key that is isolated (sandboxed)
and is only visible from within the virtualized application
An important thing to understand is that applications do not have to be either all isolated or all
integrated; the level of virtualization can be set for each file and registry key. For example
alternatively you might have a fully isolated application but have the files and registry keys for a
PDF printer plug-in as integrated. Or you can have all of the application integrated or isolated
as a whole if you want to.
MIXED MEDIA STREA MING
Application Jukebox makes it possible to stream applications from different media sources; CD,
USB stick or network delivery. This gives the Enterprise increased flexibility in deploying
applications. For instance, if a user is in a remote location with limited network access, they can
receive a preloaded application on a CD containing only the necessary data to launch the
application and then stream any additional data blocks as needed, on-demand from the
network.
MULTISTA GE PROGRESSIVE STREA MING
Applications can have additional blocks of data streamed using macros once the activation and
prefetching have taken place. An Enterprise can publish an application with a small prefetching
allowing users to start working more quickly, while in the background additional data is being
streamed.
INCREMENTA L PA TCHING
When bug fixes and minor point versions of applications are released, Enterprises need to get
the updates to their users in a timely manner; Application Jukebox makes it possible to quickly
and easily patch the application and stream only the differential, not the whole application
saving time and effort.
A NYTIME A NYWHERE
Application streaming and virtualization gives users on-demand access to desktop applications
anytime, from anywhere. Application Jukebox dramatically reduces the cost and complexity of
delivering applications to desktop and laptop computers across the enterprise.
REDUCED TOTA L COST OF OWNERSHIP
Most organizations deploy and manage their business applications using methodologies that
were introduced over a decade ago prior to the digital age and the internet phenomenon as
we know it today. The exponential growth of our dependence on the PC, and the increase in
remote workers, has led to a spiraling application and hardware Total Cost of Ownership (TCO).
Application Jukebox allows organizations to rapidly deliver desktop applications, upgrades and
patches. It gives users access to software as they need it, when they need it and where they
need it on a pull-based application delivery model. Maximizing existing infrastructure
organizations can serve many more users per server, dramatically reducing TCO.
A VOID COMPA TIBILITY A ND STABILITY ISSUES
Application Jukebox avoids application compatibility issues by isolating the streamed application
from other applications configuration/run-time environment and dramatically reduces the cost
and complexity of delivering applications. Software delivery becomes an on-demand service
Version 4.0
February 2013
Page 33/53
one where the latest release of the application is always accessible, where application
maintenance releases are automatically detected and instantly made available. Central
administration eliminates the need to recall or visit the client computer. By isolating the
streamed applications, the enterprise can guarantee software stability with an immediate roll
out of new builds to their users. This reduces the need for complex and lengthy regression
testing procedures and the need for an intricate testing infrastructure.
7.7
Version 4.0
February 2013
Page 34/53
Novell ZENworks Application virtualization offers three ways to create and configure virtualized
applications. The best method in a given situation depends on the nature of the application.
Novell ZENworks Application virtualization includes a number of auto-configuration wizards for
popular applications, which can be built and customized using a guided, step-by-step process.
This simple method is recommended for first-time users.
Snapshot an application installation. The snapshot captures a systems state before and
after an application is installed and automatically configures virtual application settings
based on observed system changes. This method is ideal for virtualizing off-the-shelf
applications.
Manually configure an application. This method is most often used by developers who
are virtualizing internally developed applications. While manual configuration requires a
high degree of technical knowledge about the applications inner workings, this does
allow extremely fine-grained control over virtual application settings. Because of the
tremendous number of variables involved, users should refer to product documentation
for additional help and insight.
Convert ZENworks AXT-based applications. Novell ZENworks Application virtualization
makes it easy to convert your legacy ZENworks applications to virtual applications and
make them a fully integrated component of your virtual application environment.
7.8
MICROSOFT APP-V
Microsoft Application virtualization (App-V) transforms applications into centrally-managed
virtual services that are never installed and don't conflict with other applications. App-V streams
applications on-demand to desktops, servers and laptops. It changes application management
from a series of tedious, manual tasks into an automated, streamlined process. App-V
dramatically accelerates application deployment, upgrades, patching and terminations by
eliminating time-consuming processes and simplifying the application management lifecycle.
With App-V, applications run reliably without failureno matter what other software is running
on that computer. All applications are instantly available on any licensed device. App-V even
allows controlled application use when users are completely disconnected. Because App-V
centralizes management of applications, users can only get the applications they have the rights
to; application usage and license metering are managed centrally so that administrators can
ensure compliance. Centralized control also enables IT to patch or upgrade once to the server
and the next time the users access the network, their applications are updated without
Version 4.0
February 2013
Page 35/53
impacting their productivity. App-V provides various delivery mechanisms including http and file
streaming, SBC integration, and standalone mode which provide application caching on the local
client for offline usage.
Microsoft Application virtualization fully integrates with Microsoft System Center Management
products, providing both users and administrators a seamless experience for running and
managing applications in the enterprise.
Application virtualization is at the heart of Microsoft Application virtualization . It decouples
applications from the operating system and enables them to run as network services.
Application virtualization can be layered on top of other virtualization technologiesnetwork,
storage, machineto create a fully virtual IT environment where computing resources can be
dynamically allocated in real-time based on real-time needs. App-V's patented application
virtualization, dynamic streaming delivery, and centralized management technologies make
everything from deployments and upgrades to migrations and business continuity initiatives
easier and faster with better agility:
Application virtualization: Enable applications to run without the need to visit a desktop,
laptop, or terminal server. Applications are no longer installed on the clientand there is
minimal impact on the host operating system or other applications. The most extensive
virtualization technology on the market, App-V virtualizes per user, per application instance, as
well as key application components. As a result, application conflicts and the need for
regression testing are dramatically reduced.
Dynamic streaming delivery: Applications are rapidly delivered, when needed, to laptops,
desktops, and terminal servers. In most cases only a small percentage of the application is
needed to launch the application. Additional components are delivered when transparently
requested by the application. This results in faster delivery of the application when needed.
Centralized, policy-based management: Virtual Application deployments, patches,
updates, and terminations are more easily managed via policies, and administered through the
App-V console or via your ESD system. Use Microsoft App-V Application virtualization to help
reduce the complexities inherent in enterprise application management. With App-V you can
reduce challenges and transform your computing environment into a dynamic, services-oriented
Version 4.0
February 2013
Page 36/53
infrastructure.
Version 4.0
February 2013
Page 37/53
App-V 5.0 no longer requires a dedicated drive (e.g. Q:\) to be available on the client devices or
available on sequencing machines. As stated earlier App-V 5.0 is less rigid with isolation and
rather that making the file system completely invisible to the end user, the file system is now
mounted in the hidden ProgramData folder. Users could navigate to this directory and launch
the application if they are clever enough. By making this change, we all get the reduced
limitation when it comes to application virtualization, thank to less rigid isolation.
A really big win for App-V 5.0 is it's optimization for VDI environments. Microsoft have worked
on the Read Only Cache concept which many have used with 4.x in VDI environments and
provided a more intuitive solution. You can now also set whether or not the application should
fully cache on a per application basis during sequencing. The background loading is now much
more staggered and slow, which is great for a VDI environment as it ensures resources are not
being drained needlessly and priority is only given to stream applications quickly, when they
have been launched.
SCCM 2012 SP1 (just released as of the creation of this document) also appears to promise a
much more comparable experience to the App-V Management Server than was experienced
when using earlier version of App-V with SCCM 2012 and SCCM 2007 R2. This new version of
App-V is the first major overhaul of the product since Microsoft purchased it and it's an exciting
move forward.
7.9
Version 4.0
February 2013
Page 38/53
Currently Roozz supports all web browsers on the Windows platform; versions for Mac, Linux,
Android, etc. are being developed. The current version of Roozz Plugin can only execute
Windows desktop applications on Windows machines. Application files are cached and executed
on the end user CPU. The Roozz Technology encapsulates the application in a thin sandbox,
when running on the end users machine. - Resulting in exactly the same execution speed and
end user experience, as when installed on the Desktop. Through their login a user can access
their rented applications on any machine that has the Roozz plugin installed.
The Roozz download technology allows the application to start before all the files are
downloaded. E.g. a game can start when the first level out of ten has been downloaded.
Similarly it also handles automatic updating seamlessly, when files change on the server. The
Roozz Backend is hosted on Microsoft Azure Cloud with more than 25 file servers globally.
In November 2011 Roozz received seed funding from Denmark's largest seed fund, Seed
Capital (http://www.seedcapital.dk/portfolio/it/roozz) and in November 2012, Accelerace Invest
joined the team of investors. Also in November, Roozz exceeded 1 million downloads of its
plugin and now has some 150 titles online.
Roozz total has a total of 10 employees with the main office in Copenhagen and staff also in
Poland and Russia.
7.10
SPOON
About Spoon
The company started in 2003 as Xenocode, but changed its name in May 2010 to Spoon.
Spoon offers the technology to virtualize and stream applications across the web to deploy
them efficiently to any Windows desktop.
With the change of the company name now also comes a strong focus on delivering any
Windows application over the web directly to the end-user. Spoons technology enables oneclick access to applications via internal and external websites and the desktop. This makes the
Spoon technology ideal for software publishers to distribute their products directly to end-users
Version 4.0
February 2013
Page 39/53
without intervention of the normal distribution channels. A good example is Autodesk deploying
its Inventor Fusion Technology Preview software using the Spoon technology.
Application virtualization and adaptive streaming
The core of the companys virtualization technology is the Spoon virtual machine (VM) kernel.
The Spoon VM Kernel is a user-mode virtualization solution able to run applications without
client installations or administrative privileges requirements for the user. The kernel is a
compact implementation of Windows operating system APIs, including the file system, registry,
process, and threading subsystems, completely implemented within the user mode space.
Based on the behavior of the user, Spoons streaming technology transfers application
components in the background. Spoon streaming works over HTTP and works with webservers, Content Distribution Networks (CDNs) and desktop management solutions. More
information about the streaming technology can be found here:
http://spoon.net/Server/Spoon-Streaming-White-Paper.pdf
Spoon Studio
Spoon Studio is the software used to enable virtualization of Windows applications. Spoon
Studio comes in three editions which basically differ in the usage focused on deployment of
virtual applications by means of the Spoon Server or standalone executables.
Spoon Server
Spoon application streaming is powered by the Spoon Server which streams the virtual
application to the end user via HTTP. The Spoon Server offers its own application portal or can
be used in combination with existing web portals like Microsoft SharePoint, IBM WebSphere or
just by adding HTML code a custom webpage. Besides, managing applications, users, groups
and their rights, Spoon Server allows for detailed analytics, all from a single web interface.
Spoon Browser Plugin
Version 4.0
February 2013
Page 40/53
Spoon web delivery uses a small browser plugin that integrates Spoon streaming and
virtualization functionality directly into the users web browser. The plugin takes only a few
seconds to configure, does not require any browser restart, and can be installed without
administrative privileges on the desktop.
7.11
Version 4.0
February 2013
Page 41/53
Version 4.0
February 2013
Page 42/53
License Management
Symantec Workspace Streaming provides businesses improved control of their application costs,
with a web-based, centralized view of application usage data across their extended network,
including up-to-date statistics on the number and location of application licenses installed and
usage statistics, such as time and frequency of use. License allocation management and
compliance features include:
Version 4.0
February 2013
Page 43/53
7.12
Remove an idle application package from a client cache after a pre-defined period of
non-use.
Monitor and enforce license compliance for offline applications.
Automatic notification to the administrator upon reaching a predefined threshold of
license utilization.
VMWARE THINAPP
Run any version of virtually any application on a single operating system without conflicts. You
can even run multiple versions of the same application. Plug VMware ThinApp, formerly known
as Thinstall, into your existing management infrastructure and accelerate your software
development and desktop deployment. Deliver and deploy applications more efficiently, more
securely, and more cost-effectively with agentless application virtualization.
ELIMINA TE INSTA LLA TION CONFLICTS WITH A PPLICATION VIRTUA LIZATION
Application virtualization encapsulates the applications from the OS and each other; eliminating
costly regression testing and conflicts from badly behaving applications. Just plug in an .MSI or
.EXE file to deploy a virtual system environment, including registry keys, DLLs, third-party
libraries, and frameworks without requiring any installation of agents or applications on the
underlying operating system.
PA CKA GE ONCE, DEPLOY EVERYWHERE (NETWORK, USB, PHYSICA L OR VIRTUA L DESKTOPS)
Deploy virtualized applications in user mode, without administrative rights. No device drivers
are installed and no registry changes are made because the entire application and its virtual OS
are delivered as a single EXE file. Transparently stream large applications from a shared
network drive with no server or client software to install. Upgrade or roll-back applications while
theyre running. The new version will execute the next time the user starts the application.
CA TER TO YOUR MOBILE WORKFORCE
Let your users run applications on virtually any computer they have access to, including kiosk
and hotel PCs. They wont need to install software or device drivers and wont need admin
rights. Applications run directly from portable storage devices, including Flash drives.
IMPROVE YOUR SOFTWA RE DISTRIBUTION PROCESS
Deliver software that protects the local OS from modifications that might cause instability or
breach security using your existing configuration management tools. Even restricted user
accounts can safely run virtualized applications without requiring a local installation, making it
much more appetizing for IT staff concerned about security.
EA SE OS A ND A PPLICATION MIGRA TIONS
ThinApp agentless application virtualization eases OS migrations by enabling applications to run
side by side on the same operating system. Users can continue with business as usual without
disruption from problematic applications. Furthermore, if an application needs to be removed
from the endpointit is a simple file-remove with no mess left to clean up in the system
registry.
LANDesk is OEM-ing the Application virtualization engine from VMware and has added specific
functionality, such as deep integration with LANDesk Client Management Suite, to the solution.
Version 4.0
February 2013
Page 44/53
8.
8.1
PRODUCT VERSION
This detailed feature compare matrix is developed with the following products and versions:
Product
Version
Cameyo
Citrix Application Streaming, XenApp
Numecent / Endeavor Application Jukebox
Microsoft App-V
Microsoft App-V
Spoon
8.2
2.0.834
6.7; Streaming Profiler and offline plugin 6.7
8.3, Enterprise Edition in virtual isolated mode
4.6 Service Pack 2
5.0
2012, Spoon Server: 2.0.8.14
Virtual Application Studio: 10.4.2380
Spoon Sandbox Manager 3.32
6.1 SP8
4.7.3
SCOPE
The scope of the feature compare matrix is to have focus on the application virtualization
solution. Integration with Microsoft SCCM or other Client Management Solutions or integration
with workspace aggregators such as VMware Horizon or VDI solutions such as VMware View
which will add valuable functionality to the solution in general is out the scope of this
whitepaper. From a Symantec perspective the focus of the feature compare matrix is to use
both Symantec Workspace Streaming (SWS) and Symantec Workspace Virtualization. Its out of
scope for this whitepaper to explain the It depends remarks.
8.3
Legenda:
= Applicable; X = Not applicable; ~= It depends; # = under development by PQR
A green or red X has nothing to do with advantage or disadvantage of a solution. It just
present the availability of the functionality.
Version 4.0
February 2013
Page 45/53
Version 4.0
February 2013
X
X
X
X
X
X
X
X
X
X
VMware ThinApp
Symantec
X
X
X
~
X
Spoon
Numecent
Microsoft App-V v4
NUMECENT
Microsoft App-V v5
Category Functionality
Virtualization Characteristics
The Solution is capable to fully virtualize/isolate Applications
The Solution is capable to fully integrate Applications with local Operating System
Configurable virtualization and integration
Solution allows multiple layers of integration(Isolated/virtualized or non-isolated
Applications will operate without any chance of conflicts
Applications integrates and communicates seamless with the OS
Manageability
Central management platform for application delivery
The solution is usable in SaaS scenario. SPLA licensing is available; applications are on-demand streamed and delivered as a service, pay per-use.
Application is delivered in a very efficient way, quick up-and running.
Stream only data which is needed to start application.
Application specific license metering, track application usage
Application virtualization Solution license usage tracking
Role based administration
Application rollback
Application has to be shut down for upgrade
Application upgrade, centrally managed
Application upgrade while in use
Cameyo
Remarks
X
X
X
Isolation mode =
X App-V only Office 2010/2013
X
X
X
~
X
X
X
X
X
X
Page 43/53
Version 4.0
February 2013
VMware ThinApp
Symantec
Spoon
Microsoft App-V v4
NUMECENT
Microsoft App-V v5
Numecent
Category Functionality
Application upgrade using deltas
The Communication between server and client can be secured without additional solutions
Native integration with 2+ Client Management solutions; No difference in manageability, support, deployment scenarios and inventory between installed and virtualized applications.
Pre-launch and post-exit scripting
Pre-launch and post-exit scripting, centrally managed via GUI
Determine virtual application pre-requirements
Determine virtual application pre-requirements, centrally managed
Determine virtual application pre-requirements, centrally managed via GUI
Limit application usage based on AD security groups, Controlled from AV solution
Limit application usage based on AD computer objects, Controlled from AV solution
Limit application usage based on AD OU's, Controlled from AV solution
Machine targeting, centrally managed
Machine targeting, application runs dependent of target OS, centrally managed
Machine targeting, application runs dependent of target OS/language/service pack, centrally
managed
Application streaming source can be based on client IP-subnet
Application streaming source can be centrally managed
Offline application usage can be time limited
File Type Association (FTA) centrally and standalone managed
Cameyo
Remarks
X
X
X
X ~
X X X
X
X
X
X
X
X
X
X
X
X
X
X
X
~
X
X
~
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X SCCM
~
~
X
X
Page 44/53
Version 4.0
February 2013
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
#
VMware ThinApp
X
X
X
X
X
X
X
X
X
X
X
#
X
X
Symantec
~
X
X
X
X
X
X
X
X
X
#
X
X
Spoon
Numecent
X
X
X
X
X
X
X
X
X
X
Microsoft App-V v4
NUMECENT
Microsoft App-V v5
Category Functionality
File Type Association (FTA) locally managed
Support for the protocol handler MAILTO://
Support for the protocol handlers MAILTO://, FTP://, FILE://
Manageable by scripting; command-line
Manageable by API/ WMI
Manageable by PowerShell - Client
Manageable by PowerShell - Server
Software development kit(SDK) available
Integration with Add or Remove programs
Group policies can never, from a security point of view, be omitted
Interoperate with roaming user profiles;
Event logging on client
Event logging on management server
Application advanced debugging option part of the solution
Windows Class isolation
Requires short file name support to be enabled
Pre-packaging diagnostics to check if packaging machine is configured correctly
Post-packaging diagnostics to check for issues and/or unsupported technology
Support for application templates for a higher packaging success ratio
Compatible with software protection and/or 3rd party DRM solutions
Cameyo
Remarks
Only with Citrix Receiver
X
X
X
#
X
Page 45/53
Version 4.0
February 2013
Numecent
Spoon
Symantec
VMware ThinApp
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Microsoft App-V v4
NUMECENT
Microsoft App-V v5
Category Functionality
Usability
Desktop and/or Laptop Online
Desktop and/or Laptop Offline
Microsoft RDSH (Remote Desktop Services) supported
Applications can run anonymous, without authentication with a directory service
No Microsoft Active Directory or NT4.0 domain required for management platform
(management is key)
Usable and supported in a Novell NDS environment
Usable and supported in a Novell eDirectory environment
Application can run from removable storage without installing a client/agent component
Application and user preferences can run from removable storage without installing a client/agent component
Application package is portable and can be stored on and imported from removable storage
Official Support for EN localized Windows client operating systems
Official Support for EN/DE/FR/ES localized Windows client operating systems
Official Support for JP/Simple Chinese localized Windows client operating systems
URL redirection to Virtualized Internet Explorer(s); locally configured
URL redirection to Virtualized Internet Explorer(s); centrally managed
Application Characteristics
Compression of virtual application package
Cameyo
Remarks
Page 46/53
Version 4.0
February 2013
X
X
X
X
X
X
~
X
~
VMware ThinApp
X
X
X
X
X
#
Symantec
Spoon
Numecent
~
~
~
#
Microsoft App-V v4
NUMECENT
Microsoft App-V v5
Category Functionality
Dynamic path relocation
Possible to package and deliver application with build-in kernel mode drivers
Virtualization of applications with user mode services
Virtualization of applications with boot time services
Virtualization of services that require privilege
Application package can be digitally signed with a certificate
Files and Registry virtualization
COM virtualization
COM+ virtualization
DCOM virtualization
Named Pipes isolation
Side by Side(SxS) support for virtualized applications
Virtualization of fonts on desktops
Virtualization of fonts on terminal server
Communication between different application virtualization environments
Performance impact when virtualized applications communicate with each other
Run application with elevated privileges(RunAs)
Compatible with Windows User Account Control
Windows long filename support
Microsoft .NET framework virtualization
Cameyo
Remarks
X
SWV Single DCO instance
Page 47/53
Version 4.0
February 2013
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
~
VMware ThinApp
X
X
X
Symantec
X
X
Spoon
X
X
Microsoft App-V v4
NUMECENT
Microsoft App-V v5
Numecent
Category Functionality
(Virtual) reboot during packaging supported
Terminal Server drive remapping supported
Windows Dynamic disks support
No maximum application package file size limitation
DOS applications support on x32 platform
Win16 application support on x32 platform
Win16 application support on x64 platform (Windows limitation)
Win32 application support on x64 platform
Win64 application support on x64 platform
MSI to virtual application package conversion wise package studio
MSI to virtual application package conversion build-in
Cameyo
Remarks
4GB
X
X
X
Page 48/53
VMware ThinApp
Symantec
# # X
Spoon
Microsoft App-V v4
NUMECENT
Microsoft App-V v5
Numecent
Category Functionality
Microsoft Office 2010 deployment without physically installed requirements
Cameyo
Remarks
E.g. Microsoft Office 2010
Deployment Kit for App-V or
Visual C++ for EVS
Architecture
Management platform is included
Application delivery using (streaming) HTTP/S protocol
Application updates delivered using (streaming) HTTP/S protocol
Application delivery using proprietary protocol (RTSP/s)
Application delivery using SMB / fileshare
No need for client/agent installation
Virtualization with client-code in user-mode
Virtualization with client code in kernel-mode
Original Microsoft Windows APIs are used by application
Multiple concurrent client or agent versions on the same platform
Memory sharing in multi-user environment
No need for a license service
No need for a file share
No need for dedicated server
MSI wrapper to deploy virtualized applications with ESD
No need for ESD infrastructure for enterprise wide deployment
Version 4.0
X
X
X
X
X
~
February 2013
X
X
X
#
X
X
X
X
#
X
X
X
X
X
X
#
X
X
X
~
X
X
X
#
X
X
X
~
Page 49/53
Version 4.0
February 2013
X
X
X
X
X
X
X
X
X
X
X
X
X
X X X X
X
X ~ X X
X
X
X
X
X
X
#
X
VMware ThinApp
X
X
X
X
X
X
#
X
#
#
Symantec
#
#
X
X
X
#
Spoon
Numecent
X
X
X
X
X
X
X
X
X
#
X
X
X
Microsoft App-V v4
NUMECENT
Microsoft App-V v5
Category Functionality
Data store can be on: Microsoft SQL Express Edition
Data store can be on: Microsoft SQL
Data store can be on: Oracle
Data store can be on: IBM DB2
Data store can be on: MySQL
Data store is XML based
The Application package format is open and documented
The Application package format can be encrypted; native tools available
Client-side persistent cache,
Centralized shared cache
Support for journaling
Support for application white listing (Applocker Windows 7)
Block Caching by network WAN acceleration devices
Solution can integrated with Content Delivery Networks such as Akamai
End user experience
Full Windows Explorer context menu integration
User driven application repair; repair via normal UI/GUI
Application behaves in essence the same as an installed application, apps are fully integrated
with other applications and local OS
User settings are preserved between application launches
Cameyo
X
X
X
X
X
X
X
#
X
#
X
X
X
X
#
X
X
X
X
X
X
X
X
X
X
X
Remarks
Page 50/53
Version 4.0
February 2013
Spoon
Symantec
X
X
X
X
X
X
X
X
X
X
X
X
ThinApp Factory
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
VMware ThinApp
Numecent
X
X
X
X
X
Microsoft App-V v4
NUMECENT
Microsoft App-V v5
Category Functionality
User settings can be redirected and stored on the network
User settings can be streamed between user and server
Localized client interface available, 4+ languages (EN/DE/FR/ES)
User Self Provisioning web portal
Allow EULA/Message to be displayed at virtual application startup
Allow user to easily terminate virtual environment (incl. running child processes)
Supported Client Platforms
Windows NT 4 Workstation
Windows NT 4 - Terminal Server Edition
Windows 2000 - Pro
Windows XP - Pro (SP2 and up)
Windows XP - Embedded
Windows 2000 - Server
Windows 2000 - RDSH
Windows 2003 - Server
Windows 2003 - RDSH
Windows Vista
Windows Server 2008 - Server
Windows Server 2008 - RDSH / Remote Desktop Session Host
Windows Server 2008R2 - RDSH / Remote Desktop Session Host
Cameyo
Remarks
Page 51/53
Version 4.0
February 2013
Spoon
Symantec
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
~ Wine (limited)
~ CrossOver (limited)
X
X
X
X
X
X
X
X
X
X
# X
# X
VMware ThinApp
Numecent
X
X
Microsoft App-V v4
NUMECENT
Microsoft App-V v5
Category Functionality
Windows Server 2012 - RDSH / Remote Desktop Session Host
Windows 7
Windows 7 x64
Windows 8 RT
Windows 8 x86
Windows 8 x64
MacOS, deliver and execute Win32 applications on MacOS
Linux, deliver and execute Win32 applications on Linux
Licensing Model of Solution
Concurrent
Device
Unlimited
Per named user
Free for personal usage (FFPU)
SPLA
Solution in general
Proven technology, the solution is being used for 2+ years in enterprise production environments. Packaged 1000+ different apps, various deployment scenarios
Varity (10+) of public available enterprise references in Europe
Varity (10+) of public available enterprise references in US
Cameyo
Remarks
~ ~
~ ~ Not public available
~ ~ Not public available
Page 52/53
8.4
X
X
X
X
X
X
X
X
X
VMware ThinApp
X
X
X
X
Symantec
X
X
X
X
Spoon
Numecent
X
X
X
X
Microsoft App-V v4
NUMECENT
Microsoft App-V v5
Category Functionality
Doesnt require a clean OS during packaging process
Packager can capture only installer process
Packager can capture all processes
Possibility of creating a High Available platform; additional services needed
Load Balancing is part of the solution
Official application virtualization training classes available
Official Certification program, VUE or Prometric
Company website for delivering (demo) 25+ applications to community
Company website for delivering (demo) 50+ applications to community
Large community resource, share recipes, FAQ, discussion
Cameyo
X
X
~
X
X
X
Remarks
FUTURE ADDITIONS
-
TBD; If you have any comments, corrections, or suggestions for improvements of this document, we want to hear from you! Please send e-mail to Ruben
Spruijt ([email protected])
Version 4.0
February 2013
Page 53/53
9.
CHANGE LOG
Change log created in version 3.1 of the document, October 2011;
Version 4.0
Page 52/53
Version 4.0
February 2013
Page 53/53
10.
CONCLUSION
Which Application virtualization Solution is THE best?!
Without a better understanding of the requirements in general it is impossible to give an
accurate and profound answer on THE question. In essence it depends on various areas as
mentioned in detail in paragraph 4.3 Strategy.
Key areas for your Application virtualization strategy are:
What do you want to achieve?, lowering TCO?, business enabler, overall cost of
ownership and cost reducer?
What are the use-cases? and does the use-case require Application virtualization?
Are you investigating a tactical (point) or strategic solution? What do you want to
solve?
What is the strategy around Client Management, PC life Cycle Management, solution
and how does Application virtualization fit?
Is a Bring Your Own Computer (BYOC) concept one of the key Access Scenarios?
What is your application delivery model? Is delivery of applications focused on SaaS,
Enterprise, SMB or the Consumer space?
Is a client or agentless Application virtualization solution required?
Do you need to integrate and/or isolate your applications from each other? Do you
need both functionality and how do you manage the application integration?
Whats your overall Application and Desktop Delivery strategy model with
solutions such as Laptop (Offline), Desktop (Online), VDI and SBC? How can Application
virtualization enhance these solutions?
Whats your overall Enterprise Mobility strategy with App-ification, MDM/MAM,
Secure Access, Data Access, Networking, Security and BYO. Enterprise Mobility is an
architectural challenge.
Does the Application virtualization solution offer shared-cache or cache-less
functionality? What is the use-case?
Bottom Line: Whats your current Application and Desktop Delivery
strategy?!
Its important to have a Vision and Strategy around Application and Desktop Delivery.
Designing, building, managing and maintaining the Optimized Desktop infrastructure using the
right Technologies, corresponding vendors and products is an important step.
This whitepaper is a useful resource in this journey!
Keep in mind:
Version 4.0
February 2013
Page 54/53
as
PQR B.V.
Rijnzathe 7
3454 PV De Meern
The Netherlands
Tel: +31 (0)30 6629729
Fax: +31 (0)30 6665905
E-mail: [email protected]
www.PQR.com
as