Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.



Published on

My presentation on MMS2011 in Las Vegas. Would you like to gain additional insight to the various best practices that other Application Virtualization customers are doing? This session will provide you with an opportunity to obtain insight from Application Virtualization MVPs with over 10 years of experience in the field. The objective of the session is to expose you to the numerous best practices, challenges and solutions that have been witnessed in the field in Application Virtualization.

  • Be the first to comment


  1. 1. Application Virtualization Best Practices: Notes From the Field <br />Ment van der Plas<br />IT Architect<br />Login Consultants<br /><br />@mentvanderplas<br />BC34<br />
  2. 2. A Quick Assumption<br />You are familiar with technical App-V terminology<br />
  3. 3. What’s Happening in the Field?<br />7 > XP<br />May 2011<br />7 > Vista Oct 2010<br />Source:<br />
  4. 4. Session Objectives and Takeaways<br />Give additional insight on App-V infrastructure myths and facts<br />Learn about App-V client configuration best-practises<br />Share sequencing challenges and solutions from the field<br />
  5. 5. Infrastructure<br />
  6. 6. Infrastructure Possibilities<br />
  7. 7. Infrastructure<br />Client<br />App-V Architecture<br />10010 0001101010101001010<br />
  8. 8. Infrastructure Myth #1<br />All App-V infrastructures are equal<br />Decision should be based on<br />Delivery possibilities<br />User-experience<br />Scalability<br />Administration<br />Growth<br />MYTH BUSTED<br />
  9. 9. Infrastructure Myth #2<br />Infrastructure has impact on<br />Number of virtual applications<br />Supported types of applications<br />Virtualization strategy<br />MYTH BUSTED<br />
  10. 10. Infrastructure Differences<br />Learn more<br /><br />Download free whitepaper<br />Choosing the right App-V Delivery Model<br />
  11. 11. demo<br />
  12. 12. Publishing Refresh Explained<br /><DESKTOPCONFIG><br /> <POLICY<br /> MANAGEDDESKTOP="TRUE“<br /> REPORTING="FALSE"><br /> <REFRESH ONLOGIN="TRUE“<br /> PERIOD="60"/> <br /> </POLICY><br /> <APPLIST><br /><App_A_manifest.xml> <br /> <App_B_manifest.xml><br /><App_C_manifest.xml><br /> </APPLIST> <br /></DESKTOPCONFIG><br />
  13. 13. Communication (common)<br />554<br /> RTSP<br />TCP 139, 445<br />UDP 137, 138<br />or 80<br /> SMB / HTTP<br />49152-65535<br /> RTP / RTCP<br />010010100011010<br />
  14. 14. Secure Communication<br />322<br /> RTSPS<br />443<br /> HTTPS<br />322<br /> RTSPS<br />010010100011010<br />
  15. 15. Infrastructure Myth #3Secure Streaming<br />Will provide secure application communication<br />Protocol X<br />MYTH BUSTED<br />RTSPS / HTTPS<br />
  16. 16. Communication (http + refresh)<br />80<br /> HTTP<br />80<br /> HTTP<br />80<br /> HTTP<br />010010100011010<br />
  17. 17. Determining Source Location<br />Stop using %SFT_SOFTGRIDSERVER%<br />Preferably use ASR, ISR, OSR or even override URL<br />More granular control <br />Override OSD content<br />
  18. 18. demo<br />
  19. 19. Application Upgrades<br /> Refresh<br /> OSDs / Icons<br /> Stream<br />010010100011010<br />100101<br />
  20. 20. Infrastructure Myths #4Application upgrades<br />Upgrades don’t work in every streaming scenario<br />“No Refresh” is an advantage for RTSP(s)<br />Don’t use upgrade scenario if app should run Side by Side <br />MYTH BUSTED<br />
  21. 21. Infrastructure Decisions and Thoughts <br />You choose your infrastructure only once<br />Important questions<br />Single console administration or broad application delivery methods?<br />Second infrastructure for virtual applications?<br />Is your network distributed? How about growth and scalability?<br />How are you going to deploy your MSI’s?<br />Like the App-V Client?<br />
  22. 22. Client<br />
  23. 23. Client Configuration Possibilities Today<br />Installation properties or transform file<br />Command line interface (sftmime)<br />Client Management Console<br />Registry (x86 and x64)<br />Group Policy Objects<br />Microsoft ADM template<br />Login Consultants ADM template (add-on)<br />MSI<br />MST<br />
  24. 24. Announcing<br />
  25. 25. Two Additional Configuration Options<br />App-V Client Pack<br />ADMX template<br />
  26. 26. Login Consultants ADMX Template Benefits<br />ADMX files are not stored in individual GPOs like ADM<br />But provided through Central Store; No “SYSVOL bloat”<br />ADMX files support multi language<br />Through optional ADML files<br />It’s one template again <br />Full options; no add-on<br />
  27. 27. PolicyPak Over ADMX<br />PolicyPak enables same UI experience as the application<br />Provides UI lockout for settings, tabs or whole page<br />Reverts settings when out of scope<br />Keeps settings managed – even when offline<br />Bonus: Delivers settings inside App-V sequences<br />
  28. 28. demo<br />
  29. 29. How Do I Get My Hands on This?<br />Learn more <br /><br /><br />Good news<br />100% free ADMX template<br />100% free PolicyPakApp-V Pack for your use<br />More details on the website including invite-only to PolicyPak 3.0 beta<br />Lead by Jeremy Moskowitz, Group Policy MVP<br />
  30. 30. Client Installation and/or Upgrade<br />Distinguish static settings from dynamic settings<br />KEEPCURRENTSETTINGS parameter<br />Prevents override locally applied registry <br />Some commandline parameters are ignored<br />Upgrades can’t be done when applications are running<br />
  31. 31. Migration Tip<br />Distribute App-V Client in your current environment<br />Better together with User State Virtualization<br /> User environment<br /> Applications<br /> Operating System<br />
  32. 32. demo<br />
  33. 33. Migration Best Practices<br />Deploy App-V in your current environment<br />App-V for Remote Desktop Services is included in RDS CAL<br />Consider User State Virtualization<br />Static, time critical settings  command line / transform<br />Dynamic configuration  ADM(x) or PolicyPak<br />Think about your App-V client update strategy<br />
  34. 34. Sequencer<br />
  35. 35. Process<br />Evaluate current process<br />Don’t only replace technology<br />Focus on application dependencies<br />
  36. 36. Common Questions<br />Virtualize middleware?<br />Apply Automatic Updates?<br />Build best for cross OS?<br />Build best for cross platform?<br />Use Dynamic Suiting Composition?<br />Clean up the sequence?<br />What are your best practices?<br />
  37. 37. Virtualize Middleware; Yes or No?<br />Direction of app-to-app communication? <br />What should be the user experience? (Office, IE plugins)<br />What’s the application update cycle?<br />Who or what is initiating the application update?<br />
  38. 38. Dynamic Suiting: Yes or No?<br />Eases administration of multiple virtual applications<br />Keeping track of relationships is key!<br />Troubleshooting effort may be increased<br />Different DSC behaviorbetween Files and Registry<br />ConfigMgr 2007 R2 integration has additional challenges <br />Dependencies have to be present on target machine<br />
  39. 39. demo<br />
  40. 40. Cleaning Up Sequences; Yes or No?<br />Settings that conflict with local applications <br />Internet Explorer proxy or homepage <br />Large installation residue<br />C:WindowsInstaller<br />C:Program FilesUninstall Information<br />Q:...<br />
  41. 41. Parsing Items<br />Parsing happens<br />in the (virtual) registry<br />In the (virtual) filesystem<br />Not inside files (xml/txt etc.)<br />Could hold some key elements to your application<br />
  42. 42. Automatic Updates<br />Don’t apply automatic updates in virtual environments<br />Different locations for disabling automatic updates<br />User Interface<br />Registry<br />“Config” files<br />Elapsed time for launch: 1.843 seconds<br />Elapsed time for launch: 2.123 seconds<br />Elapsed time for launch: 5.17 seconds<br />Elapsed time for launch: 28.211 seconds<br />
  43. 43. Sequencing for Multiple OS<br />OS Value<br />Limits the number of operating systems you can run on<br />Not mandatory; can be empty!<br />
  44. 44. Sequencing for Multiple Architecture<br />Watch for applications that use short folder names<br />Use %SFT_MNT%xxxVFSCSIDL_PROGRAM_FILES<br />Windows 7 x86<br />Windows 7 x64<br />
  45. 45. demo<br />
  46. 46. Best Practices Gone Old in App-V 4.6 SP1?<br />Installing the sequencer<br />Q: drive creation is taken care of<br />Dummy ODBC connections are created<br />Dummy Printer is installed<br />Using the sequencer<br />8.3 directory requirement is gone<br />First Run Tasks are now embedded in the wizard<br />Easier Dynamic Suiting logistics (apply to local system)<br />Best practices check before sequencing<br />Incompatibility check after sequencing<br />
  47. 47. Wrap Up<br />Infrastructure differences<br />Additional client configuration possibilities<br />Sequencing best practises<br />Deploy App-V in your current environment for smooth migration<br />Free: App-V for Remote Desktop Services<br />Free: WP “Choosing the right App-V model”<br />Free: ADMX template<br />Free: PolicyPak App-V pak<br />Free: App-V tooling<br />
  48. 48. Thank you<br />
  49. 49.
  50. 50. © 2010 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.<br />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.<br />