You're excited about the new features in App-V 4.5, but where do you get started? This talk is meant to guide IT administrators through the App-V deployment decision process. Specifically, we discuss the various deployment types, pros and cons for each type of deployment, and performance and scalability issues. By the end of the presentation, IT administrators will be able to identify the deployment that is best suited for their preferences and infrastructure.

2. MDOP: Planning the Deployment of Microsoft Application Virtualization 4.5 Bill Morein Lead Program Manager Microsoft Corporation Session Code: CLI319

3. Deployment Options Standalone ESD Infrastructure App-V Infrastructure

4. Deployment Options Standalone ESD Infrastructure App-V Infrastructure

5. Basic Infrastructure App-V Management Server

6. App-V Infrastructure – High Level App-V Management Console Active Directory App-V Streaming Server Management Web Service App-V Database Http Streaming VECD Streaming + manifest Terminal server Http Streaming Desktop VECD Streaming Terminal server App-V Clients Desktop VECD Terminal server App-V Clients Desktop

7. BOSTON Branch Office Scenario – Before 4.5 SEATTLE SFT SFT SFT SFT OSD & ICONS OSD & ICONS OSD & ICONS Applist.xml WAN APP-V MANAGEMENT SERVER DATA CENTER USER

8. Branch Office Scenario – App-V 4.5 BOSTON SEATTLE SFT SFT SFT SFT OSD & ICONS OSD & ICONS OSD & ICONS Applist.xml CONTENT CONTENT CONTENT STREAMING SERVER WAN APP-V MANAGEMENT SERVER DATA CENTER USER

9. Introduction to ASR, OSR, ISR ASR = Application Source Root OSR = OSD Source Root ISR = Icon Source Root These are overrides that can be modified within the registry Settings are global Enable greater ease of management Can be set dynamically based on the site

10. An Example Path in the OSD: RTSP://SeattleServer:554/package/package.sft ASR: HTTP://BostonServer:80 Final URL: HTTP://BostonServer:80/package/package.sft

11. ASR, OSR, ISR demo

12. ASR/OSR/ISR Reference Package Path: RTSP://ManagementServer/package/package.sft ASR:HTTP://MyLocalServer/ Actual: HTTP://MyLocalServer/package/package.sft OSD Path:RTSP://ManagementServer/content/package/package.osd OSR: MyLocalServer/content Actual: MyLocalServer/content/package/package.osd Icon Path: ManagementServer/content/package/package_Icons/package.ico ISR: HTTP://MyLocalServer/ Actual: HTTP://MyLocalServer/package/package_Icons/package.ico

13. Synchronizing Servers App-V Management Console Active Directory App-V Streaming Server Management Web Service App-V Database App-V Streaming Server VECD Streaming + manifest Terminal server Http Streaming Desktop VECD Streaming Terminal server App-V Clients Desktop VECD Terminal server App-V Clients Desktop

14. Server Synchronization Import Package into Management Server Set appropriate permissions Do not enable the package at this point Distribute the package to streaming servers This includes OSDs, Icons, SFTs Remember to maintain the same directory structure Enable the packages on the management server

15. Streaming Options IIS IIS provides better scalability and more launches per minute than the RTSP streaming server IIS is already setup and managed in many environments RTSP Active upgrade is ready to use out of the box – no client configuration required FILE Provides the ability to get applications without a server infrastructure All options provide differential streaming

16. Package Upgrade demo

17. App-V Infrastructure Summary Three essential pieces to set up a full infrastructure: Client configuration Server synchronization Streaming server options

18. Deployment Options Standalone ESD Infrastructure App-V Infrastructure

19. Standalone MSI Scenario Standardized method for deploying applications MSI does the publishing for you More details in the demo Sequencer generates MSI directly Deploy via device, SCCM or 3rd party No App-V servers required

20. Standalone MSI demo

