1. Deploy and manage Office in complex scenarios with ConfigMgr
Microsoft Ignite 2016
10/4/ :27 AM
BRK3006
Deploy and manage Office in complex scenarios with ConfigMgr
Steve Osgood Martin Nothnagel
Consultant Senior Consultant
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Objectives Today Tomorrow and beyond … Adaptive deployment
Manage Office client
In complex scenarios
For 150K seats
Tomorrow and beyond …
Give you ideas
Give you the necessary building block
Give you all the scripts shown

3. Deploy Office

4. 10/4/ :27 AM
©Shell Information Technology International Ltd. (UK)
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

5. DEFINITIONS & CAUTIONARY NOTE
Reserves: Our use of the term “reserves” in this presentation means SEC proved oil and gas reserves. Resources: Our use of the term “resources” in this presentation includes quantities of oil and gas not yet classified as SEC proved oil and gas reserves. Resources are consistent with the Society of Petroleum Engineers 2P and 2C definitions. Organic: Our use of the term Organic includes SEC proved oil and gas reserves excluding changes resulting from acquisitions, divestments and year-average pricing impact. Shales: Our use of the term ‘shales’ refers to tight, shale and coal bed methane oil and gas acreage. The companies in which Royal Dutch Shell plc directly and indirectly owns investments are separate legal entities. In this presentation “Shell”, “Shell group” and “Royal Dutch Shell” are sometimes used for convenience where references are made to Royal Dutch Shell plc and its subsidiaries in general. Likewise, the words “we”, “us” and “our” are also used to refer to subsidiaries in general or to those who work for them. These expressions are also used where no useful purpose is served by identifying the particular company or companies. ‘‘Subsidiaries’’, “Shell subsidiaries” and “Shell companies” as used in this presentation refer to companies over which Royal Dutch Shell plc either directly or indirectly has control. Entities and unincorporated arrangements over which Shell has joint control are generally referred to “joint ventures” and “joint operations” respectively. Entities over which Shell has significant influence but neither control nor joint control are referred to as “associates”. The term “Shell interest” is used for convenience to indicate the direct and/or indirect ownership interest held by Shell in a venture, partnership or company, after exclusion of all third-party interest. This presentation contains forward-looking statements concerning the financial condition, results of operations and businesses of Royal Dutch Shell. All statements other than statements of historical fact are, or may be deemed to be, forward-looking statements. Forward-looking statements are statements of future expectations that are based on management’s current expectations and assumptions and involve known and unknown risks and uncertainties that could cause actual results, performance or events to differ materially from those expressed or implied in these statements. Forward-looking statements include, among other things, statements concerning the potential exposure of Royal Dutch Shell to market risks and statements expressing management’s expectations, beliefs, estimates, forecasts, projections and assumptions. These forward-looking statements are identified by their use of terms and phrases such as ‘‘anticipate’’, ‘‘believe’’, ‘‘could’’, ‘‘estimate’’, ‘‘expect’’, ‘‘goals’’, ‘‘intend’’, ‘‘may’’, ‘‘objectives’’, ‘‘outlook’’, ‘‘plan’’, ‘‘probably’’, ‘‘project’’, ‘‘risks’’, “schedule”, ‘‘seek’’, ‘‘should’’, ‘‘target’’, ‘‘will’’ and similar terms and phrases. There are a number of factors that could affect the future operations of Royal Dutch Shell and could cause those results to differ materially from those expressed in the forward-looking statements included in this presentation, including (without limitation): (a) price fluctuations in crude oil and natural gas; (b) changes in demand for Shell’s products; (c) currency fluctuations; (d) drilling and production results; (e) reserves estimates; (f) loss of market share and industry competition; (g) environmental and physical risks; (h) risks associated with the identification of suitable potential acquisition properties and targets, and successful negotiation and completion of such transactions; (i) the risk of doing business in developing countries and countries subject to international sanctions; (j) legislative, fiscal and regulatory developments including regulatory measures addressing climate change; (k) economic and financial market conditions in various countries and regions; (l) political risks, including the risks of expropriation and renegotiation of the terms of contracts with governmental entities, delays or advancements in the approval of projects and delays in the reimbursement for shared costs; and (m) changes in trading conditions. All forward-looking statements contained in this presentation are expressly qualified in their entirety by the cautionary statements contained or referred to in this section. Readers should not place undue reliance on forward-looking statements. Additional risk factors that may affect future results are contained in Royal Dutch Shell’s 20-F for the year ended December 31, 2015 (available at and ). These risk factors also expressly qualify all forward looking statements contained in this presentation and should be considered by the reader. Each forward-looking statement speaks only as of the date of this presentation, June 21, Neither Royal Dutch Shell plc nor any of its subsidiaries undertake any obligation to publicly update or revise any forward-looking statement as a result of new information, future events or other information. In light of these risks, results could differ materially from those stated, implied or inferred from the forward-looking statements contained in this presentation. We may have used certain terms, such as resources, in this presentation that United States Securities and Exchange Commission (SEC) strictly prohibits us from including in our filings with the SEC. U.S. Investors are urged to consider closely the disclosure in our Form 20-F, File No , available on the SEC website
©Shell Information Technology International Ltd. (UK)
April 2016

