Office 365 ProPlus:Click-to-Run deployment and management

Brian ShiersSr. Product Manager – Microsoft Office Division

Office 365 ProPlusDeploy Office fast without giving up control

Side-by-side installswith older versions

Automated softwaredistribution support

Group Policy and Telemetry support

5 installs per user on PCs or Macs

Personalized settingsroam between devices

Manageable background updates

Familiar & full Office applications -locally installed, available offline

2 Office install options

Office Professional Plus 2013MSI-based installation

Everything carried over from Office 2010MAK, KMS and AD-based ActivationRequired for RDS, WTG, shared computers and closed network scenarios

Office 365 ProPlusClick-to-Run installation

Built on App-V foundationOffice Subscription-based ActivationSide by side versions supportMay be used on physical or virtual machines

Office 2010 with App-V

2

Rethinking Application Delivery

ProPlus Click-to-Run

1

32 4

5 6

7 8 9

4

23 1

5 6

7 9 8

EXE

past application

virtualization

features loaded on demand

local application integration

side-by-side version

support

1

EXE

7

21 3

8 9

4 5 62

1

demoClick-to-Run installation andSide-by-Side version support

Side-by-Side helps transition

keep older versions of Office installed alongside new Office

be proactive with compatibility risks – use as fall back

not recommended as a permanent configurationvirtual file system

Anatomy of the Click-to-Run Installation Process

• Virtual File System Added in Initiator Context

• Runs until 10% progress

Virtual File System

• Streaming begins• IntegratedOffice.exe

process moves to System Context at 10%

Streaming Service

• Final ≈ 10% installs add-ins, licensing, etc.

Finalizing

Click-to-Run managed deployment1.add users to Office 365

tenant2.download Office

Deployment Tool (setup)3.use setup to download

C2R packages4.customize configuration

XML5.add C2R packages to

software distribution infrastructure

6.deploy C2R packages with setup and configuration XML

7. layer on add-ins and customizations

† As applicable

End Users’ PCs

Optional add-insdependent appsOffice files, etc.

Office 365 ServiceOrg ID†

AD†SW Dist.

Group Policy Configuration XMLOffice Customization Tool

Office 365 ProPlus Click-to-Run

Traditional MSI-based Office installation

Streamlining the Deployment Tool Belt

Office Deployment Tool

free download on Microsoft Download Center enables downloading Click-to-Run packages

customizes installation of Click-to-Run Office products

applies software update policies

demoOffice Deployment Tool for Click-to-Run

Download Controls

Option Description Sample SyntaxAdd 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=”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" > 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" />

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.

<Add SourcePath="\\Server\Share\Office\" Version=”15.0.4128.1014” OfficeClientEdition="32" > 

download XML

Install Controls

Option Description Sample SyntaxAdd 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" > <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> </Product></Add>

Remove Used to uninstall Office products. <Configuration><Remove> <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> </Product> <Product ID="VisioProRetail"> <Language ID="en-us" /> </Product> </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<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 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="\\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" >

install XML

Install Controls Continued

Option Description Sample SyntaxOfficeClientEdition 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 http:// 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=”15.0.4128.1014” OfficeClientEdition="32" ForceDowngrade=”True”> <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> </Product></Add>

uninstall XML

demoUsing MDT to Deploy Office 365 ProPlus

MICROSOFT CONFIDENT IAL – INTERNAL ONLY

Group Policy Settings for “no prompt” Deployment

Disable First Run experienceUser Configuration\

Microsoft Office 2013\First Run

Disable First Run Movie - Enabled Disable Office First Run on application boot – Enabled

MICROSOFT CONFIDENT IAL – INTERNAL ONLY

Group Policy Settings for “no prompt” Deployment

Disable “First things First”User Configuration\

Microsoft Office 2013\Privacy\

Trust CenterDisable Opt-in Wizard on first run – EnabledEnable Customer Experience Improvement Program – DisabledAllow including screenshot with Office Feedback – DisabledSend Office Feedback – DisabledAutomatically receive small updates… - Disabled

