1 / 69

Application Virtualization Hands-On-Lab

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

toril
Download Presentation

Application Virtualization Hands-On-Lab

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Who Am I ? Nicola Ferrini • Trainer • TechnicalWriter • SystemsEngineer • Server & Application Virtualization Technology Specialist • Technet Speaker • Microsoft System Center Influencer • More on: • http://www.nicolaferrini.it/curriculum.shtml • 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

  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 Requirements: • 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

  7. Microsoft Application Virtualization Management System: Introduction and Architecture

  8. 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.) Application Profile Data Read & Write

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

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

  11. 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 Manifest.xml

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

  13. Application Support 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 3rd party app .osd and .ico .osd and .ico .OSD and .ICO .sft and .sprj Manifest.xml Manifest.xml 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 ü

  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 • 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 2003

  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 /Content Administrator Computer Active Directory Management Web Service Data Store Client Application VirtualizationManagement Server

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

  26. Planning and Installing the Microsoft Application Virtualization Client

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

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

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

  30. Minimum Recommended Client Requirements Client Processor Memory 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

  31. Key Differences Between Application Virtualization Clients Installation Description Setup • 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

  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? 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

  38. Files Used to Add or Import an Application .SPRJ .XML

  39. 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:

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

  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? 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)

  50. Communication Between Virtual Environments Virtual Environment Virtual Environment • 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 Operating System Local Application Clipboard

More Related