1. www.sharepointconference.it

2. Sponsor Platinum Gold

3. Microsoft Office 2010: Deployment Techniques Renato F. Giorgini Evangelist IT Pro Microsoft OFF309 IT Pro Trainer Nicola Ferrini

4. Agenda  Introduction  Office 2010: 32-bit and 64-bit  Product Activation: KMS & MAK  Office Migration Planning Manager (OMPM)  Office Customization Tool (OCT)  Config.XML  Managed Deployment  Network Share  GPO Scripts  System Center  Application Virtualization Deployment Update Plug-in and Add-on Deployment  Presentation Virtualization  Group Policy Customization  Q&A!

5. Planning & Deployment PhasesOperationsDeploymentConfigurationMigrationPlanning System Readiness & Inventory Application Compatibility Test File Compatibility Test Setup & Package Customization Lockdown & Control Deployment User Settings Migration Update & Maintenance

6. Planning & Deployment ToolsOperationsDeploymentConfigurationMigrationPlanning Compatibility Inspector Enterprise Learning Framework Assessment & Planning Toolkit Office Environment Assessment Tool Office Migration Planning Manager User State Migration Tool User State Migration Tool Office Configuration Tool Config.xml Group Policy SPP- VAMT, KMS SPP- VAMT, KMS Office Configuration Tool Office Configuration Tool End User Readiness SCCM GPO Start-up Scripts Virtualization Security Guide Office OnRamp TechNet Resource Center TechNet Community

7. When Support Ends for Previous Versions

8. Office 2010: 32 and 64 bit

9. OS support for Office 2010 – Windows Client  500 MHz processor, 256 MB RAM, 3 GB Disk Space (Pro Plus SKU)  Not supported 32-bit and 64-bit Side-By-Side on the same machine  http://blogs.technet.com/office2010/archive/2010/01/22/office-2010-system- requirements.aspx http://blogs.technet.com/office2010/archive/2010/01/22/office-2010-system- requirements.aspx  http://technet.microsoft.com/it-it/library/ee624351(en-us,office.14).aspx http://technet.microsoft.com/it-it/library/ee624351(en-us,office.14).aspx

10. OS support for Office 2010 – Windows Server  500 MHz processor, 256 MB RAM, 3 GB Disk Space (Pro Plus SKU)  Not supported 32-bit and 64-bit Side-By-Side on the same machine  http://blogs.technet.com/office2010/archive/2010/01/22/office-2010-system- requirements.aspx http://blogs.technet.com/office2010/archive/2010/01/22/office-2010-system- requirements.aspx  http://technet.microsoft.com/it-it/library/ee624351(en-us,office.14).aspx http://technet.microsoft.com/it-it/library/ee624351(en-us,office.14).aspx  * = Needs MSXML 6.0

11. Should we go 32-bit or 64-bit?  32-bit Office is best path for most users  Under Windows 64-bit, Office 32-bit users benefit from a full 2 GB of memory per application instance  64-bit Office is best for select set of users  Allows to use more memory - higher performance in Excel, Project  Higher security due to Hardware DEP enforcement  Office 2010 64-bit cannot be installed side-by-side with Office 2010 32-bit or previous versions of Office  Using App-V can be a possible path for some users  Consider Application Compatibility issues (DEP; VBA Code, COM...)

12. Product Activation: KMS & MAK

13. Office 2010: Two Activation Models  Local activation service in your environment  Key Management Service (KMS)  Direct activation with Microsoft  Multiple Activation Key (MAK)  Notes:  Privacy: all methods designed to protect user privacy Microsoft does not use activation information to identify or contact you  Activation not required for Office 2010 Server products SharePoint Server, Project Server, Exchange Server

14. KMS Host  One KMS host for Windows and Office  Highly scalable service (100’s of thousands)  Supported KMS host OSs:  http://technet.microsoft.com/en-us/library/dd772269.aspx http://technet.microsoft.com/en-us/library/dd772269.aspx

