Geoff Varosky's Blog

In addition to what I have posted over the past few days regarding the SharePoint 2010 Beta 2 awe and wonderment, I will be keeping this blog entry as my running post for hosting links to other blogs, resources, etc, regarding installation and configuration considerations.

• Bill Baer – Installation Notes for Microsoft SharePoint Server and Microsoft SharePoint Foundation 2010 Beta
• Sahil Malik – SharePoint 2010 Development Environment – Practical Tips
• Erik Kraus – SharePoint 2010 Beta 2 is finally here!
• Jei Li – Installation Notice for SharePoint 2010 Public Beta
• MSDN – Setting Up the Development Environment for SharePoint Server
• SharePoint Dev Wiki – Install SharePoint 2010 Public Beta on Standalone Windows Server 2008

This is a quick visual guide to installing and configuring Microsoft SharePoint Server 2010 Beta 2, as it is from my experience. My environment is configured as such:

• Virtual Image running on VMWare Player, on top of Windows 7 Enterprise x64
• Windows Server 2008 R2
• SQL Server 2008 SP1 CU2
• AD, SQL, and SharePoint all co-existing on the same virtual image

This tour will not encompass the SQL or AD configuration however. Possibly in a later post I will cover those, but, just wanted to share the experience of configuring this beauty from a first-timer’s perspective. My friend Erik Kraus has a nice post with details and links to great sources of information regarding prerequisites, and installation instructions here: http://blogs.msdn.com/ekraus/archive/2009/11/17/sharepoint-2010-beta-2-is-finally-here.aspx

First, you will need to download the beta, then double click the executable file, and you’re off to the races.

Checking the first option allows you to review the hardware and software requirements for SharePoint 2010. These are important! I suggest you do so before continuing. Once you have read these, it also make sense to read the installation guide.

Once you have read up on the requirements and installation procedures, it is time to move on down the line to the Install software prerequisites action. This will run through the SharePoint Products and Technologies 2010 Preparation tool, which as the screenshot below dictates, it installs and configures the following products:

• Application Server Role
• Web Server (IIS) Role
• Microsoft SQL Server 2008 Native Client
• Microsoft “Geneva” Framework Runtime
• Microsoft Sync Framework Runtime v1.0 (x64)
• Microsoft Chart Controls fro Microsoft .NET Framework 3.5
• Microsoft Filter Pack 2.0
• Microsoft SQL Server 2008 Analysis Services ADOMD.NET

Click Next >

Agree to the EULA and click Next >

The tool will then run through its paces, and if all goes well, you will see the following screen, letting you know that all the prerequisites have been installed or enabled.

You will now be back at the trusty splash screen. Go ahead and click on Install SharePoint Server

Then enter in your product key, which will be validated, and once so, the Continue button will light up. Click it.

Agree to another EULA and click Continue

In this “Choose Your Own Adventure” story, I selected Server Farm.

Editor’s Note: Unfortunately I missed a screenshot here, of the Server Type screen. I hope to have a screenshot of it here shortly. Onwards!

Next, on the File Location screen, these are the defaults, which I kept, as I only have the one partition on my virtual image. Then click Install Now if you are fine with these settings

The installation begins! Once this process finishes, you will be presented with the following screen to run the SharePoint Products and Technologies Configuration Wizard – let’s do that.

The wizard will then load. Go ahead and click Next > to begin.

You’ll get this familiar pop-up.. go ahead and click Yes.

Choose Create a new server farm and click Next >

Here you will need to specify your database configuration settings. Fill those in and click Next >

If by chance you are not “up to code” on your version of SQL, you will get this error

Otherwise, you will see this next screen

Here, you will specify a password for your new SharePoint farm. As it states above, the password “is used to secure farm configuration data and is required for each server that joins the farm”. It also states that it can be changed, but, you may want to jot this down somewhere. Once entered, click Next >

Specify the Central Administration port (I am partial to 9999), or let it auto-assign a random port for you. And choose your authentication method. I stuck with NTLM for now. This can be changed later on. If you decided on Kerberos here, you’d get this message after clicking Next >

But I didn’t, so we didn’t see that…. so after clicking Next > we see the following summary screen.

Click Next > here to apply these settings, or, click < Back to go back and change these if needed.

This will then kick off into the 10 step configuration process.

On successful configuration, and clicking Finish, you will be directed into Central Administration to the following URL: http://sp2010dev-01:9999/_admin/adminconfigintro.aspx?scenarioid=adminconfig&welcomestringid=farmconfigurationwizard_welcome

And you can see your new baby for the first time. Awww… so sweet and cuddly. I think I’ll name her Jane.

You will first be prompted to join the Customer Experience Improvement Program, I selected yes, and went on my merry way.

That is it for now… more to come soon! Thanks for watching.

So, here I am, going through my installation of the SharePoint 2010, and received my first error! The error (full text below), came while configuring the services via the Initial Farm Configuration Wizard

Errors occured.

The service application proxy "User Profile Service Application" could not be provisioned because of the following error: Unrecognized attribute ‘allowInsecureTransport’. Note that attribute names are case-sensitive. (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\Profile\client.config line 56)

Corelation Id: bf7f0c8a-97f2-4250-b4e5-04c4d74eff3e

DOH! In addition to this error, not only is this halting my forward progress, and not this has anything really to do with anything, but, hopefully they run a spell check before this gets to RTM. There are two spelling mistakes in the message above (bolded and underlined). Anyways, I did a bit of searching on the interwebs for this, and it appears that it is a known issue on both Windows 7, and, Server 2008 R2, the latter of which I am running.

It appears that there is a fix coming down the pipe from Microsoft, according to this post on the SharePoint TechNet Forums: http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010general/thread/041ddc78-8d18-4753-b7be-8d8113e26e62, as there is an issue with WCF on the two aforementioned platforms, as they share the same core.

There are also workarounds posted (like here: http://mphacker.spaces.live.com/Blog/cns!8040CC624DDC5404!790.entry), however, these come in the form of modifying a file within the “SharePoint Root” [14 Hive] (the file mentioned in the error). This is unsupported, but, guess what, so is the Beta copy of SharePoint 2010. However, in the article above, some issues have arisen by modifying the file directly.

There is no release date that I am aware of for the patch, however, a search on Google nets the following

It appears it was there at some point, however, it has since been removed (“Sorry, but we couldn’t find the page that you requested.”). I’ll make another post as soon as I see it comes out. In the meantime, I am holding off on my installation until the fix comes out so I can have a “clean” fresh install.

UPDATE: Hotfix has been released! WCF Hotfix (KB976462) for Windows Server 2008 R2 

Did I mention I was excited? After all of this hype, and my excessive drooling at the SharePoint Conference this year… I am installing SharePoint 2010.

I received an email from Bjørn Furuknap today, and was delighted with what it contained. So I do not steal his thunder, give a read (link below) BEFORE you go installing the beta to save you some hassle.

http://furuknap.blogspot.com/2009/11/installing-sharepoint-2010-beta-2-how.html

** Updated 11.17.09 **

A reader of my blog, Arif, posted this morning in the comments, that it can definitely be done using local accounts – he was kind enough to share this link from the SharePoint From The Field Blog: http://sharepoint.microsoft.com/blogs/fromthefield/Lists/Posts/Post.aspx?ID=112 Thanks Arif!