The 5 Critical Pillars of Office 365 Readiness
•Download as PPTX, PDF•
1 like•844 views
When moving to cloud services such as Office 365 IT professionals are required to appropriately prepare existing on-premises technologiesand optimize for the transition of their business systems to the cloud. In this webinar Eric Shupps (MVP) and Adam Levithan will discuss the 5 critical pillars for a successful move to Office 365. From network and systems optimization through to handling customizations, Adam and Eric will share their many experiences - warts and all. When moving to cloud services such as Office 365 IT professionals are required to appropriately prepare existing on-premises technologiesand optimize for the transition of their business systems to the cloud. In this webinar Eric Shupps (MVP) and Adam Levithan will discuss the 5 critical pillars for a successful move to Office 365. From network and systems optimization through to handling customizations, Adam and Eric will share their many experiences - warts and all.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to The 5 Critical Pillars of Office 365 Readiness
Similar to The 5 Critical Pillars of Office 365 Readiness (20)
More from Adam Levithan
More from Adam Levithan (20)
Recently uploaded
Recently uploaded (20)
The 5 Critical Pillars of Office 365 Readiness
- 1. 1 5 Pillars to Optimize Office 365 Readiness Eric Shupps, SharePoint Server MVP Adam Levithan, Product Manager
- 2. 2 Agenda Why Readiness? • Supporting Critical Business Initiatives • People Care 5 Pillars • Architecture • Network • Database • Customizations • Add-Ins/Apps
- 3. 4 Why Readiness? Automated business processes with performance expectations Reduction in speed/ Outage causes loss of revenue Non-compliance drives organization out of business Supporting Critical Business Initiatives
- 4. 5 Why Readiness? Business User • Want system to work • Experience Productivity Loss SharePoint Team • Receive the first call • Hands-on troubleshooting Information Technology • Responsible for entire system • Dependent on SharePoint Team People Care
- 5. 6 Readiness - Monitoring Your Efforts Gain early warning of developing performance issues through alarms and alerts Understand the relationship between SharePoint infrastructure and applications Make the correct decisions about adding or removing servers to the SharePoint farm based on performance Analyze historical information for trending, capacity planning, and to quantify the impact of future changes
- 6. 7 5 Pillars of Office 365 Readiness
- 7. 8 Approach to Optimization & Readiness Add-Ins/Apps Customizations Database Network Architecture
- 9. 10 Architecture Database Users Search BI Service Apps Web Web Database Distrib Cache Distrib Cache Office Web Apps Workflow Apps Azure O365 2013 Hybrid Yammer Delve Power BI
- 10. 11 Network Optimization Capacity Load Traffic Isolation • Web • Database • Service Applications • Search • Authentication Indexing
- 11. 12 Network Optimization Migrations/Initial Data Transfer • Internal and External Bandwidth • ExpressRoute • Azure Storage Cloud • Content Delivery Network • Geographic Distribution (WAN link balancing) • Page contents
- 12. 13 Database Optimization Migration • Content archiving • Page cleanup • Data purging • Shrink files • Versions! Operations • Disk I/O • Index maintenance • Auto-growth • Quotas Disaster Recovery • Database size • Available bandwidth
- 13. 14 Database Distribution • Provisioning overhead • Data isolation • Content storage • Query locks and throttling • Utilization • Recoverability • Resource Consumption • Availability System Services Site Collections Lists
- 14. 15 Database Fundamentals Physical hardware resources Network connectivity Disk specifications File location Index maintenance High availability
- 19. 20 Customizations Page Components • Markup • Navigation • Images • Scripts • Code • Web and App Parts Branding • Styles • Resources • Master Pages • JavaScript Injection
- 22. 23 Add-Ins/ Apps Dependencies • DNS • Infrastructure • Authentication • Certificates • Client Configuration • Bandwidth Hosting Model • Provider Hosted • SharePoint Hosted API • CSOM • JSOM • REST
- 23. 24 Next Steps What are your strongest pillars? Where do you have the most control to impact? How do you monitor and optimize the 5 pillars? What happens when you get to Office 365?
- 25. 26 Office 365 Content Summary
- 26. 27 QUESTIONS
- 27. 28 Free 14 Day Trials Preparing for the Cloud – Diagnostic Manager • Identify the most common problem areas affecting SharePoint performance • Proactively discover and diagnose SharePoint performance and availability http://pages.metalogix.com/WC_Diagnostic_Manager_Trial_Download_LandingPage-TrialDownload-Diagnostic-Manager.html http://www.metalogix.com/Products/essentials-for-office-365/overview In the Cloud – Essentials for Office 365 • Gain valuable insight into the state of your environment including trends in site and user activity, data growth, license deployment and usage, and permissioning and sharing settings.
Editor's Notes
- ADAM Critical SharePoint is being used to support complex customizations and workflows, as a result the business users have expectations for the system’s performance. Plan future SharePoint needs based on metrics supporting growth and performance. SharePoint has had an unexpected outage and it’s hard to understand the cause at a single point in time. (Network, Server, SQL)
- ADAM The business user expects perfect and consistent service and when things go wrong it should be easy to fix Who They are Not experts Just want it to work so they can do their day job Impact Productivity loss Frustration with performance and outages Damage to brand IT is held/measured based on an SLA Who they are Expectation of service which is difficult to manage Lack visibility and insight Lacks factual data Mostly hearsay or word or mouth Impact Noise and pain as a result Financial penalty impacts and scores Loss of credibility The SharePoint team experienced staff, funding, tools and process to proactively manage capacity and performance identify problems, troubleshoot and find root cause Provide tangible proof of problem Especially when its not a SP problem Network of storage Nasty site customization or list Impact act proactively - instead reactive cant predict impact of changes waste time and resources finding root cause loose credibility
- Provides IT and business with factual reporting against SLAs (Confidence IT / vender is delivering) Removes FUD from conversation Enables IT / SharePoint team so they are able to: Assessing impact of changes in Quality Assurance Visibility into operational issues Proactively monitor and prevent capacity and performance issues before they happen Alert on issues Record and send events to helped desk software Report on performance and capacity / trends, predict impact of changes Factual data and no pure opinion – substantiated information Demonstrates competence Provides techs with visibility into Health regarding the Physical hardware and OS – CPU, Disk, LAN I/O etc. Application Server and SharePoint – key IIS and .Net (pages served, .Net Garbage collection etc.) SQL Server – disk I/O, buffering etc.
- Do you have specific SLAs for SharePoint performance, uptime or response times How happy are your users with the response time of SharePoint Can you tell if there are issues with Search indexing How long does it take you to isolate performance issues How do you know if SharePoint is up and running well How do you know if you are up to or at capacity How do you identify issues that may affect SharePoint performance or bring it down
- ADAM & ERIC
- ERIC
- ERIC
- ERIC
- ERIC Physical hardware resources, network connectivity, disk size and speed, location of data files, configuration of shared storage—all aspects must be taken into consideration based on the size of the farm and the projected amount of data. SharePoint is both read and write intensive, so separating the I/O operations onto separate disks prevents excessive thrashing and cache hits Suggest - one set of disks for search databases, one for temporary databases, and still another for content databases Pre-size the databases up to the maximum recommended size (200GB) if space is available and set autogrowth to a fixed size (e.g. 10MB or 20MB). This will prevent SQL from expanding databases unnecessarily and insure that growth happens in a manageable fashion Defragment Database Indexes Indexes can become fragmented over time as new INSERT, DELETE and UPDATE operations are performed Plan for regular maintenance operations which include index defragmentation
- ERIC