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

Does Microsoft recommend deleting and cleaning up the Default Web Site instance and extra Application Pools from production web servers?

share|improve this question

migrated from Mar 27 '12 at 7:33

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

up vote 8 down vote accepted

Depends on what the server is going to be used for.

Some application installers assume the presence of the Default Web Site and DefaultAppPool, and these installers won't work properly if you've deleted the site.

Some might not even work properly if you recreate the site later before running the installer (unless you recreate it with the id 1- this was harder under IIS 6 than it is in 7).

If the server's to be used for hosting many websites and you're unlikely to run an installer that requires the use of the Default Web Site (Exchange and SharePoint in past versions used to do this), safest option is probably still to Stop or otherwise disable it, rather than to remove it outright.

As of IIS 7, any new websites created through the GUI default to getting their own App Pool, so any apps running under that website will run in that App Pool and not DefaultAppPool.

DefaultAppPool is usually a secondary consideration, and won't be used except by apps that explicitly name it or rely on its presence.

share|improve this answer

Yes, anything under the Default Web Site is still on your disk and virtual folders can be remade on another website with Powershell commands if necessary, for instance when creating an Outlook Web Access front-end.

An application pool is a pool for applications, if you remove all applications it would serve no purpose and can be removed. You can create those at any point, and they would be the same as the default application pool upon creation; as they would be default...

share|improve this answer

I think not. Also you don't want to delete it, you can limit access to this site to a particular ip address.

share|improve this answer

Normally I just stop the default website if it isn't going to be used for anything.

share|improve this answer
Could you provide some idea of why you do this and how it helps? Your answer presently has very little context. – nhinkle Mar 27 '12 at 1:46
I do the same. Keep orioginal config in place in case I need it. I use my own websites etc. for everything, and just disable default. – TomTom Mar 27 '12 at 7:39

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.