Join me at Google+ ...
November 18, 2009 - 29 Comments  

Installing SharePoint Server 2010 on Windows Server 2008 R2 and SQL Server 2008 R2 - Part 8: SharePoint Server 2010 installation

This article describes the installation of SharePoint Server 2010 and is a part of a series describing the complete installation of SharePoint Server 2010 on Windows Server 2008 R2 and SQL Server 2008 R2. There you can find an overview of the complete series and of course the farm topology and the deployment scenario.

Update: 60 min - Install SharePoint with PowerShell easy and fast

Ok lets install SharePoint... to be true the SharePoint 2010 pre-requisites installer will configure the Windows Server 2008 Web Server role as well as the Application Server role. So why did we manually configure it? Well one reason is knowledge and the other reason is spaghetti code. Let's explain this in detail...

You will gain knowledge if you manually configure Windows Server 2008. You know what's needed and how to enable it the the right way. This makes a difference between you and other people. It's the same with a PowerPoint presentation: A lot of people can retell the facts but they don't know the details. So they will fail some time...

Spaghetti code really exists and describes something unstructured or a complex thing without a flow. So if you run this installer doing his job and after that another installer doing his job and another one... well you get it. They enable features, you don't really know which ones or the details or if they are activated multiple times. Maybe one feature is contra productive or something else. Having the control is one of the things I want.

In the rest of this article I will show you how to

  • create a new SharePoint 2010 server farm,
  • configure settings for Central Administration and SQL Server and
  • set the passphrase for SharePoint 2010.

Please have also a look at

So now let's go the the tool and let it do the rest of the work for us...

 

SharePoint 2010 Products Preparation Tool

Execute setup and install SharePoint 2010 software requirements.

Execute setup. 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.

Installation process of software prerequisites. 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.

Enter product key. 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 Confoiguration Wizard.

Install complete SharePoint 2010. Wait until installation has finished.

Start the SharePoint Products Configuration Wizard.

Execute the Products Configuration Wizard. Click next.

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.

Click yes to stop services. Create anew SharePoint 2010 server farm.

Enter the application server name and add the farm account spFarmAcc. Permissions are assigned automatically by the setup administrator.
Enter a passphrase 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.

Enter SQL Server and farm account. Enter a passphrase.

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

Select port and authentication provider. Verify settings and start configuration.

Configure SharePoint Server 2010.

Wait until configuration has finished. Click finish to start Central Administration.

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

Decide to sign up for the Customer Experience Improvement Program or not. Installation of SharePoint Server 2010 has finished. 

Next steps



Get updates

 

Comments (29) -

11/26/2009 8:22:09 PM #

Excellent set of install instructions. I was going to start such a set when
I found your blogs.
Thank you.

Divya United States Reply

1/31/2010 6:22:30 PM #

thank for sharing the knowledge

satish India Reply

4/29/2010 5:36:07 PM #

Please take a look at Part 9: SharePoint Server 2010 configuration?
Any update?

alex Kenya Reply

4/30/2010 8:47:40 AM #

Hi Andreas,
Really helpful set of print screens and great guide! Hope to see part 9 as I have to move to 2010 from WSS 2007 on Win2003 R2 I don't know if I'll create a new farm on Win2008 R2 and link to actual database or just export all sites and import into new farm.
What do you think?

Karl Belgium Reply

4/30/2010 9:04:23 AM #

Hey thanks for the feedback... Smile

I will continue in May with part 9 and I'm really exited about that since it's a lot of writing.

Andreas Glaser Switzerland Reply

5/4/2010 5:19:54 PM #

Thanks for taking time putting the installation together.. Greatly appreciated.

-JR

JR United States Reply

5/6/2010 7:10:51 PM #

Its may
I'm interested in this and installing office web apps 2010
I'v heard that sharepoint is needed for Office web apps 2010 so would it be possible to add their install to this?

Richard United States Reply

5/12/2010 1:57:03 AM #

Great post - thank you!

On our domain, I ran into a problem when trying to create the SharePoint_Config database. It gave me this error similar to this:
"sharepoint exception type system.collection.generic.keynotfoundexception sharepoint 2010"

