1 / 29

Office Deployment – Notes from the Field

Learn how to integrate and deploy Office into image engineering and deployment processes, including automated master image development and dynamic changes at deployment time.

kiaria
Download Presentation

Office Deployment – Notes from the Field

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OSP340 Office Deployment – Notes from the Field Richard Smith Solution Architect – Services Client Solutions Microsoft Corporation

  2. Session Objectives and Takeaways • Session Objective(s): • Evaluate the requirements for Office deployment and position them against image engineering and deployment requirements • Determine how to integrate Office into the image engineering lab and create an automated consistent master image development process • Determine how to integrate Office into the deployment process and add dynamic changes to the master image at deployment time • Key Takeaway • Multiple deployment options for Office • Current recommended practice deployment techniques

  3. The Managed Deployment Solution Layered on to the master image Part of the master image

  4. Office 2010 Setup Controller • Multi-Product Support • Multi-Language Support • Setup.exe • x86 or x64 • One Setup.exe for all products and editions • Applies updates automatically • Admin setup is no longer a requirement • Multiple .msi files • An .msi file for each Office product • Additional Products and Suites can be copied to the installation share • Multi-language support • Languages added dynamically • Core components are language neutral • Additional language packs can be copied to the installation share • Built in customization • Setup starts the customization tool • Binds .MSI Files Together • Direct access to .msi files is not supported • Built in Customization Tools • Setup.exe /admin • Setup.exe

  5. Office 2010 Installation Source • Installation Source is a file share. • No Setup /A as in Office 2003 for preparing the share • Core components are language neutral. • Additional Office suites, products, and language packs can be added by a simple copy of the source files to the share. • Language components are identified as XX-YY (for example, en-us). • Updates are .msp files and will be applied automatically during setup, if they are in the Updates folder.

  6. Office 2010 Installation – Manual Installation

  7. Customizing Office Installations Config.xml Office Customization Tool

  8. Confix.xml Configuration file • XML syntax - Notepad is usually used for editing • Can implement additional language packs • Used for • Installation • Modification • Uninstallation • Pre-staging LIS • Must be specified in the setup.exe command line • Cannot modify application settings

  9. Office 2010 Installation - Basic Automation Techniques

  10. Office Customization Tool (OCT) Setup and Administration • Launched using Setup.exe • Graphical user interface • Used for configuring settings and options across multiple Office products • Results in an .msp configuration file • .mspfiles can simply be dropped to the Updates folder to apply common settings • Create separate .msp files for certain users or groups • Ability to add or remove additional keys and registry values • Configures shortcuts • Cannot be used to • Add additional languages • Chain the Office installation • Pre-stage LIS * 64-Bit installations need the approparite OCT from the installation source

  11. Comparison of Configuration Methods

  12. Office 2010 Installation – Using .MSP and Config.xml files

  13. Deploying Office through Image Engineering Deployment Mechanism Image Requirements Apps (inc. Office) Branding Approved Image Design Security Standards Group Policy Design

  14. Image Engineering – Office Questions • Office version – VL or ProPlus Sub (Office 365) • Install Office fully in the Image (all users get the same) • Install Office during Deployment from a Package • Package can be adapted as required • Data transfer issues in a mass deployment (1.2Gb package for SP1) • Install Office as a LIS in the image • Office is then installed during deployment from the LIS • Custom config.xml and .MSP files can be copied to the machine before installation starts • Saves transferring the Office package across the network

  15. Master Image Design

  16. Office 2010 Installation – Adding the LIS to an Image

  17. Office 2010 (LIS) • LIS is a mandatory requirement for the Office setup. • LIS contains all Office products. • LIS is stored in a secured directory on the local hard drive (MSOCACHE). • LIS can be pre-staged. • LIS avoids “Insert-Disk dialogs” when additional features will be enabled.

  18. Deploying from the LIS LIS cached in Image

  19. Office 2010 Installation – Installing from the LIS

  20. Office 2010 Volume LicenseDeployment Options

  21. Office 2010 Pro Plus Sub (Office 365)Deployment Options

  22. Office 2010 Installation - Installing Office ProPlus Sub

  23. Summary • Use Config.xml to configure language requirements • Use Config.xml and .MSP files together for maximum flexibility • Deploy Office • Completely in the Image (full install during image engineering) • LIS in the Image (LIS Install during image engineering) • From a package during deployment (full install during deployment) • Use similar techniques to deploy Office ProPlus Sub • Add additional requirements for Office ProPlus Sub (Online Sign-in Assistant, Lync, Updates)

  24. Related Content • OSP303: Supporting Microsoft Office in an Enterprise Environment • OSP224: Microsoft Office 365 Management and Deployment • OSP305: Modern Compatibility Process to Accelerate Office Deployment Find Me Later At…Ask the Experts (tonight – Hall 7)

  25. Track Resources Office 2010 / Office 2007 - Pre-cache the local installation source. Office 2010 / Office 2007 - Run Setup from the local installation source for Office. Office 2010 / Office 2007 - Deploy Office to users who are not administrators. Office 2010- Deploy Office with limited network capacity.Office 2010 / Office 2007 - Deploy Office by running Setup from a network share. Office 2010 / Office 2007 - Deploy Office by using Configuration Manager 2007/2012Office 2010 / Office 2007 - Deploy Office by using Group Policy startup scripts. Office 2010- Deploy Office by using Microsoft Application Virtualization.

  26. Resources Learning TechNet • Connect. Share. Discuss. • Microsoft Certification & Training Resources http://europe.msteched.com www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers • http://microsoft.com/technet http://microsoft.com/msdn

  27. Evaluations Submit your evals online http://europe.msteched.com/sessions

  28. © 2012 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.

More Related