Microsoft Application Virtualization 5.0: Introduction Mohnish Chaturvedi & Ian Bartlett Premier Field Engineer WCL312

Application Virtualization & What’s New in 5.0 App-V 5.0 More Ways to Manage App-V 5.0 Managing App-V 5.0 Next Generation Dynamic Suite Composition Virtual Application Connection Managing Virtual Application Interactions Virtual Application Extension Next Generation VDI Deployment Shared Content Store

2006: acquired  Scale  Distributed deployments 2008: App-V 4.5  64-bit  Office 2010, Windows : App-V 4.6  Sequencer Workflow  Package Accelerators  Best Practices 2011: App-V 4.6 SP1  Manage Server Apps  Separate Apps from Config Now: Server App-V Now: App-V 5.0 Beta 2

Integrated Platform Virtual applications work like installed applications Virtual applications use Windows standards No dedicated drive letter required Powerful Management New web-based management interface Optimize for VDI with one management workflow Rich PowerShell scripting allows automation and customization Flexible Virtualization Multiple App-V applications can share the same virtual environment Designed to support highly integrated applications Preserve existing investments in App-V

App-V 5.0  No dedicated drive letter required  No 4GB limit  Virtual Application Extension  Share peer applications with Virtual Application Connection  Shared Content Store can be updated with normal App-V workflow  Rich PowerShell scripting for sequencer, client and server  Web-based management

Sequencer  Similar UI from App-V 4.6 SP1  New package file format Package Converter  Customers can carry forward existing investments  Easily convert 4.5+ packages to the new format

 Virtual subsystem overrides  Disable virtual subsystems  Scripts Modifies a Package’s Virtual Environment  Dynamic Deployment Configuration  Dynamic User Configuration  Can combine Dynamic Configuration Types  Modify existing package content  Add to an existing package No Package Update Is Needed

 Global scope: all users on the machine  Specify Dynamic Deployment Configuration file per package on the machine  Stored when the package is added Deployment Configuration  User scope: affects the user on the machine  Specify Dynamic User Configuration file per user, per package on the machine  Stored when the package is published User Configuration

DEMO Dynamic Configuration

 Browser-based  Easily manage the lifecycle of a virtual application  Shortcuts & Applications can be modified in the UI  Advanced configuration can be imported directly to the console  One package, many configurations  PowerShell is available to automate all the tasks you’ve just seen. PowerShell Dynamic User Configuration Modified the Virtual Environment App-V Management User Interface

Virtual Application Connection Two or more App-V packages can share the same virtual environment with Virtual Application Connection.

DEMO Virtual Application Connection

 App-V Packages can be deployed in multiple Virtual Application Connection Groups  Configuration is separate from the packages Next Generation DSC  Create and configure via Server User Interface or PowerShell  Know the dependencies Integrated with App- V Management Server  Applications + Plugins  Applications + Middleware  Applications + Applications Supported Configurations  Can use PowerShell to create and manage Manage in Standalone Mode

Extension Point is registered natively with Windows Global Visibility Native –to– Virtual Virtual –to– Virtual Supported Subsystems Shortcuts File Type Associations (FTA) AppPath URL Protocols Software Clients Set Program Access and Computer Defaults (SPAD) COM Local Servers

DEMO Virtual Application Extension

Native application could not see and use mailto functionality in the virtual application URL Protocols Disabled Native application could see and use mailto functionality in the virtual application URL Protocols Enabled

 Does the Virtual Application need to interact with another Virtual Application? Use Virtual Application ConnectionUse Virtual Application Extension  Is the interaction well defined?  Does the OS or a native application need to interact with the Virtual Application?

 Store applications centrally  Save disk space in VDI/RDS  Applications can be updated per the usual process  Applications are executed on the shared store

DEMO Shared Content Store

App-V Configuration Manager 2012 SP1

 Modify the Virtual Environment with Dynamic Deployment Configuration or Dynamic User Configuration  Combine packages at runtime with Virtual Application Connection  Expose virtual application to native using Virtual Application Extension  Configure with Group Policy  Manage with PowerShell  Standard Windows tools: PowerShell, Event Logs, ETW tracing  Co-exist with App-V 4.6 client  Web-based User Interface  Manage with PowerShell  HTTP support for publishing, streaming  SMB streaming App-V ServerApp-V ClientApp-V Packages

SIMILL101 - Deploying & Managing Virtual Applications (App-V) using System Center 2012 Configuration Manager WCLILL101 - Microsoft Application Virtualization (App-V) 5.0 Overview Q-n-A continued in the Speaker Lounge Find Me Later At “Microsoft Services Premier Support” in Expo Area