If SharePoint had Warning Labels

If SharePoint had Warning Labels

By Joanne Klein

About Me

- SharePoint Architect at Conexus Credit Union

- Independent SharePoint/O365 Consultant

- Saskatchewan SharePoint User Group

- Worked with SharePoint 2007/2010/2013 and Online in O365

- Hats: End-User, Power-User, BA, Dev, Administrator, IT-Pro

- Certifications:- MCITP, SharePoint 2010 Administration- MCTS, SharePoint 2010 Developer

Most importantly… the school of hard knocks!!!

Work like a Network

- SharePoint Community www.skspug.ca

- Twitter: @JoanneCKlein #SPHelp

- Blog: JoanneCKlein.com

- Slide deck will be posted on JoanneCKlein.com

About You

What size of organization do you work in?

What version of SharePoint do you use?

About this talk

• My "Pay it Forward" SharePoint talk

• Mostly non-technical

• Comes from personal experiences

*

The Promise of SharePoint

• Intranet/Extranet• Collaboration• Content and Document Management• Regulatory Support Features• Business Process Automation• Business Intelligence• Leverage data outside of SharePoint • 3rd party products

*

My "Warnings"

Benefit

Warning

ExamplesRemediation

“Installing SharePoint is easy”

- Wizards make it easy

- No Training? You can still get SharePoint up-and-running!

- Use existing staff to install- Windows Server Administrator, SQL Administrator, .NET

Developer

Benefit

*


• Farm topology?• Hardware/Software requirements• Least-privilege permission model• Database GUIDs• SQL setup• Enabled features

Warning

*


Installing SharePoint is just the beginning!

• Patch Strategy• Back-ups• Performance monitoring/tuning• Dev/Test/QA environment

Warning

*


• Training

• Learn PowerShell

• SQL Alias (on SharePoint servers)

Remediation

• AutoSPInstaller: https://autospinstaller.codeplex.com/

• Happy SQL = Happy SharePoint• Best Practises for SQL Server in a SharePoint Farm:

https://technet.microsoft.com/en-us/library/hh292622.aspx

*

• Service Accounts: 10 for SharePoint farm, 5 additional for BI

https://technet.microsoft.com/en-us/library/hh292622.aspx

“You can customize SharePoint almost any way you want”

Benefit

…given enough time, money, and resources!

• You have a business process that needs automating?• You have a business requirement you would like

automated?

We can build a solution for it in SharePoint...

*


Levels of Development

Level 1: SharePoint UI

Level 2: SharePoint Designer, InfoPath, Workflow

Level 3: Visual Studio: .NET code, javascript, HTML, CSS

*


Comes with a "tax" the company must be willing to pay

• On-premises version upgrade?

• Maintenance and support• Available expertise

• O365 updates

Warning

*


Microsoft quote:"Be thorough in custom web design, development and testing – We know many SharePoint sites are published portals or custom web apps and we are excited about the new features we designed for these scenarios. We encourage you to review the new features and guidance to reduce the amount of custom work you need to do."


• Following recommended Microsoft guidelines• Add-in model rather than farm solutions.• New SharePoint Framework for doing client-side customizations• Office 365 Development Patterns and Practices Guidance• SPCAF – analyze your customizations!

• Understand the out-of-the-box capabilities!• Twitter Poll

Remediation

*

*

“You can make SharePoint look like it's NOT SharePoint”

- You can brand SharePoint so it doesn't resemble the out-of-the-box look of native SharePoint.

- Important for external-facing sites.

Benefit

*

Out-of-the-Box SharePoint Site

SharePoint Home (New for O365)

Branded SharePoint Sites


Microsoft quote: “Use SharePoint as an out-of-box application whenever possible -- We designed the new SharePoint UI to be clean, simple and fast and work great out-of-box. We encourage you not to modify it which could add complexity, performance and upgradeability and to focus your energy on working with users and groups to understand how to use SharePoint to improve productivity and collaboration and identifying and promoting best practices in your organization.”


• Not branding in a supported way

• Interfering with SharePoint functionality

• Branding “Tax”

Warning

*


• Engage skilled expertise to brand SharePoint.

• Consider doing light-weight branding first. (fonts/colours)

• Intranet versus Extranet versus Public-facing site

Remediation

*

“Power Users can build their own solutions”

- Self Serve

- Removes IT bottleneck

- IT can focus on complex deliverables

2Benefit

*


There are fewer controls over what is built.

• No standards!

• “In the wild” - SharePoint V-Next?

• Who supports them?

Warning

*


• Governance to guide/monitor what’s being built.

• Train Power Users!

• Company standards defined.

Remediation

*

“Users can control their own site”

- Users can have their own space in SharePoint to collaborate with others and to use in any way they want to meet their own goals.

- By delegating site ownership to the individuals who control the content of the site they become self-sufficient.

Benefit

*


Watch that users don’t shoot themselves in the foot!

• Exceeding URL lengths

• Treat document libraries as network shares• Threshold limits

• List/library setting changes • Deleting the site • Removing their own access

Warning

*


• Governance plan

• Training material and options:• Video tutorials• Documents• PowerPoint presentations• Targeted webparts

