Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

We're looking at deploying SharePoint within our company, and there's one question that I haven't been able to find any advice on. The enterprise is currently setup with a single root domain that is essentially empty, and several child domains for each of our major locations.

Our SharePoint deployment will only consist of a single SP server for the enterprise as the initial usage will be kept relatively small. A separate SQL Server used for the database.

What I haven't been able to figure out is what domain should the server be setup in? Does it matter? What about all the various service accounts? Do they need to be in the same domain as the server?


share|improve this question
up vote 0 down vote accepted

Our SP environment is setup this way, all servers and service accounts reside in the root domain, but all actual users reside in 4 child domains. Depending on how many features you want to implement for users and the nature of security restrictions with AD trusts, firewalls, etc, you would have to open up several ports from the SP servers to child DCs and other resources.

share|improve this answer

I believe that you can go as your hart contend. If all the domains are in the same forest, Or in other trust relationship, you can choose what ever looks best for you from administration point of view.

share|improve this answer
Thanks Igal. That's what I figured, but I haven't been able to find any documentation about it one way or another. – Evan M. Sep 17 '09 at 19:36

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.