Issue turned out to be a security issue for my farm account user. This article was helpful:
ethan-deng.com/...Point2010InstallationIssues.aspx

Kevin Marshall United States Reply

5/12/2010 11:35:56 AM #

Just great! Thank you for sharing this.

prog1 Germany Reply

5/12/2010 7:21:55 PM #

Part 9 has been released...

Please take a look at part 10 and part 11 which are new.

Andreas Glaser Switzerland Reply

6/30/2010 10:52:11 PM #

Awesome walk-through. I spent hours trying to use "other sources" to get this set up going, to no avail. Your tutorial takes the cake on easy implementation.

If I could add one thing (I didn't see it listed, so pardon me if I am repeating) - I am actually using a slightly different setup. I have my Sharepoint 2010 install on Server 2008 R2 and am using SQL 2008 Express R2 (my site is not going to be that big at all). I was having issues at the initial set up of the configuration database that told me either the database could not be found or the user did not have access. After much hair pulling, I finally discovered that by default in SQL Express, the SQL Browser is disabled. You have to do into Services - enable and start the browser.

I also ran the script on this page to open the firewall - www.sharepointforum.com/.../...harepoint-2010.aspx

It works really well.

Finally, I had to specify port 1433 under TCP/IP Connection properties under ALL IP.

Hope that can help someone else! Thanks!

Mike M. United States Reply

7/7/2010 10:47:42 PM #

Hi Mike,

thank you for the link to the port numbers... I added your tip to the article.

Andreas

Andreas Glaser Switzerland Reply

12/21/2011 8:38:13 PM #

I get this error as well but I have my Domain firewall disabled and the browser service set to start Automatically.

I tried using the spAdmin, spFarmAcc, and the domain Admin account; none worked.

Update: I figured it out; for SQLEXPRESS you have to specify the SQLEXPRESS instance along with the server name:

Database Server Name: SP2010\SQLEXPRESS

Q: Why do you use the spFarmAcc as the DB access account rather than the spAdmin?

Thanks,

Tmack Reply

1/3/2012 8:02:28 PM #

Hi,

thank you very much for the info... I have added the info to the post referring to your comment.

Regarding your question... back in 2007 Microsoft released an article including different accounts for the installation process. Here is the article regarding SharePoint 2010: technet.microsoft.com/en-us/library/ee662513.aspx
Actually I didn't think about the why...

Regards
Andreas

Andreas Glaser Switzerland Reply

9/2/2010 9:48:23 AM #

Hello Andreas,
So far I have installed everything as in your recipe Smile, configuread Sharepoint, but stuck under AD and accounts. Sharepoint will not accept the user [access denied] even though these are in AD. What i have found out is that users cannot log on because they are not listed under "Allow log on locally" in gpedit.msc -> Computer Configurations -> Windows Settings -> Local policies -> User rights assignment. the "Allow log on locally" option is grayed out thus do not allow any changes. Any ideas for this issue will be much appreciated.
Best regards,
martin

Martin Poland Reply

9/15/2010 3:29:11 AM #

I'd just like to say: thanks so much for this article, it really helped!

Just a tip for anyone who might gotten stuck--like I did--on the "Specify Database Access Account" step:

Part 7 in this tutorial talks about assigning "securityadmin" and "dbcreate" roles to the spAdmin account. This is important.

I was not able to assign these roles through Microsoft SQL Server Management Studio tool because it uses the current logged on user (on your Windows box) for Windows authentication for queries. You need to log on as spAdmin. This account was assigned administrative permissions to the SQL database in the "Database Engine Configuration" step.

Jonathan Australia Reply

9/15/2010 12:32:55 PM #

Thanks for the info Smile

Andreas Glaser Switzerland Reply

10/5/2011 4:06:56 PM #

Another important issue:
The Sharepoint installation account must be in Local Administrator Group on eachserver where Sharepoint will be installated

ronen Israel Reply

9/16/2010 3:16:17 AM #

Hi
Thank you very much for the instruction. I did everything according to your blog and it helped me a lot. Only one point might need to be mentioned to prevent confusion for those who follow the instruction blindly (like me Smile: In sharepoint configuration wizard where you have to enter a server name and database name, stupid me entered the name you entered in your screenshot(SP2010APP) which was your server name not mine! and I thought it is somthing to be created in database Laughing. So it is the actual server name (machine name). I got the error that says it cannot connect to master database ...
and wasted so much time.

However, your blog was the best I found in sharepoint installation.

Ladan Canada Reply

9/16/2010 7:55:15 AM #

Hey thank you very much ... glad it helped Smile

Andreas Glaser Switzerland Reply

9/23/2010 11:56:20 PM #

Guten tag, Andreas! I appreciate you taking the time to write such a helpful guide. My installation uses a remote SQL Server instance. During the "Specify Configuration Database Settings" step, it throws an error specifying the master database is not available or the setup account does not have access permissions. SQL Browser is running and named pipes are enabled. Do you have an idea how I should proceed?

Rich United States Reply

9/29/2010 8:03:41 AM #

Hi Rich,

can you please verify that you don't have Windows Firewall turned on? this was the reason in my case when i got an error...

thx for your comment Smile

Andreas Glaser Switzerland Reply

8/15/2011 1:18:29 PM #

Hallo Andreas,

I used your tutorial to install my SharePoint based on the Microsoft  Security Suggestions (technet.microsoft.com/en-us/library/ee662513.aspx) to avoid getting those security warnings all the time.

However as long as my farmadmin account is not local administrator on the sharepoint server, I can't create a new webapplication. When I assign local administrator permission, everything is working fine.

Did you encouter the same problems or have you heard of them? Somebody described the problem here: social.technet.microsoft.com/.../1f92d977-400a-4d98-ab31-b01c5586d254

Thanks in advance

Andreas Germany Reply

8/17/2011 4:04:50 PM #

Hi Andreas,

I haven't experienced the problem myself since I'm using the Setup Administrator in order to access / use Central Administration.

If you can't use the Setup Admin maybe it helps to add a usual server administrator to the farm admin group in Central Administration > Security > Manage the farm administrators group.


Regards
Andreas

Andreas Glaser Switzerland Reply

8/18/2011 1:39:03 PM #

Hi Andreas,

the reason why we're not using the setup administrator is simple, Microsoft doesn't recommend doing that in their SP2010 installation guidances and further the HealthAnalyzer keeps throwing warnings at us regarding the farmadmin being local administrator.

Since we're installing SP2010 for many customers, we have to be certain that we're not reliable for missconfigurations which differ from what Microsoft suggests, which could lead the security problems of any kind.

Andreas Germany Reply

8/19/2011 10:30:09 AM #

Ah ok... did you try to use a usual server admin and to put him in the farm administrators group via Central Administration?

Andreas Glaser Switzerland Reply

8/23/2011 9:49:31 AM #

Whats throwing me of is the following guidances: technet.microsoft.com/.../ee662513(office.14).aspx

The Setup user account is used to run the following:
-Setup
-SharePoint Products Configuration Wizard

The server farm account is used to perform the following tasks:
-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.

Microsoft Support already confirmed to me that this article (although many thousand people already read it) is flawed. The farm account should be only used as apppool account for central administration and sharepoint timer service. Configuring and managing the server farm should be done with the setup user just as you're doing it ever since.

To your last suggestion: Each local administrator gets farm administrator permission granted without any further work.

Andreas Germany Reply

9/7/2011 9:06:37 PM #

The link you provided is interesting since it contains another link (technet.microsoft.com/.../cc678863.aspx#Section2) where it is written:

"For the examples in this article, the setup user administrator account is used for farm administration, and it can be managed using Central Administration. Some configuration options require local administration permissions: for example, configuration of the SharePoint Server 2010 Search query server. The setup user administrator account requires the following permissions:" ...

Maybe it's to late but it looks like there is written the opposite of the content from your link Laughing

Andreas Glaser Switzerland Reply

9/16/2011 1:23:20 PM #

Like I said the article is flawed and those two contain opposing informations on how to setup your environment. Using the setup user for administrativ tasks seems to be the only and propper way so for your guide you're just fine.

Andreas Germany Reply

Pingbacks and trackbacks (2)+

Add comment




  Country flag
biuquote
Loading