Install SharePoint 2010

Installing SharePoint Server 2010 on

Windows Server 2008 R2 and SQL Server
2008 R2 - Part 1: Overview
15 Comments

This guide shows you how to install SharePoint 2010 on Windows Server 2008 and SQL Server
2008 including the configuration of Windows Server, Active Directory, SQL Server, SharePoint
2010 pre-requisites and SharePoint 2010.

What is your role?

Install as Administrator   Install as Developer   Install as Other

What environment do you want to install?

Install Production   Install Development Environment   Install Evaluation

SharePoint 2010 Installation

In this guide I’m going to set up the following basic SharePoint farm:

Professional Material:
 Install SharePoint 2013 based on your requirements

 Install SharePoint 2010 based on your requirements

Hardware requirements
You shouldn't mess with the hardware requirements of SharePoint in general and SharePoint
2010 in detail.

Recommendations by Microsoft needs to be respected.

This part is very short since it applies to

 a single server with built-in database and

 server farm installations including a single server or multiple servers.

So according to Microsoft TechNet [1] you need:

  Processor
Beta: 64-bit, dual processor, 3 GHz
RTM: 64-bit, four cores
 RAM
4 GB for stand-alone or evaluation installation and 8 GB for single server and multiple
server farm installation for production use
 Hard disk
80 GB
 Other
DVD drive

Software requirements for application and front-end Web

server
The software requirements [1] apply to

 a single server with built-in database and

 server farm installations including a single server or multiple servers.

Windows Server 2008

Your operation system needs to meet the following requirements:

 Windows Server 2008 SP2 64-bit,

 Windows Server 2008 R2 64-bit,
 In general you should apply updates and according to TechNet [1] you need to apply the
following update:
For Windows Server 2008 with SP2, see FIX: A hotfix that provides a method to support
the token authentication without transport security or message encryption in WCF is
available for the .NET Framework 3.5 SP1
For Windows Server 2008 R2, see FIX: A hotfix that provides a method to support the
token authentication without transport security or message encryption in WCF is
available for the .NET Framework 3.5 SP1 

Remarks:

 The second update isn’t available while writing the article. 

 The Beta version of the Microsoft SharePoint Products and Technologies 2010
Preparation Tool does not install the mentioned updates.
 If you use Windows Server 2008 with SP1 then the SharePoint Products and
Technologies 2010 Preparation Tool will install SP2.

Windows Server 2008 – Roles and features

Furthermore you need to enable the following features and roles in your operating system which
is described later in detail:

 Web Server (IIS) role

 Application Server role including .NET Framework 3.5 SP1

Remaining software requirements

The remaining software requirements can be installed by using the SharePoint Products and
Technologies 2010 Preparation Tool.
  Beta: Microsoft "Geneva" Framework
RTM: Windows Identity Foundation (WIF) - Geneva has to be uninstalled before WIF
can be installed!
 Microsoft Sync Framework Runtime v1.0 (x64)
 Microsoft Filter Pack 2.0
 Microsoft Chart Controls for the Microsoft .NET Framework 3.5
 Beta: Windows PowerShell 2.0 CTP3
RTM: Windows PowerShell 2.0
 SQL Server 2008 Native Client
 Microsoft SQL Server 2008 Analysis Services ADOMD.NET
 Beta: ADO.NET Data Services v1.5 CTP2
RTM: ADO.NET Data Services Update for .NET Framework 3.5 SP1

Part 3: Windows Server 2008 R2 configuration

This article describes the configuration of Windows Server 2008 R2 required for deploying
SharePoint Server 2010. While you don't necessarily need to manually do the steps I suggest that
you read the post so you understand what the SharePoint prerequisites installer does.

Windows Server 2008 R2 configuration

Web Server (IIS) role and Application Server role including .NET Framework 3.5 SP1

Check the “Application Server” role and add required features. 

Check the “Web Server (IIS)” role.

Proceed to the feature selection.

.NET Framework 3.5 SP1 is selected by default. Check all the role services as shown in the
picture and add all required features.
  

Check all the role services as shown in the picture and add role services if required.

Proceed checking all the role services as shown in the picture.

These role services will be installed by the SharePoint Products and Technologies 2010
Preparation Tool later if you don’t do it now.

Keep the settings and start the installation.

After finishing the installation you usually don’t have to restart and you can see the installation
results.
If some of the role services are not installed repeat the steps described above.
SharePoint 2010 software prerequisites

The remaining software requirements can be installed by using the SharePoint Products and
Technologies 2010 Preparation Tool which is part of the SharePoint installer.

 Beta: Microsoft "Geneva" Framework

RTM: Windows Identity Foundation (WIF) - Geneva has to be uninstalled before WIF
can be installed!
 Microsoft Sync Framework Runtime v1.0 (x64)
 Microsoft Filter Pack 2.0
 Microsoft Chart Controls for the Microsoft .NET Framework 3.5
 Beta: Windows PowerShell 2.0 CTP3
RTM: Windows PowerShell 2.0
 SQL Server 2008 Native Client
 Microsoft SQL Server 2008 Analysis Services ADOMD.NET
 Beta: ADO.NET Data Services v1.5 CTP2
