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

What is the best practice when going through "Configure your SP farm" Services portion? Where all the services are checked and either will use existing managed account or ask you to create new managed account?

How do I find out what are these in production so this dev can be similar to production?

share|improve this question
up vote 1 down vote accepted

Do you mean the Farm Configuiration Wizard in Central Admin?

The general consensus on the FCW is, use it very sparingly. It's fine if you want a quick overview of SharePoint or you are setting up a non-specific Dev workstation. The Wizard uses a bunch of default settings that go against most enterprise best practices, most notably using the same accounts everywhere and randomly-named databases. Also as you have found out, it's pretty obscure what exactly it is doing with your farm.

See for example these articles: Link 1, Link 2

For a controlled, repeatable installation you can look into the AutoSPInstaller Project on Codeplex

If you want to set up the services with the same information, you can look through Central Admin on your production farm and write down the settings in AutoSPInstaller's config files, so you'll have a reusable template. Some of the more obscure settings might need to be fetched with Powershell.

share|improve this answer
Thanks for the overview. our prod is setup with best practice in mind. I guess I will run some powershell or use CA ui to find service acct for ea service app. Thanks – M. Todd Feb 7 '12 at 17:41

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.