by spjeff

Site Owner Responsibility (real world governance)

November 2, 2014 by spjeff

Today I was doing research on common guidelines offered to SharePoint Site Owners.  Real Governance is more culture than DOC file.  The best written intention must be applied daily and woven into operations.   Governance often has a front and back end component.   The back end covers technology infrastructure (maintenance, monitoring, patching, failover, upgrades, capacity planning, etc.)    These firm technical areas can be more tangible with clear best practices.   Software configuration can be straightforward focused on a smaller audience of IT support personnel.


However, the front end is often ambiguous.  We must guide people’s behavior with a wider audience.  That’s challenging.


Below are public examples of Site Owner Responsibility documents.  I outlined my observations on each.   I also created a word cloud for the aggregate.   Communicating expectations early and often can create a smoother experience for both Business and IT.  Hope you found these samples helpful.   Cheers!  shades_smile


Word Cloud

  • Emphasis on “how” we manage  (frequent, accurate, daily, specific, leadership)
  • Emphasis on “continual” learning  (training, sessions, attend, brown bag, knowledge)


  • Refers to Site Owner as “Site Collection Manager”
  • Manage content
  • Manage security
  • Education component  (“quickly learn”, “functional knowledge”, “well informed”, “brown bag sessions”)

  • Overall brief
  • Manage content & security
  • Monitor space usage
  • Education component  (“attend mandatory 2-hour workshop”, “provide training to department staff”)
  • Provide 1st level support

  • Manage content & security
  • Ensure content is both accurate and updated
  • Manage all sub-sites or find a delegate

  • Attend training (2013 Site Collection and Site Administration M55033)
  • Manage content “structure”  (when to use list, library, etc.)
  • Manage security
  • Apply social networking
by spjeff

NEW CodePlex project – SPUpgradeHelper

October 28, 2014 by spjeff

Today I am happy to announce is available for download.   This project aims to smooth the “double hop” upgrade from MOSS 2007 to SP2010 to SP 2013 by reading a CSV of database targets and automating the Cmdlets needed for a consistent, repeatable, high quality, and fast process.   Please leave a comment here or on CodePlex if you found this helpful.  Cheers!  shades_smile


Project Description

Migrating MOSS 2007 to SP 2013? This script takes a CSV of databases and runs upgrade Cmdlets in bulk (DB version/Mount/Dismount/Upgrade-SPSite/Claims auth)

Upgrading MOSS to SP2013 is a tedious process with many Cmdlets, especially if you have many databases. This script aims to help automate that process.

Given a CSV with SQL instance and content database names, this script offers Cmdlets to run upgrade steps across many databases all at once. No more TXT or XLS copy and paste madness. Simply populate the CSV, get familiar with UH* Cmdlets and upgrade with ease.

Key Features

  • Read CSV of databases
  • Load helper functions into memory
  • Enable admin to more easily run Cmdlets in bulk
  • Measure time duration for each step (# minutes)
  • Provide detailed LOG file of actions, result, and duration

Quick Start Guide

  • Extract “SPUpgradeHelper.ZIP” to any SharePoint machine in your farm
  • Run “SPUpgradeHelper.ps1″ to load helper functions
  • Type in full path to your CSV file (i.e. “C:\TEMP\COLLAB.CSV”)

Function Names

  • UHCIaims – execute SPWebApplication function to upgrade Classic to Claims auth
  • UHCompatibiIity – execute Get-SPSite for “set” of databases to show GUI version (14/15)
  • UHDBVersion – execute TSQL for “set” of databases to show build number (12.0, 14.0, 15.0)
  • UHDismount – execute DisMount-SPContentDatabase for “set” of databases
  • UHMount – execute Mount-SPContentDatabase for “set” of databases
  • UHReadCSV – load CSV file into memory with upgrade “set”, SQL instance, and database names
  • UHUpgrade – execute Upgrade-SPSite for “set” of databases

NOTE – Upgrade “set” is meant for running parallel workstreams. For example, two servers with SP2010 and two servers with SP2013. That way overall upgrade can be expedited by running database set “A” through the first SP2010 and SP2013 server while database set “B” runs on the second server.

Microsoft Upgrade Process

by spjeff

WebAPI OData – 10 min video introduction (Visual Studio 2013)

October 14, 2014 by spjeff

I’ve been learning about OData and wanted to record a quick getting started video with how to create a new WebAPI project, add OData Controller, and send HTTP CRUD operations.  Below is an example using Adventure Works Departments with sample code, screenshots, and a 10 minute video introduction.   Please leave a comment if you found this helpful.  Thanks!  shades_smile

Video Content

  • Create MVC 4 web application
  • SQL Express – Adventure Works Departments
  • Add “AdventureWorks.edmx
    • Wizard driven
    • F4 set namespace
  • Add “DepartmentsController.cs
    • Create from EDMX class
    • Implements ODataController
    • Replace ID with KEY
  • Edit “WebApiConfig.cs
    • Comment out default route
    • Add OData route builder
  • Test with HTTP manually
  • Test with Chrome REST Postman
  • SQL Express – see changed data

Watch Video

WebAPI OData – 10 min video introduction (Visual Studio 2013) from Jeff Jones on Vimeo.

Sample Code