Download to read offline
![Scripting for SharePoint Online is more complex than for SharePoint On Premises
EXAMPLE: GET LIST ITEMS
C:> Get-SPList –url “http:/site/web” –List “Invoices” C:>$site = Get-SPOSite –Identity “http://site”
C:> $web = $site.Webs[“web”]
C:> $ctx.Load($list)
C:> $list = $web.List[“Invoices”]
C:> $ctx.ExecuteQuery()](https://image.slidesharecdn.com/bestpracticesfordeployingsharepointend-to-end-170513110912/85/Best-practices-for-deploying-share-point-end-to-end-14-320.jpg)
Uploaded byHaniel Croitoru
Best practices for deploying share point end to-end
The document outlines best practices for deploying SharePoint, emphasizing the importance of various deployment methods, including PowerShell and automation tools like AutoSPInstaller and DSC. It discusses factors to consider, such as technical constraints, deployment frequency, and complexity, while providing a strategic approach to building and managing SharePoint sites effectively. The content includes insights from a lead consultant with expertise in Office 365.
More Related Content
Similar to Best practices for deploying share point end to-end
![[Pinto] Is my SharePoint Development team properly enlighted?](https://cdn.slidesharecdn.com/ss_thumbnails/pfiteaf0tvqlojwipmpj-signature-d4523b3bf020616e67040d2a940ba8bf9aeab187b20da49956548f98de22ea12-poli-180606121949-thumbnail.jpg?width=640&height=640&fit=bounds)
Best practices for deploying share point end to-end
- 1. Best Practices forDeploying SharePoint End-to-End What You Need To Know By: Haniel Croitoru
- 2.
- 3. HANIEL CROITORU I’m passionate aboutprocess automation, and I work at . LEAD CONSULTANT | OFFICE 365 MVP | SPEAKER
- 4. DEPLOYMENT METHODS LEVERAGING POWERSHELL CHOOSINGWHAT TO USE MY SECRET RECIPE
- 5. Strategy for deployingSharePoint Online sites successfully in a repeatable fashion using little effort
- 6. Deployments involve morethan just code TYPES OF DEPLOYMENTS Infrastructure Deployment Solution Deployment Content Deployment Brian & Nik Lalancette Charlebois Automating SharePoint: AutoSPInstaller vs DSC 11:30am at Salle SII Canada
- 7. Deployments involve morethan just code SOLUTION DEPLOYMENTS BRANDINGCONFIGURATIONINFORMATION ARCHITECTURE
- 8. Deploying a newSharePoint site requires several focus areas to be considered SAMPLE DEPLOYMENT Content Types Lists Site Columns Content Configurations Taxonomy (Managed Metadata) Taxonomy-based Site Columns Libraries Branding
- 9. SharePoint Site Settingslets you manage most deployment activities SHAREPOINT UI
- 10. Provides additional flexibilityin configuring and customizing SharePoint SHAREPOINT DESIGNER
- 11. Scripts enable youto automate deployment steps POWERSHELL
- 12. DEPLOYMENT METHODS LEVERAGING POWERSHELL CHOOSINGWHAT TO USE MY SECRET RECIPE
- 13. There is lessmanagement required for SharePoint Online POWERSHELL FOR SHAREPOINT • SharePoint 2007/2010 On Premises • STSADM (SharePoint Team Server Administration) • 181 operations, 69 properties • SharePoint 2013/2016 On Premises • Over 700 cmdlets • SharePoint Online • SharePoint Online Management Shell (https://www.microsoft.com/en- ca/download/details.aspx?id=35588) • 33 cmdlets
- 14. Scripting for SharePointOnline is more complex than for SharePoint On Premises EXAMPLE: GET LIST ITEMS C:> Get-SPList –url “http:/site/web” –List “Invoices” C:>$site = Get-SPOSite –Identity “http://site” C:> $web = $site.Webs[“web”] C:> $ctx.Load($list) C:> $list = $web.List[“Invoices”] C:> $ctx.ExecuteQuery()
- 15. Simplifies your SharePointOnline scripting OFFICEDEV PNP POWERSHELL LIBRARY • Over 160 cmdlets • Encapsulates native SharePoint CSOM Library • Available on both SharePoint 2013 and SharePoint Online • Visit https://github.com/OfficeDev/PnP-PowerShell
- 16. Many scripts aretransferrable between environments OFFICEDEV PNP PROVISIONING ENGINE • Built on OfficeDev Core libraries • Available on SharePoint 2013, 2016 and Online • Model the design of site columns, content types, list definitions, composed looks, and pages • Automates remote provisioning tasks
- 17. DEPLOYMENT METHODS LEVERAGING POWERSHELL CHOOSINGWHAT TO USE MY SECRET RECIPE
- 18. What are thefactors you need to consider? WHEN TO USE WHAT
- 19. Are scripts andSharePoint Designer enabled on your tenant? TECHNICAL CONSTRAINTS
- 20. How often aredeployments performed? Weekly? Seldom? FREQUENCY
- 21. Do deployments requirefew or many items to complete? VOLUME
- 22. Are there manyinterdependent steps involved in the deployment? COMPLEXITY
- 23. USER ACCESS &KNOWLEDGE
- 24. DEPLOYMENT METHODS LEVERAGING POWERSHELL CHOOSINGWHAT TO USE MY SECRET RECIPE
- 25. Based on dozensof successful deployments MY DEPLOYMENTS APPROACH Gather IA Configure Tenant Build Site Master Apply Template Add Content
- 26. Define clients informationarchitecture using Excel, which is familiar to them CAPTURE INFORMATION ARCHITECTURE Content Types Lists Site Columns Content Configurations Taxonomy (Managed Metadata) Taxonomy-based Site Columns Libraries Branding
- 27. Configurations are onlyrequired once per site, unless they are changing CONFIGURE TENANT
- 28. Deployment templates canbe used to quickly deploy new sites BUILD A MASTER
- 29. Content cannot bedeployed using templates and is added at the end of the process ADD CONTENT
- 30. We work hard,we party hard! 5h00 PM 3971 Ontario E
- 31. LEAD CONSULTANT |OFFICE 365 MVP | SPEAKER Thank You! Organizers, SponsorsandYouformaking thispossible. Message Me On LinkedIn or Email linkedin.com/in/hanielcroitoru haniel@2tolead.com Download the full whitepapers at http://www.whentousewhat.com http://Office365Intranets.com
Editor's Notes
- #8 Type of deployments IA Metadata Taxonomy Site structure Configuration Finite set of configurations Today, there are some limitations (e.g. User Property creation) Branding Content Different types have different needs IA – simple, but often high in volume (e.g. building term sets, site columns) Use square corners
- #14 A large number of SharePoint on-prem cmdlets are for things not applicable in SharePoint Online Content database management Web application Central Administration configuration
- #27 Through meetings with clients, define the IA and content Build out the taxonomy, fields, content types, lists, and views