Transcript Microsoft Office 2010: Deployment Techniques

OFF309
Microsoft Office 2010:
Deployment Techniques
Renato F. Giorgini
Nicola Ferrini
Evangelist IT Pro
Microsoft
IT Pro Trainer
Agenda









Introduction
Office 2010: 32-bit and 64-bit
Product Activation: KMS & MAK
Office Migration Planning Manager (OMPM)
Office Customization Tool (OCT)
Config.XML
Managed Deployment
 Network Share
 GPO Scripts
 System Center
 Application Virtualization
 Deployment
 Update
 Plug-in and Add-on Deployment
 Presentation Virtualization
Group Policy Customization
Q&A!
Planning & Deployment Tools
Planning
Migration
Configuration
Assessment
& Planning
Toolkit
User State
Migration
Tool
SPP- VAMT,
KMS
Office
Environment
Assessment
Tool
Office
Configuration
Tool
Office
Migration
Planning
Manager
Config.xml
Compatibility
Inspector
Group Policy
Enterprise
Learning
Framework
Deployment
Operations
SCCM
Office
Configuration
Tool
Virtualization
GPO Start-up
Scripts
End User
Readiness
Guidance
• Security Guide
• Office OnRamp
• TechNet Resource Center
• TechNet Community
When Support Ends for Previous Versions
Support Timelines
Mainstream Support
End Date
Extended Support
End Date
Office XP
July 11, 2006
July 12, 2011
Office 2003
April 14, 2009
April 8, 2014
Office 2007
April 10, 2012
April 11, 2017
Office 2010:
32 and 64 bit
OS support for Office 2010 – Windows Client
Windows Vista Windows Vista
SP1
SP1
32-Bit
64-Bit
Windows 7
32-Bit
Windows 7
64-Bit
Office 2010
Client 32-Bit
Yes
Yes
Yes
Office 2010
Client 64-Bit
No
Yes
No




Windows XP
SP3
32-Bit
Windows XP
SP3
64-Bit
Yes
Yes
No
Yes
No
No
500 MHz processor, 256 MB RAM, 3 GB Disk Space (Pro Plus SKU)
Not supported 32-bit and 64-bit Side-By-Side on the same machine
http://blogs.technet.com/office2010/archive/2010/01/22/office-2010-systemrequirements.aspx
http://technet.microsoft.com/it-it/library/ee624351(en-us,office.14).aspx
OS support for Office 2010 – Windows Server
Windows Server
2008 R2
64-Bit
Windows Server
2008 SP2
32-Bit
Windows Server
2008 SP2
64-Bit
Windows Server
2003 R2
32-Bit *
Windows Server
2003 R2
64-Bit *
Office 2010
Client 32-Bit
Yes
Yes
Yes
Yes
Yes
Office 2010
Client 64-Bit
Yes
No
Yes
No
No

500 MHz processor, 256 MB RAM, 3 GB Disk Space (Pro Plus SKU)

Not supported 32-bit and 64-bit Side-By-Side on the same machine

http://blogs.technet.com/office2010/archive/2010/01/22/office-2010-systemrequirements.aspx

http://technet.microsoft.com/it-it/library/ee624351(en-us,office.14).aspx

* = Needs MSXML 6.0
Should we go 32-bit or 64-bit?

32-bit Office is best path for most users
 Under Windows 64-bit, Office 32-bit users benefit from a full 2 GB
of memory per application instance

64-bit Office is best for select set of users
 Allows to use more memory - higher performance in Excel, Project
 Higher security due to Hardware DEP enforcement

Office 2010 64-bit cannot be installed side-by-side with Office 2010
32-bit or previous versions of Office
 Using App-V can be a possible path for some users

Consider Application Compatibility issues (DEP; VBA Code, COM...)
Product
Activation:
KMS & MAK
Office 2010: Two Activation Models

Local activation service in your environment
 Key Management Service (KMS)

Direct activation with Microsoft
 Multiple Activation Key (MAK)

Notes:
 Privacy: all methods designed to protect user privacy
 Microsoft does not use activation information to identify or
contact you
 Activation not required for Office 2010 Server products
 SharePoint Server, Project Server, Exchange Server
Office Migration
Planning Manager
(OMPM)
What is OMPM?

Introduced in Office 2007 for OOXML conversion
 New features for Office 2010 concerns

Assess your environment to determine potential issues & target
deployment testing
 Document Conversions
 Add-In issues

Suite of tools for analyzing Office documents for potential migration
issues
 Scanner
 Database
 Reporting tool
 Companion tools
Scanner
Can scan local drives, network shares, SharePoint, and other
WebDAV enabled systems
 Can be configured using Offscan.ini
 Light and Deep scanning modes
 Light: collects file properties
 Deep: cracks open files and looks for issues
 Deployable via SCCM or login script

OMPM: 32-bit to 64-bit Migration

New scanner module for migration issues between 32 bit and 64 bit
editions (Excel, Access, PowerPoint, Word)
 Scan any 97-2010 file for x86->x64 migration
 ActiveX
 Macros
 COM objects
 Optionally collects Excel V4 and VBA code usage information from