Deployment tool used to create package

Uses subscription activation model

No more deployment kit or hand sequencing

Refer to KB 2772509 when using the package

App-V and ProPlus

Updating Options

Automatic from Cloud

Default option

Updates come from Microsoft Office 365 service when available

Update service is a scheduled task that runs once per day

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

Recommended for 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

Update Automation Option

\\Server\Testing$

\\Server\Production$

Patch Tuesday

Setup /download …Schedule Task N weeks later

Turn on Verbose Logging:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClickToRun\OverRideDWORD “LogLevel”Value Data “3”

Log File:integratedoffice.exe_streamserver(****************).log

Troubleshooting

Manage.

Issue detection

Document identification Solution management

Deployment

Office Telemetry enables

Report detected issues & performance

Determine frequency of documents & solutions used

Manage add-ins & solutions

Track deployments

DemoTelemetry Dashboard Introduction

How Office Telemetry Works

Telemetry Dashboard

Office 2003/2007/2010 Clients

Office 2013 Clients

Processing Service DatabaseShare

TelemetryFoundation

Group Policy

Microsoft Confidential

Skype acquisition plan.docx

Hide Filter Threshold

Obfuscatethe file properties

ab****

Specify Office solutions / file type

Threshold of use by specified limit

Sk********(1).docx

Privacy Solutions

Collection Point

Static Scan

Telemetry

Setting

Office 365 ProPlus

64kb

~25,000 Users (~8hrs)

11g

bOffice 2003+

50kb

Policy & Registry

Telemetry Agent

System info

Telemetry

Static Scan

Most recently used filesAdd-ins startupRegistered add-insRuntime eventsIssue logging

ProPlus Pre ProPlusGroup Policy Template

Registry setting

office15.admx and office15.adml

User Configuration\Administrative Templates\Microsoft ProPlus\Telemetry Dashboard

Windows Registry Editor Version 5.00[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\osm]"CommonFileShare"="\\\\<SERVERNAME>\\<SHARENAME>""Tag1"="<TAG1>""Tag2"="<TAG2>""Tag3"="<TAG3>""Tag4"="<TAG4>""AgentInitWait"=dword:00000258"Enablelogging"=dword:00000001"EnableUpload"=dword:00000001"EnableFileObfuscation"=dword:00000000"AgentRandomDelay"=dword:000000F0

Database size

SQL Server

Windows

Settings

Windows Server 2008+(Windows 7+)

SQL Server 2005+(Express Edition)

1 Telemetry Processor

Up to 25,000 usersDatabase can handle multiple Telemetry Processors

Telemetry ProcessorError log%systemroot%\ServiceProfiles\NetworkService\AppData\Local\Temp\DPERRORLOG.txt

10,000 users x 1yr

12gb

SQL SettingAccess permission “td_readonly”

TD Management Tool Size Down | Copy/Move Data | DB Settings

Osql.exe

> osql.exe -E -S servername\instancename -d databasename -Q "EXEC sp_addrolemember 'td_readonly', 'domain\grouporuser'"

> osql.exe -E -S servername\instancename -d databasename -Q "update [ServerSettings] Set [IntValue] = 3 Where [Name] = 'SolutionFilterThreshold'"

> tdadm.exe –o delete –sf server_name –df db_name –datetime 12312011

DemoTelemetry DashboardDeep Dive

CleanupCopy / Delete / Move

Replace

abac

Setting / Permission

PrivacyReplace Collected data to obfuscate.Change server settings of Solution threshold easily

OptimizationCopy/Move old events data to separate database Delete data of userX, department, file name.Replace or manage tags

DeploymentChange server settings to manage Change permission to allow / decline user to access easily

Telemetry Dashboard Admin Tool

The ToolsOffice Deployment Tool for Click-to-RunTelemetry Dashboard Admin ToolOffice Telemetry Resource

IT Pro events, webcasts and guides for the new Office

OfficeIgnite.com www.microsoft.com/garage