Demystifying the Deployment of Office 2010 on App-V

2. Demystifying the Deployment of Office 2010 on App-V Adam Kiu Program Manager, Application Virtualization Microsoft Corporation

3. Session Objectives and Takeaway • Session Objective(s): • Why Office 2010 on App-V? • Simplify your deployment of Office 2010 • Planyour customized Office 2010 Deployment • Sequencea Office 2010 Package • Publish the Office 2010 package to users on App-V • Key Takeaway(s): • Understand Office 2010 benefits on App-V • Deploy Office 2010 on App-V easily and every time

4. Presentation Flow • Why Office 2010 and App-V • Planning • Sequencing • Deploying • Additional Resources

5. Why Virtualize Office on App-V? Built-in management infra. SCCM integrated, centralized Easy servicing, add-in delivery control No Install, instantly use Side-by-side, conflict resolution

6. Why App-V: The Isolated Application Integration Limitations

7. Microsoft App-V 4.6 Office 2010 Deployment Kit for App-V

8. Office 2010 Deployment Kit for App-V What is it? • MSI ~10 MB, available from download center http://www.microsoft.com/downloads/details.aspx?FamilyID=479f12f2-5678-493e-bce1-682b3ece5431 • Optional for: • Virtual Proxies – for 32-bit Office 2010 packages • Fast Search in Outlook • Work on documents in SharePoint library • Send to OneNote printer • Mail control panel applet • Simple MAPI • Office Document indexing Required for: Office 2010 Licensing – client activation

9. Virtual Proxy – tech overview Scenario – Open an Office file from a SharePoint Library Local Environment Virtual Environment Virtual File System Virtual Registry Apps OSD FTA Shortcuts Launch path SharePoint OSD FTA Shortcuts Launch path OSD Launch path ActiveX control (altered to be VE aware) ActiveX control

10. BMW “The plans include virtualization of the Microsoft Office 2010 suites, which will run alongside a locally installed version of Microsoft Office 2007 for testing purposes. This will enable the new functionality to be evaluated before Office 2010 is deployed in production.” BMW Group MDOP Customer Case Solution Study

11. Presentation Flow • Planning • Understanding Limitations and Features • Integration with Other Apps and Add-ins • Client Considerations • Office Install Considerations • Creating a Test Plan • Sequencing • Deploying • Additional Resources

12. Limitations, Features of App-V & Office 2010

13. Planning – Critical Questions • Is Office being used more as a ‘platform’? • Are there applications to integrate that must stay native?

14. Planning - Which Office 2010 products can be virtualized with App-V? Suites (32-bit and 64-bit) • Office Professional Plus • Small Business Basics • Standard Standalone apps (32-bit and 64-bit) • PowerPoint • Project Professional/Standard • Publisher • SharePoint Designer • Visio Premium/Professional/Standard • Word • Access • Excel • SharePoint Workspace • InfoPath • OneNote • Outlook

15. Planning - What Applications Will Office 2010 Integrate With? Most Common:

16. Add-in/Dependency Options Increased control but increased complexity!

17. Planning - What We Recommend

18. Planning – Package Size • Maximum Package Size is 4 GB! • Real-life package size tests • Impact on: • Streaming • Bandwidth • Maximum size limit

19. Planning – Other Client Considerations

20. Planning – Office 2010 licensing • Virtual/local Office 2010 have the same licensing requirements, options, and keys • Activation options: KMS (Key Management Service) • KMS Host server required. Clients will activate against that server MAK (Multiple Activation Key) • A product key with pre-determined amount of allowed activations. Clients will activate against Microsoft servers over the Internet Combo – KMS for some products, MAK for others • More information online http://technet.microsoft.com/en-us/library/ee624349.aspx • Why plan for this? - The Deployment kit is installed differently based on your licensing choices

21. Planning - Office 2010 Customizations • Same options as local installs - • Office Customization Tool (OCT) • Group Policy • Config.XML • Setup command-line options http://technet.microsoft.com/en-us/library/ee656738.aspx

