application virtualization hands on lab n.
Skip this Video
Loading SlideShow in 5 Seconds..
Application Virtualization Hands-On-Lab PowerPoint Presentation
Download Presentation
Application Virtualization Hands-On-Lab

Loading in 2 Seconds...

play fullscreen
1 / 69

Application Virtualization Hands-On-Lab - PowerPoint PPT Presentation

  • Uploaded on

Application Virtualization Hands-On-Lab. Nicola Ferrini Who Am I ? Nicola Ferrini. Trainer Technical Writer Systems Engineer Server & Application Virtualization Technology Specialist Technet Speaker Microsoft System Center Influencer More on:

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Application Virtualization Hands-On-Lab' - toril

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
application virtualization hands on lab

Application VirtualizationHands-On-Lab

Nicola Ferrini

who am i nicola ferrini
Who Am I ? Nicola Ferrini
  • Trainer
  • TechnicalWriter
  • SystemsEngineer
  • Server & Application Virtualization Technology Specialist
  • Technet Speaker
  • Microsoft System Center Influencer
  • More on:
  • Name
  • Company affiliation
  • Title/function
  • Job responsibility
  • Application Virtualization experience
  • Server management experience
  • Your expectations for the Hands-on-lab
hands on lab outline
Hands-on-lab Outline
  • Optimizing Windows Desktop Management in the Enterprise
  • Microsoft Application Virtualization Management System: Introduction and Architecture
  • Planning and Installing the Microsoft Application Virtualization Client
  • Administering the Application Virtualization Management Server
  • Advanced Application Virtualization Administration Tasks
  • Planning and Deploying the Application Virtualization Sequencer
  • Advanced Sequencing
microsoft application virtualization
Microsoft Application Virtualization

Dynamically delivering the virtual application solution

  • Applications to users at log on
  • Centralized permissions
  • Sandboxed applications
  • Accelerates desktop deployment
  • Minimizes application coexistence testing
  • Runs real-time usage reports
  • Enables device roaming


  • Server components require Windows Server 2003 or
  • later
  • Requires SQL 2000 or later
  • Client requires Windows XP or later
  • Certain components require .NET Framework 2.0
what is application virtualization
What Is Application Virtualization?

Operating System

Read Only

System Files

(Registry, .ini,

DLL, etc.)

Read & Write

System Services

(cut and

paste, OLE,

printers, etc.)

Read & Write

Virtual Environment

(Registry, .ini, DLL,

Group Policy, etc.)


Profile Data

Read & Write

application management lifecycle
Application Management Lifecycle










Testing will effect multiple stages in the lifecycle



application deployment
Application Deployment
  • Deploying
  • No client installs
  • No client footprint
  • No wasting resources
  • Pre-configuration of applications


application packaging
Application Packaging
  • Each published application contains:
  • .osd file – Open Software Description "link" files
  • .ico file – Icon file

.osd and .ico

.osd and .ico

  • Each package contains:
  • .sft file – Microsoft Application Virtualization-enabled application
  • .sprj file – Microsoft Application Virtualization project file
  • Manifest.xml - Used in package distribution

.sft and .sprj

.osd and .ico


application updates
Application Updates
  • Updates
  • Update once on server
  • Seamless update to clients


application support
Application Support


  • Support
  • Reduced application conflicts
  • Reduced help desk calls
  • Increased license compliance
application termination
Application Termination


  • Termination
  • Centrally deactivate the application
reduces common deployment and management problems
Reduces Common Deployment and Management Problems

3rd party app

.osd and .ico

.osd and .ico

.OSD and .ICO

.sft and .sprj



Application Virtualization packages contain the complete environment

for the application

Potentially conflicting applications have

their own environment



.sft and .sprj

.OSD and .ICO

Applications in a suite can

share the environment


delivering pre configured applications
Delivering Pre-Configured Applications
  • Sequencing engineer builds the package and configures the application to address user requirements
running multiple versions of a single application on the same computer
Running Multiple Versions of a Single Application on the Same Computer

Virtual Environment 1

  • Each application runs in its own Virtual Environment, which allows different applications to share the same hardware with two versions of the same application

Virtual Environment 2


providing centrally managed application deployment and maintenance
Providing Centrally Managed Application Deployment and Maintenance
  • The management console is used to connect to the Web service, which is the central component for all Microsoft Application Virtualization
on demand delivery
On-Demand Delivery

Streams application when requested by user

Application will be streamed either by launching the application or by file invocation

Application Virtualization (App-V) Client reads the .osd file to determine the correct App-V Server to stream the application

App-V Server checks the data store to ensure the user is still entitled to the application and there are available licenses

App-V Server will use the RTSP protocol to stream the virtual application to the client

