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

What are the pros and cons of running an ASP.NET web application in a domain (having domain controllers etc)

Edit Is it possible to scale up to a Server Farm without a domain? yes


1) Easier to Manage Permissions/Access across machines?


1) Requires additional machines/expertise (domain controller and possibly a backup)

(will update based on answers)

share|improve this question

migrated from Aug 21 '09 at 11:24

This question came from our site for computer enthusiasts and power users.

up vote 1 down vote accepted

You don't need to run a domain to do a farm but I guess it will simplify your set-up a little in respect of permissions etc as you've said. You'll still need to do the usual MachineKeys syncing etc between servers to handle scenarios where requests are jumping between servers.

It's generally not recommended by MS to have your public facing web (or DB servers) also acting as DC's although I've done it on a number of occasions where we had limited resources and never had any issues.

share|improve this answer

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.