6. COMPANY PROFILE
Shell is an innovation-driven global group of energy and petrochemical companies
We are active in more than 70 countries
Worldwide, we employ 93,000 full-time employees
Our fuel retail network has around 43,000 service stations
On average, we produce 3 million barrels of oil equivalent per day (crude oil and natural gas).
In 2015, we:
generated earnings* of $3.8 billion
had $28.9 billion of capital investment
spent $1.1 billion on R&D
Royal Dutch Shell plc is a UK company, with its headquarters in the Netherlands
We are listed on the stock exchanges of Amsterdam, London and New York
*On a current cost of supplies basis attributable to Royal Dutch Shell plc shareholders
Source: 2015 Annual Report and Form 20-F
©Shell Information Technology International Ltd. (UK)
Copyright of Royal Dutch Shell plc

7. How and where we work Microsoft Ignite 2016 10/4/2017 11:27 AM
©Shell Information Technology International Ltd. (UK)
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

8. Environment at Shell Windows 7 x86/x64 150K+ seats Diverse hardware
Office 2010 x86
20+ languages
2,000+ Add-Ins/Apps
ConfigMgr 2012 R2
Sites with DPs
Satellite sites w/o

9. Scope of Work Dos Don‘ts Pre-stage content on clients
Support 20+ languages
Support multiple application sets
Don‘ts
But don‘t pre-stage 20 Languages Packs per client (~5 GB)
Juggle with 63 different configuration.xmls
Multiples this by the number of application sets

10. Action plan Pre-stage Office source files w/ en-us
Microsoft Ignite 2016
10/4/ :27 AM
Action plan
Pre-stage Office source files w/ en-us
Capture current state into config.xml
Remove previous Office client
1st pass: Install from local cmcache w/ en-us
2nd pass: Install additional language packs from DP
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

11. Demo Steve Osgood Microsoft Ignite 2016 10/4/2017 11:27 AM
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

12. Microsoft Ignite 2016 10/4/2017 11:27 AM
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

13. Manage Office

14. Striking the balance Agility Predictability Test LOB apps Readiness
Control
Feature adoption
Rollback
Security

15. ProPlus click-to-run servicing model (BRK2003)
10/4/ :27 AM
ProPlus click-to-run servicing model (BRK2003)
Deferred Channel (DC)
Every 4 months w/ rolled up Feature & Security Updates
Intended for Enterprise environments
First Release for Deferred Channel (FRDC)
Intended for validation before DC release
CC: ~50 FRDC: ~5, DC: ~145,000
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

16. Lifecycle of an Office client
Initial Deployment
Receive a security update
Switch to pilot group
Rollback
Leave Pilot
FRDC DC
V 2000
V 2001
V 1000
V 1001

17. Scope of Work Dos Don‘ts
Make multiple channels & languages available every month
Enable user to join standing pilot
Keep the client secure
Allow rollback
Enable users to leave standing pilot
Don‘ts
Manual processes
Juggling with build numbers every month
Invent new processes

18. Solution depends on environment
Configuration Manager 1602 or newer
You’re all set
Full support of handling C2R releases
Full integration into Software Update point
Configuration Manager 2012 or older / 3rd party
Newer builds are treated as applications/packages
No OOB-support for delta difference compression
Have to add logic to handle scenarios

19. Create automated solutions for
Microsoft Ignite 2016
10/4/ :27 AM
Create automated solutions for
Downloading multiple channels & languages
Create/Update the ConfigMgr package
Programs to Switch Channels/Rollback/Update
Distribute & deploy content
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

20. Demo Martin Nothnagel Microsoft Ignite 2016 10/4/2017 11:27 AM
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

21. Objectives Today Tomorrow and beyond … Adaptive deployment
Manage Office client
In complex scenarios
For 150K seats
Tomorrow and beyond …
Give you ideas
Give you the necessary building block
Give you all the scripts shown

22. Join the conversation on the Microsoft Tech Community
Microsoft Ignite 2016
10/4/ :27 AM
Join the conversation on the Microsoft Tech Community
BRK Deploy and manage Office in complex scenarios with Configuration Manager
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

