Skip to main content

Bad Practice #2: No Governance Plan

This is the bare bones necessities you need to cover for a successful SharePoint implementation. It isn't pretty or well explained, but will get you started in the right direction.

Item/List/Site Recovery – Who is responsible? How will you back them up? Does it work?

Versioning – How many? At least one for backup reasons? Who manages this?

Monitoring – You are monitoring your farm, Web apps, app pools, databases, drives, NICs, zones, firewalls, etc – right?

Reporting – How are you doing reporting on things like performance and security?

Developer Customization – How do you control developer customizations and custom code? Solutions? Features? Both? Ad-hoc? (I hope not! the latter!)

SharePoint Designer Customization – Does everyone have SPD? Is that a good think/

Windows Server configuration management – Who controls the configuration and change management of the server platforms themselves/

Server farm configuration management – How many farm admins do you have? Do you trust them? Are they trained?

SQL Server - Are you monitoring uptime and performance? Are you using multiple databases where it makes sense? What types of drives do they live on? Are you mirrored/clustered? How do you test patches? What’s autogrow set to for logs and data?

Themes – Do you control how many / what themes are available in the sites/

Site Quotas – Do you control how large site collections are? This is the only way to control the 2nd stage of the Recycle Bin, right?

Navigation consistency – Do you need a consistent navigation story for both global and current? How will you accomplish this consistency?

Recycle Bin settings – How large is your 1st stage? Who sees it? How large is the 2nd stage? Who manages and restores from the 2nd stage?

Upload size – What’s your maximum upload size? Why? Will IIS timeout over WANs or sluggish VPNs?

Site and Site Collection Creation – Who creates Site Collections? Sites? Who can delete them? Manage them? Authorize access?

How will your users authenticate? Multiple AuthN sources? How will you accomplish that?

Security - Farm level – Who’s in command? How are you auditing that?

Security - Site Collection Level – Who controls security for site collections? How are you sure/

Authorization Mechanism/training – Do people know how to authorize access within your organization. Are they following the proper procedures, like need-to-know or FOUO?

Search - Farm/SSP Level config and change management – Who Controls Search management? Don’t get your search management mangled

Search - Site Collection config and change mgmt. – Who is controlling the end user search experience? Keywords, best bets, Google ads, scopes, etc..

Document Creation/Publish/Mgmt, etc – How do you control findability keywords? Content types? Consistent metadata? Publication? Approval?

Metadata management (taxonomy) – What’s your taxonomy look like?

Content Types – Are your content types truly farm unique? Who defines and manages these?

Information Management Policies – Who controls and audits your IM Policies?

IIS Config mgmt. – Are you wathing your IIS configuration management/change management? Are you server admins messing with your IIS configs? Are you backing these up independently?

Comments

Popular posts from this blog

How to get SPUser or SPGroup from Person or Group field

You have person or group field in SharePoint list and you want to programmatically get the user or person. The below code to gets SPUser from User or Group field in the list when multiple choice and Groups are not allowed in the field: //get SPUser SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValue userFieldValue = (SPFieldUserValue)userField.GetFieldValue(item["Users"].ToString()); SPUser user = userFieldValue.User; This part of code would help you to get SPUser when multiple choice is allowed and groups are not allowed: //Multiple choices are allowed SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValueCollection userFieldValueCollection = (SPFieldUserValueCollection)userField.GetFieldValue(item["Users"].ToString()); foreach (SPFieldUserValue userFieldValue in userFieldValueCollection) {     Console.WriteLine("     " + userFieldValue.User.LoginName); } And when group

SharePoint publishing page scheduling

In SharePoint 2010 publishing enabled team site collection is not showing schedule button in publish ribbon. Solution: Here is how to enable it  though the UI: Locate the SharePoint Server Web site on which you want to enable content approval and item scheduling. Click  Site Actions , click  Site Settings , and then click  Modify Pages Library Settings . Under  General Settings , click  Versioning Settings . Click  Yes  next to  Content Approval , and then click  OK . Click  Manage item scheduling .   Click to enable the  Enable scheduling of items in this list  check box, and then click  OK .

Changing Content Type Hub URL

Change the Hub URL through powershell by using: Set-SPMetadataServiceApplication -Identity " " -HubURI " " For Ex: Set-SPMetadataServiceApplication -Identity "Managed Metadata Service" -HubURI "http://contenttype.Domain.Com" When you try to do this you get this rather scary message: This is SharePoint telling you that this is a major thing so be careful! Essentially all your content types that you have published out will be removed if they can, and you have to republish all of your content types out again which can cause some issue.