1. Application Virtualization Hands-On-Lab Nicola Ferrini info@nicolaferrini.it

2. Who Am I ? Nicola Ferrini Trainer Technical Writer Systems Engineer Server & Application Virtualization Technology Specialist Technet Speaker Microsoft System Center Influencer More on: o http://www.nicolaferrini.it/curriculum.shtml http://www.nicolaferrini.it/curriculum.shtml o http://www.windowserver.it/ChiSiamo/Staff/tabid/71/Default.aspx http://www.windowserver.it/ChiSiamo/Staff/tabid/71/Default.aspx

3. Introduction Name Company affiliation Title/function Job responsibility Application Virtualization experience Server management experience Your expectations for the Hands-on-lab

4. 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

5. Microsoft Desktop Optimization Pack FeatureDescription Microsoft Enterprise Desktop Virtualization Enable legacy applications and accelerate upgrades to a new operating system Microsoft Application Virtualization Dynamically stream software as a centrally managed service Microsoft Asset Inventory Service Translate software inventory into business intelligence Microsoft Diagnostics and Recovery Toolset Powerful tools to accelerate desktop repair Microsoft Advanced Group Policy Management Enhance group policy through change Management System Center Desktop Error Monitoring Proactively manage application and operating system failures

6. 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 Requirements:

7. Microsoft Application Virtualization Management System: Introduction and Architecture

8. What Is Application Virtualization? Read & Write Virtual Environment (Registry,.ini, DLL, Group Policy, etc.) Application Read & Write Read Only System Files (Registry,.ini, DLL, etc.) System Services (cut and paste, OLE, printers, etc.) Profile Data Operating System

9. Application Management Lifecycle Packaging Management Deployment Updates Support Termination Business Continuity Monitoring/ Asset Management Testing will effect multiple stages in the lifecycle

10. Application Deployment Deploy Deploying No client installs No client footprint No wasting resources Pre-configuration of applications

11. Application Packaging.sft and.sprj.osd and.ico Manifest.xml Each published application contains:.osd file – Open Software Description "link" files.ico file – Icon file Each package contains:.sft file – Microsoft Application Virtualization-enabled application.sprj file – Microsoft Application Virtualization project file Manifest.xml - Used in package distribution

12. Application Updates Update Updates Update once on server Seamless update to clients

13. Application Support Support Reduced application conflicts Reduced help desk calls Increased license compliance

14. Application Termination Terminate Termination Centrally deactivate the application

15. Reduces Common Deployment and Management Problems Potentially conflicting applications have their own environment Applications in a suite can share the environment Application Virtualization packages contain the complete environment for the application.sft and.sprj.OSD and.ICO.osd and.ico Manifest.xml.sft and.sprj.osd and.ico 3 rd party app

16. Delivering Pre-Configured Applications Sequencing engineer builds the package and configures the application to address user requirements

17. Running Multiple Versions of a Single Application on the Same Computer Virtual Environment 1 Virtual Environment 2 2003 Each application runs in its own Virtual Environment, which allows different applications to share the same hardware with two versions of the same application

18. 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

19. 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

20. 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%

21. Microsoft Application Virtualization Sequencer

22. 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

23. Publishing an Application

24. Accessing an Application Data Store Administrator Computer Management Web Service Active Directory /Content Application Virtualization Management Server Client

25. Accessing an Application on a Microsoft Application Virtualization Streaming Server Application Virtualization Client (Windows Desktop or Terminal Server) Microsoft Application Virtualization Streaming Server /Content Microsoft Application Virtualization Management Server Sequencer RTSP (port 554)/RTSPS (port 322) DC REFRESH RTSP/RTSPS SMB/HTTP

26. Planning and Installing the Microsoft Application Virtualization Client

27. Application Virtualization Clients Application Virtualization Desktop Clients Application Virtualization for Terminal Services Application Virtualization Management Server Terminal Services Desktop Clients

28. Application Virtualization Desktop Client Application Virtualization Management Server Application Virtualization Desktop Client Network

29. Application Virtualization for Remote Desktop Services Application Virtualization Management Server Terminal Services Client Network LAN, VPN, Internet LAN Remote Desktop Server Application Virtualization for Remote Desktop Services

30. Minimum Recommended Client Requirements 12 MB for installation + 2048 MB for cache 12 MB for installation + 4096 MB for cache Disk Space 128 MB 1 GB RAM (minimum 256 megabytes (MB), actual figure dependent on number of users and applications) Memory Microsoft Windows XP Microsoft Windows Vista Microsoft Windows 7 Microsoft Windows 2003 Terminal Services Microsoft Windows 2008 Terminal Services Microsoft Windows 2008 R2 Remote Desktop Services Operating Systems ClientProcessor For Terminal Servers Must meet operating system minimum requirement For Desktop Must meet operating system minimum requirement

31. Key Differences Between Application Virtualization Clients Uses the %APPDATA% location by default User Data directory Recommend the entire content of the.sft file be preloaded into the file system cache for Terminal Services Application streaming InstallationDescription Setup Two differences: default installation location and default cache size Cache settings A larger cache is generally required for Terminal Services Client

32. Application Virtualization Client – Applications

33. Application Virtualization Client – File Type Associations

34. Application Virtualization Client – Publishing Servers

35. Command Line Client Configuration – SFTMIME.EXE

36. Administering the Microsoft Application Virtualization Management Server

37. What Is the Applications Container? Add or import sequenced applications Configure virtualization access settings for applications The Applications Container is used to: Organize applications into application groups Remove applications and application groups

