Attention: open in a new window. PDFPrint

The SharePoint 2010 Beta Setup Mess

After seeing the presentations of the SharePoint Server 2010 on the Microsoft stand on the CeBIT 2010 I decided to install an own instance to test the features of the new SharePoint Server. I just started to fulfill all basic requirements:

  1. Getting myself a 64bit capable machine with Windows Server 2008 R2 installed
  2. Installing the SQL Server 2008 including SP1 (ignoring the incompability warning and installing SP1 directly after the SQL Server Setup does a great job)
  3. During the setup I found out that it is necessary to install at least the CU1 for the SQLServer 2008 SP1. It turned out that it was not possible to install this UC1 at all (at least on my system) so I used the UC6 I’ve found here:

Then I started the Setup to install all the SharePoint Server 2010. After installing the “software prerequisites” using the menu item on the welcome screen I just started the setup. Within the setup I did not use the single-click installation but chose the creation of a full installation creating a new server farm. So far so good.

But now, if you try to start with the configuration you will find a big difference between the MOSS 2007 and MOSS 2010 setup: The setup will not allow any selection of a local user for the database connection but needs a ActiveDirectory-user. This site describes how you could install a MOSS 2010 using a local account:

In my case just using the command

PSCONFIG.EXE -cmd configdb -create -server MOSS
-database SharePoint_config
-user MOSS\SharePoint_user
-password SharePoint_user_pass
-passphrase SharePoint_user_pass
-admincontentdatabase SharePoint_admincontent

did the job and I did not need to use the New-SPConfigurationDatabase script. I installed the MOSS2010 system on an local SQL-Server called on the system called MOSS using a previously created user MOSS\SharePoint_user with the password SharePoint_user_pass to connect to the databases SharePoint_config (for configuration) and SharePoint_admincontent (for the admin-content database). The SharePoint-setup complained about the local user (and warned, that it could only be used for local databases) but continued installing the content databases. Afterwards executing


allowed me to finish the setup process by selecting that I did not want do disconnect from the current server farm.

If you like using the configuration script instead, take a look at this site to learn how to get the SPModules for powershell:

Edit: You might also take a look at this article as there is also an other bug during service creation!