RTM: ADO.NET Data Services Update for .NET Framework 3.5 SP1

Pop3, SMTP, Outlook

Since Windows Server 2008 the Pop3 server feature is deprecated. If you need mail you have to
install Exchange Server or something similar. 

IE Enhanced Security Configuration

Don’t do this in production environment! If you are deploying SharePoint 2010 in a development
environment you can disable Internet Explorer Enhanced Security configuration if you want to
open Central Administration and other SharePoint 2010 sites directly on the server.

Use the server manager to disable enhanced security for users and administrators.
Part 4: Active Directory installation and
configuration
18 Comments

This guide shows you how to install and configure Windows Server 2008 Active Directory
Domain Services. This isn’t necessary but if you are going to deploy a development environment
I suggest to create a closed environment.

This way you have everything on your own so you don’t depend on something or someone.

Development Environment:
This step usually applies to developers creating an isolated dev environment independent of your
companies infrastructure. You are independent, can go where you want without a connection to
your company and you can make changes as you want.

Active Directory installation

Don’t use the server manager to install the Active Directory role because you are prompted to
use dcpromo.exe and you are left with an uncompleted installation.

Open the ”Run” dialog box and type dcpromo.

Click next checking ”Use advanced mode installation”.

Click next and after that check ”Create a new domain in a new forest”.
Type a new full qualified domain name like “aglaser.net”.

Type a NetBIOS name like “AGLASER”

Select a forest functional level and select a domain functional level.

Note: Please be aware that your choice affects other things. Here is a comment from Wes
Preston which you should consider if you are installing a all-in-one demo machine:

- If selecting AD-2003 mode, the SPAdmin account needs to be added to the Domain Admins
group in AD
- If selecting AD-2008 R2 mode, the SPAdmin account can be added to the Local Admins group

Please test it by yourself.

Make sure “DNS server” is checked.

After clicking next you may get a warning that one of your network adapters has a dynamically
assigned IP address. Click “Yes” if you are sure you have one network adapter with a static IP
address.
Click “Yes” because you don't have to care about a DNS server in a parent zone since this is a
testing environment.
Click next again.

Type in a “Directory Services Restore Mode Administrator Password”.

Click next to start the installation wizard.

After installing the AD and the DNS server you have to restart your computer.

Active Directory configuration

So far I didn’t need to do any configuration since the out-of-the-box installation was enough. If
you see the following screens you are fine.

Next Step
Part 5: Administrative and service accounts

This article describes the administrative and service accounts required for deploying SharePoint
Server 2010.

Basic Installation Accounts

It is strongly recommended to create domain accounts and use them as service accounts. You
need to create at least the following accounts in Active Directory:

Basic Installation Accounts

Required Account Example

SQL Server Service Account sqlSvcAcc

SharePoint Setup Administrator spAdmin

SharePoint Farm Account spFarmAcc

Difference to SharePoint 2007

Service accounts in SharePoint 2007 needed 2 properties when they were created in Active
Directory:

 User cannot change password and 

 Password never expires.

This isn’t necessary with SharePoint 2010 since we now have managed accounts capable of
password expiration and automatic change.

So in my development environment I will choose the options "User cannot change password"
and "Password never expires".

Assign permission
You need to assign permission only to the SharePoint 2010 setup administrator.
SQL Server service account

You don’t need to assign permissions since they are assigned during installation of SQL Server
2008.

The SQL Server service account is used to run SQL Server and should be a domain account.

Setup administrator

You need to manually assign permissions.

The setup administrator is used to install SharePoint 2010.

The SharePoint 2010 setup administrator has to be a member of the administrators group on
every server SharePoint should be installed.

The SharePoint 2010 setup administrator needs to have the securityadmin and dbcreator role.
The sysadmin role is assigned if you decide during SQL Server 2008 installation that your
SharePoint 2010 setup administrator should be the SQL admin.

I decided to do so in my Hyper-V development environment.

Farm account

You don’t need to assign permissions since they are automatically assigned by the SharePoint
2010 setup administrator.

The farm account is used for the following things [1]:

 "Configure and manage the server farm."

 "Act as the application pool identity for the SharePoint Central Administration Web site."
 "Run the Microsoft SharePoint Foundation Workflow Timer Service."

Step 6: SQL Server 2008 R2 software requirements

This article describes the software requirements regarding SQL Server 2008 required for
deploying SharePoint Server 2010.

Software requirements for database server

You need to meet the following requirements if you want to install SharePoint Server 2010
without the built-in database:

 SQL Server 2005 64-bit with Service Pack 3 (SP3)  and Cumulative update package 3 for
SQL Server 2005 Service Pack 3,
 Beta: SQL Server 2008 64-bit with Service Pack 1 (SP1)  and Cumulative update
package 2 for SQL Server 2008 Service Pack 1,
 RTM: SQL Server 2008 SP1 and Cumulative Update 2, CU 5 or later but NOT CU3 or
CU4,
 SQL Server 2008 R2

