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: 5% [?]

This is an alternative to the "disable loopback check" which is no longer recommended by Msft due to security concerns related to local activation.

Problem

You are able to browse SharePoint normally from external sources, but when you attempt to access SharePoint on the local server for anything other than the machine name you are presented with multiple login prompts that ultimately result in a login error

Explanation

The http request fails because a loopback check runs and fails preventing Kerberos from succeeding (because there’s no SPN for the url you are using to access SharePoint)

Solution

As always, take backups, snapshots, and test in staging!!!

You will need registry access to complete the steps mapped out below

Firstly, open regedit and search for MSV1_0

Create a new Multi-String Value

Set the value of the BackConnectionHostNames with one entry per line

If the steps above don’t work modify the hosts file appropriately in c:\windows\system32\drivers\etc to contain references to to local IP address for each hostname

Popularity: 3% [?]

This article describes the installation process for a SQL server on an all-in-one SharePoint 2010 development server.

If you didn’t follow Part 1 of the SharePoint 2010 Installation series you’ll need to create a SQL service account to support the SQL Server 2008.  While there are many ways to configure SQL and many possible features that you can activate, the steps below demonstrate a “least” features approach allowing you to simply install and run a dumb SQL Server.

Let’s start by mounting the SQL Server ISO to a virtual host.  Once mounted the operating system will ask you if you’d like to run Setup.exe.  If you do not have a SQL ISO I recommend downloading the latest version from Microsoft here: http://www.microsoft.com/sqlserver/2008/en/us/trial-software.aspx .  The version I install below is SQL Server 2008 Standard.

Run setup when the virtual drive auto-plays

Under installation choose "New SQL Server stand-alone installation…"

If you followed my installation steps in Part 1 your setup support rules should all pass

For a development server you can safely ignore the messages below

Do not install Reporting Services if you plan on configuration SSRS in an integrated SharePoint mode

Use the service accounts create in Part 1 of this series

Add the uses who you would like to have administrative rights to the SQL Server

Take a snapshot

Install any SQL Service Packs (Currently SP1)

Configure a SQL Server Alias for SharePoint, this allows you to re-home your SharePoint client to use a different SQL Server (possibly a different instance) when necessary. 

(Note that I have a more detailed article about how to create a SQL Alias on a server with no SQL Client tools installed)

Enable TIP/IP

Under the 32 bit Client 10.0 Configuration (32 Bit)

** yes, one would think you need to do it under the 64 bit but SQL Server Management Studio thunks to 32 bit

Repeat the steps above for SQL Native Client 10.0 Configuration

** SharePoint uses the 64 Bit Native Client

Test your connection using enterprise manager

Note that the above version 10.0.2531 is not supported by SharePoint, we will need to install a hotfix (only available by request) from Microsoft.

Search the internet for KB970315 and download the necessary binaries

http://support.microsoft.com/kb/970315

In the next part of this series we will install and configure SharePoint on our server.

Popularity: 6% [?]

If you are running Windows Server 2003 or a pre Windows Server 2008 R2 build then please refer to this article: http://www.sharepointassist.com/2009/01/27/61738644-f196-11d0-9953-00c04fd919c1-launch-permissions/ . However, if you are running Windows Server 2008 R2 or higher follow the steps below to correct the Event 10016 DCOM error 61738644-F196-11D0-9953-00C04FD919C1 related to the IIS-WAMREG Admin Service.

Always test these changes in your development and staging environment!!!

The DCOM Errors will appear in the System event log as Event 10016

Normally, to correct this problem  you would simply open component services and fix the problem http://www.sharepointassist.com/2009/01/27/61738644-f196-11d0-9953-00c04fd919c1-launch-permissions/

You don’t have rights with R2 because only the trusted installer has rights to change the security on this component.

Launch regedit

Accept the UAC warning

Type F3 and search for the following string: 61738644-F196-11D0-9953-00C04FD919C1 related to the IIS-WAMREG Admin Service.

