Ignite Webcast 2 - New Office Deployment Integration

advertisement
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
22
1
4
7
1
5
8
6
9
7
4
9
5
8
8
6
9
3
1
2
2
3
1
3
4
local application integration
EXE
side-by-side version support
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 addins, licensing, etc.
Finalizing
Office 365 Service
add users to Office 365 tenant
2. download Office Deployment
Tool (setup)
3. use setup to download C2R
packages
4. customize configuration XML
5. add C2R packages to software
distribution infrastructure
6. deploy C2R packages with
setup and configuration XML
7. layer on add-ins and
customizations
1.
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
Description
Parent control to determine source, architecture, product and
languages to download.
Sample Syntax
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" >
Language
Version
Or:
OfficeClientEdition="32"
OfficeClientEdition="64"
Language determines the language DAT files to be downloaded <Language ID=”ja-jp" />
with the Click-to-Run package.
<Language ID=”es-es" />
<Language ID="en-us" />
<Language ID="fr-fr" />
Version is used as part of the <Add> control and specifies the <Add SourcePath="\\Server\Share\Office\"
version to be downloaded. If version is not specified, setup.exe Version=”15.0.4128.1014” OfficeClientEdition="32" >
will download the latest build. Available version numbers will be
posted to KB article in the future.
Option
Add
Description
Parent control to determine source, architecture, product and
languages to download.
Remove
Used to uninstall Office products.
Product
Multiple products may be nested under the <Add> control and
multiple languages may be nested under the <Product> control.
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.
Sample Syntax
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>
<Configuration>
<Remove>
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
<Product ID="VisioProRetail">
<Language ID="en-us" />
</Product>
</Remove>
</Configuration>
<Remove All=”TRUE”>
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>
<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" >
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
<Add SourcePath="\\Server\Share\Office\"
OfficeClientEdition="32" >
Or:
OfficeClientEdition="32"
OfficeClientEdition="64"
<Language ID=”ja-jp" />
<Language ID=”es-es" />
<Language ID="en-us" />
<Language ID="fr-fr" />
Configures automatic updating behavior. Updates may be To use a local file share:
either from the public Office 365 service, local location,
<Updates Enabled="TRUE" UpdatePath="\\Server\Share\Office\"
local file share or private http:// site.
/>
To use the CDN:
<Updates Enabled="TRUE” />
To disable:
<Updates Enabled="False" />
Set to determine the installation display experience. Level <Display Level="None" AcceptEULA="TRUE" />
options are None and Full. You can also accept the end
<Display Level="Full" AcceptEULA="FALSE" />
user license agreement (EULA) on behalf of your users
with the AcceptEULA command.
The logging control lets you determine he log name and <Logging Name="OfficeSetup.txt" Path="%temp%" />
path where logs are written to.
<Logging Name="OfficeSetup.txt"
Path="%deployroot%\smsosdlogs\" />
This command forces an install, uninstall or update. Office <Property Name="FORCEAPPSHUTDOWN" VALUE="1" />
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 <Add SourcePath="\\Server\Share\Office\"
greater than the target version number. This would be
Version=”15.0.4128.1014” OfficeClientEdition="32"
used in roll back scenarios if you detect an issue that
ForceDowngrade=”True”>
requires you to roll back to a previous version.
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
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/enus/preview/blogs/office365preview/default.aspx
Download