• Train your site owners!!!!

Remediation

*

“Granting permissions is ultra flexible”

- Granular permissions: site, library, list, folder, item level.

- Permissions can utilize:- Active Directory groups- SharePoint groups- Individual accounts

Benefit

*


Left unchecked, this can become a support nightmare.

• No way to see "Employee x” all access• Breaking inheritance and performance

Warning

*

• Employee leaves• Beware of Item level permissions


• Governance• Standardize groups (visitors – members – owners)

• Invest in 3rd party product• Break permission inheritance as infrequently as possible• Assign permissions at highest-level possible• Permissions can drive layout (segment by security level)

• Centralize security administration

Remediation

*


Active Directory Groups

• Administered by IT Staff• Can Nest AD groups

• SharePoint Owners can’t see who’s in an AD group

• Can’t use with Person/Group column

Remediation

*

SharePoint Groups

• Administered by SP Owners• Cannot nest SharePoint groups

• SharePoint Owners can see who’s in a SharePoint group

• Can use with Person/Group columnHYBRID

APPROACH!

“It’s a great place to store documents”

- Drag-and-drop- Versioning- Check-in/Check-out/Approval/Publish- Familiar folder structure- Record declaration- Real-time co-authoring- Browser-based office documents

Benefit

*


Lack of planning results in a terrible end-user experience and can leave end-users frustrated with SharePoint.

• No Information Architecture• No Corporate Taxonomy• Expensive network share!

Warning

*


• Define Information Architecture

• Decide on IA Features

Remediation

*

Site Collections Sites & Subsites

Libraries & ListsMetadata Managed

MetadataContent Types

Content OrganizerContent HubInformation Management Policies


Information Architecture

Corporate Portal

Division Areas

Project SitesTeam/Committee

SitesPersonal Sites

Structure & Governance


• Governance for Information Architecture above the line

• Configure search – “Findability”

• Train content owners - "Putability"

Remediation

*

“Just use search to find what you’re looking for”

- Display search results from across your organization

- Customize search webparts

- Show federated search results

- Preview Office documents

Benefit

*

Custom Search Results

SearchPreview


Search is only as good as Information Architecture• No metadata/No content types - search results will

definitely suffer.

• OOS required for Document Preview **On-Premises

Warning

*


• Define Information Architecture

• Customize your search results

• Install Office Online Server (previously Office Web Apps) in your on-premises environment

Remediation

*

“Build it and they will come”

- Leading-edge capabilities in O365- Frictionless collaboration- Work from any location on any device- Both inside and outside your organization

- Easy to sign-up for an O365 Tenant

Benefit

*


• Don't assume your employees will embrace the new features and know how to use it effectively.

• No guidelines and governance? Confused staff

• The “Wild West of collaboration”

• What features are available and what to use when? (individual, group, and organizational level)

Warning

*


• First Release program – sign up!

• Don't just rely on a one-time training event• Executive-level support is critical

Remediation

• Organizational Change Management

• Engage the early adopters and innovators in your organization

*


Remediation• "When to Use What in O365" whitepaper

by Richard Harbridge and Kanwal Khipple from 2ToLead

• SharePoint• OneDrive for Business• Yammer• Outlook/Exchange• Skype for Business• O365 Groups• Delve Boards• Video Portal

http://www.2tolead.com/whitepaper-when-to-use-what-in-office-365 *

Extra: How do I Resource a SharePoint team?

SharePoint Architect *Information ArchitectSearch ArchitectSharePoint Back-end DeveloperSharePoint Front-end DeveloperSharePoint AdministratorBusiness Analyst

Beware of Multiple Hats!Power UserOrg Change ManagerBusiness Intelligence AnalystWindows Server Administrator *SQL Administrator *Security/Identity AdministratorNetwork Administrator

Extra: What’s in a SharePoint Governance Plan?

• Site Creation• Permission Management• Information Architecture• Site Lifecycle and

Retirement

• Customization• Navigation• Search• Roles & Responsiblities

Even with these warnings, SharePoint is still Awesome!

• Future of SharePoint event – Microsoft has stated SharePoint is a focus for them – there WILL be another version of on-premises SharePoint!

• Flexible and powerful product that does many things VERY well.

• "Feature Packs" - O365 capabilities will be brought down to On-Premises SharePoint!!!

*

Thank you and Happy SharePointing!

Slides posted at JoanneCKlein.com

@[email protected]

SK SharePoint User Group: www.skspug.ca@SKSPUG

Reference LinksTodd Klindt’s service account recommendations

http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=391

Best Practises for SQL Server in a SharePoint Farmhttps://technet.microsoft.com/en-us/library/hh292622.aspx

AutoSPInstallerhttps://autospinstaller.codeplex.com/

O365 Developer Patterns and Practices http://dev.office.com/PNP

SPCAF (SharePoint Code Analysis Framework)https://www.spcaf.com

When to Use What in O365 whitepaperhttp://www.2tolead.com/whitepaper-when-to-use-what-in-office-365

Date post:	08-Feb-2017
Category:	Technology
Upload:	joanne-klein
View:	326 times
Download:	0 times

If SharePoint had Warning Labels

Technology