Remarks:

 Setup doesn’t check your SQL Server edition. It is checked by the SharePoint Product
and Technologies Configuration Wizard after setup.
 If you install SQL Server 2008 RTM on Windows Server 2008 R2 you need to apply SP1
for SQL Server 2008 after installation.

Step 7: SQL Server 2008 R2 installation and configuration

This guide shows you how to install and configure SQL Server 2012. The configuration includes
assigning permissions and configuring networking.

SQL Server 2008 installation

The installation of SQL Server 2008 compared to SQL Server 2008 R2 is almost the same and
described below.

If you get a compatibility warning while trying to install SQL Server 2008 on Windows Server
2008 R2 you can proceed with install.

Before running SQL Server you need to apply Service Pack 1.

SQL Server 2008 R2 installation

If you haven’t done yet  install .NET Framework 3.5 SP1.

On the left side click “Installation” and on the right side click "New installation or add features
to an existing installation".

Install the setup support files.

Select “SQL Server Feature Installation”.

Select the “Database Engine Services” feature and the “Management Tools - Basic” feature.
Check additional features if needed.

Check additional features if needed.

Keep the default instance and default folders.

Use the same account for the services and select the sqlSvcAcc you created in Active Directory.

Keep the collation settings you can see in the screenshot.

Add the SharePoint 2010 setup administrator user as a “SQL Server Administrator”.

Click next at the “Installation Configuration” Rules screen.

Start the installation of SQL Server 2008 R2.

SQL Server 2008 R2 configuration
There are 2 configuration steps you need to do: assign permission to the SharePoint 2010 setup
administrator and configure networking.

Assign permission

The SharePoint 2010 setup administrator needs to have the securityadmin and dbcreator role.
The sysadmin role is assigned if you decide during SQL Server 2008 installation that your
SharePoint 2010 setup administrator should be the SQL admin.

I decided to do so in my Hyper-V development environment.

Configure networking

At the end you need to configure networking if you are planning to deploy a farm with multiple
SharePoint Server 2010 servers.

According to TechNet [1] you need to “ensure that SQL Server 2005 or SQL Server 2008 is
updated to the required level and configured as follows”:

 SQL Server 2005: Local and remote connections are enabled and are configured to use
the TCP/IP protocol.
 SQL Server 2008: The TCP/IP protocol is enabled for the network configuration.
RTM: TechNet still says (May 6, 2010) you need TCP/IP but you don’t need Named
Pipes. From my experience you need Named Pipes.
Difference to SharePoint 2007

In SharePoint 2007 you needed to configure named pipes which isn’t necessary in SharePoint
2010.

Step 8: SharePoint Server 2010 installation

This guide shows you a SharePoint 2010 installation on Windows Server 2008 using SQL Server
2008. It includes the SharePoint 2010 Products Preparation Tool, the installation process and the
SharePoint 2010 Configuration Wizard.

After finishing the process you are able to launch Central Administration.

SharePoint 2010 Products Preparation Tool

Please log on using the SharePoint installation account (SharePoint Setup Administrator -
spAdmin). Execute setup and install SharePoint 2010 software requirements.

If you configured Application Server and Web Server (IIS) role as described the process takes
only some minutes or less.

SharePoint Server 2010 installation

Enter the product key and choose the advanced installation mode.

Always use complete install so you are able to change server roles as you want to.

Wait until the installation of the binary files has finished.

After that the installation will continue with the SharePoint Configuration Wizard.

Start the SharePoint Products Configuration Wizard.

Click yes and choose to create a new server farm.

You don't need to care about stopped services if you create a new server farm.
Enter the application server name and add the farm account spFarmAcc. Permissions are
assigned automatically by the setup administrator.
Enter a pass phrase to secure farm configuration data. It is also needed if you join a new server to
the farm. 

Note: If you have trouble with the configuration database the comment of Mike M. might help
you. He used SQL Express where the SQL Browser was disabled. You have to enable it into
Windows Services.
Update: Please also read the comment by tmack below... he needed to use
SP2010\SQLEXPRESS as the Database Server Name when using SQL Server Express.

Select a port and a authentication provider. How about 2010 as a port number ;)

Configure SharePoint Server 2010.

Et voilà SharePoint Server 2010 was successfully installed. The next article descries the
configuration using Central Administration.
Step 9: SharePoint Server 2010 initial configuration

The configuration of SharePoint 2010 can be split in different parts including basic configuration
as well as the configuration of services and Service Applications.

The following 3 steps should be done right after the installation:

Diagnostic logging
Configure diagnostic logging because writing event log files can reduce performance.

If you need best practices for configuring diagnostic logging check out reference [2] at the
bottom of the article.

Configure usage and health data collection

Next it is necessary to configure usage and health data collection.

Otherwise it will be configured automatically if you create a search service application where
you can’t rename the database.
Outgoing e-mail
Next you can specify a mail server to send alerts, invitations or notifications.

If you don't specify an outgoing mail server you will be remembered by the SharePoint 2010
health analyzer.

Step 10: SharePoint 2010 Service Application configuration