1. Microsoft Office 365 ProPlus Deployment for IT Pros
Curtis Sawin, Technology Solutions Professional, Microsoft
Dean Yamada, Senior Premier Field Engineer, Microsoft

2. About the Presenters Curtis Sawin Technology Solutions Professional
Microsoft
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.

3. About the Presenters Dean Yamada Senior 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.

4. Course Modules 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

5. Introduction to Click-to-Run

6. Agenda
Understanding Click-to-Run
Deployment
Updates

7. Understanding Click-to-Run

8. Common Deployment Blockers
Will our files work in the new Office?
Common Deployment Blockers
Will our customizations and add-ins work?
Wouldn’t it be easier to do nothing?
How do I handle consumerization and people with multiple devices?

9. Click-to-Run

10. Office 365 ProPlus Deploy Office quickly without giving up control
Familiar & full Office applications locally installed, available offline
Side-by-Side installs with older versions
5 installs per user on PCs or Macs
Personalized settings
roam between devices
Automated software distribution support
Manageable background updates
Group Policy and Telemetry support

11. Get Office Fast

12. Tale of Two Package Types
Click-to-Run (C2R)
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
MSI
Streaming Installation
Slipstreamed Servicing
User-based Licensing
Retail Activation
SKU Level Application Suites
Classic Installation
Layered Servicing
Volume Licensing
Volume Activation
Selective Application Installation
Office 365 ProPlus is C2R
Office 2013 Professional Plus is MSI

13. Tale of Two Package Types
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
Tale of Two Package Types
Click-to-Run installation
Built on App-V foundation
Office subscription-based activation
May be used on physical or virtual machines

14. Why Click-to-Run?
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

15. Rethinking Application Delivery
Today’s application virtualization
Features loaded on demand
Local application integration
Side-by-Side version support 2 1 2 1 4 2 3 1 5 6 7 9 8 7 2 1 3 8 9 4 5 6 5 6 7 8 9 1 2 3 4
Office 2010 with App-V
Click-to-Run
EXE
EXE

16. Anatomy of the Click-to-Run Installation Process
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

17. Demo
Click-to-Run Installation and Side-by-Side Version Support

18. Side-by-Side Helps Transition virtual file system
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

19. Reduced upfront testing with deployments in 3–5 months
Light Testing
Office Coexistence Testing
1 Month
Training
User Acceptance Testing
User Interface Training
New Capability Training
1-2 Months
Click-to-Run Enterprise Office Deployment
Deployment
Pilot
Desktop Imaging
Stand-alone Installs
1-2 Months
Reduced upfront testing with deployments in 3–5 months
3-9 Months
Office Compatibility
Inventory
Triage
Testing
Fixing

20. Deployment

21. Click-to-Run Managed Deployment Add users to Office 365 tenant.
Org ID†
Click-to-Run Managed
Deployment
SW Dist.
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.
AD†
End Users’ PCs
Optional add-ins, dependent apps, Office files, etc.
† As applicable

22.   Streamlining the Deployment Tool Belt Office 365 Click-to-Run
Group Policy
Configuration XML
Office Customization Tool
Traditional MSI-based Office installation 

23. Office Deployment Tool

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

25. Configuration.xml Example
<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>

26. Demo
Office Deployment Tool for Click-to-Run

27. XML Controls to Download
Option
Description
Sample Syntax
Add
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=” ” OfficeClientEdition="32" >
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="VisioProRetail">
<Language ID=”ja-jp" />
<Product ID="ProjectProRetail">
<Language ID=”es-es" />
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=" 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.
Or:
OfficeClientEdition="32"
OfficeClientEdition="64"
Language
Language determines the language DAT files to be downloaded with the Click-to-Run package.
<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.
XML Controls to Download
download XML

28. XML Controls to Install
Option
Description
Sample Syntax
Add
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" >
Remove
Used to uninstall Office products.
<Configuration>
<Remove>
<Product ID="VisioProRetail">
</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
<Language ID=”ja-jp" />
<Product ID="ProjectProRetail">
<Language ID=”es-es" />
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="%Applications%\Office\" OfficeClientEdition="32" >
<Add SourcePath="C:\Source\Office\" OfficeClientEdition="32" >
<Add SourcePath=" contoso.com/Office" OfficeClientEdition="32" >
XML Controls to Install
install XML

29. XML Controls to Install, cont.
Option
Description
Sample Syntax
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" />
Updates
Configures automatic updating behavior. Updates may be either from the public Office 365 service, local location, local file share or private 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=” ” OfficeClientEdition="32" ForceDowngrade=”True”>
<Product ID="O365ProPlusRetail">
</Product>
</Add>
XML Controls to Install, cont.
uninstall XML

30. Updates

31. Updating Options Default option
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

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

33. Demo
Office Deployment Tool for Click-to-Run
Part II

34. Fast, controllable, minimal risk

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

36. © 2013 Microsoft. All rights reserved
© 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.