Application Virtualization

1. Lionel Cau Snr Consultant & MS Practice Mger Sogeti Switzerland Application Virtualization

2. Microsoft Infrastructure Transformation (MIT) Competence Center Performs a completeassessment evaluatesyourmaturitylevel, deliversa ready to use and relevant IT director plan A completeproject management kit helpingyou in a short time frame to evaluate, prepare, organize and build a Vista migration Microsoft Infrastructure Optimisation(MIO) eXcellenceinMigrationProjet (XMP) 3 branches of a star, 3 stars of a branch ! Strategic planning Migration projects Virtualization and costs Combines virtualizationbenefitswith a qualityfocused and a costreducingapproach SoftGridRightShore MIT: Alwayskeeping in mindtechnology and methodology

3. Agenda • MDOP overview • What’sincluded, how to purchase ? • SoftGridtechnology basics • MSAV 4.5 • DynamicVirtualization • Extendingscalability • Globalization • Security • Application Virtualization and SCCM integration • Virtualization and costs • Sequencing best practices • Tips and tricks

4. MDOP overview

5. ALERT:Application X has failed Virtualize and Stream Apps ManageGroup Policies RepairDesktops InventoryAssets Monitor Crashes App App App App App App App App App App App System Center DEM OperationsManager 2007 System Center Virtual App Server Translating software inventory into business intelligence Enhancing group policy through change management Dynamically streaming software as a centrally managed service Proactively managing application and operating system failures Powerful tools to accelerate desktop repair

6. Microsoft Application VirtualizationAbove the kernel virtualization for applications • Applications are virtualized per instance: • Files (incl System Files) • Registry • Fonts • .ini • COM/DCOM objects • Services • Semaphores, Mutexes • Name Spaces • Applications do not get installed or alter the operating system • Yet Tasks process locally on the host computer • Dramatically reduces application conflicts and regression testing

7. Microsoft Application Virtualization Platform3 Key Components

8. Sequencing and deploying a virtual Office 2007 demo Lionel Cau Snr Consultant & MS Practice Mger Sogeti Switzerland

9. Microsoft Application VirtualizationMultiple benefits • Application isolation and management • Conflicts and dependenciesresolved • Active Update • Diverse Client Base • Supports Windows XP Pro, Windows Vista, Windows Server 2003 and 2008 Terminal Services, and Vista Enterprise Centralized Desktop • Permission Based • User clicks on desktop shortcuts - authentication, authorization and licensing checked every time users launch a virtual application • Centrally Served and On Demand Delivery • The first time the Server delivers “just enough” code (20-40%) to client or TS machine. As more code is needed, it is dynamically delivered. • Locally Executed • App executes on desktop, laptop and/or Terminal Server, not on the Server • Cached for Performance • App code is cached for repeat use • Options to cache at login or on first launch • Disconnected Use Support • Entire set of applications are cached for limited time before expiring

10. Application coexistence examples • Multiple versions of the same application • Office 2007 and Office 2003 • Branched versions of the same application • Office 2003 and Office 2003 SP1 • Multiple JRE Versions • Multiple MDAC versions • Multiple Oracle Drivers • Different configurations of the same application • Same database client, two different target database configurations • Virtual configurations of local applications • Internet Explorer add-ins (JRE, ActiveX, etc.)

11. SoftGrid 4.5

12. Dynamic Virtualization Introducing Dynamic Suite Composition (DSC) Combined Virtual Environment • Applications known to not conflict may be administratively set up to share the same virtual environment. • Mandatory and optional dependency configuration options as controlled via OSD • Virtual applications may now share common dependencies • Benefits: • Achieve one to many • Greatly improve the ability deploy and manage an application with multiple plug ins and/or add ins • Reduce cost of patching dependent application (i.e. plug ins, middleware, etc) • Improve management of plug in distribution to different user groups Administrative option to allow for combinations of virtual environments called Dynamic Suite Composition

