Thanks to Chandima for this tip on how to avoid having GUIDs in your database names. I have a post here that details how to change the database name after the fact, but Chandima tells us how to avoid this to begin with.
Avoid those GUID database names
My installs are always done using the PSCONFIG and STSADM command line utility. Here is a quick overview of my install steps. The prerequisites for the install are that you have 5 domain accounts created in your AD. Add the "setup account" as the Local administrator to the server where you are installing SharePoint. (See my previous detailed post about accounts and setup) Essentially by using the command line tool you can create and configure the farm very easily.
- Run the "OfficeServerwithSP1.exe" (Select Advanced and Install as "Complete")
- Make sure that I DON’T run the "Configuration Wizard"
- Open command prompt and set the location to "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN"
- Run the following command. This will create your configuration DB and the Central Admin content DB
psconfig.exe -cmd configdb -create -server KCSPRV01 -database SP_Config_KC -user KC\SPAdmin -password pAss5worD2 -admincontentdatabase SP_Central_Admin_Content_KC- Provision the Central Administration web site by running this script (In this case my CA web site is http://KCSPRV01:6036
psconfig.exe -cmd adminvs -provision -port 6036 -windowsauthprovider onlyusentlm- Install all the required services
psconfig.exe -cmd services install- Secure the resources and grant the appropriate permissions and registry entries (This is an important step to ensure that you grant the correct permissions)
psconfig.exe -cmd secureresources- Start the Office Server Search Service (OSEARCH)
stsadm.exe -o osearch -action start -role IndexQuery -farmcontactemail demo@kcue.net -farmperformancelevel PartlyReduced -farmserviceaccount KC\SPSearch -farmservicepassword pAss5worD2- Start the SharePoint search service (SPSEARCH) Requires a DB to be created
stsadm.exe -o spsearch -action start -farmserviceaccount KC\SPSearch -farmservicepassword pAss5worD2 -farmcontentaccessaccount KC\SPSearch -farmcontentaccesspassword pAss5worD2 -databaseserver KC -databasename SP_Search_KC- Install all MOSS features by running – psconfig.exe -cmd installfeatures
Now you are done! No guid DB’s in the above install. You should be able to now navigate to Central Administration and configure your SSP and continue your farm configuration.
You can also configure My sites host and your Shared Services Provider using the command line.
If you require to build a farm then you can also use a scripted farm build as per the guidelines provided on TechNet.
Random Posts
Loading…