Office 365 ProPlusManaging Updates

Office 365 ProPlus Deployment Track

Time TrackDay 1: 2.00pm – 2:45pm

Introduction to Office 365 ProPlusLAB: Install and configure AADSync

Day 1: 3:30pm – 4:45pm

Planning & Deployment - Part 1LAB: ODT & Shared computer activation

Day 1: 4:45pm – 6:30pm

Ask the Experts Reception

Day 2: 9:30am – 10:45am

Planning & Deployment - Part 2LAB: Deploy Office using SCCM

Day 2: 1:15pm – 2:30pm

Managing UpdatesLAB: Update Office through Group Policy

Day 2: 2:45pm – 4:00pm

Office Telemetry and CompatibilityLAB: Using Telemetry Dashboard

Day 2: 4:15pm – 5:30pm

Troubleshooting Installations & Updates

Session AgendaOffice Servicing Overview

Managing Office Updates

Introduction to Telemetry

Builds, rather than updates

Provided monthly. Contains security, non-security changes.

Cumulative…At most one update away from evergreen

Monthly, cumulative builds

Calculated deltas Flexible options for management,

control

Enables agility

Office 365 ProPlus Servicing Overview

Background updating

Deltas are calculated and downloaded in background

Several options to provide IT controls

Take control of change

Manage change via small ripples, rather than large, disruptive waves

Consistency enables process automation

Reduces time to get new features to user

MICROSOFT CONFIDENT IAL – INTERNAL ONLY

Update Schedule Task• Runs after user login and around 3am (Sunday, Tuesday, Thursday) • Task can be configured to check the CDN or local source• Can be disabled

User Initiated• Update Now in the Account section

under the File Menu• Requires admin rights

Command-line Update• %programfiles%\Microsoft Office 15\Client[x86|x64]\OfficeC2RClient.exe /update

user [updatetoversion=“15.0.4569.1508”]

Office Update Triggers

MICROSOFT CONFIDENT IAL – INTERNAL ONLY

Phases of Update

Update Apply• Requires applications to be

closed• Will apply on reboot• User interaction is possible

Update Download• Binary delta

compression

Configuring Updates at install time Using the Office Deployment Tool

<Configuration> <Add SourcePath="\\server\share" OfficeClientEdition="32">

<Product ID="O365ProPlusRetail"> <Language ID="en-us" />

</Product> </Add>

<Updates Enabled="TRUE" UpdatePath="\\Server\share\" TargetVersion="15.1.2.3" Deadline=“12/16/2014 18:30"/>

</Configuration>

Defaults – updates are checked for on a daily basis on the Microsoft CDN

Use <Update> tag to turn on or off updates

Options include: Update location, Version and deadline

Computer Configuration\Administrative Templates\

Microsoft Office 2013\ Updates

Enable Automatic UpdatesHide option to enable or disable updatesUpdate VersionUpdate DeadlineUpdate PathDisable Update notifications

Configuring Updates via Group Policy

Organizational units Security group filtering

Loop-back processing Group Policy Preferences

Computer name

LDAP Queries

DNS Suffix

AD site

IP address range

Group Policy enables you to utilize…

How Automatic Updates Work

Scheduled Task

triggered

Do nothing

No

No Ready to

apply?

New build

available?

Most Common Path

Apply Update (Scenario 1 of 3)

Scheduled Task

triggered

Download delta

Update Office

Yes

Yes

No

No Office process

es running?

Ready to

apply?

New build

available?

How Automatic Updates Work

Apply Update (Scenario 2 of 3)

Scheduled Task

triggered

3 or 6 days have

passed?

Download delta

Do nothing

Yes

Yes Yes

No

No Office process

es running?

Ready to

apply?

New build

available?

How Automatic Updates Work

Apply Update (Scenario 3 of 3)

Scheduled Task

triggered

3 or 6 days have

passed?

Prompt user via Toast or

Business Bar

Download delta

Update Office

Open Office apps

Yes

Yes Yes Yes

Yes

Yes

No Office process

es running?

Ready to

apply?

User selects apply?

Select “Close

programs?”

New build

available?

How Automatic Updates Work

Scheduled Task

triggered

3 or 6 days have

passed?

Prompt user via Toast or

Business Bar

Download delta

Update Office

Do nothing

Open Office apps

Yes

Yes Yes Yes

No No No

No

No Yes

Yes

No Office process

es running?

Ready to

apply?

User selects apply?

Select “Close

programs?”

New build

available?

How Automatic Updates Work

DemoUpdating Office 365 ProPlus

Object Model & API Virtually static since Office 2010 (http://aka.ms/Kj6vya)Office App model is future direction……no planned changes to object model/APIs

Builds supported for 12 monthsConsistent with MSI/Service Pack lifecycle policyEnables validation of builds

Telemetry provides objective dataFacilitates a fact-based approach to manage risk

Helps manage change

Extensibility Model Build lifecycle

Manage Risk Manage change

Updates & Future Compatibility

Managing Office UpdatesCommon Questions

“How can I test/approve

updates?”

“How can I automate

update management

?”

“How can I back out,

if necessary

?”

“How can I determine if it worked?”

Managing UpdatesA sample plan

Goals

Process is automated

Builds are validated for 2 weeks

Backout is enabled

Opt-out is available

Validation Group

Production Group

Managing Updates – A sample plan

Option Details

1. Define & configure “pilot” group Determine who will validate new builds

Determine internal source(s) to contain

Office builds

Use Group Policy & global group filtering to

configure update source (eg, “\\server1\

Source1”) for testing group

(Optional) Configure to download from

cloud

Managing Updates – A sample plan

Option Details

Use Group Policy to configure update

source(s)

and/or

Define update source at install time using

the UpdatePath element

2. Define production update source

Managing Updates – A sample plan

Option Details

Run setup.exe /download

UpdateSource1.xml

SourcePath set to Pilot update location

Create a scheduled task to automate

download

Run task 2nd Friday of each month

3. Configure pilot update source

Contents of UpdateSource1.xml:

<Configuration> <Add SourcePath="\\Server1\Source1" OfficeClientEdition="32"> <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> </Product> </Add>

</Configuration>

Managing Updates – A sample plan

Option Details

4. Configure prod update source

Run setup.exe /download

UpdateSource2.xml

SourcePath set to Production update

location

Create a scheduled task to automate

download

Run task 4th Friday of every month

Disable this task to “opt-out” of distributing

to production

(Optional) Use software distribution tools to

schedule deployment to many locations

Managing Updates – A sample plan

Option Details

Backout plan - Use OfficeC2RClient.exe

(via Software distribution) to downgrade to

previous build

Enforcement – Use OfficeC2rClient.exe

(via Software distribution) to update to

current build

(Optional) Use Update deadline in Group

Policy to enforce 5. Manage outliers

Officec2rClient.exe /update user forceappshutdown=True displaylevel=False updatetoversion=15.1.2.3

Report detected issues & performance

Determine frequency of documents & solutions used

Manage add-ins & solutions

Track deployments

Office Telemetry Enables

Mining Data from the DashboardCustom Reports

ActiveX Macros Builds Scope

LABUpdate Office through Group Policy and SCCM

Import Administrative Templates

Create and Deploy GPOs

Final group discussion

OBJECTIVES