Microsoft Office 365 ProPlus Deployment for IT ProsCurtis Sawin, Technology Solutions Professional, MicrosoftDean Yamada, Senior Premier Field Engineer, Microsoft

About the PresentersCurtis SawinTechnology Solutions ProfessionalMicrosoft• Technology Solutions Professional specializing in Office Compatibility and

Office Deployment.

• Passionate about installation technology and dabbles in SQL Server Reporting Services development.

• Spoken at several Industry conferences, including MMS (Microsoft Management Summit), TechEd Europe, TechEd North America, SPC (Microsoft SharePoint Conference), and TechReady. He is a frequent contributor to the Office IT Pro Blog.

• Been with Microsoft since 2007.

http://www.linkedin.com/pub/curtis-sawin/0/99/935http://blogs.technet.com/b/office_resource_kit/

About the PresentersDean YamadaSenior Premier Field Engineer Microsoft

• Senior Premier Field Engineer, specializing in proactive deliveries of Office Premier Workshops and onsite Office Setup, Deployment and Migration advisories.

• Published in TechNet and authored various Office KB articles. He has also authored Office 2010: New Features and Advanced Topics and Office 2010: Troubleshooting & Supporting Premier Workshops, which has laid the groundwork for the current Office 2013 Premier Workshops.

• Been with Microsoft since 2005.

http://blogs.technet.com/b/office_sustained_engineering/

www.linkedin.com/pub/dean-yamada/1/6a5/734//

Course ModulesOffice 365 ProPlus Deployment for IT Pros

01 | Office 365 ProPlus Identity, Licensing & ActivationAn overview of the identity, licensing, and activation requirements of Office 365 ProPlus

02 | Office Telemetry OverviewIntroduces Office Telemetry, what Telemetry can do for you, and details all the Office Telemetry components

03 | Advanced Telemetry In-depth about the Office Telemetry infrastructure, capacity planning, performance, and the Telemetry

Dashboard Administration Tool

04 | Telemetry Custom Reporting Examples of how to mine data from the Office Telemetry database, and a behind-the-scenes look at custom reporting

05 | Office 365 ProPlus Click-to-Run Deployment OverviewIntroduces Microsoft’s new streaming and virtualization technology, Click-to-Run, which is used to deploy Office 365 ProPlus

06 | Click-to-Run Deep Dive Internals of how Click-to-Run works, and real world tips and tricks that will enable you to successfully deploy

Office 365 ProPlus

07 | Office and App-VOffice 365 ProPlus and App-V work together, discussing the advantages of this approach, and demonstrating how it works

Introduction to Click-to-Run

Agenda

Understanding Click-to-Run

Deployment

Updates

Understanding Click-to-Run

Will our files work in the new Office?

Will our customizations and add-ins work?

How do I handle consumerizationand people with multiple devices?

Common Deployment Blockers

Wouldn’t it be easier to do nothing?

Click-to-Run

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

Get Office Fast

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

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?

Office 2010 with App-V

2

Click-to-Run

1

32 4

5 6

7 8 9

4

23 1

5 6

7 9 8

EXE

Today’s application virtualization

Features loaded on demand

Local application integration

Side-by-Side version support

1

EXE

7

21 3

8 9

4 5 62

1

Rethinking Application Delivery

• Virtual File System Added in Initiator Context

• Runs until 10 percent progress

Virtual File System

• Streaming begins

• IntegratedOffice.exe process moves to System Context at 10 percent

Streaming Service • Office apps

may be launched at ≈ 15 percent

• Usually 2 minutes or less

Apps ready for use

• Office caching focuses on launched apps and features

• Total 3–5 minutes depending on connection

Caching • Final ≈ 10 percent installs add-ins, licensing, and so on

Finalizing

Anatomy of the Click-to-Run Installation Process

DemoClick-to-Run Installation and Side-by-Side Version Support

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

Reduced upfront testing with deployments in 3–5 months

3-9

Month

s

Office Compatibility

Inventory

Triage

Testing

Fixing

Deployment

Pilot

Desktop Imaging

Stand-alone Installs

1-2

Month

s

Training

User Acceptance Testing

User Interface Training

New Capability Training

1-2

Month

s

Light Testing

Office Coexistence Testing

1 M

onth

Click-to-Run Enterprise Office Deployment

Deployment

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.

Group Policy Configuration XMLOffice Customization Tool

Office 365 Click-to-Run

Traditional MSI-based Office installation

Streamlining the Deployment Tool Belt

MICROSOFT CONFIDENT IAL – INTERNAL ONLYMICROSOFT CONFIDENT IAL – INTERNAL ONLY

Office Deployment Tool

MICROSOFT CONFIDENT IAL – INTERNAL ONLYMICROSOFT CONFIDENT IAL – INTERNAL ONLY

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>

DemoOffice Deployment Tool for Click-to-Run

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

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" />

DemoOffice Deployment Tool for Click-to-RunPart II

Summary Simplify the Upgrade Experience

Deploy Office quickly with Side-by-Side installs

User subscription licensing

Streamlining the Deployment Timeline

Using the Office Deployment Tool to deploy Office fast

Click-to-Run Updates Slipstreamed updates in builds

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