Microsoft Office 365 ProPlus DeploymentBruce Weaver and Todd FurstTechnical guys

Agenda

Why are we doing this?

What are we talking about?

What’s similar to what you know?

What’s different from what you know?

Let’s see it in action!

Parting thoughts…

Why are we doing this?

Why Office 365 ProPlus?• Enables user-based licensing of Office for up to

5 devices per user• Delivers Office as a service – we want to help

get you out of upgrade jail• It’s what you’re licensed for!

What are we talking about?

Office 365 ProPlusDeploy Office quickly without giving up control

Automated softwaredistribution support

Group Policy and Telemetry support

5 installs per user on PCs or Macs

Personalized settingsroam between devices

Manageable background updates

Familiar & full Office applicationslocally installed, available offline

Side-by-Side installswith older versions

What’s similar to/different from what you know?

Click-to-Run (C2R) MSI

Streaming Installation

Slipstreamed Servicing

User-based Licensing

Retail Activation

SKU Level Application

Suites

Windows 7 or newer

Windows Integration

App-to-App Integration

Add-in Extensibility

Group Policy Support

Automated Deployment

Telemetry

Supports Offline Use

On premises or cloud storage

Classic Installation

Layered Servicing

Volume Licensing

Volume Activation

Selective Application

Installation

Tale of Two Package Types

Office 365 ProPlus is C2R Office 2013 Professional Plus is MSI

MSI-based installation

Everything carried over from Office 2010MAK, KMS, and AD-based activation

Required for RDS, WTG, shared computers, and closed network scenarios

Click-to-Run installation

Built on App-V foundation

Office subscription-based activation

May be used on physical or virtual machines

Tale of Two Package Types

What’s similar to/different from what you know?

Streaming installation allows Office apps to run almost instantly and features load based on usage

Use Office 365 both online and offline

Works with existing Office add-ins, customizations, macros, and legacy Office file formats

Unobtrusive background updates with IT control

Support for update testing and push deployment

Office apps are streamed from Office 365 or on premises tools

Office Side-by-Side means that you do not need to uninstall previous versions of Office in order to use the new Office

Why Click-to-Run?

A picture is worth a bunch of words…

Let’s see it in action

Demo: I’m a user and need Office fast

Keep older versions of Office installed alongside new Office

Be proactive with compatibility risks—use as a fall back

Not recommended as a permanent configuration

virtual file system

Side-by-SideHelps Transition

Deploy Office 365 ProPlus – bring in the IT Pros!

(A) Directly from Office 365

(B) From an on-premises location

(A) and (B) both use Click-to-Run

Group Policy Configuration XMLOffice Customization Tool

Office 365 Click-to-Run

Traditional MSI-based Office installation

Streamlining the Deployment Tool Belt

Office Deployment Tool

Office Deployment Tool Syntax

• {location of tool}\setup.exe /{mode} {location of configuration.xml}

• \\server01\Office\setup.exe /download \\server01\office\configuration.xml

Mode Purpose

download Copy product and language source files down to an on-premises location

configure Install and configure products and languages (remove also)

packager (optional) Create a package for Microsoft Application Virtualization (App-V) 5.0

Configuration.xml Example• <Configuration>

<Add SourcePath="\\Server01\Office\"OfficeClientEdition="32"> <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> </Product> </Add>

<Updates Enabled="TRUE" UpdatePath="\\Server01\Office\" /> <Display Level="None" AcceptEULA="TRUE" /> <Logging Name="OfficeSetup.txt" Path="%temp%" />

• </Configuration>

Demo: I’m an IT Pro and need to provide Office to users

1. Add users to Office 365 tenant.2. Download Office Deployment Tool

(setup).3. Use setup to download C2R

packages4. Customize configuration XML.5. Add C2R packages to software

distribution infrastructure.6. Deploy C2R packages with setup

and configuration XML.7. Layer on add-ins and

customizations.

† As applicable

End Users’ PCs

Org ID†

AD†SW Dist.

