Thursday, June 21, 2012

SharePoint 2010 - Metro Style Interface: Recommendation

Metro Interface already on SharePoint 2010? No problem! The guys from LifeInSharePoint created a fabulous masterpage and design solution to start your project. It is up and running in minutes, it is configurable an looks as nice as SharePoint 2013 interface and you can get it on 2010. Great!


Most Important features:
  • Liquid Layout
  • Cufon Integration
  • Jquery Accordion Quicklaunch with Sub Item Count
  • Full Solution with single Site Feature to activate branding (Thanks CKS:Dev Team)
  • Custom Site Settings Action to choose one of three colour schemes (Green, Blue & Red)

SharePoint 2010 - Feature Admin Tool: Recommendation

The Swiss army knife for feature management in SharePoint 2010!

If you need to batch manage features in your farm, the best tool I can reccomend is:

  • This tool allows detection and removal of broken features and feature definitions in SharePoint content databases.
  • It provides a simple and clean UI
  • It allows activation/deactivation/installation/uninstallation of features
  • You can manage features of all scopes

SharePoint 2010 - Move Managed Metadata Databases (MMD) between Farms

Managed metadata and taxonomy is one of the cool things in SharePoint. If you are responsible for the managment of a multi farm infrastructure with development(DEV), integration(INT) and production(PRO) systems you have to provide a solution for moving managed metadata content across different farms. I tried different approches like export/import, shared service application, etc, but none of them provide a complete solutionö. Andrew Connell is the man who can help you. In his article he describes how to move the whole service database from one farm to another.

Usually taxonomy and term store is managed and maintained on production system. If your developers need a copy of the database for testing purposes, or your project manager needs a up to date integration system, you can just move the database as described in the article.

HINT: I automated the database backup/restore process for repeating actions with MS SQL SSIS. It allows you to prepare a package with all parameters and actions required for the movement.

At the end you get a "click once" deployment between farms! Quite nice..

SharePoint 2010 - Move Nintex Workflow Databases between SharePoint farms

Some months ago my project manager came to me and asked if it is possible to move a content database from production farm to development farm. Our developers needed real content to test different extensions. I answered YES, with a big smile. BUT the I recognized, that we use Nintex Workflows. If I would only copy the SharePoint content database, all Nintex workflows would be in a inconsistent state and not functioning on development/integration farm. So I stopped smiling and started searching for a solution.

First of all: Nintex published some whitepapers about this issue.

Based on this inputs I created a approch to move our content and Nintex Workflow databases:

  1. Backup SharePoint Content Database
  2. Backup Nintex Database
  3. Both have to be in Sync. No Workflow changes while Backup

  1. Restore SharePoint Content Database
  2. Delete existing Nintex Database
  3. Restore Nintex Database
  4. Mount SharePoint Database
  5. Perform IIS Reset
  6. Change license key to development key
HINT: I automated the database backup/restore process for repeating actions with MS SQL SSIS. It allows you to prepare a package with all parameters and actions required for the movement.

At the end you get a "click once" Nintex database deployment between farms! Quite nice..