13. <SOFTPKG GUID="246FD4DA-D89B-4191-A65E-EA119D800578" NAME="Microsoft Office Word 2007" VERSION="12.0.4518.1014"> 2: <IMPLEMENTATION> <CODEBASE HREF="RTSP://stream.mdopdemo.net:554/MSOF2K7EE.001/MSOF2K7EE.001.sft" GUID="741F7E81-7E31-499B-A719-0796A6797857" PARAMETERS="" FILENAME="MSOF2K7EE.001\Microsoft Office\Office12\WINWORD.EXE" SYSGUARDFILE="MSOF2K7EE.001\osguard.cp" SIZE="1663291041"/> <OS VALUE="WinVista"/> <OS VALUE="WinXP"/> <WORKINGDIR/> <VIRTUALENV TERMINATECHILDREN="FALSE"> <ENVLIST/> <DEPENDENCIES> <CODEBASE HREF="RTSP://stream.mdopdemo.net:554/SNAGIT.001/SNAGIT.001.sft" GUID="A7ACA34F-25C2-4BB2-9623-CA344C801E89" PARAMETERS="" FILENAME="SNAGIT.001\TechSmith\SnagIt 8\SnagIt32.exe" SYSGUARDFILE="SNAGIT.001\osguard.cp" SIZE="52757501"/> </DEPENDENCIES> </VIRTUALENV> Dynamic Virtualization Introducing Dynamic Suite Composition (DSC)

14. Extending scalability Current scalability challenges • Currentdistributeddeploymentis not mature • No branch office support • Each SoftGrid site is managed as a separate entity • Internet facing scenarios are not supported  Lightweight Server • Currently, there are few interoperability with Electronic Software Delivery systems • Dual management infrastructure • No easy way of making sure the entire application is in cache before user goes offline  MSI utility and SCCM 2007 integration

15. Supported 4.2 Deployment Scenario • Distributed Deployment • Local DB per server • Replicated package content • Managed as separate entities • SQL replication NOT supported • Questions • Replicationover the wan … • Streamingover the wan ? • ODBCover the wan !!?

16. Lightweight Infrastructure Component • Application Virtualization Streaming Server • New server role in the 4.5 release • Provides application streaming services only • No dependency on configuration database or Active Directory • No desktop configuration service • No UI: registry or GPO based management • Supports RTSP://, RTSPS:// and FILE:// • Security based on ACLs • No integratedreplicationmecanism • Integrates with ESD solutions

17. Full infrastructure System Center Application Virtualization Management Server MSAV MANAGEMENT SERVER • Characteristics • Publishing Service • Streaming Delivery • Package/Active Upgrade • Requires Active Directory and SQL Server • When to Use • Virtual app specific publishing is needed and ESD publishing will not work • Per user assignment and configuration of virtual apps • User controlled refresh capability • Rapid application deployment during the production day • Considerations • Not good for a distributed branch environment (AD and/or SQL) • No replication of DB records • Separate management from ESD system

18. Lightweight infrastructure System Center Application Virtualization Lightweight Server MSAV LIGHTWEIGHT SERVER • Characteristics • No Publishing Service • Streaming Delivery Only • Package/Active Upgrade • No SQL or Active Directory • No metring or licensingnor UI • ACL Control of application • Detection interval for new apps • When to Use • Alternate publishing is available (ESD, Script, etc.) but streaming is still desired • Lower server maintenance option which is good for the branch • Package/Active Upgrades still desired • Considerations • Content must be replicated through ESD or other means • Complete updated SFT must be replicated to sites

19. New Options for Resource Targeting Configurable Source Roots for Virtual Application Components • Group Policy configurable client registry paths for resource paths controlling virtual application resource locations • Overrides OSD and Application Record root paths • Can be FILE://, RTSP://, RTSPS:// • Appends resource specific information to overridden path • Example: • OSD Path is RTSPS://FullServer.Apps.Com/Content/MyApp/MyApp.SFT • ASR is set toRTSPS://BranchServer.Apps.Com/ • Client will use RTSPS://BranchServer.Apps.Com/Content/MyApp/MyApp.SFT

20. Combined Streaming Infrastructure Streaming Delivery for the Enterprise • Tworemarksthere: • Beware to replicationconsiderationsrelated to updates • VECD and MSAV: technicallyand licensingspeaking

