Microsoft Application Virtualization (APP-V) 5.

Anil Popuri, BPS_WT-Practice

Document Control

Document Information

File Name BPS_All_Presentation_Template_V2.0

Owner Anil Popuri

Author Anil Popuri

Distributed To / Contributions by

Updated / Revised By

Reviewer Priya Agarwal

Approver Ajay Walia

Issue Date 18/12/2013

Revised Date
BPS ALL
Practice

Revision History

Version
Date Prepared by/Modified by Significant Changes
No.
1 18/12/2013 Anil Popuri Initials Draft
Agenda

Microsoft Application Virtualization (APP-V) 5.0

 Application Virtualization Introduction & Why Microsoft

APP-V
 Citrix and APP-V (How APP-V is different from Citrix and
how Citrix + APP_V work together)
 APP-V Product components
 Installing MS APP-V Management and Publishing Server
 Installing MS APP-V Desktop Client
 Installing MS APP-V Sequencer
 Sequencing walk through & Package Editor
 Handling Upgrade &Connection Groups
 Dynamic Configuration files and Scripting
 Publishing the Application
 Devices that can access APP_V + OS which support APP-V
Application Virtualization Introduction

Application virtualization separates the app from the OS, allowing IT to deliver applications in the
most efficient way possible.
It is a software layer that improves portability, manageability and compatibility of applications .
Application Virtualization Advantages:
AppA v1.0 AppA v2.0 AppB v1.0 AppB v2.0
 Application don't have to install apps
Application Virtualization Layer
 Easy to patch and upgrade
 Can run multiple versions of same application
OS Layer
 In the age of BYOD, application streaming
allows to deliver apps to many kinds of
Hardware base physical machine
endpoints.

Application Virtualization Tools:

Microsoft App-V
Symantec Workspace Streaming
VMware ThinApp
InstallFree Bridge
Endeavors Application Jukebox
Why enterprise need Application Virtualization

Applications are isolated

 Isolation allows the application to behave consistently regardless of the changes in the
OS or other applications in the system
 Lowers application testing costs for enterprises

Applications are delivered on demand (SaaS)

Brings the benefits of Software as a Service (SaaS) to rich Windows applications
Applications can be streamed from a variety of locations: locally, IIS server, App-V
Server, System Center Configuration Manager or other Electronic Software Distribution
(ESD) products and devices

Centralized management and servicing

Service in one central location, stream to all users
User based application targeting
Simplified management and deployment of applications to enterprises
Why enterprise need Application Virtualization
For Immediate Cost Savings
Simple, Easy, and Cost-Effective Application Management
Save
$21
REDUCE Less demand
IT costs for application-related
for application user support
Faster Application
Cost
Testing & Preparation
Savings
REDUCES IT throughout
cost by Delivery
by $26/pc/yr $21/pc/yr
REDUCES IT
Streamlined Process REDUCES Lifecycle:costs by $13/pc/yr
IT costs by $22/pc/year
the Application
• 82% said users spend less time dealing with application issues
• 31% less time for application testing and • 83% deploy applications
• preparation rollout27%
Traditional before for labor savings
a mission-critical
delivery to the user applications
more quickly. Save
• Support calls were reduced an average of 18% $22
equivalent to • IT costs related to Cost without
• •46%
70%reported a decrease
say application in the timedecreasedapplication
virtualization time todeployment Virtualization
spent packaging
deploy $82/PC
applications
mission-critical annually decreased by an
applications by an average
average
of 52% $115

of 20% Cost with

Virtualization
Cost without $94
Virtualization
Save $75
Save
$13 Cost with
$12
Virtualization
Save $53
Save
$8
Cost without $6 Cost without
Virtualization Virtualization
$36 Cost without $36
Cost without
Virtualization Cost with
Cost with Virtualization
$24
Cost with Virtualization
Virtualization Cost
$21with
Virtualization Virtualization $24
$24
$16 $15

Application Regression Packaging Application Application Application

Compatibility Testing Testing Delivery Updates Support
Cost without Virtualization Cost with Virtualization
* Savings may vary per organization, Results based on respondents answers and applied to the
Microsoft War on Costs TCO Baseline
Why Microsoft APP-V

 Run applications as a “service”  Run applications without conflicts

 Access anywhere  No changes to system

 Safely run apps side-by-side
 Over the web
 No OS decay over time
 Portable devices  Lower migration costs
 Just in time deployment (Click-to-Run)  State separation
 Installer does not run  Store app state separate from
OS state
 Instant gratification
 State categorized as user versus
 Simple servicing system
 User state stored in profile,
 Update once, deliver everywhere