23. Stop by the Office 365 ProPlus booth
Microsoft Ignite 2016
10/4/ :27 AM
Stop by the Office 365 ProPlus booth
Explore our Office IT Pro Heroes at aka.ms/officedeployment
Meet us and enter to win
Visit the Office 365 ProPlus booth in the Microsoft Showcase Productivity area
Engage with our Office 365 ProPlus engineering team and experts
Learn how our Preferred Practices can help you deploy Office 365 ProPlus
Enter to win a Surface Pro 4 kit
3 drawings
per day
Play the game
Waiting for the next session?
Play the IT Pro Hero game
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

24. Q&A

25. ProPlus Playlist – aka.ms/proplusatignite
Microsoft Ignite 2016
10/4/ :27 AM
ProPlus Playlist – aka.ms/proplusatignite
Code
Title
Speaker
Time
THR2018
Run Perpetual (C2R-P): what is it and how to implement it
Jalal Babool
9/26/ :10
BRK2003
Deploy Microsoft Office 2016 the right way
Chris Hopkins, Yoni Kirsh, Maurijn Donders, Armin Sturm, Sergio Dammroze, Carlos David Castillo,Steve Reay, Brian Canady
9/27/2016 9:00
THR3000
THR3000R
No Change-Run Microsoft Office on Citrix
Jon Maunder, Adam Pulsakowski
9/27/2016 9:50
9/29/ :20
THR2019 THR2019R
Gain new side-by-side support for Office 2013 family and Office 2016 family of click-to-run products
9/27/ :05
9/29/ :10
THR3003 THR3003R
Script Microsoft Office deployments with PowerShell
Russell Smith, Josh Gingras, Adam Stigall
9/27/ :50
9/29/ :35
BRK2005
Run Microsoft Office on virtual desktops
9/27/ :15
BRK2208
Understand Office Mac: what Windows admins need to know
Steven Nesbitt
9/28/ :45
BRK3006
Deploy and manage Office in complex scenarios with Configuration Manager
Martin Nothnagel, Steve Osgood, Steve Reay
9/27/ :30
BRK2006
Manage Microsoft Office apps on all of your devices
Brent Whichel, James Hammonds, Curtis Sawin
9/28/2016 9:00
THR2020
Deploy successfully: top 10 Office 365 ProPlus installation/activation tips
9/28/ :20
BRK2004
Grok the Office engineering roadmap for deployment and management
Amesh Mansukhani
9/28/ :15
BRK3002
Deploy Microsoft Office 365 Client using Configuration Manager
Amesh Mansukhani, Yoni Kirsh, Maurijn Donders, Doug Davis
9/29/ :30
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

26. Related Resources
Preferred Practices guide to Office 365 ProPlus deployment
Deploy, ramp-up on new services and onboard new users with Microsoft FastTrack:
Join the Microsoft Tech Community to collaborate, share and learn from the experts:

27. Appendix

28. Office IT Pro Deployment Scripts
Microsoft Ignite 2016
10/4/ :27 AM
Office IT Pro Deployment Scripts
Homepage
Sample wrapper scripts
Capture and/or generate configuration
Edit the configuration.xml
Remove older Office clients
Install Office 365 ProPlus
On-premises update management
Office Scripts Wiki
© 2016 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

