Server Fault is a question and answer site for system and network administrators. 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 Windows Server 2008 R2 that is not join to any domain.

I have developed an web application that will display the domain name and the username on the server itself.

However, when I publish my web application to IIS, it always fail and display different types of error messages (because I change settings such as Enabled ASP.NET Impersonation, Disable Anonymous Authentication, Set Application Pool to Classic and so on)

So, I was wondering if it is necessary for the Server to join in a domain so that I can reduce any unnecessary error message and be able to zoom into the correct direction?

share|improve this question
up vote 1 down vote accepted

If your application is throwing errors due to configuration changes you've made to IIS, then joining an AD domain isn't going to help you.

You'll just need to buckle down, read through the error messages, and start your troubleshooting process.

share|improve this answer
Are there any good guides on how to setup a IIS and the different configuration required for different scenarios and purpose? (that you can recommend) – Jack Sep 7 '12 at 2:59
Sorry, no recommendations here. – EEAA Sep 7 '12 at 3:03
Agreed, this is a config and code issue. What kind of application have you developed (recently) that requires you to make all of those config changes. None of them should be needed. – Brent Pabst Sep 13 '12 at 19:55

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.