21. Standalone MSI Scenario Recap Great if you already use packages with MSI Requires the following settings: Networknline = 0 ConfigurationequireAuthorizationIfCached = 0 NetworkimitDisconnectedOperation = 0 The SFT needs to be in the same directory

22. Standalone SFTMIME Scenario SFTMIME is the command line tool installed with the App-V client App-V 4.5 has a new manifest file that allows you to do publishing easily with SFTMIME Can achieve the same functionality as MSI publishing and add your own customizations

23. Standalone without MSI demo

24. Standalone SFTMIME Reference Add the Package: sftmime add package:<name> /manifest <manifest path> Load the Package: sftmime load package:<name> /sftpath <SFT path>

25. Standalone SFTMIME Reference There are a lot of options: sftmime /help verb:<option> Some common options: Configure Delete Unload

26. Standalone Summary There are many ways to get apps to clients MSI is the simplest SFTMIME is the most configurable Always good to know for testing and troubleshooting

27. Deployment Options Standalone ESD Infrastructure App-V Infrastructure

28. Application Virtualization in Configuration Manager R2 Integrate Application Virtualization into System Center Configuration Manager 2007 R2 New in ConfigMgr 2007 R2: Enables customers using ConfigMgr to manage and deploy virtual applications Client roaming is supported so the client is always going to the “closest” server Maintain the dynamic nature of Application virtualization Version checking, user-based targeting, streaming

29. Config Manager R2 Core Scenarios

30. Streaming Delivery – End-to-End Admin creates vapp package SCCM Site Server SCCM Admin SCCM Client refers to program information on the DP to register the package Package is replicated to DP‘s Client The program information is used by SCCM to publish virtual application Streaming-Enabled DP User launches the application and streams directly from DP App Virt Cache Only blocks required to run the application are downloaded

31. Download and Execute– End-to-End Admin creates vapp package SCCM Site Server SCCM Admin Package is replicated to DP‘s Client SCCM publishes virtual application DP Package (SFT) is pushed to client via BITS When launched, package is loaded into cache App Virt Cache

32. Clients and Launching Virtual ApplicationsRoaming Supported User launches and application Streaming-Enabled DP Management Point Application Shortcut Adv Client hands off to App Virt client for vapp streaming Advanced Client talks to MP and performs a location request launcher talks to the Advanced Client Shortcut calls SCCM launcher Launcher (SCCM) App Virt 4.5 Client SCCM Advanced Client Once the DP location is established, the Advanced Client sets the source URL for the package via SFTMIME

33. Where to Find More Information Documentation for App-V 4.5 on Technet http://technet.microsoft.com/en-us/library/cc843848.aspx White Papers http://technet.microsoft.com/en-us/appvirtualization/cc843994.aspx Documentation feedback Public email alias (appvdocs@microsoft.com ) App-V Forums on Technet http://social.technet.microsoft.com/Forums/en-US/category/appvirtualization

34. question & answer

35. Required Slide Speakers, TechEd 2009 is not producing a DVD. Please announce that attendees can access session recordings at TechEd Online. www.microsoft.com/teched Sessions On-Demand & Community www.microsoft.com/learning Microsoft Certification & Training Resources http://microsoft.com/technet Resources for IT Professionals http://microsoft.com/msdn Resources for Developers Resources

36. Related Content Today from 12:20 – 1300 CLI02-DEMO: Windows Optimized Desktop Solutions Demo Tomorrow from 9:00 – 10:15 CLI03-IS: Microsoft Application Virtualization Discussion Tomorrow from 12:20 – 13:30 CLI04-DEMO: Application Virtualization: The Future of Application Management and Deployment Friday from 10:45 – 1200 CLI403: Microsoft Desktop Optimization Pack: Microsoft Application Virtualization 4.5 Sequencing Deep Dive Required Slide Speakers, please list the Breakout Sessions, TLC Interactive Theaters and Labs that are related to your session.

37. Complete an evaluation on CommNet and enter to win an Xbox 360 Elite!

38. Required Slide © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.