roams with profile
 Users automatically stay up to date
 Provides centralized management
 Reduces disk requirements  admins can limit users' access to
certain apps
 Integrates with Windows To Go  Popular in corporates moving to Windows

 Allows applications to stream over a WAN 7 or 8 and Enhanced application

using Direct Access diagnostics and monitoring

Citrix VS Microsoft APP-V

APP-V Integration with Citrix XenDesktop:

App-V integration started with Citrix from XenApp 6 and delivered applications to XD 5.6
desktops by installing App-V client on desktops.
Citrix now discontinued their streaming features in XenDesktop 7 (XenApp 7) and pushing
customers to use Microsoft APP-V for streaming solution.
Now XenDesktop 7 can configure and publish App-V applications directly from XD 7 Citrix
studio console to delivery groups.
When users logged on Citrix Store Front using Citrix Receiver, they will see all the applications
made available to them.
SystemGuard

SystemGuard tracks and analyses configuration repositories and resources used by the
application and intercepts the use of these resources, redirecting them to the virtualized instances
of the resources.
SystemGuard is the heart for Microsoft App-V Platform.

Enables Side-by-Side execution

Eliminates common application deployment

and management problems like:

• Application Conflicts
• Version Incompatibilities
• Multi-User Access
• Multi-Tenancy Issues
• Regression Testing
Microsoft APP-V Components

Microsoft Application Virtualization Management Server: The App-V Management Server

provides a centralized location to manage the App-V infrastructure for delivering virtual
applications.

Microsoft Application Virtualization Publishing Server: The App-V Publishing Server provides
with entitled virtual applications for streaming to the specific user and hosts.

Microsoft Application Virtualization Desktop Client: The App-V Desktop Client sets up and
manages virtual environments at runtime on Windows endpoints. It retrieves and publish the
applications on the endpoints.

Microsoft Application Virtualization Remote Desktop Services (RDS) Client: The App-V RDS
Client enables Remote Desktop Session Host servers to utilize the capabilities of the App-V
Desktop Client for shared desktop sessions.

Microsoft Application Virtualization Sequencer: The App-V Sequencer is a tool used to

transform traditional applications into virtual applications, which consists of APP-V supported
files.
Microsoft APP-V Architecture

App-V provides three methods for deploying application virtualization:

• Standalone Model via sequencing and client
• Streaming Model using the native streaming capabilities of App-V
• Full Infrastructure Model provides software distribution, management, and reporting
capabilities (includes application streaming)
Package Streaming & Methods

Application Streaming is the process of transporting the application specific data/content as

quickly as possible to the endpoints. Ultimately the required resource to run and use the
application is being delivered to the user.

RTSP: Real Time Streaming Protocol

SMB: Server Message Block
HTTP: Hypertext Transfer Protocol
Package Streaming Optimization
Feature blocks are designed to optimize the application streaming over Network. Below are few
benefits of feature blocks
 Creates minimum launch threshold that allows launching larger applications and does not require to
download the entire package.
 Helps to reduce the total network bandwidth used when launching the application for the first time
and saves hard disk space on the client.
 Enables users to have quick access to the applications upon deployment.

In App-V 4.x if we chose to optimize the package for streaming, it creates FB1 (Primary Feature Block) and FB2
(Secondary Feature Block).

In App-V 5.0, FB0 known as the Publishing

Feature Block, contains everything required for
the publish of our application such as icons,
metadata and scripts.
FB1 (Primary Feature Block), contains the
assets we need to launch our application.
FB2 (Secondary Feature Block): Contains
everything else required to function the
application.

Creating feature blocks is recommended in full infrastructure mode

Key Changes in APP-V 5.0

App-V 4.6 App-V 5.0

 Uses dedicated drive letter (Q: drive)  No dedicated drive letter required
 4GB package limit  No size limit
 Isolated from local applications  Virtual Application Extension
 Share middleware with Dynamic Suite  Share peer applications with Virtual
Composition Application Connection
 Read-only Shared Cache supports VDI/RDS  Shared Content Store can be updated with
environments normal App-V workflow
 Limited command-line scripting  Rich PowerShell scripting for sequencer,
 Installed management console client and server
 Web-based management
Microsoft Application Virtualization

Management Server
&
Publishing Server
Installing Microsoft APP-V Management Server