21. Standalone Mode Detached Delivery of Virtual Applications MSI WRAPPING OF MSAV FILES • Characteristics • New sequencer option • Interoperability with SMS 2003 R2 and SCCM 2007 • Server is not required • Virtual applications can be inventoried via Add/Remove • Third party ESD systems may also control virtual applications • Standalone mode virtual applications may be delivered via media or from a file share • When to Use • When no expectation of a streaming server • Interoperability with ESD without requiring a new infrastructure • Considerations • Specific application virtualization client mode • Streaming, licensing and metering functions as well as active upgrade are not enabled

22. MSI wrappingand standalone mode demo Lionel Cau Snr Consultant & MS Practice Mger Sogeti Switzerland

23. Extending Scalability Supportability Enhancements • Betterfeatures • Background Streaming • Auto-load options (on first launch, on login) • Windows Server 2008 Terminal Services Support (x86 only) • Better Standards & CEC Support • Microsoft Update for all Application Virtualization components (client, server, sequencer) • Microsoft Update support for virtualized applications at sequencing time (not available at run time) • Volume Shadow Copy Service (VSS) Writer support • Better Management • System Center Operations Manager 2007 Management Pack • ADM Template & WMI Provider for Client • Best Practice Analyzer / Desired Configuration Monitoring • Better Diagnostics & Reporting • Watson Integration on Client and Server • Event Log Support on Client and Server

24. Globalization Globalization and Localization Features • Installing on any supported OS language* • Mixed language environments (server/client) • Detecting & respecting the user locale & regional settings (implies that all the resource files for all languages are available) • Sequencing non-English/Localized applications • Foreign language Active Directory and server support

25. Microsoft Security Standards Increased security as a whole • Release developed in compliance with Microsoft Security Initiatives (TwC, SWI, SDL) • Enable Internet facing scenario • No VPN required • MS App Virt Client is on an Untrusted network • MS App Virt Server is on an Untrusted network • Secure by Default configuration out of the box • Client privileges locked down • TLS Support via Schannel (on by default) • Kerberos support • Server Authentication

26. SCCM integration

27. Application Virtualization Mgmt in R2 • Integrate SoftGrid 4.5 feature set into the release of System Center Configuration Manager 2007 R2 SP1 • Make managing virtual applications the same experience for the SCCM administrator as managing standard or “physical” software • Requires SCCM 2007 R2 SP1 and MSAV 4.5 • Server Side: • Copy the Application Virtualization Streaming Server (lightweight component) to the Primary Site Server • use Distribution Point (DP) properties page to enable the streaming component to be installed and configured on the DP • Client Side: • Customers must first deploy the SoftGrid 4.5 client to workstations • Enable virtual application deployment for the Advertised Programs Client Agent • Sends client policy to enable virtual applications on client computers • Maintain the dynamic nature of SoftGrid virtualization • Version checking, user-based targeting, streaming

28. SoftGrid Client-side scalability SCCM Advanced Client (Desktop publishing, inventory) SCCM launchhandler (Vapplauncher) SFTMIME (ADD, CONFIGURE, DELETE) WMI Provider (Get properties for Packages and Applications) SoftGrid Client Agent (SFTTray) SoftGrid Registry

29. Virtual Application Advertisements • A SCCM administrator uses the New Advertisement Wizard and can specify things like the following: • The collection of machines that the package should be delivered to • The time at which it should be delivered • Should it be mandatorily delivered or should the user or users have an option to install or reject the package? • When delivered, should it be added as a streaming virtual application or a locally available virtual application (“stream from DP” or “Download and Execute”) • Stream from DP – SFT file is accessed from the distribution point and stays on the distribution point • download and execute - the SFT file is downloaded and is local to the client computer

