Office Deployment – Notes from the Field

Richard SmithSolution Architect – Services Client SolutionsMicrosoft Corporation

OSP340

Session Objectives and Takeaways

Session Objective(s): Evaluate the requirements for Office deployment and position them against image engineering and deployment requirementsDetermine how to integrate Office into the image engineering lab and create an automated consistent master image development processDetermine 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 OfficeCurrent recommended practice deployment techniques

operating system master image

hardware-based software & drivers

security configuration

enterprise applications

role-based applications

individual applications

user settings

Enterprise Desktop Stack

image engineering

security management

user profile management

hardware lifecycle

imag

e de

ploym

ent

applicationlifecycle

The Managed Deployment Solution

Part of the master image

Layered on to the master image

Office 2010 Setup ControllerSetup.exex86 or x64One Setup.exe for all products and editionsApplies updates automaticallyAdmin setup is no longer a requirement

Multiple .msi filesAn .msi file for each Office productAdditional Products and Suites can be copied to the installation share

Multi-language supportLanguages added dynamicallyCore components are language neutralAdditional language packs can be copied to the installation share

Built in customization Setup starts the customization tool

Setup.exe

Binds .MSI Files Together

•Direct access to .msi files is not supported

Multi-Product Support

Multi-Language Support

Built in Customization

Tools•Setup.exe /admin

Office 2010 Installation Source

Installation Source is a file share.No Setup /A as in Office 2003 for preparing the shareCore 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.

Office 2010 Installation – Manual Installation

Customizing Office Installations

Office Customization

ToolConfig.xml

Specify the path of the network installation point.

Select the products to install.

Customize Setup options, including logging and the location of the Setup customization file and software updates.

Specify installation options, such as user and company name.

Copy the LIS to the user's computer without installing Office.

Add or remove languages from the installation.

Sections covered by OCT (extracts):• Setup

• Installation location and name• Additional network sources• Licensing and UI

• Features• User settings• Feature insallation state

• Additional Content• Add files• Remove files

• Outlook• Outlook profile

Confix.xml Configuration file

XML syntax - Notepad is usually used for editingCan implement additional language packsUsed for

InstallationModificationUninstallationPre-staging LIS

Must be specified in the setup.exe command lineCannot modify application settings

Office 2010 Installation - Basic Automation Techniques

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 .msp files 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

Comparison of Configuration Methods

Config.xml Setup Customization File (.msp)

Specify the path to the network installation point X X

Select which product or language to install X X

Specify additional network distribution sources X X

Change the installation state of Office product features X

Change where Setup looks for the setup customization file and software updates X

Copy the local installation source to the user's computer without installing Office X

Chain Office installations X X

Make last-minute or one-off customizations X

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

Deploying Office through Image Engineering

Deployment Mechanism

Apps (inc.

Office)

Branding

Security Standards

Approved Image Design

Image Requirements

Group PolicyDesign

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 requiredData 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 LISCustom config.xml and .MSP files can be copied to the machine before installation startsSaves transferring the Office package across the network

Master Image DesignNew Client

CO

RE

IM

AGE

DY

NA

MIC

A

DJ

US

TM

EN

TS

AP

PL

ICA

TIO

N

DE

LIV

ER

Y

WINDOWS 7 ENTERPRISE OPERATING SYSTEM

BASE HARDWARE SUPPORT

FIREWALL AND AV CLIENT

MICROSOFT OFFICE 2010 FULL INSTALL OR LIS INSTALL

SYSTEM CENTER ADVANCED CLIENT (Added by ConfigMgr 2007/2012 at deployment time)

DRIVER INJECTION

LANGUAGE INJECTION

BUSINESS SPECIFIC POLICY AND SETTINGS – ACTIVE DIRECTORY GROUP POLICY

FOUNDATION LAYER APPLICATIONS (e.g. Acrobat Reader, WinZip, Office Install (from LIS), QuickTime)

CORE UTILITIES (e.g. Flash Viewer, Shockwave Player, Visio Viewer)

BUSINESS LAYER APPLICATIONS (e.g. SAP GUI, Business Unit Dependant Applications)

END USER LAYER APPLICATIONS (e.g. Exception Targetting of Applications to Individual Users)

LAYER 1

LAYER 2

LAYER 3

LAYER 4

Office 2010 Installation – Adding the LIS to an Image

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.

Deploying from the LIS

LIS cached in Image

Configuration Manager Packages

Packages are assigned to the deployment task sequence

2. Install PackageRuns setup.exe from the local

LIS using the /config and /adminfile switches to specify

the setup files

1. Setup PackageCopies a config.xml and .MSP

file to the LIS

Office 2010 Installation – Installing from the LIS

Office 2010 Volume LicenseDeployment Options

Office 2010 Pro Plus Sub (Office 365)Deployment Options

Office 2010 Installation - Installing Office ProPlus Sub

SummaryUse Config.xml to configure language requirementsUse Config.xml and .MSP files together for maximum flexibilityDeploy 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 SubAdd additional requirements for Office ProPlus Sub (Online Sign-in Assistant, Lync, Updates)

Related Content

Find Me Later At…Ask the Experts (tonight – Hall 7)

OSP303: Supporting Microsoft Office in an Enterprise Environment

OSP224: Microsoft Office 365 Management and Deployment

OSP305: Modern Compatibility Process to Accelerate Office Deployment

Track ResourcesOffice 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.

Resources

Connect. Share. Discuss.

http://europe.msteched.com

Learning

Microsoft Certification & Training Resources

www.microsoft.com/learning

TechNet

Resources for IT Professionals

http://microsoft.com/technet

Resources for Developers

http://microsoft.com/msdn

Evaluations

http://europe.msteched.com/sessions

Submit your evals online

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