I got some inspiration reading the Technet article Deploy by using DBA-created databases (SharePoint Server 2010) the other day. We can deploy SharePoint 2010 without the central administration (CA) database having the annoying GUID.
If we run the SharePoint configuration Wizard after installation it will create content database with GUID. However, if we create CA content database using PowerShell we can have the database name of our choice. I have also referred to the SPModule PowerShell Scripts available from Microsoft. Here are the steps:
1. Run Setup on each server computer in the farm. You must run Setup on at
least one of these computers by using the Complete installation option.
2. Do not run the SharePoint Products Configuration Wizard after Setup
finishes.
From the SharePoint 2010 Management Shell, use the
New-SPConfigurationDatabase command to create a new configuration database,,for example:
New-SPConfigurationDatabase -DatabaseName "SharePoint_Config"
-DatabaseServer "SQL_DB" -Passphrase (ConvertTo-SecureString "MyPassword"
-AsPlainText -force) -FarmCredentials (Get-Credential)
-AdministrationContentDatabaseName "SharePoint_Admin_Content"
The cmdlet above creates a config db named “SharePoint_Config” and also
creates the central admin content database and names it
“SharePoint_Admin_Content”. Values in quotes in the above command can be
customized.
For more information, see New-SPConfigurationDatabase:
http://technet.microsoft.com/en-us/library/ff607838.aspx
4. Run the following commands in order
a. #install help collections
Install-SPHelpCollection -All
b. #Secure resources
Initialize-SPResourceSecurity
c. #Install Services
Install-SPService
d. #Install Features
Install-SPFeature -AllExistingFeatures
e. #Provision Central Administration on port 2010
New-SPCentralAdministration -Port 2010 -WindowsAuthProvider "NTLM"
f. #Install Application content
Install-SPApplicationContent
This finishes the setup and provisions Central Administration website on port 2010.
If we run the SharePoint configuration Wizard after installation it will create content database with GUID. However, if we create CA content database using PowerShell we can have the database name of our choice. I have also referred to the SPModule PowerShell Scripts available from Microsoft. Here are the steps:
1. Run Setup on each server computer in the farm. You must run Setup on at
least one of these computers by using the Complete installation option.
2. Do not run the SharePoint Products Configuration Wizard after Setup
finishes.
From the SharePoint 2010 Management Shell, use the
New-SPConfigurationDatabase command to create a new configuration database,,for example:
New-SPConfigurationDatabase -DatabaseName "SharePoint_Config"
-DatabaseServer "SQL_DB" -Passphrase (ConvertTo-SecureString "MyPassword"
-AsPlainText -force) -FarmCredentials (Get-Credential)
-AdministrationContentDatabaseName "SharePoint_Admin_Content"
The cmdlet above creates a config db named “SharePoint_Config” and also
creates the central admin content database and names it
“SharePoint_Admin_Content”. Values in quotes in the above command can be
customized.
For more information, see New-SPConfigurationDatabase:
http://technet.microsoft.com/en-us/library/ff607838.aspx
4. Run the following commands in order
a. #install help collections
Install-SPHelpCollection -All
b. #Secure resources
Initialize-SPResourceSecurity
c. #Install Services
Install-SPService
d. #Install Features
Install-SPFeature -AllExistingFeatures
e. #Provision Central Administration on port 2010
New-SPCentralAdministration -Port 2010 -WindowsAuthProvider "NTLM"
f. #Install Application content
Install-SPApplicationContent
This finishes the setup and provisions Central Administration website on port 2010.
Comments
All what is missing is to start the required services of the SharePoint Administration and Timer.