Click-to-Run Managed Deployment

Optional add-ins,dependent apps,Office files, etc.

Option Description Sample SyntaxAdd Parent control to determine source, architecture,

product and languages to download. From CDN: <Add OfficeClientEdition="32" > <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> </Product></Add>From local network:<Add SourcePath="\\Server\Share\Office\" Version=”15.0.4128.1014” OfficeClientEdition="32" > <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> </Product></Add>

Product The targeted products to download within the <Add> command. Multiple products may be nested under the <Add> control and multiple languages may be nested under the <Product> control.

Office 365 ProPlus<Product ID="O365ProPlusRetail"> <Language ID="en-us" /></Product><Product ID="VisioProRetail"> <Language ID=”ja-jp" /></Product><Product ID="ProjectProRetail"> <Language ID=”es-es" /></Product>

SourcePath Location where the Office is downloaded to. If unspecified, the downloaded content will be saved to the folder where the setup.exe is located.

<Add SourcePath="\\Server\Share\Office\" OfficeClientEdition="32" ><Add SourcePath="%Applications%\Office\" OfficeClientEdition="32" ><Add SourcePath="C:\Source\Office\" OfficeClientEdition="32" ><Add SourcePath="http://source. contoso.com/Office" OfficeClientEdition="32" >

OfficeClientEdition Determines the architecture of the product to download, 32 or 64 bit. Note: 32-bit is still the recommended architecture for new Office versions. Cross-architecture installations are not permitted; if a 32-bit Office version is already installed on a system, the 64-bit Click-to-Run package will not install and vice versa.

<Add SourcePath="\\Server\Share\Office\" OfficeClientEdition="32" > Or:OfficeClientEdition="32"OfficeClientEdition="64"

Language Language determines the language DAT files to be downloaded with the Click-to-Run package.

<Language ID=”ja-jp" /><Language ID=”es-es" /><Language ID="en-us" /><Language ID="fr-fr" />

Version Version is used as part of the <Add> control and specifies the version to be downloaded. If version is not specified, setup.exe will download the latest build. Available version numbers will be posted to KB article in the future.

<Add SourcePath="\\Server\Share\Office\" Version=”15.0.4128.1014” OfficeClientEdition="32" > 

download XML

XML Controls to Download

XML Controls to Install

Option Description Sample SyntaxAdd Parent control to determine source, architecture, product

and languages to download. From local folder: <Add SourcePath=”%deployroot%\applications\Office365” OfficeClientEdition="32" > <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> </Product></Add>From local network:<Add SourcePath="\\Server\Share\Office\" OfficeClientEdition="32" > <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> </Product></Add>

Remove Used to uninstall Office products. <Configuration><Remove> <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> </Product> <Product ID="VisioProRetail"> <Language ID="en-us" /> </Product> </Remove></Configuration> <Remove All=”TRUE”>

Product Multiple products may be nested under the <Add> control and multiple languages may be nested under the <Product> control.

Office 365 ProPlus<Product ID="O365ProPlusRetail"> <Language ID="en-us" /></Product><Product ID="VisioProRetail"> <Language ID=”ja-jp" /></Product><Product ID="ProjectProRetail"> <Language ID=”es-es" /></Product>

SourcePath Location where the Office is installed from. If SourcePath is unspecified, setup will first look for installation source in the local folder and if not present it will look to the CDN source.

<Add SourcePath="\\Server\Share\Office\" OfficeClientEdition="32" ><Add SourcePath="%Applications%\Office\" OfficeClientEdition="32" ><Add SourcePath="C:\Source\Office\" OfficeClientEdition="32" ><Add SourcePath="http://source. contoso.com/Office" OfficeClientEdition="32" >

install XML

Option Description Sample SyntaxOfficeClientEdition Determines the architecture of the product to

download, 32 or 64 bit. Note: 32-bit is still the recommended architecture for new Office versions. Cross-architecture installations are not permitted; if a 32-bit Office version is already installed on a system, the 64-bit Click-to-Run package will not install and vice versa.

