SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a new SharePoint installation to do and i really don't want to have GUIDs in the databases. What do i need to do before install to avoid this. maybe create the databases before installation or maybe using Powershell. But what are the steps to take to do this i.e when to use Powershell to install the config DB etc.. Thanks in advance

share|improve this question
up vote 5 down vote accepted

The best description I've seen is Todd Klindts How to create a SharePoint 2010 farm with no GUIDs using PowerShell

If you've already created your farm you can follow his other post Getting the GUID out of the AdminContent database in SharePoint 2010

share|improve this answer
Thanks Per.But i don't want to get rid of it i want to avoid it before installation. Cheers – naijacoder Aug 2 '12 at 6:46
Sorry was the wrong post, answer updated – Per Jakobsen Aug 2 '12 at 6:52
Thanks.No idea how i missed that on todds blog.Do you know if i can use this approach for services applications too? – naijacoder Aug 2 '12 at 7:09
Most of the service applications will allow you to specify the database names in the UI unless you use the Wizard. If you want some wizard like experience and/or are setting up a lot of farms then you might want to take a look a SPAutoInstaller – Per Jakobsen Aug 2 '12 at 7:14

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.