primary and secondary feature blocks
Primary and Secondary Feature Blocks
  • Package .sft don’t have to be delivered at one time
  • Sequencer can mark certain blocks of the .sft as critical launch phase or primary feature block (FB1)
    • During initial stream after FB1 is downloaded, application can launch
  • All other blocks are stored in secondary feature block (FB2)
    • When user accesses feature not in FB1, individual blocks of data are downloaded from FB2
    • Operation known as Out-of-Sequence Operation
  • User customized settings are stored in UsrVol_sftfs_v1.pkg and stored in user’s %AppData%
app v management server and client requirements and interactions
App-V Management Server and Client Requirements and Interactions
  • Client for desktops and terminal services
  • Small footprint
  • Microsoft Windows XP, Windows 2003 Server, or newer
  • 12 megabyte (MB) for installation files, at least 2048 MB for cache file
accessing an application
Accessing an Application


Administrator Computer

Active Directory


Web Service

Data Store


Application VirtualizationManagement Server

accessing an application on a microsoft application virtualization streaming server
Accessing an Application on a Microsoft Application Virtualization Streaming Server



Application Virtualization Client

(Windows Desktop

or Terminal Server)

RTSP (port 554)/RTSPS (port 322)DC REFRESH

Microsoft ApplicationVirtualization Management Server



Microsoft ApplicationVirtualization Streaming Server

application virtualization clients
Application Virtualization Clients

Application Virtualization

Desktop Clients

Application Virtualization





for Terminal


Terminal Services

Desktop Clients

application virtualization desktop client
Application Virtualization Desktop Client

Application Virtualization






Desktop Client

application virtualization for remote desktop services
Application Virtualization for Remote Desktop Services

Application Virtualization for

Remote Desktop


Application Virtualization




Remote Desktop








minimum recommended client requirements
Minimum Recommended Client Requirements




Disk Space

Operating Systems

For Terminal Servers

Must meet operating system minimum requirement

1 GB RAM (minimum 256 megabytes (MB), actual figure dependent on number of users and applications)

12 MB for installation + 4096 MB for cache

  • Microsoft Windows 2003 Terminal Services
  • Microsoft
  • Windows 2008 Terminal Services
  • Microsoft
  • Windows 2008 R2 Remote Desktop Services

For Desktop

Must meet operating system minimum requirement

128 MB

12 MB for installation

+ 2048 MB for cache

  • Microsoft Windows XP
  • Microsoft Windows Vista
  • Microsoft Windows 7
key differences between application virtualization clients
Key Differences Between Application Virtualization Clients




  • Two differences: default installation location and default cache size

Cache settings

  • A larger cache is generally required for Terminal Services Client

Application streaming

  • Recommend the entire content of the .sft file be preloaded into the file system cache for Terminal Services

User Data directory

  • Uses the %APPDATA% location by default
what is the applications container
What Is the Applications Container?

The Applications Container is used to:

  • Add or import sequenced applications
  • Configure virtualization access settings for applications
  • Organize applications into application groups
  • Remove applications and application groups
considerations for importing applications
Considerations for Importing Applications

Considerations to keep in mind:

  • Where will the application shortcuts go?
  • What file type associationswill the application use?
  • Which security groups need access to the application?

.osd Path

  • Make sure the path specified in the .osd file matches the content path to the server
  • Server name may be specified as a system variable

For example:

importing applications
Importing Applications

Import applications by:

  • Using Action menu option, Import Applications Wizard
  • Specifying the .sprj or .osd file provided by the Sequencer
demonstration importing an application
Demonstration: Importing an Application

In this demonstration, you will see how to import an application

lab publishing applications into the application virtualization environment
LAB:Publishing Applications into the Application Virtualization Environment
  • Exercise 1: Configuring System Options
  • Exercise 2: Publishing an Application
  • Exercise 3: Verifying Application Virtualization Functionality
modifying published applications and configuring version upgrades
Modifying Published Applications and Configuring Version Upgrades

Modifying Imported Applications

Configuring File Type Associations

What Is a Package?

Overview of the Active Upgrade Process

Retiring a Package Version

modifying imported applications
Modifying Imported Applications
  • Allows administrators to change options defined during the initial application import
overview of the active upgrade process
Overview of the Active Upgrade Process

Sequencing administrator provides updates to the application package

  • Select package to be updated, and then add new version
  • Type in updated .sft file path
  • Type in the relative path
  • Confirm package
  • Ask client to reload application
retiring a package version
Retiring a Package Version
  • To retire a package version, delete the version of the package no longer in use
what does the application virtualization sequencer do
What Does the Application Virtualization Sequencer Do?

Application Virtualization Sequencer:

  • Packages applications that are deployed to desktops and Terminal Servers and run by the Virtual Application Client
  • Prepares applications that are streamed from a Virtual Application Server
  • Packages the application into an MSI package for distribution using a software deployment platform such as System Management Software (SMS), or System Center Configuration Manager (SCCM)
communication between virtual environments
Communication Between Virtual Environments





  • Virtual environments are isolated from each other
  • Basic copy and paste is available between virtual environments, and is facilitated by the Virtual Application Client

