Installing SharePoint Server 2010 on a development system. Part 2.

This is the 2nd part of my post on Installing SharePoint Server 2010 on a development system.

Now it’s time to run the SharePoint Products Configuration Wizard.

Welcome to SharePoint Products

Click Next.

Ok to restart services?

You will be asked if it is ok to restart certain services during the wizard. Click Yes.


Since we will creating a new server farm, select that option and click Next.

Database settings

Specify your SQL Server name, the config database name, and the username/password used to connect to the SQL Server. Click Next.

Now, if you don’t have updated your SQL Server 2008 to the latest service pack and/or CU, you will get this error, which leads you to this KB article

Unsupported version

In my case, I had SQL Server 2008 Service Pack 1 installed, but needed the cumulative update package 2.  I applied the CU and Ok.

Set passphrase

Enter the far passphrase and click Next.


In this step you set the port number used by the Central Administration Web Application. If you don’t have any specific needs, leave it with the default value. You also set whether the authentication provider should be NTLM or Kerberos. Click Next.


Click Next and the Wizard will start its processing.

SharePoint products are configured

SharePoint Configuration Successful

Click Finish.






Congratulations, your SharePoint Server is installed and configured.

Installing SharePoint Server 2010 on a development system. Part 1

Installing SharePoint Server 2010 on a development system. Part 1

In this post I will guide you through the process of setting up a SharePoint Server 2010 development server. The platform I will cover here will be Windows Server 2008 (R2) and not Windows 7. (Which is, in contrast to SharePoint Server 2007, is both doable and supported). Also, I will not cover installing an instance of SQL Server 2008.

When we first insert the media (either a DVD or if you have mounted a downloaded .iso file), you will be greeted by this splash screen:

SharePoint 2010 setup splash screen

We will start by clicking the Install software prerequisites. This handy utility will install and configure all the features, components and updates before running the actual SharePoint Server installation.

Preparation tool welcome screen

Click Next to continue


Accepting the License Agreementt(s)

Check to accept and click Next.

Installing prerequisites

When the preparation tool has finished, you will need to restart your system.

Finish screen

Click Finish to do so.

After the re-boot, the prerequisites are all installed and enabled.

Installtion complete

Click Finish to continue. You will then have to re-start the SharePoint setup by starting the Splash.hta executable. This time we are ready to install SharePoint by clicking on “Install SharePoint Server”.

Start the SharePoint Server installation

Enter product key

Enter your product key and click Continue.

Accept the terms

Accept the terms and click Continue.

Choose Server Farm

Since we will be running the SQL Server on a separate system, we select the Server Farm option.








Choose Complete

Select the Complete option and click Install Now.

Installation progress

After the installation has completed, you will have the option to run the SharePoint Products Configuration Wizard:

Run Configuration Wizard

Leave it selected and click Close.

How to use the SPGridView filter together with a SPDataSource

Normally you will no problems finding examples on how to use the SPGridView together with an ObjectDataSource and use the filtering mechanism. But what about using the SPDataSource object?

This can also be done fairly simple. You do the basic things as you do using an ObjectDataSource object, however, there are two things that you will have to change.

1. The ObjectDataSource has a FitlerExpression property that set the filter for the data source. That isn’t available on the SPDataSource object. Instead we have the SelectCommand property. The format string for this property is the same as in a standard CAML Query where clause.

2. We will need to set the SPGridView DataSourceID property instead of the more normally used DataSource property.

3. We have to add the SPDataSource control to the Controls colelction of the Web Part.

So let’s look at some code samples.

First, we have our usual suspects, one SPGridView and one SPDataSource:

private SPGridView gridView;
private SPDataSource dataSource;
this.dataSource = new SPDataSource();
this.dataSource.ID = "myDataSource";


In our CreateChildControls() method ( if it’s in a Web Part), we can do much of the work. I have commented the code, so I will not say so much about it more.

this.gridView = new SPGridView();
// Get our currnet Web object
SPWeb web = SPContext.Current.Web;
// And the SPList
SPList taskList = web.Lists["Tasks"];
// Assign the SPlist to our SPDataSource object
dataSource.List = taskList;
// Add our SPDataSource object to the Controls collection so that our SPGridView can find it.
// Disable auto generation of columns
this.gridView.AutoGenerateColumns = false;
this.gridView.ID = "gridView1";
// Add the Title column.
BoundField colTitle = new BoundField()
DataField = "Title",
HeaderText = "Title",
SortExpression = "Title"
// Add the Status column
BoundField colProgress = new BoundField()
DataField = "Status",
HeaderText = "Status",
SortExpression = "Status"
// Enable filtering
this.gridView.AllowFiltering = true;
// We will not filter on the Title, so start with a comma
this.gridView.FilterDataFields = ",Status";
// Set the propertyname of the data source object
this.gridView.FilteredDataSourcePropertyName = "SelectCommand";
// Set the filter format. {1} will contain the column and {0} will contain the value.
this.gridView.FilteredDataSourcePropertyFormat = "<View><Query><Where><Eq><FieldRef Name='{1}'/><Value Type='Text'>{0}</Value></Eq></Where></Query></View>";
// Set the DataSource ID to our SPDataSource.ID
this.gridView.DataSourceID = "myDataSource";
// Add the GridView to our Controls collection
// Now data bind.

No spyware protection warning from Windows Home Server

Ever since I have start to user Windows Home server, this warning: no spyware protection has bugged me every time I re-boot my PC. I am running Windows 7 with Microsoft Security Essentials, both updated with the latest Windows Update and security definitions. So I’m pretty sure that I have spyware protection on my system.

It turns out that the Security Center service is set to have a delayed start. This means that the Windows Home Server Connector starts before the Security Center. The result is that it thinks that no Spyware Protection is installed on your system. So how to fix this?

It’s really simple. All you have to do is to tell the Service Manager to not delay start the Security Center Service. Press your Windows Key and type “services”. (Or press Windows Key+R and type “services.msc”) .

Services applet

Right-click the Security Center entry and select Properties.

Security Center

Change the Startup type to Automatic (instead of Automatic Delayed Start) and click Ok.

That should do it. The next time you re-boot your PC, the warning should have gone away.