specific opt-in customers for future VBA work

New reporting options for these issues

Is not a general-purpose macro scanner
Demo:
OMPM
Office
Customization Tool
(OCT)
Office Customization Tool

The primary tool for most customizations
 Setup.exe /admin
 Allows to customize (and re-customize) an Office Installation
 Future modifications are applied as Updates

Customizations are saved in a .MSP file
 If saved under \Updates folder it’s automatically applied during setup
 It is possible to force the use of a specific MSP File:
 Setup.exe /adminfile <FileName.msp>
 It is possible to apply, post-setup, other MSP customizations
 Msiexec.exe /p <FileName.msp>

Customizes the following areas:
 Setup, Features, Additional content, Outlook (multiple) profiles
OCT: 32-bit and 64-bit Support

Each setup, 32-bit and 64-bit, can be run with /admin switch

32-bit MSP patches cannot be applied directly to 64-bit Office

Users can customize once for a mixed environment:
 32-bit OCT:
 Can import 64-bit patches and apply them to 32-bit products
 Can export 32-bit patches as 64-bit patches
 64-bit OCT:
 Can import 32-bit patches and apply them to 64-bit products
 Can export 64-bit patches as 32-bit patches
Demo:
OCT
Config.XML
Config.XML
If saved in the same folder of setup.exe it’s automatically applied
 Otherwise Setup looks for Config.XML in the core product folder
 It is possible to force the use of a specific file:
 Setup.exe /config <FileName.XML>
 The options contained in the Config.XML take precedence over the
.MSP customizations


Used to:
 Copy the installation source locally without installing Office
 Specify the path of the network installation point
 Select which product or language to install
 Change where Setup looks for Customization files and updates
 Make last-minute or one-off customizations without running the
OCT to create a new customization file
Demo:
Config.XML
Managed
Deployment
Deployment options
http://technet.microsoft.com/en-us/library/ee683866(office.14).aspx
System Center
Application
Virtualization
Network Share
Presentation
Virtualization
Group Policy
Startup Script
Note: Group Policy software installation (GPSI) is not supported.
Network Share

Leave the installation files on a network share accessible by clients.

Advantages:
 Easier implementation for smaller IT departments
 Network share and access are the only requirements
 Users can initiate (manually) the installation as they are ready

Limitations:
 Difficult to control and monitor who installs Office
 User needs Admin privileges on local machine
 Difficult to manage installation times by end users, which can
cause congestion
Group Policy Startup Scripts

Use Group Policy to assign computer startup scripts that run the setup.

Advantages:
 Leverages Active Directory and Group Policy infrastructure
 AD handles the elevation of privileges required for application
installation
 Can use a similar process to apply updates and service packs
 A script can be written in any language supported by the client

Limitations:
 Installation not managed as Group Policy software installation (GPSI)
 Group Policy has limited awareness of the installation state
 Script or batch file required to uninstall/reinstall on multiple computers
 Difficult to determine exactly which updates were applied for each client
System Center
System Center Essentials
 System Center Configuration Manager (SCCM)


Advantages:
 Network bandwidth management
 Centralized control, monitoring, reporting,
and issue resolution for deployment
 Reduced need for help desk to troubleshoot at the desktop

Limitations:
 Requires supporting infrastructure & expertise
Demo:
System Center
Deployment with
Application
Virtualization
(App-V)
Benefits Of App-V:
Run applications as a “service”

Access anywhere
 Over the web
 Portable devices

Just in time deployment (Click-to-Run)
 Installer does not run
 Instant gratification

Simple servicing
 Update once, deliver everywhere
 Users automatically stay up to date
Benefits Of App-V
Run applications without conflicts

No changes to system
 Safely run apps side-by-side
 No OS decay over time
 Lower migration costs

State separation
 Store app state separate from OS state
 State categorized as user versus system
 User state stored in profile, roams with profile
App/OS Model Comparison
Traditional App/OS Model
Virtualized App/OS Model
How Does It Work?

App packaged using Sequencer
 Installation monitored to capture resources
 All app resources stored in an app image (.SFT)

App image placed on server for distribution

App streamed to client over network
 SMB, HTTP(S), RTSP(S)
 Can leverage DFSR replica and BranchCache
 Other distribution mechanisms possible (USB)

App-V runs app in Virtual Environment (VE)
 App virtualization layer handles resource requests
Application Virtualization running…
Operating System
Read Only
System Files
(Registry, .ini,
DLL, etc.)
Read & Write
Read & Write
Application
System Services
(cut and
paste, OLE,
printers, etc.)
Virtual Environment
(Registry, .ini, DLL,
Group Policy, etc.)
Read & Write
Profile Data
Office 2010 Deployment with App-V

Use Microsoft Application Virtualization to stream applications on-demand

Advantages:
 Centralized application management
 Support for roaming users and making applications available quickly
 Can run multiple versions of Office on the desktop
 Previously incompatible applications can run on the same desktop
 Centralized image simplifies updates, management & helpdesk

Limitations:
 Requires a supporting infrastructure and resources
 Consider network bandwidth availability for streaming applications
 Integration into existing infrastructure, such as the patch management