22. Planning - Create a Test Plan • Tip: Get top 5 list of KW’s most important scenarios and ensure it passes. Example list:

23. Presentation Flow • Planning • Sequencing • Sequencing Prep • Demystifying the Deployment Kit flags • Updating and patching • Tricky sections– Virtual Registry editing and adding applications • Dynamic Suite Composition • Deploying • Additional Resources

24. Sequencing Office 2010 • We do not provide pre-sequenced Office 2010 for use in production environments • Consult App-V Best practices • Sequencing station • VM’s recommended • Match target machines • Basic flow -

25. Install Deployment Kit on sequencing station msiexec /i OffVirt.MSI [featureflags] [license flags] Use the MSI that matches the target OS architecture:

26. Install Deployment Kit on sequencing station msiexec /i OffVirt.MSI [featureflags] [license flags] Use the option that matches the target OS architecture 32-bit: 64-bit: ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core,OSppWoW64

27. Install Deployment Kit on sequencing station msiexec /i OffVirt.MSI [featureflags] [license flags] KMS Product ID (consult recipe), example: [optional] KMS Host settings: MAK Product Key(s): Allow users to activate: PROPLUS=1 KMSSERVICENAME=“kms.contoso.com” KMSSERVICEPORT=1689 PIDKEYS=12345-ABCDE-12345-ABCDE-12345 USEROPERATIONS=1

28. Monitor Office Install - Office 2010 patches • Office 2010 updates already available today – include those in the initial package • Two ways to capture the patches: • Drop them in the \Updates folder and they will be applied during Office install • Apply after Office installation is complete (while monitoring is on!)

29. Registry Settings Explained • Registry Changes can be made during monitoring or post in Sequencer • Some registry settings explained: • 64-bit OS – Use WOW6432Node • Visio – SxSAppExtensions • Sharepoint Registry – {See recipe} • Office 2010 – Merge with Local {See recipe} • Outlook 2007/2010 Co-existence – {See recipe} • OMS Add-in – {See recipe}

30. OSD Files - Explained • OSD Version Numbers only have to match, not match Office version number

31. Dynamic Suite Composition Adding an add-on to my Office 2010 package demo

32. Presentation Flow • Planning • Sequencing • Client Deployment • Recommend push order on Client • Installing Licensing • Publishing Methods • Configuring Virtual Proxies • Additional Resources

33. Push order on the client Recommendation:

34. Install Deployment Kit on client - Licensing msiexec /i OffVirt.MSI [license flags] Use the MSI that matches the target OS architecture:

35. Install Deployment Kit on client - Licensing msiexec /i OffVirt.MSI [license flags] KMS Product ID (consult recipe), example: [optional] KMS Host settings: MAK Product Key(s): Allow users to activate: PROPLUS=1 VISIOPREM=1 KMSSERVICENAME=“kms.contoso.com” KMSSERVICEPORT=1689 PIDKEYS=12345-ABCDE-12345-ABCDE-12345 USEROPERATIONS=1

36. Package Publishing

37. Configure Deployment Kit – Virtual Proxies • msiexec/i OffVirt.msi • ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2runWDSProxy,Click2runOWSSuppProxies • PACKAGEGUID={SFT package GUID} • PACKAGEVERSION=“OSD version for proxies, • Outlook, and OneNote” • OUTLOOKNAME=“OSD app name for Outlook” • ONENOTENAME=“OSD app name for OneNote” • MAPISERVER=“OSD app name for MAPI proxy” • VIRTUALSEARCHHOST=“OSD app name for Search proxy” • MLCFG32CPL=“OSD app name for virtual mail applet” • OWSSUPPServer=“OSD app name for SharePoint proxy” Installs local proxy components and points to their virtual counterparts by matching on PackageGUID, app version, and app name