Active Directory Domain Services and DNS should configured on the DC computer
Configure the Active Directory Groups and Accounts
• Organizational Unit (OU)
• Microsoft Application Virtualization Administrative Group
• Microsoft Application Virtualization Users Group
• Microsoft Application Virtualization Computers Group
• Domain User Account
• Application Groups (Optional)
Install Prerequisites
• Microsoft .NET Framework 4.0 Extended
• Microsoft Visual C++ 2010 SP1 Redistributable 64-bit Package
• Microsoft Visual C++ 2010 SP1 Redistributable 32-bit Package
• Microsoft Silverlight
• Windows PowerShell 3.0
• Microsoft SQL Server 2008 R2

Configure the Application Server

• Add the Application Server role and all required role features needed

Configure IIS for Windows Server

• Add the web server (IIS) roles with required role service enabled

Register ASP.NET with .NET 4.0 Framework in IIS

• “C:\Windows\Microsoft.Net\Framework\v4.0.30319\aspnet_regiis.exe” –ir
• “C:\Windows\Microsoft.Net\Framework64\v4.0.30319\aspnet_regiis.exe” -ir
Installing Microsoft APP-V Management Server

Login to the server as a domain admin account and Run appv_server_setup.exe.

The Microsoft App-V Server 5.0 Setup wizard helps to Install & configure server
Installing Microsoft APP-V Management Server

Enter the Active Directory security group which will be responsible for managing App-V
infrastructure, in the Port binding field specify the port number and in the Website name specify
appropriate name.

After this, on the Ready page  install

on the Finished page Close
Configuring Microsoft APP-V Management Server

Configure the Publishing Server refresh interval: By default the Publishing Server asks the
App-V database for published applications every 10 minutes (600 seconds). This is called a
publishing refresh.
Can be changed by editing Registry hive:
HKLM\Software\Microsoft\AppV\Server\PublishingService,
find the value PUBLISHING_MGMT_SERVER_REFRESH_INTERVAL to modify

Share the content folder: The content share is the central library of App-V packages. The
content store contains the source files of the packages published by the App-V publishing
server. Should have access to App-V management server and AppV Administrators.

Configure Firewall to Allow Incoming Connections: Go to Control Panel, Windows

Firewall, Advanced Settings, Inbound Rules in the actions pane and cerate new Rule to open
888 & 889 ports.
Microsoft Application Virtualization

Client/Agent
Installing Microsoft APP-V Desktop Client

Login to the server as a domain admin account, Install .NET Framework 4.0, Windows
PowerShell 3.0 and after restart Run appv_client_setup.exe.

On the Microsoft Application Virtualization

(App-V) Client 5.0 Setup wizard, click Install

On the Software License Terms page, select I

accept license terms
Installing Microsoft APP-V Desktop Client

On the Microsoft Update Opt In page, select I

don’t want to use Microsoft Update

On the Customer Experience Improvement

Program page. Select Join the Customer
Experience Improvement Program

When the installation is complete, click Close

Installing Microsoft APP-V Desktop Client

Start All Programs  Application

Virtualization Client
Configuring Microsoft APP-V Desktop Client

Configure the App-V 5.0 client to communicate with the App-V 5.0 Publishing Server
Open Windows PowerShell as Administrator, import the App-V Client PowerShell module
 Import-Module appvclient
Then to register the publishing server:
 Add-AppvPublishingServer -Name name_of_AppV_Publishing_Server -URL http://name_of_appv_server:889
Then for initial sync and to test connectivity:
 Set-AppVPublishingServer –ServerID 1 –GlobalRefreshEnabled 1 –GlobalRefreshOnLogon 1

UserRefreshEnabled, Values: (0/1): Enables a publishing refresh for the user

UserRefreshOnLogon, Values: (0/1): Specifies whether or not a user refresh should be initiated at user logon
UserRefreshIntervalUnit, Values: (Hours(0) or Days (1)): Specifies the unit for the UserRefreshInterval setting
UserRefreshInterval, Values: (0-744): Specifies the frequency of the refresh with the publishing server, can be in
days or hours.
Microsoft Application Virtualization

Sequencer
Installing Microsoft APP-V Sequencer

APP-V Sequencer is used to create the virtual applications and application packages that are
streamed from the App-V Publishing Server to the App-V Clients.

 Always sequence 32-bit applications on a 32-bit sequencing OS and can be delivered to 64-bit
clients. Sequenced on a 64-bit sequencing OS, can only be delivered to 64-bit clients.
 The computer used for the Sequencer should have a fresh & clean windows operating system.
Do not install Sequencer on a computer that hosts Management Server or Desktop Client.

Login with domain admin account, Install .NET Framework 4.0, Windows PowerShell 3.0 and after
restart run appv_sequencer_setup.exe
 Installing Microsoft APP-V Sequencer

