• 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/935 http://blogs.technet.com/b/office_resource_kit/
• 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.
www.linkedin.com/pub/dean-yamada/1/6a5/734//
http://blogs.technet.com/b/office_sustained_engineering/
Office 365 ProPlus Deployment for IT Pros
01 | Office 365 ProPlus Identity, Licensing & Activation
An overview of the identity, licensing, and activation requirements of Office 365 ProPlus
02 | Office Telemetry Overview
Introduces 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 Overview
Introduces 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-V
Office 365 ProPlus and App-V work together, discussing the advantages of this approach, and demonstrating how it works
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
consumerization
and people with
multiple devices?
Click-to-Run
Deploy Office quickly without giving up control
Click-to-Run (C2R)
Streaming Installation
Slipstreamed Servicing
MSI
Windows 7 or newer
Windows Integration
Classic Installation
App-to-App Integration
Add-in Extensibility
Layered Servicing
User-based Licensing
Group Policy Support
Volume Licensing
Retail Activation
Automated Deployment
Volume Activation
SKU Level Application Suites
Telemetry
Selective Application
Supports Offline Use
On premises or cloud storage
Office 365 ProPlus is C2R
Installation
Office 2013 Professional Plus is MSI
MSI-based installation
Everything carried over from Office 2010
MAK, 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
Office apps are
streamed from
Office 365 or
on premises
tools
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 Side-by-Side
means that you do
not need to
uninstall previous
versions of Office in
order to use the
new Office
Today’s application virtualization
Features loaded on demand
22
Local application integration
1
4
7
1
5
8
6
9
7
4
9
5
8
8
6
9
3
1
2
2
3
1
3
4
Side-by-Side version support
EXE
EXE
• Virtual File
System Added
in Initiator
Context
• Runs until 10
percent
progress
Virtual File
System
Streaming
Service
• Streaming
begins
• IntegratedOffice.
exe process
moves to
System Context
at 10 percent
• Office apps may
be launched at
≈ 15 percent
• Usually 2
minutes or less
Apps ready for
use
Caching
• Office caching
focuses on
launched apps
and features
• Total 3–5
minutes
depending on
connection
• Final ≈ 10
percent installs
add-ins,
licensing, and so
on
Finalizing
Click-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
1 Month
1-2 Months
1-2 Months
3-9 Months
Reduced upfront testing with
deployments in 3–5 months
Deployment
1.
2.
3.
4.
5.
6.
7.
Add users to Office 365 tenant.
Download Office Deployment Tool
(setup).
Use setup to download C2R packages
Customize configuration XML.
Add C2R packages to software
distribution infrastructure.
Deploy C2R packages with setup and
configuration XML.
Layer on add-ins and customizations.
End Users’ PCs
Optional add-ins,
dependent apps,
Office files, etc.
† As
applicable


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
SourcePath
Product ID
Language ID
Updates Enabled
OfficeClientEdition
Office Deployment Tool for Click-to-Run
Option
Add
Description
Parent control to determine source, architecture, product and
languages to download.
Sample Syntax
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" >
Language
Version
Or:
OfficeClientEdition="32"
OfficeClientEdition="64"
Language determines the language DAT files to be downloaded <Language ID=”ja-jp" />
with the Click-to-Run package.
<Language ID=”es-es" />
<Language ID="en-us" />
<Language ID="fr-fr" />
Version is used as part of the <Add> control and specifies the <Add SourcePath="\\Server\Share\Office\"
version to be downloaded. If version is not specified, setup.exe Version=”15.0.4128.1014” OfficeClientEdition="32" >
will download the latest build. Available version numbers will be
posted to KB article in the future.
Option
Add
Description
Parent control to determine source, architecture, product and
languages to download.
Remove
Used to uninstall Office products.
Product
Multiple products may be nested under the <Add> control and
multiple languages may be nested under the <Product> control.
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.
Sample Syntax
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>
<Configuration>
<Remove>
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
<Product ID="VisioProRetail">
<Language ID="en-us" />
</Product>
</Remove>
</Configuration>
<Remove All=”TRUE”>
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>
<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" >
Option
OfficeClientEdition
Language
Updates
Display
Logging
Property
FORCEAPPSHUTDOWN
ForceDowngrade
Description
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.
Language determines the language DAT files to be
downloaded with the Click-to-Run package.
Sample Syntax
<Add SourcePath="\\Server\Share\Office\"
OfficeClientEdition="32" >
Or:
OfficeClientEdition="32"
OfficeClientEdition="64"
<Language ID=”ja-jp" />
<Language ID=”es-es" />
<Language ID="en-us" />
<Language ID="fr-fr" />
Configures automatic updating behavior. Updates may be To use a local file share:
either from the public Office 365 service, local location,
<Updates Enabled="TRUE" UpdatePath="\\Server\Share\Office\"
local file share or private http:// site.
/>
To use the CDN:
<Updates Enabled="TRUE” />
To disable:
<Updates Enabled="False" />
Set to determine the installation display experience. Level <Display Level="None" AcceptEULA="TRUE" />
options are None and Full. You can also accept the end
<Display Level="Full" AcceptEULA="FALSE" />
user license agreement (EULA) on behalf of your users
with the AcceptEULA command.
The logging control lets you determine he log name and <Logging Name="OfficeSetup.txt" Path="%temp%" />
path where logs are written to.
<Logging Name="OfficeSetup.txt"
Path="%deployroot%\smsosdlogs\" />
This command forces an install, uninstall or update. Office <Property Name="FORCEAPPSHUTDOWN" VALUE="1" />
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.
This element is used when the installed version number is <Add SourcePath="\\Server\Share\Office\"
greater than the target version number. This would be
Version=”15.0.4128.1014” OfficeClientEdition="32"
used in roll back scenarios if you detect an issue that
ForceDowngrade=”True”>
requires you to roll back to a previous version.
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
http://technet.microsoft.com/en-us/library/jj219426.aspx
Updates
Automatic
from Cloud
Automatic from
Network
Rerun Setup in
Software Dist.
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" />
Office Deployment Tool for Click-to-Run
Part II
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