This article is part 3 in a 4 part series that shows how I build my SharePoint 2010 development environment from the ground up.  In the previous series I built a Windows 2008 R2, configured the Active Directory Domain Services role, provisioned SharePoint service accounts, configured the IIS role, installed and configured SQL 2008, updated SQL, and configured a SQL Server alias.

Now that you’ve diligently followed all of the steps in Part 1 and Part 2 of this series, and taken snapshots along the way, you’re ready to install SharePoint 2010!

The first step is to download the latest SharePoint 2010 media from Microsoft (note that the link might change)
http://www.microsoft.com/downloads/details.aspx?FamilyID=77C30C6C-47FC-416D-88E7-8122534B3F37&displaylang=en

Warning- If you click on "Install SharePoint Server" before installing the prerequisites you will receive an warning similar to the one below, mainly requiring "Geneva" which is required for SharePoint 2010 "Claims Based Authentication".

Our warning also asked us to install "Geneva" and IIS which we can do using the "Install software prerequisites " button

If the installation fails make sure that your server has an internet connection because the installation of Geneva requires that the server download content

Restart the installation after provisioning an internet connection and the installation should succeed

You should have received the keys in an email from Microsoft (if you are installing a trial)

Always choose Server Farm!!!

You almost always always always always will want to run a “Complete” install.  If you are wondering why your computer has multiple SQL Server instances as well as SQL Express then most likely you ran a stand-alone installation in the past.

I like to configure my Central Administration port as 8080. 

Login to Central Admin as the user you were logged in as when you first ran the SharePoint Products and Technologies Wizard (this is contrary to what you might think as we would assume that we would login as the application pool account)

I always like to configure alternate access mappings immediately

Next we want to create our top level web application that will host our top level site collection

No search, failover, or service application have been created so we’ll leave the defaults for now

Now create a site collection

If you get repeated login attempts that fail and you’ve tried your admin and application pool accounts, you might be unable to browse SharePoint locally related with Kerberos and host headers, see my article Unable to Brows SharePoint Locally Or Search Fails To Index Content to resolve the problem.

In the next part of this series we install Visual Studio 2010 and build run a few sample development tasks.

Popularity: 16% [?]