On the Software License Terms page, select

I accept license terms

On the Customer Experience Improvement

Program page. Select I don’t Join the
Customer Experience Improvement
Program
When the installation is complete, click Close
Sequencing walk through
The Microsoft Application Virtualization (App-V) Sequencer used to package applications to be
deployed to systems using the App-V Client.
• Windows Defender and other anti-virus applications should be turned off prior to sequencing

For the applications requiring reboot, if given the

option click “yes.” The Sequencer will reboot and
automatically continue once logged back
Package Editor

The package editor is comprised of several tabs that enable further configuration modification.
These tabs helps to modify the following settings:
• Changing shortcuts and file type associations.
• Modifying registry settings.
• Adding and deleting files in the package.

Override Local Directory:

Instructs the client to Ignore
the local file or folders and only
view the file or folder inside
the package.

Merge with Local Directory:

Instructs the client to view the
contents of both the virtual
and local files or folders
Package Editor

PowerShell command for sequencing:

New-AppvSequencerPackage –Name “Microsoft WordViewer” –Path “C:\Packages” –Installer
“C:\SourceFiles\WordViewer.msi” –PrimaryVirtualApplicationDirectory “C:\Program Files\Word Viewer”

To know more options:

Get-Help New-AppvSequencerPackage
Sequence files

App-V Packages created during the sequencing process are comprised of several files

File Description
.APPV The Virtual Application Package file containing all assets and state organized
into stream able feature blocks.
.MSI Executable deployment wrapper allowing the manual deployment of .APPV files
or deployment via existing third party deployment platforms.
_DeploymentConfig.XML Used for customizing the default publishing parameters for all applications in a
package.
_UserConfig.XML Used for customizing the publishing parameters directed to specific user groups
for all applications in a package.
.CAB Optional: Package Accelerator file used to automatically rebuild a previously
sequenced virtual application package.
.APPVT Optional: Sequencer Template file used to retain commonly re-used sequencer
settings.

Inside .APPV file

App-V Sequencer Tokens

App-V Sequencer tokens can be viewed in the Tools Options dialog box, under Parse Items
Each of these tokens are parenthesized with a [{ and }].
Known Folder Token Known Folder Path

AccountPictures C:\Users\<username>\AppData\Roaming\Microsoft\Windows\AccountPictu
res
Administrative Tools C:\Users\<username>\AppData\Roaming\Microsoft\Windows\Start
Menu\Programs\Administrative Tools
AppData C:\Users\<username>\AppData\Roaming
Application Shortcuts C:\Users\<username>\AppData\Local\Microsoft\Windows\Application
Shortcuts
Cache C:\Users\<username>\AppData\Local\Microsoft\Windows\Temporary
Internet Files
CD Burning C:\Users\<username>\AppData\Local\Microsoft\Windows\Burn\Burn
Common C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative
Administrative Tools Tools
Common AppData C:\ProgramData
Common Desktop C:\Users\Public\Desktop
Common Documents C:\Users\Public\Documents
Common Programs C:\ProgramData\Microsoft\Windows\Start Menu\Programs
Common Start Menu C:\ProgramData\Microsoft\Windows\Start Menu
Common Startup C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
Common Templates C:\ProgramData\Microsoft\Windows\Templates
Sequencing Limitations

Limitation Description
• App-V requires a logged in user to initiate the launch of an
Applications that start services at boot time application.

• App-V cannot virtualize drivers. It is possible to bypass this

issue and install the driver locally on the target computer.
Applications that require device drivers • Some user-mode device drivers can be virtualized.

• For example, a program that will initiate a command and

launch another program. Normally both programs would be
included in the same suite. However if this application
launches or initiates commands in several applications it may
not be feasible to include all of the applications in the same
suite.
Applications that are required by several
• This is especially true if one of the reasons for deploying App-V
applications for information or access is to avoid application conflicts. Always remember that the
virtual “bubble” can see the OS and what’s installed on it but
the OS cannot see the “bubble” and interact with it. On the
same note, remember that one “bubble” cannot see another
unless they are brought into the same virtual environment
using Connection Groups.
• Such as Internet Explorer®
Applications that are a part of the OS
• Because COM+ is dynamic and happens at runtime, there’s no
Applications that use COM+ way for the Sequencer to capture this information.

COM DLL surrogate virtualization • For example, DLLs that run in Dllhost.exe
 Sequencing for Connection Groups (Plug-ins and Middleware)