Right mouse key on the key in the left hand pane then select permissions (do NOT change anything yet) and press the Advanced button

On the advanced security settings screen

1. Select the Owner Tab
2. Select a user in the “Change owner to:” box
3. Check the “Replace owner on subcontainers and objects”
4. Press apply

Now on the properties tab you may grant “Full Control” to the Administrators or another appropriate group

Now launch component services and locate the IIS WAMREG Admin Service

On the properties screen for the service

1. Choose the Security tab
2. Press Edit on the Security tab
3. Press Add on the Launch and Activation Permissions window
4. Choose the appropriate user which is most likely your Application Pool account

Grant the user Local Launch permissions and press OK

That’s it, you should no longer see the errors in your System Event log

Popularity: 12% [?]

A lot of clients and colleagues ask me how I build out SharePoint in my lab so I decided to author a simple "how I did it" article on SharePoint 2010 installation. My environment is an 8GB Vista 64 Bit Ultimate running VMWare workstation 7.0. The host operating system typically only supports my Subversion repository and runs nothing else, all development, testing, and configuration happens on my development (guest) OS which, in this case is a 64 Bit Windows Server 2008 R2 *** It must be 64 bit ***.

Warnings and Gotchas

• SharePoint Server must be 64 Bit
• If you install the server as a domain controller it should have a fixed/static IP address
• No matter how well you configure your server the SharePoint installer will still want to install additional roles and services from the internet therefore the server must have a network connection
• SQL Server requires version 10.0.2714 or so which is quite difficult to configure as it requires several hot fixes to get to the necessary patch level

This server is a full SQL Server, Domain Controller, SharePoint Application Server, and Development Server so it’s more than just "all-in-one". For that reason, I have included some screenshots showing how I configured everything on this server.

Here’s the requisite software

• Windows Server 2008 R2 (64 Bit)
• SQL Server 2008 – You will have to every service pack imaginable so please please please get the most recent media you can find
• VMWare or HyperV Virtual Environment
• SharePoint 2007
• Visual Studio 2010
• SharePoint Designer 2010

Download the Windows Server 2008 R2 ISO

http://www.microsoft.com/windowsserver2008/en/us/trial-software.aspx

Install Windows Server 2008 R2 on VMWare or in your HyperV environment – The steps to follow can easily be ported to a HyperV installation so don’t worry, just continue on.  If you’re building a physical box, no problem, simply continue on past the VMWare portion.

Note that I’m naming this server something generic so that I can clone it before installing SharePoint 2010, that way if I make a mistake I can roll back.

Don’t be stingy on the space, you’ll regret it later if you are

After installation completes you should see a screen similar to the one shown below

Before you do anything (if this server is going to be a Domain Controller), you need to give it a hard IP

Add the Active Directory Domain Services role

Set the password in computer management (since we’re not part of a domain yet do not use active directory users and computers ‘ADUC’)

Leave the "DNS Server" checkbox checked, this will allow you to easily test Alternate Access Mappings in SharePoint

The server will reboot and log you back in automatically, if you are not logged back in remember to use the administrator account as the accounts you previously had on the server may no longer be valid depending on the password complexity that you originally chose.

Add the following roles if you haven’t done so already

• Application Server
• Remote Desktop Services
• Web Server (IIS)
• IIS 6 Management Compatibility

Leave the default services selected for the IIS Web Server (IIS) Role

Add IIS 6 Management Compatibility (required by SharePoint 2010)

After reboot, under administrative tools open Active Directory Users and Computers. Create an organizational unit called "Service Accounts" and create the following users.

• SharePoint Application Pool
• SharePoint Search Service
• SharePoint Search Content Access
• SQL Service

Also create a SharePoint Administration account that you might use instead of your personal login. Hint, this is useful when you want to take screenshots and not have your name on every single item (Unless you’ve got a nerdy name like Ulysses and you want to see it everywhere).

Run windows update

Now shut down the server and take a snapshot

Take a snapshot!

The next part of this series will cover the SQL 2008 installation and configuration.

Popularity: 6% [?]