Skip to main content

SharePoint 2010 Central Admin database GUID

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.
Labels:

Comments

Anonymous said…
Tested and worked fine thanks.
All what is missing is to start the required services of the SharePoint Administration and Timer.
July 14, 2012 at 11:52 PM
Post a Comment

Popular posts from this blog

Difference between the architectures of SSPs and SharePoint Service Application

SharePoint 2010 has some new features and components, which help to overcome difficulties such as redundancy and service-sharing that we faced while using SharePoint 2007.  Services in MOSS 2007 were implemented with the help of Shared Service Providers or SSPs. But we cannot use the services of one SSP for another SSP. So each SSP has to have its own set of services and applications, which increases redundant data in the farm.  For example, different managers in the same organization use a SharePoint site to maintain official data associated with an SSP. This SSP is associated with different services, such as Search service, BDC service, and a user profile service. A project manager in this organization requests an exclusive user profile service to maintain project data security. To provide this, we first need to create a separate SSP for the project manager and then a separate service called user profile service - project name. Next, we need to associate the SSP with ...
5 comments
Read more

SharePoint Designer Workflow Failed to Start - Cancelled by System Account

I was working on a List workflow the other day in SharePoint Designer 2010. This list already had a workflow which was working perfectly fine and I needed another manual workflow in it. No matter what I tried the workflow would fail and would log a message in the history list that Workflow failed to start and it was cancelled by System Account . I observed that the same happened with new workflows in that list, new workflows in other lists and I even tried creating new subsites and workflows were behaving the same way. I googled for a while and there were many suggestions to clear SPD cache which did not help me. I played with SPD 2010 for a while and observed that the workflow xml and xoml files were checked out. I read in some blogs that this could cause this issue as well. I tried to check those files in but then I was greeted with a new error! " Cannot perform this operation. The file is no longer checked out or has been deleted ." I had no clue what was happening...
10 comments
Read more

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.
2 comments
Read more