Can’t be. Can it? This is indeed last in this 2 part series on MOSS scripted installation. Later in the week, I will round up all posts and make a single ‘index’ of the series. 

I started MOSS2007 installation series last year. I haven’t been able to publish this post – in draft since November 2007.

Call this blessing in disguise, since I learnt few things and made changes in this script as time went by.

I have been using this script in our test environment – virtual as well in single server installation for our project. To give you a brief overview of the project – I am the sole developer for installation of 1300 single server MOSS installation (selfish plug 🙂 ). It has to be scripted 100% up until web apps and site collection creation. More on the project later – a lot will come through, since I am working on 2 projects interlinked  – this is the biggest project in Australia on Microsoft Office SharePoint Server 2007 platform.

So far I have achieved the following unattended installation

  1. .Net3
  2. SQL Server Express Edition / SQL Server 2005
  3. Microsoft Office SharePoint Server 2007
    1. Customised config.xml to setup Server12
    2. Psconfig.exe command line to do post setup configuration (Install features, Secure resources, Provision Central Administration)
    3. STSADM command line (Extending Web Apps and Creating Sites)

Let’s see 3.2 and 3.3 here

Command to create SharePoint_Config database with the instance name, username and password specified as parameters when executing the batch file. I will upload the batch file and share the same via skydrive by this weekend.

psconfig -cmd configdb -create -server %COMPUTERNAME%\%5 -database SharePoint_Config -user %3 -password %4

Following commands install help collections; secure resources, installs – services, features and application content and also provision the Central Administration on port 8000.

psconfig -cmd helpcollections -installall

psconfig -cmd secureresources

psconfig -cmd services -install

psconfig -cmd installfeatures

psconfig -cmd adminvs -provision -port 8000 -windowsauthprovider onlyusentlm

psconfig -cmd applicationcontent -install

Command is to setup Office Search Service

stsadm -o osearch -action start -role indexquery -farmcontactemail %2 -farmserviceaccount %3 -farmservicepassword %4 -defaultindexlocation "C:\Program Files\Microsoft Office Servers\12.0\Data\Applications"

Command to create Shared Service Provider Web application with database name that you provide

stsadm -o extendvs -url http://%COMPUTERNAME%:8010 -ownerlogin %1 -owneremail %2 -databaseserver %COMPUTERNAME%\%5 -databasename WSS_Content_SSPAdmin -exclusivelyusentlm -apidname "SSP – 8010" -apcreatenew -apidtype configurableid -apidlogin %3 -apidpwd %4

Command to create My Site Web application with a database name that you provide

stsadm -o extendvs -url http://%COMPUTERNAME%:8020 -ownerlogin %1 -owneremail %2 –databaseserver %COMPUTERNAME%\%5 -databasename WSS_Content_MySite -exclusivelyusentlm -apidname "My Sites – 8020" -apcreatenew -apidtype configurableid -apidlogin %3 -apidpwd %4

Command to create Shared Service Provider and My Site

stsadm -o createssp -title "Shared Service Provider" -url http://%COMPUTERNAME%:8010 -mysiteurl http://%COMPUTERNAME%:8020 -indexserver %COMPUTERNAME% -indexlocation "%Programfiles%\Microsoft Office Servers\12.0\Data\Applications" -ssplogin %3 -ssppassword %4 -sspdatabasename SSPDB -searchdatabasename SEARCHDB

Command to create your Site Collection using appropriate site template

stsadm -o extendvs -url http://%COMPUTERNAME%:80 -ownerlogin %1 -owneremail %2 – databaseserver %COMPUTERNAME% -databasename WSS_Content -exclusivelyusentlm -apidname "SharePoint Site Collection" -sitetemplate SPSPortal -apidtype configurableid -apidlogin %3 -apidpwd %4

5 Parameters used in the commands above.

OwnerLogin OwnerEmail ServiceAccount ServiceAccountPassword DatabaseInstanceName

This series has been mentioned in a blog post written on SharePointBlogs – alongwith names like Joel Oleson, Ben Curry by echef.

Stay tuned, subscribe via email to know when I share the script and more on the project. Lots of juice to come, promise.