• 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/
• 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/
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
Folder and Registry Structure
Behind the Scenes
How Automatic Updates Work
Notes from the Field
Understanding the
Folder Structures
C:\Program Files\Microsoft
Office 15\root\office15
ClientX86 or ClientX64 folder
within, based on the OS bitness
IntegratedOffice will run in two
processes, System and User Context
during install
IntegratedOffice continues to run
under System context for the
lifetime of Office 2013 C2R
Verify file size and size on disk
are identical
VFS folder holds all remaining
non-Program Files folder
contents
Contains XML manifest files
Registry Staging On-Demand
.DAT files
Understanding the
Registry Structures
Click-to-Run
Installation
Registry Structure
2 = Success
3 = Failure
Demo
Looking at Important Folders and
Registry Hives
Behind the Scenes
Scheduled Tasks
Run under system context
Manage updates, subscription
maintence, telemetry data
collection…
…and background streaming
Demo
Importance of IntegratedOffice Service
Managing Updates
Attribute
Enabled
Value
TRUE or FALSE
UpdatePath
\\server\share\
C:\Preload\Office
http://Apps/Office/
""
Description
Optional. If Enabled is set to TRUE, the Click-to-Run update system
will check for updates. If it is set to FALSE, the Click-to-Run update
system is dormant.
Optional. If UpdatePath is not set, Click-to-Run installations obtain
updates from the Microsoft Click-to-Run source (Content Delivery
Network or CDN). This is by default.
Automatic
from Cloud
If UpdatePath is set to empty (""), updates are obtained from the
Microsoft Click-to-Run source, CDN.
UpdatePath can specify a network, local, or HTTP path of a Clickto-Run source.
TargetVersion 15.1.2.3
Environment variables can be used for network or local paths.
Optional. If TargetVersion is not set, Click-to-Run updates to the
most recent version from the Microsoft Click-to-Run source.
If TargetVersion is set to empty (""), Click-to-Run updates to the
latest version from the Microsoft Click-to-Run source.
TargetVersion can be set to an Office build number, for example,
15.1.2.3. When the version is set, Office attempts to transition to
the specified version in the next update cycle.
Automatic from
Network
How Automatic
Updates Work
Task runs 15, 45, 75 minutes after
logon and Sun, Tues, Fri @ 3:00–
7:00 AM
Delta is downloaded transparently
User interaction is possible
Apply
Update (Scenario
32
1 of 3)
Most Common
Path
Demo
Automatic Updates – Behind the
Scenes
Notes from the Field
Notes from the Field:
Sample Update Management Process
1. “Testing” group is configured to get automatic
updates from the cloud
SourcePath="\\MyServer\Office\"
2. Everyone
else is configured to get automatic
updates from an internal source
3. Patch Tuesday – Testing group gets latest
build.
4. Last Friday of every month – Setup.exe
/download places latest build in internal source
(hint: use a scheduled task!)
Notes from the Field:
Sample Update Management Process
Goals
Risks
• Builds are tested for 2–3 weeks prior
to general release
• Process is automated
• “Opt-out” mechanism is available (for
example, disable the scheduled task)
• Depending on severity of issue,
testing group may need to be
downgraded
• Out of band builds?
Notes from the Field:
Notes from the Field:
Task Scheduler service disabled
%windir%\system32\Tasks folder, insufficient
permissions
Using Office Deployment Tool from network
share, computers must have “read” access to
source
Using Office Deployment Tool with a mapped
network drive is not supported
Installing language packs post-install is not an
option
Notes from the Field:
Proxy or Firewall blocking access to activate C2R.
Unauthenticated access is required
http://technet.microsoft.com/en-us/library/jj219420.aspx
Notes from the Field:
Side-by-Side Issue: Word 2007/2010 repairs in
SxS mode, causing file type associations to revert
to the older version of Office.
Scenario:
Office 365 ProPlus is installed from the local system
account (or a different user account), then Office apps
are used by the current user.
(Symptomatic when using software distribution tools)
HKCU keys are not written to the current user’s profile.
Notes from the Field:
Side-by-Side Issue: Word 2007/2010 repairs in
SxS mode, causing file type associations to revert
to the older version of Office.
Workaround:
For Office 2010, add:
HKCU\Software\Microsoft\Office\14.0\Word\Options\
NoReReg = 1 (Dword)
For Office 2007, add:
HKCU\Software\Microsoft\Office\12.0\Word\Options\
NoReReg = 1 (Dword)
(hint: Group Policy Preferences is great for this)
Where Click-to-Run lives
 Understand important folder and
registry locations
The Background Processes
 Scheduled Tasks and Services
Automatic Updates Decoded
 How updates work behind the scenes
What are we seeing in the field?