15
Designing Office 2010 Deployment

Designing office 2010 deployment

Embed Size (px)

Citation preview

Page 1: Designing office 2010 deployment

Designing Office 2010 Deployment

Page 2: Designing office 2010 deployment

System Requirements

Office XP Office 2003 Office 2007 Office 2010

Min. RAM (MB)

64 128 256 256

Min. CPU (MHz)

133 233 500 500

2575

125175225275325375425475

Page 3: Designing office 2010 deployment

Office Apps Boot Faster

Word Excel PowerPoint

Office 2007 0.42 0.25 0.36

Office 2010 0.29 0.19 0.19

0.025

0.075

0.125

0.175

0.225

0.275

0.325

0.375

0.425

Page 4: Designing office 2010 deployment

Redesigned Excel Calc Engine

Excel 2003

Excel 2007

Excel 2010

Re-calc time (sec)

334.86 67.31 6.74

2575

125175225275325

Recalc time (sec)

Excel 2003

Excel 2007

Excel 2010

Drawing chart (sec)

3.65 44.95 2.37

2.5

12.5

22.5

32.5

42.5

Drawing chart (sec)

Page 5: Designing office 2010 deployment

Deployment tools

Discover & Explore

Microsoft Assessment & Planning Toolkit (MAP)

Office Environment Assessment Tool (OEAT)

Office Migration Planning Manager (OMPM)

Office Code Compatibility Inspector (OCCI)

Manage

Office Security Guide via Security Compliance Manager

Group Policy Admin Templates

Activation Volume Activation

Management Tool KMS Host Pack

SharePoint Service ConfigurationInteractive Guides

Pilot & Deploy

Office Customization Tool (OCT)

Config.xml Microsoft Deployment

Toolkit (MDT) User State Migration Tool

(USMT) Office Deployment Kit for

App-V

SPRINGBOARD SERIES for Office 2010

Page 6: Designing office 2010 deployment

Microsoft Assessment & Planning Toolkit (MAP)• System readiness assessment for Office 2010

Office Environment Assessment Tool (OEAT)• Discovery & Assessment of Office 2010 Add-ins and interfacing programs

Office Migration Planning Manager (OMPM)• Office file readiness assessment and migration tools

Office Code Compatibility Inspector• Provides guidance to an Office developer to remediate VBA code

Page 7: Designing office 2010 deployment

Microsoft Assessment and Planning Toolkit

MAP

Windows Server 2008 &

R2

Hyper-VVirtual Server

2005 R2

Windows7

2010 Microsoft Office

SCVMM

SQL Server 2008

Forefront/NAP

Other Products

• Integrated Automated Toolkit for migration planning from desktops to servers

• Agent-less inventory• Technology migration and

readiness assessment and proposal generation

• Multi-Product Planning and Assessment Tool

Page 8: Designing office 2010 deployment

Top 3 Questions on MAP

• Is this tool secure?• MAP requires the user to enter local admin credentials for the client machines

and servers; non-admin user cannot gain access to the machines and will get no results from the MAP tool.

• MAP encrypts the data traffic from the MAP machine to the assessed server and client machines.

• MAP does not persist or store any credentials required for WMI to remotely gather information on the server and client machines.

•How much data traffic do we get?• A typical network of desktops would see 300kB to 1MB per PC of data traffic

generated by MAP.

•What’s the impact on each computer?• Very minimal. The MAP tool only pings about 30 machines at any given

instance.

Page 9: Designing office 2010 deployment

OMPM2010 Highlights:

– Bulk Macro Compatibility Scanning • Incorporates logic from OCCI tool • Registers count of potential number of VBA issues due to changes in object model

– Bulk 64-bit compatibility Scanning • Incorporates logic from OCCI tool• Registers count of potential number of 64-bit (declare) VBA issues due use of 64-bit Office

– Pre-defined Date Filtering for Scans• New configuration options in the Offscan.ini file • Skipped can be logged

– SQL 2008/2008 R2 support • Support for SQL Server 2008/2008 R2 has been enabled• Remains compatible with SQL 2005

– Various bug fixes – existing OMPM and OFC bugs • List includes: old create date files failing on import, OFC conversion does not complete, etc.

Alternatives: – Converter Technologies

Page 10: Designing office 2010 deployment

OS Support for Office 201032-Bit and 64-Bit Versions

Introduction

Windows 732-Bit

Windows 764-Bit

Windows Vista

32-Bit

Windows Vista

64-Bit

Windows XP SP3

32-Bit

Windows XP64-Bit

Office 2010 Client 32-Bit Yes Yes Yes Yes Yes No

Office 2010 Client 64-Bit No Yes No Yes No No

Page 11: Designing office 2010 deployment

Deployment Options: Client

Group Policy software installation (GPSI) is not supportedN

ote

Other Virtualization

Application Virtualization

Group Policy Startup Scripts

Network Share

Managed Deployment

Managed Deployment

Page 12: Designing office 2010 deployment

Network ShareOffice 2010 Deployment

Make the installation files for Office 2010 available on a network share that is accessible by targeted clients.

Limitations

Difficult to control and monitor who installs Office

Difficult to manage installation times by end users, which can cause congestion

Advantages

Easier implementation for smaller IT departments

Network share and access are the only requirements

Users can initiate the installation as they are ready

Page 13: Designing office 2010 deployment

Group Policy Startup ScriptsOffice 2010 Deployment

Use Group Policy to assign computer startup scripts.

Advantages

Leverages Active Directory and Group Policy infrastructure

Active Directory handles the elevation of privileges required for application installation

Administrators can use a similar scripting process to apply security updates and service packs

A script can be written in any language that is supported by the client computer

Limitations

Product installation is not managed in the same way as Group Policy software installation (GPSI)

Group Policy invokes the script and has limited awareness of the installation state

A command-line script or batch file is required to uninstall or reinstall the product on multiple computers

Difficult to determine exactly which updates and service packs were applied for each client computer

Page 14: Designing office 2010 deployment

Application VirtualizationOffice 2010 Deployment

Use Microsoft Application Virtualization as part of a deployment option to stream applications on-demand to the desktop.

Advantages

Centralized application management

Support for end-user roaming and making applications available to end users quickly

Can run multiple versions of Office on the desktop

Previously incompatible applications can run on the same desktop

Centralized image simplifies helpdesk

Limitations

Requires a supporting infrastructure and resources for Microsoft Application Virtualization

Network bandwidth availability for streaming applications to end-user devices

Integration into existing infrastructure, such as the patch management process

The Unknown!

Page 15: Designing office 2010 deployment

Springboard Resources

• Tools• Planning guides• Posters• http://aka.ms/

springboardoffice