• •

MSI-based installation Everything carried over from Office 2010 MAK, KMS and AD-based Activation

• •

Click-to-Run installation Built on App-V foundation Office Subscription-based Activation

Office apps are streamed from Office 365 or on premises tools Streaming installation allows Office apps to run almost instantly & 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 & push deployment Office side-by-side means that you will not need to uninstall previous versions of Office in order to use the new Office

today’s application virtualization features loaded on demand local application integration side-by-side version support

2 2 EXE EXE

demo

Click-to-Run installation and Side-by-Side version support

Anatomy of the Click-to-Run Installation Process

•Virtual File System Added in Initiator Context •Runs until 10% progress Virtual File System Streaming Service •Streaming begins •IntegratedOffice.exe process moves to System Context for at 10% •Office apps may be launched at ≈ 15% •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% installs add ins, licensing, etc.

Finalizing

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

Office 365 Service

End Users’ PCs Optional add-ins dependent apps Office files, etc.

† As applicable

Streamlining the Deployment Tool Belt

 

demo

Office Deployment Tool for Click-to-Run

Option

Add Product SourcePath

Description

Parent control to determine source, architecture, product and languages to download. The targeted products to download within the command. Multiple products may be nested under the control and multiple languages may be nested under the control.

Location where the Office is downloaded to. If unspecified, the downloaded content will be saved to the folder where the setup.exe is located.

Sample Syntax

From CDN: From local network: Office 365 ProPlus 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 Version Language determines the language DAT files to be downloaded with the Click-to-Run package. Version is used as part of the 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.

Option

Add Remove Product SourcePath

Description

Parent control to determine source, architecture, product and languages to download. Used to uninstall Office products.

Sample Syntax

From local folder: From local network: Multiple products may be nested under the control and multiple languages may be nested under the control.

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.

Office 365 ProPlus

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

Or: OfficeClientEdition="32" OfficeClientEdition="64" 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: To use the CDN: 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.

The logging control lets you determine he log name and path where logs are written to.

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.

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.

demo

Using MDT to Deploy Office 365 ProPlus

demo

Using Software Distribution to Deploy Office 365 ProPlus

Automatic from Cloud Automatic from Network Rerun setup in software dist

http://blogs.office.com/b/office-next/ http://technet.microsoft.com/en-US/office http://community.office365.com/en us/preview/blogs/office365preview/default.aspx