process
Improved Application Virtualization Support
Tighter integration with Microsoft App-V
Potential to simplify deployment & management
 Microsoft invested in App-V with Click-to-Run
 Office 2010 requires App-V 4.6 (available in MDOP 2010)
 App-V requires deployment specific sequencing
 Features improved with App-V 4.6/Office 2010 include:

Will Office 2010 be supporting virtualization?
YES...and not exactly
Virtualization Agent*
Operating System
Virtualization Agent*
On machine
Operating System
On machine
Hardware
Hardware
App. C
App. B
App. C
App. B
Office
Redist
App. A
Office 2010
Virtualized
App. A
Virtualized
Office 2007
Office 2007
Office 2010

Well Yes….
1. We’re building the Office “redistributable”? The virtualization enabler
“bits” for Office 2010
1. SPP Licensing components
2. Windows Desktop Search for Instant Search in Outlook
3. SharePoint Proxy (so virtualized office can edit documents hosted by
SharePoint)
4. URL protocol handers (mailto:, feed, feeds, stssync, webcal, webcals)
5. Filters for office document indexing
6. (Virtual) Mail Control Panel applet (needed for some advanced account
configuration scenarios)
7. Simple MAPI proxy (ex Right click on file, Send To -> Mail)
8. Send to OneNote Printer driver
2. Work has been done to make Office 2010 run faster when virtualized
Application Virtualization Management Server
and Client Requirements and Interactions

Client for desktops and
terminal services

Small footprint

Windows XP, Windows 2003
Server, or newer

12 megabyte (MB) for
installation files, at least 2048
MB for cache file
Demo:
Application
Virtualization
Reducing Application Conflicts
Manifest.xml

Application Virtualization packages
contain the complete
environment
for the application

Applications in a suite can
share the environment
Manifest.xml

Potentially conflicting
applications have
their own environment
Side-by-Side execution
Demo: SSxS
(Super Side by
Side) 
Application Updates
Update
Updates
• Update once on server
• Seamless update to clients
Demo: Dynamic
Suite
Composition
APP-V e RDS : Better Together

APP-V 4.6 supports 64 bit OS:
 Remote Desktop Services of Windows Server 2008 R2
 Terminal Services of Windows Server 2008

Easy deployment, management and applications maintenance

Remote access to the applications, also using web

RemoteApp and WebAccess Integration
Demo:
Presentation
Virtualization
Group Policy
Customization
Group Policies
Administrators can use Group Policy to mandate user settings for
Office
 Office policy settings are contained in the Administrative Template
(.adm or .admx and .adml) files
 Administrators can use settings to create highly restricted or lightly
managed desktop configurations
 Group Policy settings have precedence over OCT settings
 Administrators can use settings to disable file formats that are not
secure across the network

Demo: GPO
Next Steps
Plan deployment carefully 
 Plan KMS/MAK Activation
 Assess current environment (files, add-ins, ...)
 Customize Office Installation (OCT, Config.xml)
 Secure deployment using GPO & Admin Templates
 Use, every time is possible, Application Virtualization 

Additional (learning) resources:


Office 2010 – System Requirements:

http://technet.microsoft.com/it-it/library/ee624351(en-us,office.14).aspx
Application Virtualization:

http://technet.microsoft.com/en-us/subscriptions/downloads/default.aspx

http://www.microsoft.com/appv

http://blogs.technet.com/softgrid/default.aspx

http://www.microsoft.com/italy/server/windowsserver2008/panoramica/introduzione-a-microsoft-application-virtualization.mspx

http://support.microsoft.com/?kbid=980861

MAP:

http://microsoft.com/map

USMT:

http://technet.microsoft.com/en-us/library/dd560750(WS.10).aspx
Office Activation Technologies:

http://technet.microsoft.com/volumeactivation






OMPM:
 http://technet.microsoft.com/en-us/library/dd901407.aspx (Office 2007 Link)

http://technet.microsoft.com/en-us/library/cc179179.aspx

http://www.microsoft.com/downloads/details.aspx?familyid=13580cd7-a8bc-40ef-8281-dd2c325a5a81&displaylang=en

http://channel9.msdn.com/Wiki/OfficeDeployment/OMPMv1/

http://blogs.technet.com/office_resource_kit/archive/2010/01/22/office-2010-application-compatibility-tools.aspx
OCT:

http://technet.microsoft.com/en-us/library/cc764476.aspx (Office 2007 Link)
Config.xml:
 http://technet.microsoft.com/en-us/library/cc179195.aspx (Office 2007 Link)
VAMT:

http://www.microsoft.com/downloads/details.aspx?familyid=9893F83E-C8A5-4475-B025-66C6B38B46E3&displaylang=en
ELF:

http://www.microsoft.com/technet/desktopdeployment/bdd/ELF/Welcome.aspx
Questions
and
Answers
Grazie!
Non dimenticare di compilare
i moduli di Feedback!
www.sharepointconference.it
Renato & Nicola!
© 2010 Microsoft Corporation and Italian SharePoint & Office Conference. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be
registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft
must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of
any information provided after the date of this presentation.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.