38. Configure Deployment Kit – Virtual Proxies • msiexec/i OffVirt.msi • ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2runWDSProxy,Click2runOWSSuppProxies • PACKAGEGUID={SFT package GUID} • PACKAGEVERSION=“OSD version for proxies, • Outlook, and OneNote” • OUTLOOKNAME=“OSD app name for Outlook” • ONENOTENAME=“OSD app name for OneNote” • MAPISERVER=“OSD app name for MAPI proxy” • VIRTUALSEARCHHOST=“OSD app name for Search proxy” • MLCFG32CPL=“OSD app name for virtual mail applet” • OWSSUPPServer=“OSD app name for SharePoint proxy” No spaces after commas

39. Configure Deployment Kit – Virtual Proxies • msiexec/i OffVirt.msi • ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2runWDSProxy,Click2runOWSSuppProxies • PACKAGEGUID={SFT package GUID} • PACKAGEVERSION=“OSD version for proxies, • Outlook, and OneNote” • OUTLOOKNAME=“OSD app name for Outlook” • ONENOTENAME=“OSD app name for OneNote” • MAPISERVER=“OSD app name for MAPI proxy” • VIRTUALSEARCHHOST=“OSD app name for Search proxy” • MLCFG32CPL=“OSD app name for virtual mail applet” • OWSSUPPServer=“OSD app name for SharePoint proxy” {Braces required}

40. Configure Deployment Kit – Virtual Proxies Case sensitive • msiexec/i OffVirt.msi • ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2runWDSProxy,Click2runOWSSuppProxies • PACKAGEGUID={SFT package GUID} • PACKAGEVERSION=“OSD version for proxies, • Outlook, and OneNote” • OUTLOOKNAME=“OSD app name for Outlook” • ONENOTENAME=“OSD app name for OneNote” • MAPISERVER=“OSD app name for MAPI proxy” • VIRTUALSEARCHHOST=“OSD app name for Search proxy” • MLCFG32CPL=“OSD app name for virtual mail applet” • OWSSUPPServer=“OSD app name for SharePoint proxy”

41. Configure Deployment Kit – Virtual Proxies • msiexec/i OffVirt.msi • ADDDEFAULT=Click2runOneNoteProxy,Click2runOutlookProxies,Click2runWDSProxy,Click2runOWSSuppProxies • PACKAGEGUID={5971AF75-7831-4AE9-906F-0F30C7DD0CA5} • PACKAGEVERSION=“14.0.4736.1000” • OUTLOOKNAME=“Microsoft Outlook 2010” • ONENOTENAME=“Microsoft OneNote 2010” • MAPISERVER=“Microsoft Virtual Office Simple Mapi Proxy Server” • VIRTUALSEARCHHOST=“Search MAPI Protocol Handler Host” • MLCFG32CPL=“Windows Control Panel” • OWSSUPPServer=“Microsoft SharePoint Client Support Manager” Example virtual proxy configuration command line

42. Presentation Flow • Planning • Sequencing • Deploying • Additional Resources

43. On-line Resources

44. Related Content • Breakout Sessions/Chalk Talks/Hands-on Labs • Wednesday 5:30 – 6:30 • OFS301-IS – Demystifying the Deployment of App-V 4.6 and Office 2010: A Guided Tour • Wednesday 1:20 - 2:05 • VIR302-LNC – App-V End-to-End: Understanding How to Package and Deploy Virtual Applications Quickly • Wednesday 4:00 – 5:00 • VIR304 – How to Create App-V Packages More Efficiently with the New App-V 4.6 SP1 Sequencer • Thursday 10:30 – 11:30 • VIR304-IS – Microsoft App-V Top Customer Scenarios • VIR04-HOL - Microsoft Application Virtualization 4.6 Service Pack 1 Sequencer Technology Preview

45. Session Evaluations Tell us what you think, and you could win! All evaluations submitted are automatically entered into a daily prize draw*  Sign-in to the Schedule Builder at http://europe.msteched.com/topic/list/ * Details of prize draw rules can be obtained from the Information Desk.

46. © 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. 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.