Upload
evelyn-leonard
View
214
Download
2
Tags:
Embed Size (px)
Citation preview
Session Objectives
• What you should consider before deploying Microsoft Office 2010®
• Planning and Preparation Tools to assist with Office 2010 deployments
• IT Professionals will come away understanding what tools are available to support Office deployments
• Enable IT Pros to start their evaluation, planning and deployment cycle of Office 2010
Deployment LifecycleCore Office deployment project lifecycle
Planning
Migration
ConfigurationDeployment
Operations
Planning Tools
• Planning starts in 3 key assessment areas:− System readiness − Application compatibility − File readiness
• Where do you start?− Hardware - inventory and
identify − Application & File scans can
build from the initial assessment• Consider group wise assessments
− Not just technical readiness
Getting Ready for Office 2010 Planning & Assessment
System Readiness• Inventory Office Applications • Assess hardware & OS readiness• Suggests key upgrades• Summary proposal of 2010 readiness
Application Compatibly• Identify interfacing add-ins & interfaces• Tag known compatible apps• Mitigate VBA and macro code
File Readiness • Scan & identify potential format deltas• Identify potential macro issues• Migrate Office files to OpenXML formats
• Microsoft Assessment Planning Toolkit (MAP)
• Office Environment Assessment Tool (OEAT)• Office Compatibility Code Inspector (OCCI)
• Office Migration Planning Manager (OMPM)
Guidance• Desktop Deployment Planning Service (SA)• Training Vouchers(SA)
• Office Resource Kit (ORK)• TechNet Resource Centers
Microsoft Assessment Planning Toolkit Overview
• Microsoft Assessment Planning Toolkit – from Technet• Agentless network wide inventory• Initial readiness assessment and environment analysis• Outputs leveraged to start detailed scans and planning• Current MAP 4.0 can be leveraged today
− Use Office 2007 Assessment
Hardware Inventory• Agentless• HW Analysis
Compatibility Analysis• Hardware compat
• Inventory of Apps
Readiness Report• Excel data report
• Recommendations*
MAP – What’s Coming
• MAP will be revised in conjunction with Office 2010
• Additional Office planning features:− Detailed analysis report workbook− Summary proposal report− Upgrade scenario support
• Clear definition and link to Office application compatibly tool
• Initial tool beta in H1 2010 – CTP today!
Office Environment Assessment Tool • Comprehensive environment scanning tool
− Installed applications− Installation environment.
• Focus of OEAT scan− Office client add-ins − Programs that interact with Office clients
• Environmental assessment (drill down from MAP)
• Add-ins assessment - list of 3d party programs and information about the program’s compatibility with Office 2010.
Enterprise Learning Framework• Content customized
by applications• Content provided
by audience• Content outlined by
timeline• Includes project
promotion and support content
•End user awareness content•Early awareness
Raising Awareness
•Identify targeted learning topics•Gets users up and running quickly
Minimizing Disruption
•Concise learning topics •Minimizes impact to end users
Shortening Training
•Crucial learning topics•Expedites adoption
Gaining Productivit
y
Office Migration Planning Manager (OMPM)Meet the tool• Primary content assessment tool• Suite of tools for analyzing Office
documents for potential migration issues− Scanner− Database− Reporting tool− Companion tools
• Introduced in Office 2007 for Open XML conversion
• Analysis highlights potential issues
Office Document AssessmentDocument discovery with OMPM
• Scanning and reporting tools• Command-line scanner execution• Can scan network shares, WebDav
shares, and client systems• Aggregates scan results in a SQL or
SQL Express database• Indicates potential compatibility issues
IF legacy documents are converted to the 2007 XML format
• Scan can be executed locally or from central server
• Scanner functions controlled by admin settings in the config file
• Is not a general-purpose macro scanner
Migration
PlanningManager
Desktop
File Server
SharePoint Server
Using OMPMConsiderations for OMPM usage
• Use the tool to target potential file compatibility issues
• Don’t plan to scan your entire environment• Target representative content groups• Don’t panic – not all warnings are show
stoppers• Plan time to analyze the results
− Is the content relevant− What is the business impact
Suite Overview: Scanner
• Light and Deep scanning modes− Light: Collects file properties− Deep: Cracks open files and looks for issues
• Deployable via SCCM or login script• Can scan servers, SharePoint, and other WebDav
enabled systems• Scan controlled by config file – offscan.ini
Suite Overview: Database
• Provides SQL database to store scan results− SQL 2000, 2005 and 2005 Express
• Command line tools to provision database and import data
• Scan logs are imported for analysis – xml results in CAB file
• Plan retrieval process to minimize network load
Suite Overview: Reporting
• Access reporting tool connects to scan DB− Identify key issues and target migration testing− View reports by file, machine, workgroup,
issue type, etc.• Also review scan coverage
Suite Overview: Companion Tools
• Optional tools to update content• Version Extraction Tool (VET)
− Separates multiple .doc versions of document
• Office File Converter (OFC)− Bulk converts Office 97-2003 files to
Office 2007 Open XML format− Convert on file share or desktop− Source content can be maintained
What’s New for OMPM in 2010
• x86->x64 migration• Macro scanning• SQL 2008 compatibility• Improved performance• Lots of small improvements and new
features• New version aligned with 2010• Start analysis with current tool
X86 → x64 Migration
• New scanner module for migration issues between x86 and x64 (XL, Access, PPT, Word)− Scan any 97-2010 file for x86->x64 migration− Scans
− 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
OMPM FAQs
• Are macros scanned?− Yes – all documents with a VBA project are
identified, additional filter possible for macros• Maximum number of scans for analysis?
− 1 million logs – divide analysis into multiple scan databases or directly query database
• Is Office required on the computer being scanned?− No, Office is not required for the scan
• Will a file conversion update/loose file metadata (last change, author, etc.)?− No – data is preserved from the original
Office Migration Planning Manager ResultsExample enterprise scan for file readinessThe Scan• 39 terabytes scanned • 95 million files scanned• 5.8 million Office files found• Geo-distributed servers
Results Summary• Very low issue rates
− 0.00004% red issues− 0.0022% yellow issues
• Significant time to plan & coordinate scans
• Actual scan completed in 30 days
Conclusions• Start assessment early• Tool is enterprise scale• Leverage best practices to run tool at scale• Tool best used to obtain quantitative assessment• Compatibility Mode actually addresses most issues• Issue perception larger than actual issues found
Migration
• Proper planning analysis will enable targeted migration activities
• Migration activities require developer and IT Pro involvement
• Migration does not need to be a single big-bang event
• Testing is key to verify migrations are complete
User State Migration Tool 4.0
• Scriptable tool providing migration support
• Tool is delivered with Windows and is primarily used during OS migrations
• Tool includes packed Office application migration rules including:− Email Settings− Dictionaries− Templates− Documents
• Application configuration will be revised
Office 2010 Compatibility Inspector Tool• Act on potential issues identified by
OMPM• Integrates into Office VBA and VS(TO)• Code changes needed for 64 bit
migration• Enables user comment/mark those
areas in the code for update • Summary of scan result provided• A detailed report for review• Scan performed per file• Tool in testing phase
OMPM for Migration
• OMPM also is used for migration• Office File Converter is leveraged to
bulk migrate files• Total migration of files is not
recommended• Use planning process to selectively
migrate key documents based on business value and frequency of use
Configuration
• Configuration will develop the package for deployment
• Consider the activation strategies as it will impact the package to be created
• Tools are provided to simplify the customizations for the specific deployment
Realizing Office 2010Configuration & Management
Deployment• Many methods for delivering install packages (caching, MSI, scripts, SCE/SCCM, virtualization)• Deployment method influences degree of control & monitoring
Build Package• Define applications and preference• Bundle supporting elements, i.e.
• Add-ins, languages, guides, etc.
Control Environment• Enforce system wide policy• Control Office application @ a granular level – over 4000 objects
• Office Configuration Tool(OCT)• Config.xml
• Group Policies – Office admin templates
Guidance•Office Resource Kit (ORK)•Security Guide
• TechNet Community• TechNet Resource Centers
Licensing
• Microsoft Office licensing is evolving• Software Protection Platform (SPP)
provides two technologies for Enterprise and Corporate customers to manage their software licenses:
− Key Management Service (KMS) − Multiple Activation Key (MAK)− A combination of KMS and MAK
• Mitigates risk of improper use of software
Volume Activation
• Activation for all VL Office 2010 client products− Provisioned and managed by IT pros− Transparent end user experience
• Activation not required for Office 2010 server products
• Tools− VAMT 2.0− Software licensing management script
Volume Activation & VAMT 2.0
• Volume Activation
− Required for all Office 2010 client products
• Activation methods
− Key management service (KMS)
− Multiple activation key (MAK)
• Tools
− VAMT 2.0
− Software licensing management script
KMS Host
• One KMS host for Windows and Office• KMS host
− KMS activates computers on a local network− Eliminates need for individual computers to connect
to Microsoft for activation• Software licensing management script
− Manage KMS host− Manage KMS clients− Monitoring
• Highly scalable service (100’s of thousands)− MSIT: Co-host, 10’s of thousands
Operating System Office
Windows
Windows Server 2003 √ √
Windows Vista √
Windows Server 08 √
Windows 7 VL √ √
Windows Server 2008 R2
√ √
Volume Activation Management Tool (VAMT)• VAMT Key Features
− Search in the enterprise network− Deploy MAK product keys to clients− Proxy MAK activation− Trigger MAK online and KMS activations
• MMC snap-in− VAMT 1.x is standalone tool
Office Customization Tool
• The primary tool for most customizations
• Saves customizations in a Setup customization (.msp) file
• Customizes the following areas:− Setup − Features− Additional content− Microsoft Office Outlook− Mange Registry settings
• 2010 Deltas include SPP support
OCT 64-Bit SupportLeverage existing packages to create 64-bit deployments
• On an x64 machine, users can use the 64-bit OCT
• 32-bit patches cannot be applied to 64-bit Office products
• Users customize once for a mixed environment:− The 32-bit OCT can import 64-bit patches and
apply them to 32-bit products, and then export 32-bit patches as 64-bit patches
− The 64-bit OCT can import 32-bit patches and apply them to 64-bit products, and then export 64-bit patches as 32-bit patches
Config.xmlAdditional controls to customize the deployment package
• Secondary tool for customization of the Office package
• Use OCT first then use Config.xml to override MSP Settings
• Only way to deploy Language Packs• Enables chaining of deployments
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
• Over 4000 group policy control objects
DeploymentMethods to manage the deployment
System Center
Configuration Manager
Virtualization
Group Policy Startup Scripts
Network Share
Managed Deploymen
t
End User Readiness Intranet
• A pre-loaded intranet starter site will be made available for enterprises to deploy
• The content will pull from the best of the Office Online content providing IT Pros the ability to setup a internal readiness site
• The site can be customized to fit the enterprise
• Technical deployment of site has minimal requirements
• Goal is to minimize end user readiness requirements for deployment
OCT for Operations
• OCT is not only used for initial deployment• OCT can be leveraged to package future
updates• OCT can be used to package future support
pack updates and control features
Resources
• Where to go for each of the toolsMAP: http://microsoft.com/map USMT: http://technet.microsoft.com/en-us/library/dd560750(WS.10).aspxOffice Activation Technologies: http://technet.microsoft.com/volumeactivation OMPM: http://technet.microsoft.com/en-us/library/dd901407.aspx (Office 2007 Link)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=enELF: http://www.microsoft.com/technet/desktopdeployment/bdd/ELF/Welcome.aspx
OperationsDeploymentConfigurationMigrationPlanning
Planning & Deployment Tools
Guidance• Office Resource Kit (ORK• SA Benefits
Compatibility Inspector
Enterprise Learning
Framework
Microsoft Assessment &
Planning Toolkit
Office Environment Assessment
Tool
Office Migration Planning Manager
Office Configurati
on Tool
Config.xml
Group Policy
SPP- VAMT, KMS
Office Configuration Tool
End User Readiness
SCCM
Start-up Script
Virtualization
• Security Guide• Office OnRamp
• TechNet Resource Center• TechNet Community
© 2009 Microsoft Corporation. All rights reserved. Microsoft 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.