Installing SharePoint 2010 Beta 2 – How to Completely Mess up Everything

Update: If you want a free 35 page ebook, covering amongst other, installing the public Beta of SharePoint, just head over to the Introducing SharePoint 2010 website and download the free first issue.

Well, it’s finally here. The first official beta of SharePoint 2010.

16.11

Warning! Before you pop the Champagne, you should pay careful attention, as the install process is somewhat tricky. In fact, you risk having to reinstall SharePoint completely, or even your entire server, if you do this like some did in SharePoint 2007. And it’s a big cleanup job.

DO NOT start installing anything until you have read this entire article.

Let me walk you through the steps until you’re screwed, pardon my language.

Of course, you’ll need the installer file (en_office_sharepoint_server_2010_beta_x64_x16-19249.exe in my case) that contains the nice setup splash screen you see above.

If you ready me previous post on installing SharePoint 2010 Beta 1, you may remember that I never got the prerequisites install to work. You’ll be happy to know that, this time, at least to me everything went smoothly. Hit the Install software prerequisites link and go through the steps:

11-16-2009 10-24-34 AM

The prerequisite installer will download any required file for you if you are connected to the internet, so just kick back and relax for a few moments.

After installing the required software and configuring everything, you can now hit Install SharePoint Server. However, this is where things get really tricky.

If you are like me, you’re used to setting up a local farm-configured machine and use local accounts for running services and connecting to the database.

DO NOT attempt this in SharePoint 2010 Beta 2.

Here’s the catch. SharePoint 2010 requires a domain account for any setup that is not Standalone setup. And you know what the Standalone is right? that’s the “I’m completely stupid” mode, in which you get a limited SQL Server Express.

That’s right, gone are the days of single server installs with SQL server and somewhat configurable setups. Either your SharePoint Server 2010 needs to be part of a domain or you are reduced to the “My brain went AWOL” mode.

So you need a domain controller. Don’t think it’s as easy as adding one to your SharePoint server, though, as adding an AD controller role after you have configured all your prerequisite services leads to… issues.

If you are too eager to start the install and have already run the prerequisite installer, well, it’s time to remove all the services and roles, add the AD controller, and then run everything from scratch.

OK, so in short, get your AD up and running prior to starting SharePoint install. If not, you’ll be very, very surprised and, like me, reinstall at least a couple of times.

.b

Found this article valuable? Want to show your appreciation? Here are some options:

a) Click on the banners anywhere on the site to visit my blog's sponsors. They are all hand-picked and are selected based on providing great products and services to the SharePoint community.

b) Donate Bitcoins! I love Bitcoins, and you can donate if you'd like by clicking the button below.

c) Spread the word! Below, you should find links to sharing this article on your favorite social media sites. I'm an attention junkie, so sharing is caring in my book!

Pin It

Published by

Bjørn Furuknap

I previously did SharePoint. These days, I try new things to see where I can find the passion. If you have great ideas, cool projects, or is in general an awesome person, get in touch and we might find out together.

4 thoughts on “Installing SharePoint 2010 Beta 2 – How to Completely Mess up Everything”

  1. Thanks for this post. I was able to install AD DS on my VM first and avoid the issue you ran into. So far so good. I'll post my full experience once I've got all the goodies installed. So far I've got Windows Server 2008 Standard, SharePoint Server 2010, and Visual Studio 2010 installed. Next is Office 2010…

Leave a Reply

Your email address will not be published.