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.

Comments

Anonymous said…
Tested and worked fine thanks.
All what is missing is to start the required services of the SharePoint Administration and Timer.

Popular posts from this blog

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker: ...

"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.

Page layout HTML changes not reflected in associated aspx

I had this issue for quite sometime with a SharePoint Online project I was working on. I use Design Manager to create a new layout page and add snippets to the html layout. I would create webpart zones, add my webpart snippets on to the html, save and publish but the resulting aspx page wouldn't have any of my webparts in it. I checked it from SPD 2013 and everything looks perfect, I can see all the code snippets in there. It was really strange and I had no clues. I had some content search webparts in the layout and one content editor webpart with a link to a text file with some css in it. After countless hours on the internet I read about few other people having similar issues when they had custom css on the layout pages to hide quick launch. I tried removing my content editor webpart and everything seems to be normal. A new page created using the layout had all the webparts in it and even the layout preview was displaying fine. I needed this css somewhere on the page and ...