30. Package Upgrade • Scenario: the virtual package is revised with a new update • SCCM administrator updates the source contents of the SCCM package and updates the distribution points with the new, sequenced output • SCCM uses Binary Delta Replication for both site to site and site to DP data transfer to update the package on the DP • SCCM R2 supports differentialupdates for recomposing full package on DP (4.5 sequencerisnow able to produce delta .sft) • Administrator re-runs advertisements • With streaming delivery, the next time the end-user launches the application, the server will deliver the updated virtual application(s) • With local delivery, changes are downloaded via BITS and RDC to the local SCCM cache and then applied locally when they are completely downloaded

31. Virtualization and costs

32. Application virtualization TCO • Application virtualization: benefits • Minimize application conflicts and regression testing • Simplify OS migrations and patching • Build business continuity for applications • Intelligently manage desktops including security • Reduce PC management costs • Accelerate application availability and deployment • Application virtualization: costs • Licensing • Training • Distributed architecture design and setup • Client distribution (TS or local) • Sequencing • Maintenance

33. MAV platform SMS/SCCM Management Console SMS/SCCM Database Microsoft Application Virtualization Management Console Active Directory SMS/SCCM Distribution Point Management Web Service SMS/SCCM application delivery System Center Application Virtualization Management Server Microsoft Application Virtualization Database Windows application VECD Streaming + manifest Terminal server System Center Application Virtualization Streaming Server Microsoft Application Virtualization Sequencer Microsoft Application Virtualization Clients Desktop Virtualized application VECD Streaming Terminal server MSI-wrapped virtualized application Microsoft Application Virtualization Clients Desktop Standalone Microsoft Application Virtualization Client VECD Terminal server Application delivery via MSI on CD Microsoft Application Virtualization Clients Desktop

34. Sequencing: shorter but not easier Albeit process gets rid of many setup’s issues, there are others things to consider because of virtualisation’smecanism

35. Pre-sequencing best practices • Identify and categorize applications • criticity, impact, business lines • features and relationships • setup phase, execution phase • reducenumber of applications ! • Build or formalizeyour DSL • sources and licences • maintain one identification formper application includingmain tests to perform and history • assignatleast one contact per application • technical contact • and/or super user

36. Sequencing best practices • Sequencer should be placed in an isolated environment • No agents or background applications (Search, WSUS, AV…) • Virtual machine or physical CPU • Must have a second drive with a letter that matches the virtual drive used by the client (Default is drive Q) • Use naming conventions • Understandwhatshouldbeinside FB1 and FB2 • Understandwhatis VFS, MNT and VREG • Do not hesitate to modify OSD files • Beware of licensingrequirements • Beware of upgrading scenarios • Build Tests scenarios: sequencingislike packaging in a lot of ways • Deploy to a staging environment

37. Tips and tricks demo Lionel Cau Snr Consultant & MS Practice Mger Sogeti Switzerland

38. Sequencing best practices • Guidelines • Baselines • Collaborate • Tests • Recipes • Updates • Maintain SLAs

39. SOGETI is making SoftGrid much more accessible announcing

40. Formalize, Industrialize, Mutualize Generalize Request and Delivery Process: 1: Requests for packaging are submitted by customer 2: Sogeti’s Service Delivery Manager valids requests and identify application technical specifications 3: Sogeti’s Service Delivery Manager gather all required sources files and licences in order to complete request 4: Once requests are planned, files are uploaded to dedicated offshore secured ftp/file server for customer project 5: Sequencers download files from ftp/file server on dedicated virtual application server for customer project 6: Packages are created and tested on virtual application Server 7: Tests are performed till requirements are achieved including tests on Vista machine 8: Sequencers store packages + recipes + applications related documents on ftp/file server 9: Sequenced packages are downloaded to customer’s file server 10: Sogeti’s Service Delivery Manager manages delivery + fullfills request history and incident management

41. Conclusion

42. MSAV : a mature platform • Integrationwith AD • Distributeddeployment • Availability, Capacity, Scalability • Security • Backup and DRP • Command line tools and automation • Integrationwith ESD • Roamingusers and site awareness • Mobile users and disconnected mode • Integrationwith TS/Citrix • Documentation, knowledge base, white papers • Troubleshootingtools and techniques • Users’ communities, blogs and forums • References, case studies, analysts and product adoption • Dedicated 3rd party utilities • Dedicated 3rd party service offerings

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