15. Multiple Activation Key (MAK)  One MAK per product per organization  Flexible options to install MAK on every PC client:  Office Customization Tool (OCT)  Automated install file (Config.xml)  Change key “Backstage View”  Volume Activation Management Tool 2.0  Options to activate MAK products:  Online  Phone or proxy activation through VAMT 2.0

16. Volume Activation Management Tool (VAMT)  Volume Activation Management Tool (VAMT) 2.0  Search for Windows and Office in the enterprise network  Deploy product keys to clients  Proxy MAK activation  Trigger MAK online and KMS activations  MMC snap-in  For info:  www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=826 5fdef-b921-4dbf-ba8b-bb1cbe238ce6 www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=826 5fdef-b921-4dbf-ba8b-bb1cbe238ce6  www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=989 3f83e-c8a5-4475-b025-66c6b38b46e3 www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=989 3f83e-c8a5-4475-b025-66c6b38b46e3

17. Office Migration Planning Manager (OMPM)

18. What is OMPM?  Introduced in Office 2007 for OOXML conversion  New features for Office 2010 concerns  Assess your environment to determine potential issues & target deployment testing  Document Conversions  Add-In issues  Suite of tools for analyzing Office documents for potential migration issues  Scanner  Database  Reporting tool  Companion tools

19. Scanner  Can scan local drives, network shares, SharePoint, and other WebDAV enabled systems  Can be configured using Offscan.ini  Light and Deep scanning modes Light: collects file properties Deep: cracks open files and looks for issues  Deployable via SCCM or login script

20. OMPM Commands Reference  Provision SQL Server Database for Logs:  CreateDB.bat \  Run Scan on client machine  Offscan.exe  Import OMPM File Scanner data files into the database  ImportScans.bat \  Import OMPM File Scanner action files into the database  ImportActions.bat \

21. Reporting Tool: Issue Summary

22. Reporting Tool: File Summary

23. OMPM: 32-bit to 64-bit Migration  New scanner module for migration issues between 32 bit and 64 bit editions (Excel, Access, PowerPoint, Word)  Scan any 97-2010 file for x86->x64 migration ActiveX Macros COM objects  Optionally collects Excel V4 and VBA code usage information from specific opt-in customers for future VBA work  New reporting options for these issues  Is not a general-purpose macro scanner

24. Demo: OMPM

25. Office Customization Tool (OCT)

26. Office Customization Tool  The primary tool for most customizations  Setup.exe /admin  Allows to customize (and re-customize) an Office Installation  Future modifications are applied as Updates  Customizations are saved in a.MSP file  If saved under \Updates folder it’s automatically applied during setup  It is possible to force the use of a specific MSP File: Setup.exe /adminfile  It is possible to apply, post-setup, other MSP customizations Msiexec.exe /p  Customizes the following areas:  Setup, Features, Additional content, Outlook (multiple) profiles

27. OCT: 32-bit and 64-bit Support  Each setup, 32-bit and 64-bit, can be run with /admin switch  32-bit MSP patches cannot be applied directly to 64-bit Office  Users can customize once for a mixed environment:  32-bit OCT: Can import 64-bit patches and apply them to 32-bit products Can export 32-bit patches as 64-bit patches  64-bit OCT: Can import 32-bit patches and apply them to 64-bit products Can export 64-bit patches as 32-bit patches

28. What happens during Setup? 1. Run Setup. 2. Check prerequisites. 3. Read XML data. 4. Build the feature tree. 5. Create a local installation source on the user's computer. 6. Install Office. 7. Apply the customization file. 8. Apply software updates.

29. Demo: OCT

30. Config.XML

31.  If saved in the same folder of setup.exe it’s automatically applied  Otherwise Setup looks for Config.XML in the core product folder  It is possible to force the use of a specific file:  Setup.exe /config  The options contained in the Config.XML take precedence over the.MSP customizations  Used to:  Copy the installation source locally without installing Office  Specify the path of the network installation point  Select which product or language to install  Change where Setup looks for Customization files and updates  Make last-minute or one-off customizations without running the OCT to create a new customization file

