Setting up a SharePoint 2010 Beta 2 Development EnvironmentPosted: January 1, 2010
In this post I will go though my SharePoint 2010 Beta 2 setup experience as development environment. Here I am setting up a single server farm with AD, SharePoint and SQL sitting in a single development box. I am using Windows 2008 R2 (64bit) as the OS and following is the high level initial steps that I‘ve taken to configure the base OS. The full list of Hardware and Software Requirements can be found in Determine hardware and software requirements (SharePoint Server 2010) and Jeremy Thake has a excellent Wiki page outlining the detail steps on SharePointDevWiki.
1) Add Active Directory Domain Services server role and Configured the Domain using Active Directory Domain services installation wizard. Also add add Web Server (IIS) role and Application Serve role.
2) Create Service 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. I will be using local Administrator as the setup account for this dev environment and the following accounts.
|Account type||Account name|
|Farm Account or DB Access Account||SpSqlService|
For detail description of required accounts and permissions refer to Administrative and service accounts required for initial deployment .Additionally you should create for every service a separate service account in order to meet least-privilege security best practice.
3) Disable the loop back adapter check using this PowerShell script written by Michael Blumenthal. You might have to temporary change the power shell execution policy from remotesigned (Default) to unrestricted using “set-executionpolicy unrestricted” before attempting to run the the script.
Why we need this?
Recently Microsoft released an update, which prevents that you can log on locally to a website which has a FQDN. The following KB article describes the issue. You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or a later version
To resolve you can disable the loopback check completely, or just for the used FQDNs. Alternatively If you have more then one server in you farm a better way to do so is a custom stsadm extension. Gary Lapointe has written such an extension. Take a look at it: Setting Back Connection Host Names for SharePoint 2007 Using STSADM. I used the PowerShell script.
5) Download and Install Microsoft Chart Controls for Microsoft .NET Framework 3.5
6) Download and install Microsoft "Geneva" Framework Runtime (2008R2\x64\AdfsSetup.exe)
7) Download and Install ADO.NET Data Services v1.5 CTP 2
Note: If you are using Windows Server 2008 you will need to download and install following additional components (Windows Server 2008 SP 2, Windows Management Framework With PowerShell 2 and WCF Fix )
8 ) Run SharePoint Server Setup and Select “Install Software prerequisites” option
One all software requirements are satisfied you should see the following screen.
9) Now we are ready to Install SharePoint Server 2010 and setup the farm environment. Run the Setup and follow the Wizard. When you come to Installation Type “Server Farm” option.
10) Select “Complete” option from for the Server Type
11). At the end of the installation Check Run Configuration Wizard option and Click Close button.
12) This will open Run Confuguration Wizard. When you come to Connect to a server farm Select “Create a new server farm option”
13) Specify the Database server name and specify the domain sql service user account that we have created earlier.
14) Specify a passphrase
15) Accept the defaults for the Central Administration Web Application
16) Verify the Configuration details and proceed
Now we have finished running SharePoint Configuration Wizard. This has created core SharePoint Databases,Web Apps and Associated App pools and Services.
Following are the application pools that has been created at this point.
|SharePoint Central Administration v4||SharePoint Farm Account||It’s responsible for Central Administration on the machines hosting it|
|The SharePoint Topology Service Application||SharePoint Farm Account||The app pool name in IIS is a GUID, in SharePoint it is SharePoint Web Services System.This hosts the Topology Service Application, which is known as the Application Discovery and Load Balancer Service Application|
|The SharePoint Security Token Service Application||SharePoint Farm Account||The app pool name in IIS is a GUID, in SharePoint it is SecurityTokenServiceApplicationPool|
|SharePoint Web Services Root||LocalService Status: Stopped||This hosts the SharePoint Web Services IIS Web Site and is on every machine in the farm. This is the host web site for Service Applications. Service Applications WCF end points are hosted in here.|
17) Launch Farm Configuration Wizard from Central Administration. This will provision Service Applications, and Allows you to create top level content web application and site collection.
Specify the service account for running farm services.
Create a root level Site Collection
After farm configuration wizard is finished will we have the following additional Application Pools.
|SharePoint Web Services Default||SharePoint Services Account (spService)||Hosts all the other Service Applications|
|SharePoint – 80||SharePoint Services Account (spService)||This is the default application pool used to host end user Content Web Application|
Now we have working site collection for development purposes. Additionally if you are going to develop sandbox solutions you will need to start SharePoint Foundation User code Service as described in Configure a farm for sandboxed solutions.
Hope this helps!