Virtual Application Client

  • Dynamic Suite Composition is the only exception that allows communication between virtual environments






overview of the sequencing process
Overview of the Sequencing Process
  • Standard installation process is
  • monitored by Sequencer to discover:
    • Files
    • Registry entries
    • INI files
    • Environment variables
  • Changes are packaged into a virtual environment
  • Application is executed to determine initial startup requirements
  • Application is sequenced, and .sft, .sprj, .ico, .osd, and Manifest.xml files are generated
  • Virtualized application is moved to the Application Virtualization Server, and then tested




components of a sequenced application
Components of a Sequenced Application
  • .sft file contains the sequenced Windows® application
  • .sprj XML-based text file contains parse items and exclusions for application suites
  • .ico files used for application shortcuts to .osd files
  • .osd provides necessary information to launch the application
  • Manifest.xml stores information about the application, and is used by Application Virtualization Streaming Servers
considerations related to the sequencer environment
Considerations Related to the Sequencer Environment
  • Use a clean operating system install
  • Sequence on the lowest operating system version used in the target environment
  • Do not install monitoring agents or antivirus-type software, or any software that runs background tasks
  • Reset environment after each package is created
typical configuration for the sequencer
Typical Configuration for the Sequencer
  • C:\ drive (NTFS)
  • Operating System
  • Service Packs
  • Q:\ drive (NTFS)
  • Application Installation Path
  • Package Root Directory (8.3 format)
  • Install Files for Application
best practices for sequencing
Best Practices for Sequencing
  • Disable the program’s automatic update feature while the application is being sequenced
  • Perform local install first
  • Document install process
  • Complete the application configuration while the Sequencer is still monitoring, post-installation
  • Do not apply compression and keep block size to 32KB
  • Install path using 8.3 naming convention
  • Always reply “Yes” when asked to reboot
  • Set application components
overview of sequencing wizard
Overview of Sequencing Wizard
  • The Virtual Application Sequencer provides a wizard that can be used to sequence most applications
  • Creating a new package launches the Sequencing Wizard, which guides you through the proper wizard sequence for package creation

Add Files

Package Information

Monitor Installation

Configure Applications

Sequence Package

Launch Applications

sequencing wizard monitor installation
Sequencing Wizard – Monitor Installation

Click Begin Monitoring and install the application to the Q:\Package Root directory.

sequencing wizard add files to virtual file system
Sequencing Wizard – Add Files to Virtual File System
  • Add additional files here to the VFS that may not have been captured during monitoring
sequencing wizard configure applications
Sequencing Wizard – Configure Applications
  • Review programs that were detected by the Installation Wizard
  • Modify shortcuts / FTA’s
  • Modify application name and icon
sequencing wizard launch applications
Sequencing Wizard – Launch Applications

Launch any applications you wish to place into FB1 and configure those applications for the default configurations

sequencing wizard sequence package
Sequencing Wizard – Sequence Package

The virtual environment has been created, and the application has been placed into the virtual environment

manually modifying the sequencer package
Manually Modifying the Sequencer Package
  • You can fine-tune the wizard settings once the package is created
  • You can add or remove files from the Virtual File System
  • You can edit the Virtual Registry to remove registry data that may not pertain to the application
  • You can edit the .osd file before it is packaged
post sequencing steps
Post-Sequencing Steps

Save the project to a folder on the Sequencer

  • Use the same folder name that was specified in the “Package Name” text box in the Package Information page
  • Transfer files to the Virtual Application Server

Application Virtualization


overview of the dynamic suite composition
Overview of the Dynamic Suite Composition

With DSC

  • Provides the ability to link applications in separately sequenced packages



  • In previous versions of Application Virtualization (formerly SoftGrid), if an application required the Java runtime, every application had to have the Java Runtime Environment (JRE) sequenced into it
  • With Dynamic Suite Composition, the JRE is sequenced separately, and every application that requires it can reference the JRE package
lab sequencing applications for virtualization
LAB: Sequencing Applications for Virtualization
  • Exercise 1: Sequencing an Application
online resources
Online Resources
  • Office 2010 – System Requirements:
  • Application Virtualization:
  • Prescriptive guidance for sequencing Office 2010 in Microsoft App-V
  • Office Activation Technologies:
  • Office Customization Tool:
  • VirtualizzareOffice 2010 con App-V 4.6
    • Office 2010 con App-V 4.6.pdf
virtual labs
Virtual Labs
  • Application Virtualization
    • TechNet Virtual Lab: Learning App-V Basics
    • TechNet Virtual Lab: Learning App-V Intermediate Skills
    • TechNet Virtual Lab: Learning to ConfigureApp-V for Standalone Client Mode
    • TechNet Virtual Lab Express: Windows 7: Microsoft Application Virtualization (APP-V)
  • Remote Desktop Services
    • TechNet Virtual Lab Express: Windows Server 2008 R2: Remote Desktop Services