38. Files Used to Add or Import an Application.SPRJ.XML File typeDescription.sprj Describes which applications are part of a specific application suite Contains parse items and exclusions Is XML-based.osd Specifies application launch information to the virtualization client Provides application virtualization settings Is XML-based.sft Up to 4 gigabyte (GB) application storage file Contains application assets that make up the application Separated into multiple feature blocks Is XML-based.ico Used to represent application shortcut icons Manifest.xml Used in specific streaming infrastructure scenarios to inform clients how to access sequenced applications

39. Considerations for Importing Applications 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.osd Path Where will the application shortcuts go? What file type associations will the application use? Which security groups need access to the application? Considerations to keep in mind: For example:

40. Importing Applications Import applications by: Using Action menu option, Import Applications Wizard Specifying the.sprj or.osd file provided by the Sequencer

41. Demonstration: Importing an Application In this demonstration, you will see how to import an application

42. LAB: Publishing Applications into the Application Virtualization Environment Exercise 1: Configuring System Options Exercise 2: Publishing an Application Exercise 3: Verifying Application Virtualization Functionality

43. 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

44. Modifying Imported Applications Allows administrators to change options defined during the initial application import

45. Overview of the Active Upgrade Process 1.Select package to be updated, and then add new version 2.Type in updated.sft file path 3.Type in the relative path 4.Confirm package 5.Ask client to reload application Sequencing administrator provides updates to the application package

46. Retiring a Package Version To retire a package version, delete the version of the package no longer in use

47. LAB: Configuring Active Upgrades for Published Applications Exercise: Configuring Package Versions

48. Planning and Deploying the Application Virtualization Sequencer

49. What Does the Application Virtualization Sequencer Do? 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) Application Virtualization Sequencer:

50. 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 Dynamic Suite Composition is the only exception that allows communication between virtual environments Virtual Environment Virtual Environment Virtual Application Client Operating System Clipboard Local Application

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

52. 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

53. 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

54. 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

55. Best Practices for Sequencing Perform local install first Document install process Install path using 8.3 naming convention Set application components Disable the program’s automatic update feature while the application is being sequenced Complete the application configuration while the Sequencer is still monitoring, post-installation Always reply “Yes” when asked to reboot Do not apply compression and keep block size to 32KB

56. Overview of Sequencing Wizard Package Information Monitor Installation Add Files 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 Sequence Package Launch Applications Configure Applications

57. Sequencing Wizard - Package Information

58. Sequencing Wizard – Monitor Installation Click Begin Monitoring and install the application to the Q:\Package Root directory.

59. Sequencing Wizard – Add Files to Virtual File System Add additional files here to the VFS that may not have been captured during monitoring

60. Sequencing Wizard – Configure Applications 1.Review programs that were detected by the Installation Wizard 2.Modify shortcuts / FTA’s 3.Modify application name and icon

61. Sequencing Wizard – Launch Applications Launch any applications you wish to place into FB1 and configure those applications for the default configurations

62. Sequencing Wizard – Sequence Package The virtual environment has been created, and the application has been placed into the virtual environment

63. Manually Modifying the Sequencer Package You can fine-tune the wizard settings once the package is created 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 You can add or remove files from the Virtual File System

64. Save the project to a folder on the Sequencer Post-Sequencing Steps Application Virtualization Server 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

65. Example: Overview of the Dynamic Suite Composition Legacy 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

66. LAB: Sequencing Applications for Virtualization Exercise 1: Sequencing an Application

67. Online Resources Office 2010 – System Requirements: o http://technet.microsoft.com/it-it/library/ee624351(en-us,office.14).aspx http://technet.microsoft.com/it-it/library/ee624351(en-us,office.14).aspx Application Virtualization: o http://blogs.technet.com/b/appv/ http://blogs.technet.com/b/appv/ o http://technet.microsoft.com/en-us/library/cc843848.aspx http://technet.microsoft.com/en-us/library/cc843848.aspx o http://www.microsoft.com/italy/server/windowsserver2008/panoramica/introduzione-a- microsoft-application-virtualization.mspx http://www.microsoft.com/italy/server/windowsserver2008/panoramica/introduzione-a- microsoft-application-virtualization.mspx Prescriptive guidance for sequencing Office 2010 in Microsoft App-V o http://support.microsoft.com/kb/983462/en-us http://support.microsoft.com/kb/983462/en-us Office Activation Technologies: o http://technet.microsoft.com/volumeactivation http://technet.microsoft.com/volumeactivation Office Customization Tool: o http://technet.microsoft.com/en-us/library/cc179097.aspx http://technet.microsoft.com/en-us/library/cc179097.aspx Virtualizzare Office 2010 con App-V 4.6 o http://www.nicolaferrini.it/ita/articoli/Virtualizzare Office 2010 con App-V 4.6.pdf http://www.nicolaferrini.it/ita/articoli/Virtualizzare Office 2010 con App-V 4.6.pdf

68. Virtual Labs Application Virtualization o TechNet Virtual Lab: Learning App-V Basics TechNet Virtual Lab: Learning App-V Basics o TechNet Virtual Lab: Learning App-V Intermediate Skills TechNet Virtual Lab: Learning App-V Intermediate Skills o TechNet Virtual Lab: Learning to Configure App-V for Standalone Client Mode TechNet Virtual Lab: Learning to Configure App-V for Standalone Client Mode o TechNet Virtual Lab Express: Windows 7: Microsoft Application Virtualization (APP-V) TechNet Virtual Lab Express: Windows 7: Microsoft Application Virtualization (APP-V) Remote Desktop Services o TechNet Virtual Lab Express: Windows Server 2008 R2: Remote Desktop Services TechNet Virtual Lab Express: Windows Server 2008 R2: Remote Desktop Services

69. Thank You!