<Add SourcePath="\\Server\Share\Office\" OfficeClientEdition="32" > Or:OfficeClientEdition="32"OfficeClientEdition="64"

Language Language determines the language DAT files to be downloaded with the Click-to-Run package.

<Language ID=”ja-jp" /><Language ID=”es-es" /><Language ID="en-us" /><Language ID="fr-fr" />

Updates Configures automatic updating behavior. Updates may be either from the public Office 365 service, local location, local file share or private http:// site.

To use a local file share:<Updates Enabled="TRUE" UpdatePath="\\Server\Share\Office\" />To use the CDN: <Updates Enabled="TRUE” />To disable:<Updates Enabled="False" />

Display Set to determine the installation display experience. Level options are None and Full. You can also accept the end user license agreement (EULA) on behalf of your users with the AcceptEULA command.

<Display Level="None" AcceptEULA="TRUE" /><Display Level="Full" AcceptEULA="FALSE" />

Logging The logging control lets you determine he log name and path where logs are written to.

<Logging Name="OfficeSetup.txt" Path="%temp%" /><Logging Name="OfficeSetup.txt" Path="%deployroot%\smsosdlogs\" />

Property FORCEAPPSHUTDOWN

This command forces an install, uninstall or update. Office Click-to-Run updating is designed to be a background experience and updates are applied when a user closes and reopens the Office program. This property in the configuration file will force the operation without prompting the user, so there is some chance of data loss when programs are closed.

<Property Name="FORCEAPPSHUTDOWN" VALUE="1" />

ForceDowngrade This element is used when the installed version number is greater than the target version number. This would be used in roll back scenarios if you detect an issue that requires you to roll back to a previous version.

<Add SourcePath="\\Server\Share\Office\" Version=”15.0.4128.1014” OfficeClientEdition="32" ForceDowngrade=”True”> <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> </Product></Add>uninstall XML

XML Controls to Install, cont.

http://technet.microsoft.com/en-us/library/jj219426.aspx

Let’s talk about updates

Automatic from Cloud

Default option

Updates come from Microsoft Office 365 service when available

Update service is a scheduled task that runs daily

Automatic from Network

Runs daily

Set to look on premise at defined network location (UNC or HTTP)

Admin copies in source, update service checks for newer versions to location

Rerun Setup in Software Dist.

Useful in distributed environments with enterprise software distribution (ESD)

Update mode is disabled during setup (client never checks for updates)

ESD distributes Office and reruns Setup for each build update (still only loading deltas)

Local pre-caching of install files not recommended due to bandwidth requirements—install from distribution or management point

Updating Options

Update Settings in Configuration.xml

Method of distributing updates Setting to use

Automatically from Office 365 <Updates Enabled="TRUE" />

Or

<Updates Enabled="TRUE" UpdatePath="" />

Automatically from an on-premises location

<Updates Enabled="TRUE" UpdatePath="\\Server01\Office\" />

By rerunning Setup.exe <Updates Enabled="FALSE" />

Demo: I’m an IT Pro and want to leverage existing tools to provide Office to users

Summary Deliver Office as a service

Deploy Office quickly with Side-by-Side installs

Install on up to 5 devices as part of user-based subscription

All the control you need Using the Office Deployment

Tool to deploy Office fast Leverage existing tools and

process if required

MSI is out, Click-2-Run is in for Office 365 ProPlus subscribers

© 2013 Microsoft. All rights reserved. Microsoft, Windows 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.

Check out the Season 1 Archive – it’s 100% Click-to-Run

www.microsoft.com/garage

For more information…• Office Deployment Tool download

• Office 365 ProPlus on TechNet

• Content roadmap for deploying Office 365 ProPlus

• Office IT Pro blog

• Office for IT pros TechCenter

• Office 365 ProPlus Deployment for IT Pros on Microsoft Virtual Academy

• Office 365 ProPlus on Garage Series YouTube playlist