Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Deploying Office 365 Pro Plus @ Windows 10 Partner Technical Bootcamp Microsoft Norway October 2015

1,087 views

Published on

Slides from the session about Office 365 Deployment

Published in: Technology
  • Be the first to comment

Deploying Office 365 Pro Plus @ Windows 10 Partner Technical Bootcamp Microsoft Norway October 2015

  1. 1. Jan Ketil Skanke Microsoft Office 365 ProPlus: Deployment and Management
  2. 2. Maintain critical third-party apps after upgrades Avoid complex and expensive deployment cycles Need more time to test
  3. 3. It’s all about management Better network traffic management Enhanced distribution management Flexible update management Simplified activation management
  4. 4. Current Branch for Business deferred feature updates Challenge Frequent updates put third-party apps at risk and truncate planning and testing. Solution Office deferred updates consolidate and deliver features three times a year. Security updates are still delivered continuously. Validation Three-tiered approach ensures market-driven quality: • Early adopters • Current branch • Current branch for Business
  5. 5. Current Branch for Business 100’s of thousands 100’s of millions 10’s of millions Build vetted through market adoption and feedback Enables IT and ISVs to have early access and validate builds against LOB apps Ensures insight into upcoming features Builds deployed using existing software deployment solutions Your Users
  6. 6. Current Branch Customer experience Features are released to broad market Customers are up to date with features as they are released after broad early adopter validation Opportunity for enterprises to test and validate new features Security updates and fixes are delivered regularly Time Dates are for illustration purposes only
  7. 7. Features are delivered 3 time/year Security updates are delivered regularly for 4 months Business customers on auto-update will be moved to a new branch Business customers can wait to receive feature updates for an additional 4 months, providing access to two branches Validation builds are stabilized and available for testing 4 months prior to declaring as deferred branch Dates are for illustration purposes only Time Current Branch for Business Customer experience
  8. 8. Aligning Office and Windows 10 Current Branch Current Branch for Business Features One branch in market at a time Monthly features, bug fixes, and security patches Two branches available (subsequent branch overlaps preceding branch) Regular security updates Availability Windows 10: 2-3 times a year Office 365: Monthly Windows 10: 2-3 times a year Office 365: 3 times a year, consistent dates Serviceability Windows 10: Approximately 4 months Office 365: 12 months Windows 10: 8 months Office 365: 4-8 months (first 4 months, then another 4 months) Deployment technology Windows 10: WSUS, Windows Update, and Windows Update for Business Office 365: SCCM, Microsoft Intune, third-party software deployment tools Windows 10: WSUS, Windows Update for Business Office 365: SCCM, Microsoft Intune, third-party software deployment tools
  9. 9. Office as a service lifecycle Current branch Current Branch for Business Scenarios Sales force, BYOD, test systems Anyone not using mission-critical systems Anyone not using add-ins Knowledge workers, sales force, road warriors Anyone using add-ins and requiring a slightly slower pace Anyone who should be up-to-date, but not necessarily in the forefront of features Features Available monthly Regular security updates and bug fixes One branch in market at a time Consumed through Office CDN or existing software distribution method Available 3 times per year Regular security updates and bug fixes Two branches available simultaneously Consumed through Office CDN or existing software distribution method Serviceability 30 days Breaking changes addressed; new build deployed 4 months mainstream support, 4 months extended support Security-only updates Support 12 months 8 months
  10. 10. Deploy the product Many options Local installation Network installation Enterprise software distribution Windows image Application virtualization Remote Desktop Services
  11. 11. Installation basics Multiple languages Office Deployment Tool Microsoft Intune SCCM Pre-installed Windows image Microsoft Deployment Toolkit Self-installation Managed deployment Already on device
  12. 12. Local drives and distribution points Local drive or desktop Distribution point or network share Office 365 Content Delivery Network From “here” From “there” From “anywhere”
  13. 13. Office as a service lifecycle Deployment scenarios Desktop SCCM application model Local cache User-targeted Distribution point or network share Streaming installation Binary delta compression Content Delivery Network Streaming installation Users on the go
  14. 14. From “here” Entire source deployed No SourcePath attribute defined Office 365 Deployment Tool (setup.exe)
  15. 15. From “there” Separates setup.exe (1 MB) from source files (1 GB) Defines SourcePath attribute Allows source files to be updated independently Office 365 Deployment Tool (setup.exe)
  16. 16. From “anywhere” “Outsources” distribution infrastructure Doesn’t define SourcePath attribute Always deploys latest build Office 365 Deployment Tool (setup.exe)
  17. 17. Getting ready Update rules Download from distribution point Run from distribution point Detection rules for SCCM Office 365 Office 365 ProPlus
  18. 18. Creating an application Content location Install/uninstall program settings Detection rule Installation behavior Task sequencer Create Deployment Type Wizard Add name, publisher, software version Select language Consider services needed for select groups Manually specify application information
  19. 19. Premade applications “SharedComputerLicensing” Value attribute set to “1” Deployment to all users or a subset Task sequencer Shared computer activation (SCA) Same core source package Three deployment types
  20. 20. Packages and programs Updates in Office 365 ProPlus Automatic updates Turned on by default Office 365 ProPlus updates package Executable file with specific parameters Setting to update to specific version Deployment Wizard Targeted to particular users Validation with push updates
  21. 21. Flexible update management Office deferred updates Challenge Frequent updates put third-party apps at risk and truncate planning and testing. Solution Office deferred updates consolidate and deliver features three times a year. Security updates are still delivered continuously. Validation Three-tiered rollout ensures market-driven quality: • Early adopters • Current branch • Deferred branch
  22. 22. Enhanced distribution management Better integration with SCCM Challenge Use existing tools to consistently deploy and manage updates. Solution Better integration with SCCM 2016 enables powerful distribution features: • Use of application model • Support for distribution points • Support for WSUS notifications Work is ongoing for integration with SCCM 2012. SCCM 2007 will not be supported.
  23. 23. Deployment method MSI Click-to-Run Local installation source Yes Yes Network installation point Yes Yes Group Policy computer startup script Yes Yes System Center Configuration Manager Yes Yes Microsoft Intune Yes Yes Remote Desktop Services Yes Yes Microsoft Application Virtualization (App-V) 5.0 Service Pack 2 Yes Yes Microsoft Deployment Toolkit (MDT) 2012 Yes Yes
  24. 24. Summary Office 365 ProPlus can be deployed through a self-service or managed installation. With flexible deployment options, users can get updates from a local drive, a distribution point/network share, or the cloud. Update packages and programs allow administrators to simplify the update process while maintaining control. Office deferred updates capture ongoing user feedback and lead to market-driven quality. Better SCCM integration means more robust distribution management.

×