Getting started

Install SharePoint 2013, 2010 or 2007 - Step by Step

This guide shows you how to install SharePoint 2013, 2010 or 2007 without missing important steps.

Updated:

Install SharePoint 2016

How to install SharePoint 2016 IT preview (work in progress):

  1. Install SharePoint 2016

Install SharePoint 2013

Installing SharePoint 2013 is NOT about clicking the wizard:

  1. Install SharePoint 2013
  2. SharePoint 2013 Create Search Service Application with PowerShell
  3. SharePoint 2013 User Profile Synchronization with PowerShell
  4. Scripted Installation for SharePoint 2013 - Problems and Solutions
 
 

Install SharePoint 2010

This tutorial is designed to get you up and running with the basics of installing SharePoint in seven easy lessons.

  1. Install SharePoint 2010
  2. Install SharePoint Foundation 2010
  3. SharePoint 2010 installation requirements
  4. SharePoint 2010 installation best practices
  5. SharePoint 2010 Service Pack 1 - Part 1: Overview
  6. SharePoint 2010 Service Pack 1 - How to create a slipstream copy
  7. Install PowerPivot for SharePoint

Install SharePoint 2007

If you need to install SharePoint 2007 please rely on the following tutorial:

Install SharePoint 2007
 

How to do the installation of SharePoint is independent of its version an important task not only for IT professionals but also for developers. Imagine the following situation: You develop a SharePoint Web Part, a timer job or something else and it doesn't work after deployment.

If you have a poorly installed SharePoint environment it might happen that it's not the developers fault. Anyway it's not working and with a poor SharePoint deployment there are much more things to check in order to solve the problem resulting in loss of time and money. It's important how you install it...

Otherwise it's also possible that a SharePoint solution works on a development environment and not on a production environment. SharePoint production environments are deployed using best practices... e.g. regarding service accounts. If you use the farm account as the application pool account a Web Part can properly run within your development environment using elevated privileges. Within a production environment it can throw an error because of a different application pool account with different privileges. Again we see that we need to care about how we install it...

So setting up a good performing SharePoint environment is a task for a lot of people with different jobs. Even for a project manager it's important to understand that a proper installed SharePoint environment saves time and therefore money during development as well as during deployment to a test or production environment.