32. Demo: Config.XML

33. Managed Deployment

34. System Center Presentation Virtualization Group Policy Startup Script Network Share Application Virtualization Deployment options http://technet.microsoft.com/en-us/library/ee683866(office.14).aspx Note: Group Policy software installation (GPSI) is not supported.

35. Network Share  Leave the installation files on a network share accessible by clients.  Advantages:  Easier implementation for smaller IT departments  Network share and access are the only requirements  Users can initiate (manually) the installation as they are ready  Limitations:  Difficult to control and monitor who installs Office  User needs Admin privileges on local machine  Difficult to manage installation times by end users, which can cause congestion

36. Group Policy Startup Scripts  Use Group Policy to assign computer startup scripts that run the setup.  Advantages:  Leverages Active Directory and Group Policy infrastructure  AD handles the elevation of privileges required for application installation  Can use a similar process to apply updates and service packs  A script can be written in any language supported by the client  Limitations:  Installation not managed as Group Policy software installation (GPSI)  Group Policy has limited awareness of the installation state  Script or batch file required to uninstall/reinstall on multiple computers  Difficult to determine exactly which updates were applied for each client

37. System Center  System Center Essentials  System Center Configuration Manager (SCCM)  Advantages:  Network bandwidth management  Centralized control, monitoring, reporting, and issue resolution for deployment  Reduced need for help desk to troubleshoot at the desktop  Limitations:  Requires supporting infrastructure & expertise

38. Demo: System Center

39. Deployment with Application Virtualization (App-V)

40. Benefits Of App-V: Run applications as a “service”  Access anywhere  Over the web  Portable devices  Just in time deployment (Click-to-Run)  Installer does not run  Instant gratification  Simple servicing  Update once, deliver everywhere  Users automatically stay up to date

41. Benefits Of App-V Run applications without conflicts  No changes to system  Safely run apps side-by-side  No OS decay over time  Lower migration costs  State separation  Store app state separate from OS state  State categorized as user versus system  User state stored in profile, roams with profile

42. App/OS Model Comparison Traditional App/OS ModelVirtualized App/OS Model

43. How Does It Work?  App packaged using Sequencer  Installation monitored to capture resources  All app resources stored in an app image (.SFT)  App image placed on server for distribution  App streamed to client over network  SMB, HTTP(S), RTSP(S)  Can leverage DFSR replica and BranchCache  Other distribution mechanisms possible (USB)  App-V runs app in Virtual Environment (VE)  App virtualization layer handles resource requests

44. Application Virtualization running… Read & Write Virtual Environment (Registry,.ini, DLL, Group Policy, etc.) Application Read & Write Read Only System Files (Registry,.ini, DLL, etc.) System Services (cut and paste, OLE, printers, etc.) Profile Data Operating System

45. Application Packaging.sft and.sprj.osd and.ico Manifest.xml Each published application contains:.osd file – Open Software Description "link" files.ico file – Icon file Each package contains:.sft file – Microsoft Application Virtualization-enabled application.sprj file – Microsoft Application Virtualization project file Manifest.xml - Used in package distribution

46. Office 2010 Deployment with App-V  Use Microsoft Application Virtualization to stream applications on-demand  Advantages:  Centralized application management  Support for roaming users and making applications available quickly  Can run multiple versions of Office on the desktop  Previously incompatible applications can run on the same desktop  Centralized image simplifies updates, management & helpdesk  Limitations:  Requires a supporting infrastructure and resources  Consider network bandwidth availability for streaming applications  Integration into existing infrastructure, such as the patch management process

47. Improved Application Virtualization Support Tighter integration with Microsoft App-V  Potential to simplify deployment & management  Microsoft invested in App-V with Click-to-Run  Office 2010 requires App-V 4.6 (available in MDOP 2010)  App-V requires deployment specific sequencing  Features improved with App-V 4.6/Office 2010 include:

48. Will Office 2010 be supporting virtualization?  YES...and not exactly Office 2007 Virtualization Agent* Operating System Hardware On machine Virtualized Virtualization Agent* Operating System Hardware On machine Virtualized Office Redist App. A App. B App. C Office 2010 App. A App. B App. C Office 2007 Office 2010

49. Well Yes…. 1. We’re building the Office “redistributable”? The virtualization enabler “bits” for Office 2010 1.SPP Licensing components 2.Windows Desktop Search for Instant Search in Outlook 3.SharePoint Proxy (so virtualized office can edit documents hosted by SharePoint) 4.URL protocol handers (mailto:, feed, feeds, stssync, webcal, webcals) 5.Filters for office document indexing 6.(Virtual) Mail Control Panel applet (needed for some advanced account configuration scenarios) 7.Simple MAPI proxy (ex Right click on file, Send To -> Mail) 8.Send to OneNote Printer driver 2. Work has been done to make Office 2010 run faster when virtualized

50. Click-to-Run  New software delivery mechanism based on core virtualization and streaming technologies from App-V  It’s fast  With Click-to-Run, it’s easier to always be running the latest and most secure version of Office  It’s low impact, and co-exists with other software on the machine  It has full language support, and will work on both 32-bit and 64-bit Operating Systems

51. Application Virtualization Management Server and Client Requirements and Interactions  Client for desktops and terminal services  Small footprint  Windows XP, Windows 2003 Server, or newer  12 megabyte (MB) for installation files, at least 2048 MB for cache file

52. Demo: Application Virtualization

53. Reducing Application Conflicts Potentially conflicting applications have their own environment Applications in a suite can share the environment Application Virtualization packages contain the complete environment for the application.sft and.sprj.OSD and.ICO.osd and.ico Manifest.xml.sft and.sprj.osd and.ico 3 rd party app

54. Running Multiple Versions of a Single Application on the Same Computer Virtual Environment 1 Virtual Environment 2 2003 Each application runs in its own virtual environment, which allows different applications to share the same hardware with two versions of the same application

55. Side-by-Side execution

56. Demo: SSxS (Super Side by Side)

57. Application Updates Update Updates Update once on server Seamless update to clients

58. Dynamic Suite Composition (DSC)  Application known to not conflict may be administratively set up to share the same virtual environment.  Mandatory and Optional dependency configuration options  Virtual applications may now share common dependencies  Customer 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 Combined Virtual Environment

59. Demo: Dynamic Suite Composition

60. Deployment Scenarios using the.msi File Application Sequencing Workstation.msi File CD Delivery GPO Delivery SCCM Delivery MSI Install User Click Sequencer-generated MSI No streaming server Load from file Manual deployment or electronic software distribution (ESD) Configured through registry Preserve virtualization Simple deployment No network or server needed at run-time Pre-cached and available to all users Virtualized Application SFTFS.FSD

61. APP-V e RDS : Better Together  APP-V 4.6 supports 64 bit OS:  Remote Desktop Services of Windows Server 2008 R2  Terminal Services of Windows Server 2008  Easy deployment, management and applications maintenance  Remote access to the applications, also using web  RemoteApp and WebAccess Integration

62. Demo: Presentation Virtualization

63. Group Policy Customization

64. Group Policies  Administrators can use Group Policy to mandate user settings for Office  Office policy settings are contained in the Administrative Template (.adm or.admx and.adml) files  Administrators can use settings to create highly restricted or lightly managed desktop configurations  Group Policy settings have precedence over OCT settings  Administrators can use settings to disable file formats that are not secure across the network

65. Administrative Templates  http://www.microsoft.com/downloads/details.aspx?FamilyID=C343 6A99-5C80-48CE-83E8- 481F9C3D2288&displaylang=en&displaylang=en http://www.microsoft.com/downloads/details.aspx?FamilyID=C343 6A99-5C80-48CE-83E8- 481F9C3D2288&displaylang=en&displaylang=en