Connection Groups in App-V enables virtual applications to interact with other applications,
middleware or plug-ins that have been virtualized in separate virtual application packages by
sharing a common virtual environment.
Advantages: Combined Virtual Environment
• Reduce the size of the primary packages.
• Enables individual packages servicing.
• Secondary packages can be reused with other
primary applications.
• Provides better control of access permissions
on the secondary applications.
For creating a separate package for a plug-
in/Middleware to the Primary Application, select the
Add-on or Plug-in/Middleware option

Create a Connection Group on the App-V Management

Server to link the primary & secondary packages.
Application Package Upgrade
Throughout the lifecycle of application management, Applications will need to be updated.
Types of Upgrades:
Update Application in Existing Package : Applies an update to an application or program that is part of an
existing virtual application package. Ex : Installing the application updates.

Edit Package: Helps to modify the properties and configuration associated with an existing virtual application
package rather than adding or updating files.

Add New Application: Helps to add a new application or program to an existing virtual application package. Ex :
Installing the additional applications.
• Updating a Package that will Replace the Existing Package
The Sequencer will save the updated package with a _# at the end of the APPV file name.
Ex: WordViewer2007_2.APPV
• Updating a Package for Deployment with the Existing Package
Should Select the “Save As” option to generate New GUID & Name it as <AppNameV2>.APPV file.
Ex: WordViewer2007V2.APPV
The PowerShell command for upgrading:
Update-AppvSequencerPackage –AppvPackageFilePath
“C:\Packages\ExcelViewer\ExcelViewer.appv” –Name “ExcelViewer” –Path
“C:\Packages\ExcelViewer” –Installer “C:\SourceFiles\ExcelViewerSP2.msi”
Dynamic Configuration and Scripting
Dynamic Configuration allows for specifying a policy for a package at either the machine/user level.
In few instances it is necessary to make modifications to the application to provide proper
functionality within the App-V environment. Ex: Apps requires access to a specific mapped drive or
device drivers to be installed natively or Killing process while terminating application.
 Deployment Configuration Files are applied to the package, which can be deployed to AD
groups containing Machine or User accounts. PackageName_DeploymentConfig.xml file.
 UserConfig files are applied to the package to AD groups containing User accounts.
PackageName_UserConfig.xml file.

Script Execution Time Can be specified in Can be specified in User

Deployment Configuration Configuration
(Script runs as) (Script runs as)
AddPackage X (System Account)
PublishPackage X (System Account) X (Current User)
UnpublishPackage X (System Account) X (Current User)
RemovePackage X (System Account)
StartProcess X (Current User) X (Current User)
ExitProcess X (Current User) X (Current User)
StartVirtualEnvironment X (Current User) X (Current User)
TerminateVirtualEnvironment X (Current User) X (Current User)
Microsoft Application Virtualization

Console
http://localhost:<PortNo>/console.html
Publishing the Applications

Launch Internet Explorer and browse to http://localhost:888/console.html.

Adding a package to the APPV Management Server:

PACKAGES node  ADD or UPGADE PACKAGES Brows Select .APPV file Open Add

To access the console, logged-in user must be a member of the

AppV Administrators group in AD.
Publishing the Applications

Now it shows the PACKAGE IMPORT progress after importing, click Close
Publishing the Applications

Assigning Permissions to a User Group:

Right-click on the Name of the package  Edit active directory access  FIND & SELECT VALID
ACTIVE DIRECTORY GROUPS  Grant Access  Close

Again right-click on the

Name of the package and
then click PUBLISH

The Status field will turn from a black icon to a green icon,
and the status should now say published
Streaming the Application

To access the newly published application, Log-in to the App-V Client machine as a member of
the user group to which the application is assigned.
Application should now be available to clients at the designated shortcut locations.

Launch the application: Start All Programs  Application shortcut

Devices that can access APP_V + OS which support APP-V

APP-V 4.x

Desktop OS support Server OS support

Windows XP Windows Server 2008
Windows Vista Windows Server 2008 R2
Windows 7 Windows Server 2012
Windows 8

APP-V 5.x

Desktop OS support Server OS support

Windows 7 Windows Server 2008 R2
Windows 8 Windows Server 2012

Linux or Mac OS X
Android or iOS
Q&A

For App-V related information & Technical Discussion Forums on the web

App-V Team Blog - http://blogs.technet.com/b/appv/

RSS Feed - http://blogs.technet.com/App-V/rss.xml

http://www.appvirtguru.com
http://blogs.technet.com/virtualworld
http://social.technet.microsoft.com/Forums/en-US/category/appvirtualization
 Drop mail to DL for further queries:

BPS & UCC Practice [email protected]

Thank you