29. Deployment wrapper script
Function Get-ScriptPath {
if ($PSScriptRoot) {
Return($PSScriptRoot)
} else {
Return((Get-Item -Path ".\").FullName) }
Function Remove-OldFiles {
write-host "`t Removing configuration.xml files left over from previous run ..."
if (Test-Path $ConfFilePath){
Remove-Item $ConfFilePath -Force
if (Test-Path $ConfLPFilePath){
Remove-Item $ConfLPFilePath -Force
Function Remove-AddLPs($ConfigXML) {
$xml = [xml](Get-Content $ConfigXML)
$ChildNodes = $xml.SelectNodes('//Language')
foreach ($child in $ChildNodes){
If (!($child.ID -eq "en-us")) {$Child.ParentNode.RemoveChild($Child)}
$XML.Save($ConfigXML) | Out-Null
Function Get-CountAddLP($ConfigXML) {
$i = -1 #Start with -1 because we only need additional LangPacks
$i += 1
Return $i
Function Generate-NewConfXml($ConfXML) {
write-host "Let's dynamically create the configuration.xml"
write-host "`t Capture installed apps into xml..."
Generate-ODTConfigurationXml -Languages AllInUseLanguages -targetFilePath $ConfXML
read-host
write-host "`t Remove Office-Version & SourcePath; Specify Channel=Deferred"
Set-ODTAdd -Version $NULL -SourcePath $NULL -Channel Deferred -targetFilePath $ConfXML | Out-Null
write-host "`t Set UI to None, show no EULA"
Set-ODTDisplay -Level None -AcceptEULA $true -targetFilePath $ConfXML | Out-Null
write-host "`t Enable updates"
Set-ODTUpdates -Enabled $true -Channel Deferred -TargetFilePath $ConfXML | Out-Null
write-host "`t Force Apps to be shut down, we don't take prisoners :)"
Set-ODTConfigProperties -ForceAppShutDown $true -TargetFilePath $ConfXML | Out-Null
write-host "`t Done."
write-host
#===============PREFACE==============================
#Let's roll
Write-Host "Starting up ..."
Write-Host "`t Setting variables ..."
$scriptPath = Get-ScriptPath
$ConfFilePath = "$scriptPath\configuration.xml"
$ConfLPFilePath = "$scriptPath\configurationLP.xml"
$LPCount = 0
#Import all required functions
write-host "`t Importing GitHub Scripts ..."
. $scriptPath\Generate-ODTConfigurationXML.ps1
. $scriptPath\Install-OfficeClickToRun.ps1
. $scriptPath\Remove-PreviousOfficeInstalls.ps1
. $scriptPath\SharedFunctions.ps1
. $scriptPath\Edit-OfficeConfigurationFile.ps1
#Start from scratch and remove files which might be left over from previous executions
Remove-OldFiles
#================CREATE BASE XML WITH EXCLUDED APPS=====================
#Query installed products, generate new configuration.xml and update it
#By default we exclude Access, Groove and Publisher
#Let's check if the user was entitled to have one of these and give them back to him
#Create configuration.xml from scratch
Generate-NewConfXml($ConfFilePath)
#Always exclude Groove
write-host "Always exclude legacy OneDrive client (Groove)..."
Set-ODTProductToAdd -ProductId "O365ProPlusRetail" -targetFilePath $ConfFilePath -ExcludeApps "Groove" | Out-Null
Write-host
#================ADDITIONAL LANGUAGES=====================
#Check for and handle additional languages
write-host "Check for and handle additional languages"
$LPCount = Get-CountAddLP($ConfFilePath)
write-host "`t Number of additional languages detected: $LPCount"
if ($LPCount -eq 0){
write-host "`t No action needed."
write-host "`t Copy configuration.xml for second install pass..."
Copy-Item -Path $ConfFilePath -Destination $ConfLPFilePath -Force
write-host "`t Update sourcepath"
#Dynamic-UpdateSource -targetFilePath $ConfFilePath (
Set-ODTAdd -Version $NULL -Channel Deferred -SourcePath "\\w12r2weurope\OfficeSource\DC" -targetfilepath $ConfLPFilePath| out-null
write-host "`t Strip languages from original configuration.xml"
Remove-AddLPs($ConfFilePath)
#================SHOW WHAT WE'VE GOT=====================
#Let's dump the configuration.xmls to console
Clear-host
write-host "Configuration.xml used for base install:"
Format-XML (Get-Content $ConfFilePath) -indent 4
Read-Host
if ($LPCount -gt 0){
write-host "Configuration.xml used for language pack install:"
Format-XML (Get-Content $ConfLPFilePath) -indent 4
write-host "Let'S roll and install"
Write-Host "`t Remove-PreviousOfficeInstalls"
write-host "`t First pass from local ConfigMgr cache"
write-host "`t`t Install-OfficeClickToRun -targetFilePath $ConfFilePath"
write-host "`t Second pass from DP or other source"
write-host "`t`t Install-OfficeClickToRun -targetFilePath $ConfLPFilePath"
# Configuration.xml file for Click-to-Run for Office 365 products reference.

30. Resources Preferred Practices guide to Office 365 ProPlus deployment
10/4/ :27 AM
Resources
Preferred Practices guide to Office 365 ProPlus deployment
Deploy, ramp-up on new services and onboard new users with Microsoft FastTrack:
Join the Microsoft Tech Community to collaborate, share and learn from the experts:
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

31. Deploy, ramp-up on new services and onboard new users with Microsoft FastTrack:

32. Join the Microsoft Tech Community to collaborate, share, and learn from the experts:

33. Please evaluate this session
10/4/ :27 AM
Please evaluate this session
Your feedback is important to us!
From your PC or Tablet visit MyIgnite at
From your phone download and use the Ignite Mobile App by scanning the QR code above or visiting
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

34. 10/4/ :27 AM
© 2014 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.