66. Group Policy Registry Keys  Computer policy settings:  HKEY_LOCAL_MACHINE\Software\Policies (the preferred location)  HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVe rsion\Policies  User policy settings:  HKEY_CURRENT_USER\Software\Policies (the preferred location)  HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVers ion\Policies  Office 2010  HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Office\14.0  HKEY_CURRENT_USER\Software\Policies\ Microsoft\Office\14.0

67. Demo: GPO

68. Next Steps  Plan deployment carefully  Plan KMS/MAK Activation  Assess current environment (files, add-ins,...)  Customize Office Installation (OCT, Config.xml)  Secure deployment using GPO & Admin Templates  Use, every time is possible, Application Virtualization

69. Additional (learning) resources:  Office 2010 – System Requirements:  http://technet.microsoft.com/it-it/library/ee624351(en-us,office.14).aspx http://technet.microsoft.com/it-it/library/ee624351(en-us,office.14).aspx  Application Virtualization:  http://technet.microsoft.com/en-us/subscriptions/downloads/default.aspx http://technet.microsoft.com/en-us/subscriptions/downloads/default.aspx  http://www.microsoft.com/appv http://www.microsoft.com/appv  http://blogs.technet.com/softgrid/default.aspx http://blogs.technet.com/softgrid/default.aspx  http://www.microsoft.com/italy/server/windowsserver2008/panoramica/introduzione-a-microsoft-application-virtualization.mspx http://www.microsoft.com/italy/server/windowsserver2008/panoramica/introduzione-a-microsoft-application-virtualization.mspx  http://support.microsoft.com/?kbid=980861 http://support.microsoft.com/?kbid=980861  MAP:  http://microsoft.com/map http://microsoft.com/map  USMT:  http://technet.microsoft.com/en-us/library/dd560750(WS.10).aspx http://technet.microsoft.com/en-us/library/dd560750(WS.10).aspx  Office Activation Technologies:  http://technet.microsoft.com/volumeactivation http://technet.microsoft.com/volumeactivation  OMPM:  http://technet.microsoft.com/en-us/library/dd901407.aspx (Office 2007 Link) http://technet.microsoft.com/en-us/library/dd901407.aspx  http://technet.microsoft.com/en-us/library/cc179179.aspx http://technet.microsoft.com/en-us/library/cc179179.aspx  http://www.microsoft.com/downloads/details.aspx?familyid=13580cd7-a8bc-40ef-8281-dd2c325a5a81&displaylang=en http://www.microsoft.com/downloads/details.aspx?familyid=13580cd7-a8bc-40ef-8281-dd2c325a5a81&displaylang=en  http://channel9.msdn.com/Wiki/OfficeDeployment/OMPMv1/ http://channel9.msdn.com/Wiki/OfficeDeployment/OMPMv1/  http://blogs.technet.com/office_resource_kit/archive/2010/01/22/office-2010-application-compatibility-tools.aspx http://blogs.technet.com/office_resource_kit/archive/2010/01/22/office-2010-application-compatibility-tools.aspx  OCT:  http://technet.microsoft.com/en-us/library/cc764476.aspx (Office 2007 Link) http://technet.microsoft.com/en-us/library/cc764476.aspx  Config.xml:  http://technet.microsoft.com/en-us/library/cc179195.aspx (Office 2007 Link) http://technet.microsoft.com/en-us/library/cc179195.aspx  VAMT:  http://www.microsoft.com/downloads/details.aspx?familyid=9893F83E-C8A5-4475-B025-66C6B38B46E3&displaylang=en http://www.microsoft.com/downloads/details.aspx?familyid=9893F83E-C8A5-4475-B025-66C6B38B46E3&displaylang=en  ELF:  http://www.microsoft.com/technet/desktopdeployment/bdd/ELF/Welcome.aspx http://www.microsoft.com/technet/desktopdeployment/bdd/ELF/Welcome.aspx

70. Questions and Answers

71. Grazie! Non dimenticare di compilare i moduli di Feedback! www.sharepointconference.it Renato & Nicola!

72. © 2010 Microsoft Corporation and Italian SharePoint & Office Conference. 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.