Office 365 ProPlus Deployment and Management

addressing common deployment blockers 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?

wouldn’t it be easier to do nothing?

Click-to-Run deployment considerations

are my users local administrators?

what tools are being used now for software deployment?

what are the benefits of subscription vs. perpetual?

identity management?

Paradigm Shift for Office Installation

MSI• Installs can easily take 30 minutes or more• Basis of Office deployments since Office

2000• To be offered as VL media in new Office• Device-based activation• Highly customizable per device• Allows local apps to interact with it

Click-to-Run• First launch is up and running in about 2

minutes• Is primary installation type in the new Office• Is linked to Office 365 for managed

customers• User-based activation• Also highly customizable per device• Also allows local apps to interact with it• Does not require App-V infrastructure or

MDOP

Office 2010 with App-V

2

Rethinking Application Delivery

Click-to-Run

1

32 4

5 6

7 8 9

4

23 1

5 6

7 9 8

EXE

today’s 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

TelemetricFoundation

New Office Telemetry

Maintaining HealthConfiguration management

End-user client troubleshooting

Preparing for ChangeRecently used file analysis

Compatibility verification

TelemetricFoundation

RegularUpdates

VersionUpgrades

Health Monitoring

Troubleshooting End User Issues

Traditional Enterprise Office DeploymentUp to One Year Before First Seat Deployed

Offi

ce

Com

patibi

lity

Inve

ntor

y

Tria

ge

Test

ing

Fixi

ng

Trai

ning

Use

r

Acc

epta

nce

Test

ing

Use

r In

terf

ace

Trai

ning N

ew

Cap

abili

ty

Trai

ning

Dep

loym

ent

Pilo

t

Des

ktop

Im

agin

gSt

anda

lone

In

stal

ls

3-9 Months 1-2 Months 2-4 Months

Ligh

t Te

stin

gO

ffice

Coe

xist

ence

Te

stin

g

Trai

ning

Use

r

Acc

epta

nce

Test

ing Use

r In

terf

ace

Trai

ning N

ew

Cap

abili

ty

Trai

ning

Dep

loym

ent

Pilo

t

Des

ktop

Im

agin

gSt

anda

lone

In

stal

ls

Offi

ce

Com

patibi

lity

Inve

ntor

y

Tria

ge

Test

ing

Fixi

ng

1 Month 1-2 Months 3-9 Months1-2 Months

Click to Run Enterprise Office DeploymentReduced Upfront Testing with Deployments in 3-5 Months

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

Virtual Application Package Communicates with Native Applications

• Enables native executables to run with Click-to-Run package

• Redefines isolation model to suit Office platform extensibility

Does not Require Re-Sequencing or Composition

Support for most common object types

• Simple and Extended MAPI

• ActiveX controls

• Browser Helper Objects: URL Redirection

Click-to-Run Add-In File IntegrationJust in Time Virtualization

Foo.exe

Mapi.dllBubble

Native Virtual Environment

Office C2R

Mapi.dll

How it Works

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.

Click-to-Run self-installation

user has Office 365 account and is provisioned for ProPlus

clicks on “Install software…” tile

views and manages previous installs if available

installs Office 365 ProPlus directly from the Internet

Click-to-Run self-installation

user has Office 365 account and is provisioned for ProPlus

clicks on “Install software…” tile

views and manages previous installs if available

installs Office 365 ProPlus directly from the Internet

Office on demand Sync you documents in

SkyDrive Pro with your Windows devicesCreate a new

document using Office Web Apps

Click a document to open using the Office Web Apps

Get rich consistent document rendering with Office Web Apps

Word Web App opens by default

Lightweight editing

capabilities supported on the browser

When you click Edit in Word, if Word is not installed or is an older version, Word is streamed to your PC on demand from the cloud

Log to Office 365 from any browser and get access to your

email, calendar, people, newsfeeds, sites & documents

Office apps streamed from the cloud in real time

Simplified way to upgrade Office in your PC

Runs side by side with older versions of Office

Office desktop apps delivery in Office 365 Traditional OfficeClick-to-Run Office on Demand Experience carried over from

Office 2010

Software as a Service Software as a Service Packaged Software

Works without SkyDrive Pro Requires SkyDrive Pro Incremental Office 15 investments

Always up-to-date or update controlled by admin

Always up-to date Service Pack Updates

Streamlined install-time controls NA Granular install-time controls (OCT)

Subscription upgrade rights Subscription upgrade rights Software Assurance

Offline is the key feature Roaming is the key feature Classic control is the key feature

Fully installed to the machine Transient state Fully installed to the machine

Fast product streaming Fast product streaming No CTR support; App-V & TS

Full featured Office Excludes some Office features Full functionality

Full Add-in support No Outlook, OneNote, or Lync support (Just Web Apps)

Full Add-in support

No add-in support, loads what is already there though

Available for use offline Not intended for offline use Available for use offline

Licensed per user (Fixed number of installs)

Licensed per user (Unlimited uses) Licensed per device

Subscription only Subscription only Device-based

Sign-in required Sign-in required Sign-in optional

Requires admin rights to install No admin rights required Requires admin rights to install

Start Menu shortcuts No Start Menu shortcuts Start Menu shortcuts

Added to Add/Remove Programs (ARP) Not in ARP In ARP

Customizations via config.xml, Group Policy and add-ins

No customizations Customizations via Office Customization Tool, GP, config.xml and add-ins

Comparing Office Delivery Types

Streamlining the Deployment Tool Belt

Group Policy Configuration XMLOffice Customization Tool

Office 365 ProPlus Click-to-Run

Traditional MSI-based Office installation

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

XML controls to download

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

XML controls to install

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

XML controls to install 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

Click to Run

75 6 EXE

21

8 9

Optimized Software Updates

e 365

1

32

5 6

7 8 9

4

23 1

5 6

7 9 8

Builds are manifested as

components

Client performs delta

comparison

Clients only receive delta

updates

User not impacted

ΔδΔδΔδ

3 43 4

4

7

21 3

8 9

4 5 6

47

21 3

8 9

4 5 6

5 6

Office 2010 with App-V

2

1

EXE

2

1

2

1

2

1

EXE

1

32 4

5 6

7 8 9

4

23 1

5 6

7 9 8

7

21 3

8 9

4 5 6

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

Office deployment without the wait

Download the Office Deployment Tool and use it

Read TechNet Library and Office 365 Preview Blog

Next steps

2 3

Sign up for an Office 365 Preview account

1

Links to IT Pro Resources Office Next Bloghttp://blogs.office.com/b/office-next/

TechNet Office Tech Centerhttp://technet.microsoft.com/en-US/office

Office 365 Preview Bloghttp://community.office365.com/en-us/preview/blogs/office365preview/default.aspx