Jan Ketil Skanke

Microsoft Office 365 ProPlus: Deployment and Management

Adoption challengesBased on user feedback

Maintain critical third-party apps after upgrades

Avoid complex and expensive deployment cycles

Need more time to test

It’s all about management

Better network traffic management

Enhanced distribution management

Flexible update management

Simplified activation management

Current Branch for BusinessOffice deferred updatesdeferred feature updatesChallenge

Frequent updates put third-party apps at risk and truncate planning and testing.

SolutionOffice deferred updates consolidate and deliver features three times a year.Security updates are still delivered continuously.

ValidationThree-tiered approach ensures market-driven quality:• Early adopters• Current branch• Current branch for Business

Current Branch Current Branch for Business

Time

100’s of thousands

100’sof millions

10’s of millions Build vetted through market

adoption and feedback

Enables IT and ISVs to have early access and validate builds against LOB apps

Ensures insight into upcoming features

Builds deployed using existing software deployment solutions

Your Users

Early Adopters

Market driven quality

Current BranchCustomer experienceFeatures are released to broad marketCustomers are up to date with features as they are released after broad early adopter validationOpportunity for enterprises to test and validate new featuresSecurity updates and fixes are delivered regularly

Timejan feb mar apr

may

jun jul aug

sep

oct nov

dec

Dates are for illustration purposes only

Features are delivered 3 time/yearSecurity updates are delivered regularly for 4 monthsBusiness customers on auto-update will be moved to a new branch Business customers can wait to receive feature updates for an additional 4 months, providing access to two branchesValidation builds are stabilized and available for testing 4 months prior to declaring as deferred branch

Dates are for illustration purposes only

Timejan feb mar apr

may

jun jul aug

sep

oct nov

dec

Current Branch for BusinessCustomer experience

DB1

DB2

DB3

Feature update

Extended support

Security update

Office deferred updatesAligning Office and Windows 10

Current Branch Current Branch for BusinessFeatures One branch in market at a time

Monthly features, bug fixes, and security patchesTwo branches available (subsequent branch overlaps preceding branch)Regular security updates

Availability Windows 10: 2-3 times a yearOffice 365: Monthly

Windows 10: 2-3 times a yearOffice 365: 3 times a year, consistent dates

Serviceability

Windows 10: Approximately 4 monthsOffice 365: 12 months

Windows 10: 8 monthsOffice 365: 4-8 months (first 4 months, then another 4 months)

Deployment technology

Windows 10: WSUS, Windows Update, and Windows Update for BusinessOffice 365: SCCM, Microsoft Intune, third-party software deployment tools

Windows 10: WSUS, Windows Update for BusinessOffice 365: SCCM, Microsoft Intune, third-party software deployment tools

Office deferred updatesOffice as a service lifecycle

Current branch Current Branch for Business

Scenarios Sales force, BYOD, test systemsAnyone not using mission-critical systems Anyone not using add-ins

Knowledge workers, sales force, road warriorsAnyone using add-ins and requiring a slightly slower paceAnyone who should be up-to-date, but not necessarily in the forefront of features

Features Available monthlyRegular security updates and bug fixesOne branch in market at a timeConsumed through Office CDN or existing software distribution method

Available 3 times per yearRegular security updates and bug fixesTwo branches available simultaneouslyConsumed through Office CDN or existing software distribution method

Serviceability

30 daysBreaking changes addressed; new build deployed

4 months mainstream support, 4 months extended supportSecurity-only updates

Support 12 months 8 months

Deploy the productMany optionsLocal installationNetwork installationEnterprise software distributionWindows imageApplication virtualizationRemote Desktop Services

Deploying at a glanceInstallation basics

Multiple languagesOffice Deployment ToolMicrosoft IntuneSCCM

Pre-installed Windows imageMicrosoft Deployment Toolkit

Self-installation

Managed deployment

Already on device

Update locationsLocal drives and distribution points

Local drive or desktop Distribution point or network share

Office 365 Content Delivery Network

From “here” From “there” From “anywhere”

Office as a service lifecycleDeployment scenariosDesktop

SCCM application modelLocal cacheUser-targeted

Distribution point or network shareStreaming installationBinary delta compression

Content Delivery NetworkStreaming installationUsers on the go

Deployment optionsFrom “here”

Entire source deployedNo SourcePath attribute defined

Office 365 Deployment Tool (setup.exe)

Deployment optionsFrom “there”

Separates setup.exe (1 MB) from source files (1 GB)Defines SourcePath attributeAllows source files to be updated independently

Office 365 Deployment Tool (setup.exe)

Deployment optionsFrom “anywhere”

“Outsources” distribution infrastructureDoesn’t define SourcePath attributeAlways deploys latest build

Office 365 Deployment Tool (setup.exe)

Deployment optionsGetting ready

Update rulesDownload from distribution pointRun from distribution point

Detection rules for SCCMOffice 365Office 365 ProPlus

Application modelCreating an application

Content location Install/uninstall program settingsDetection ruleInstallation behaviorTask sequencer

Create Deployment Type Wizard

Add name, publisher, software versionSelect languageConsider services needed for select groups

Manually specify application information

Application modelPremade applications

“SharedComputerLicensing” Value attribute set to “1”Deployment to all users or a subsetTask sequencer

Shared computer activation (SCA)

Same core source package

Three deployment types

Packages and programsUpdates in Office 365 ProPlusAutomatic updates

Turned on by default

Office 365 ProPlus updates packageExecutable file with specific parametersSetting to update to specific version

Deployment WizardTargeted to particular usersValidation with push updates

Flexible update managementOffice deferred updatesChallenge

Frequent updates put third-party apps at risk and truncate planning and testing.

SolutionOffice deferred updates consolidate and deliver features three times a year.Security updates are still delivered continuously.

ValidationThree-tiered rollout ensures market-driven quality:• Early adopters• Current branch• Deferred branch

Enhanced distribution managementBetter integration with SCCMChallenge

Use existing tools to consistently deploy and manage updates.

SolutionBetter integration with SCCM 2016 enables powerful distribution features:• Use of application model• Support for distribution points• Support for WSUS notifications

Work is ongoing for integration with SCCM 2012.SCCM 2007 will not be supported.

MSI vs. Click-to-RunExactly the same deployment options

Deployment method MSI Click-to-Run

Local installation source Yes Yes

Network installation point Yes Yes

Group Policy computer startup script Yes Yes

System Center Configuration Manager Yes Yes

Microsoft Intune Yes Yes

Remote Desktop Services Yes YesMicrosoft Application Virtualization (App-V) 5.0 Service Pack 2 Yes Yes

Microsoft Deployment Toolkit (MDT) 2012 Yes Yes

Summary

Office 365 ProPlus can be deployed through a self-service or managed installation.

With flexible deployment options, users can get updates from a local drive, a distribution point/network share, or the cloud.

Update packages and programs allow administrators to simplify the update process while maintaining control.

Office deferred updates capture ongoing user feedback and lead to market-driven quality.Better SCCM integration means more robust distribution management.