1 / 55

Microsoft Office 2010: Deployment Techniques

Microsoft Office 2010: Deployment Techniques. Renato F. Giorgini. Evangelist IT Pro Microsoft. OFF309. IT Pro Trainer. Nicola Ferrini. Agenda. Introduction Office 2010: 32-bit and 64-bit Product Activation: KMS & MAK Office Migration Planning Manager (OMPM)

illias
Télécharger la présentation

Microsoft Office 2010: Deployment Techniques

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Microsoft Office 2010: Deployment Techniques Renato F. Giorgini Evangelist IT Pro Microsoft OFF309 IT Pro Trainer Nicola Ferrini

  2. 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!

  3. Planning & Deployment Tools Planning Migration Configuration Deployment Operations Assessment & Planning Toolkit User State Migration Tool SPP- VAMT, KMS SCCM Office Environment Assessment Tool Office Configuration Tool Virtualization Office Configuration Tool Office Migration Planning Manager Config.xml GPO Start-up Scripts Compatibility Inspector Group Policy End User Readiness Enterprise Learning Framework Guidance • Office Resource Kit (ORK) • SA Benefits • Security Guide • Office OnRamp • TechNet Resource Center • TechNet Community

  4. When Support Ends for Previous Versions

  5. Office 2010: 32 and 64 bit

  6. OS support for Office 2010 – Windows Client • 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-system-requirements.aspx • http://technet.microsoft.com/it-it/library/ee624351(en-us,office.14).aspx

  7. OS support for Office 2010 – Windows Server • 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-system-requirements.aspx • http://technet.microsoft.com/it-it/library/ee624351(en-us,office.14).aspx • * = Needs MSXML 6.0

  8. 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...)

  9. Product Activation:KMS & MAK

  10. 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

  11. Office Migration Planning Manager(OMPM)

  12. 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

  13. 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

  14. 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

  15. Demo: OMPM

  16. Office Customization Tool(OCT)

  17. 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

  18. 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

  19. Demo: OCT

  20. Config.XML

  21. 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

  22. Demo: Config.XML

  23. Managed Deployment

  24. Deployment options http://technet.microsoft.com/en-us/library/ee683866(office.14).aspx Note: Group Policy software installation (GPSI) is not supported.

  25. 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

  26. 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

  27. 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

  28. Demo: System Center

  29. Deployment with Application Virtualization(App-V)

  30. 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

  31. Benefits Of App-VRun 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

  32. App/OS Model Comparison Traditional App/OS Model Virtualized App/OS Model

  33. 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

  34. Application Virtualization running… Operating System Read Only System Files (Registry, .ini, DLL, etc.) Read & Write System Services (cut and paste, OLE, printers, etc.) Read & Write Virtual Environment (Registry, .ini, DLL, Group Policy, etc.) Application Profile Data Read & Write

  35. 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

  36. Improved Application Virtualization SupportTighter 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: • SharePoint • Directly open/edit/save hosted documents • OneNote • Send to OneNote print driver • All • Activation model support • Outlook • Fast Search using Windows Desktop Search • URL Protocol Handlers (Mailto, feeds, webcal(s)) • Send to Mail integration • Enable advanced account configuration

  37. Will Office 2010 be supporting virtualization? • YES...and not exactly Office 2007 Office 2010 Office 2010 Virtualized Office 2007 App. A App. B App. C App. A App. B App. C Virtualized Office Redist Virtualization Agent* Virtualization Agent* On machine Operating System Operating System On machine Hardware Hardware

  38. Well Yes…. 1. We’re building the Office “redistributable”? The virtualization enabler “bits” for Office 2010 • SPP Licensing components • Windows Desktop Search for Instant Search in Outlook • SharePoint Proxy (so virtualized office can edit documents hosted by SharePoint) • URL protocol handers (mailto:, feed, feeds, stssync, webcal, webcals) • Filters for office document indexing • (Virtual) Mail Control Panel applet (needed for some advanced account configuration scenarios) • Simple MAPI proxy (ex Right click on file, Send To -> Mail) • Send to OneNote Printer driver 2. Work has been done to make Office 2010 run faster when virtualized

  39. 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

  40. Demo:Application Virtualization

  41. Reducing Application Conflicts 3rd party app .osd and .ico .osd and .ico .OSD and .ICO .sft and .sprj Manifest.xml Manifest.xml Application Virtualization packages contain the complete environment for the application Potentially conflicting applications have their own environment ü ü .sft and .sprj Applications in a suite can share the environment .OSD and .ICO ü

  42. Side-by-Side execution

  43. Demo: SSxS(Super Side by Side) 

  44. Application Updates Update • Updates • Update once on server • Seamless update to clients

  45. Demo: Dynamic Suite Composition

  46. 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

  47. Demo: Presentation Virtualization

  48. Group Policy Customization

  49. 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

  50. Demo: GPO

More Related