Using a Script Configuration to SharePoint -vs- Using the Configuration Wizard.

Add a comment April 16th, 2010

I’ve been deploying SharePoint for years, I’ve always used the Microsoft Office SharePoint Configuration Wizard to configure the farm.  Recently I had a customer ask me how they could customize the name of the AdminContent database that the wizard randomly names it something like:


I’ve never minded this much; however,  if you happen to be using the same SQL server instance for multiple SharePoint deployments, it could get confusing as to which AdminContent goes with which farm, or maybe you want ALL your your SharePoint databases to follow a certain naming convention.

Whatever the reason might be,  I put together this small script that will allow you to customize the AdminContent database name as well as being able to offer the ability to hand your customer or whoever a sure way of configuring SharePoint the same every time:

cd C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN
PSConfig.exe -cmd configdb -create -server SQLServerName\Instance -database NameOfConfigDB -user DOMAIN\FarmAdminAccount -password FarmAdminPassword -admincontentdatabase NameOfAdminContentDB
psconfig.exe -cmd helpcollections installall
psconfig.exe -cmd secureresources
psconfig.exe -cmd services -install
stsadm -o spsearch -action start -farmserviceaccount DOMAIN\WSSSearchAccount -farmservicepassword WSSSearchPassword
stsadm -o osearch -action start -role IndexQuery -farmserviceaccount DOMAIN/OfficeSearchAccount -farmservicepassword OfficeSearchPassword -farmcontactemail
psconfig.exe -cmd services -provision
psconfig.exe -cmd installfeatures
psconfig.exe -cmd adminvs -provision -port PortNumberForCentralAdmin –windowsauthprovider onlyusentlm
psconfig.exe -cmd applicationcontent -installcode

For a complete reference of commands and switches, please visit:

  1. No comments yet.Be the first ?
  1. No trackbacks yet.
Comments feed