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'm working with a company whose infrastructure team could use some guidance for deploying a .Net application. I've seen some incredible guides for programming best practices with .net. Are there any similar guides or resources for configuring IIS and windows that I could pass along?

Any assistance appreciated.


locked by HopelessN00b Dec 5 '14 at 10:19

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

Not sure if this is what you are looking for, but checkout the IIS 6 Operations Guide on MS TechNet.

There are a lot of free MSDN magazine articles and TechNet articles about IIS and ASP.NET optimization and so on. You can search for that inside – Lex Li Jun 8 '09 at 12:28

A few things that I've learned (the hard way) over the past few years about deploying for .NET:

  1. Create App Pools - For all applications important enough to "not be bothered" by the need to jumpstart the web server processes of other apps, give them their own Application Pool.

  2. InProc == Pure Evil - imho (flames will no doubt ensue) In-Proc session state is one of the most dangerous features in .NET. It makes processes less resistant to restarts and encourages some poor practices. Using the Session State server where possible is how we operate these days.

  3. Minimalism is a good thing - Remove any IIS services that you don't need. If you don't need FTP, Mail etc; turn these off.

Another excellent guide/checklist here:

And a decent security article here:


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