SharePoint Thing a Day 001 – Governance

December 1, 2017 by Joel Jeffery

Avoid death by fileshare!

SPThing – 001 – Get Mandate – SharePoint Thing a Day

A post shared by JFDI Consulting (@jfdiconsulting) on Dec 1, 2017 at 2:37am PST

SharePoint, Teams, Planner and Office 365 projects need executive sponsorship. Without a mandate from above, adoption will falter or fail.

If you allow a gap between what you want users to do, and what they technically can do, users will work around what you put in place.

Get mandate; state policy; win adoption.

#spthingaday

View

Open

#spthingaday 003 - Information Architecture. Folde

#spthingaday 003 - Information Architecture. Folders are evil. Use metadata. #SharePoint, #Office365..
On a fileshare, all you have is path and filename. That's the only axis by which you can classify your stuff. So you nest folders, within folders, within folders. Then you pack the filename with extra bits of information - like the initials of the last editor, or the version number.
You don't need to do this in SharePoint. Use metadata.
Add columns to your libraries. Text columns, number columns, choice columns, managed metadata columns. Each file can have several of these values simultaneously. But a file can only live in one folder at a time.
Use metadata.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement ...

14 0

View

Open

#spthingaday 001 - Governance. Avoid death by file

#spthingaday 001 - Governance. Avoid death by fileshare #SharePoint, Teams, Planner and #Office365 projects need executive sponsorship.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement ...

15 0

View

Open

#spthingaday 060 - SharePoint Search. Changing the

#spthingaday 060 - SharePoint Search. Changing the Search Topology. #SharePoint, #SharePointSearch.. The Search Service in SharePoint on-premise is made up of six components.

Crawl, Content Processing, Index, Analytics, Query and Administration.

Each of these components can be placed on one or more servers in your Farm.

To make any one Search component support high availability, you need to make sure there are at least two servers in your Farm running it.

SharePoint Server 2010 had only 3 types of component, and Microsoft let you manage their placement via Central Admin, in the browser.

From SharePoint 2013 onwards, this was deemed too difficult to express graphically.

For SharePoint 2013 and 2016, topology changes need to be made via PowerShell.

Tomorrow, we'll look at just what PowerShell cmd-lets you need to use.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement ...

12 0