The team at EPC Group approaches the architecture and design of SharePoint 2013 and/or Office 365’s Information Architecture using a the three-prong approach that provides placeholders for the requirements that must be documented but also sets expectations for the SharePoint project team to design an IA that is scalable and has organization’s long-term SharePoint roadmap in mind
Ensuring Your System & Information Archiecture Architecture Strategy Aligns with Your SharePoint Roadmap When an organization is near the point of kicking off and performing a upgrade and/or migration initative to SharePoint 2013 and/or Office 365 , it is key to ensure core elements have been designed and put in place to meet not only the current needs of the organization over the next 12 months but for at least the next 24-36 months via a SharePoint roadmap
Understanding the Underlying System Architecture Behind My Sites & Communities in Office 365 & SharePoint 2013 When an organization’s deploys My Sites for their users, the underlying SharePoint 2013 system architecture create a web application, a My Site host site collection, an individual site collection, and several SharePoint service applications and features. Note: The Office 365 | SharePoint Online architecture does differ from that of an on-premise SharePoint 2013 deployment but I have covered the major topical areas for both below
Storage Design of SharePoint 2013 and Hybrid Office 365 Environments When looking at storage in terms of the actual system architecture design perspective , the following initial items should start this conversation: • How has storage been allocated for this effort or what may be available for this initiative?
The SharePoint System Architecture roadmap components must be developed by the business and functional requirements of the information architecture which contains the planning for sites, document libraries, and ultimately the content
1 Comment - no search term matches found in comments.
A lot of IT organizations are playing catch-up around governance and their information management policies and have pushed back on BYOD due to the added complexity it brings and ultimately forces specific polices to be approved
This post is meant to provide you with a visual overview of the underlying scalability considerations and related best practices for a Hybrid SharePoint 2013 and Office 365 Environment . SharePoint Farm Resource Hierarchy SharePoint 2013 | Hybrid Office 365 Web App Resource Hierarchy Deployment Impact Examples - IIS Reset (EPC Group Example) Deployment Impact Examples- App Pool Reset (EPC Group Example) Maintenance Windows (Backup, code promotion, etc.) Understanding Isolation Modes in SharePoint 2013 & Office 365 Hybrid Deployments In SharePoint 2013: Each “customer” = one site collection under managed path Similar to today Each Web Application = one app pool Similar to today Each Web Application = one URL Similar to today Exception Process for Host Header named site collections (vanity URL’s) Along Side or in an Office 365 Hybrid Deployment: BYO Servers Leverage existing architecture Hybrid Considerations (Seamless SharePoint 2013 On-Prem \ Office 365 Cloud Search Integration) Scaling Web Front-ends and Understanding When to Scale App Scale and Tipping Points EPC Group’s Nationally Recognized Practice Areas EPC Group leading SharePoint , Office 365 , Infrastructure Design and Business Intelligence Practice areas continue to lead the way in providing our clients with the most up-to-date and relevant information that is tailored to their individual business and functional needs. Additional "From the Consulting Trenches" strategies and methodologies are covered in EPC Group's new book, " SharePoint 2013 Field Guide: Advice from the Consulting Trenches" covering not only SharePoint 2013, Office 365 and SharePoint Online but Information Management, ECM\RM and overall compliance strategies in this ever changing world of " Hybrid IT
So you have a very good and well established SharePoint application and all is going well but it is now 2013 and Microsoft have done again; they have gone out and release yet another version of Microsoft SharePoint which is SharePoint 2013. And now you feel the need to migrate your data to the new version of SharePoint then you need to look no further to obtain more information Because that is what this article is all about
Overview With the SharePoint Server 2013 Preview being released yesterday there are a lot of organizations who are currently involved in large SharePoint 2010 deployments who are wondering how best they can adjust or minimize any system architecture or information architecture changes as well as governance updates to their current initiative. I have had the pleasure of being able to test SharePoint Server 2013 for about the past year and with the preview and public information becoming available I wanted to put together this article to cover some of the major changes that are coming with SharePoint Server 2013 (also SharePoint Foundation 2013) and things for you to think about in your current or planned SharePoint 2010 implementation. Due to some release information restrictions I will use a lot of information verbatim that Microsoft released publically yesterday but it is key to go with a Hybrid SharePoint Deployment methodology in your current SharePoint 2010 deployment to adapt properly to a future upgrade of SharePoint 2013
1 Comment - I was a little bummed after playing with 2013 for a week now to see that the ECM functionality is not substantially changed...I did several tests of importing 2010 taxonomies into 2013 and it worked like a charm!
SharePoint 2013’s Search uses a componentized model that is based on a Shared Services architecture