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

There is a current debate between co-workers about the INETPUB folder. There are several people whom want not to deploy web apps into the inetpub folder but create a virtual directory instead and have the apps live in a different folder. And, there are some that want to use the inetpub folder and not have to create the virtual directories.

I was wondering are there any pros or cons for not putting apps in the inetpub folder and just reference them through a virtual directory?

share|improve this question
up vote 1 down vote accepted

I don't see any reason NOT to use the INETPUB folder, but that said, we don't use it.

However, the REASON we don't use it is because for purely technical reasons. Our back-end pre-processor (a proprietary ISAPI DLL) plays much nicer when you use a different directory.

The only other reason I can think of to not use it is "Security though Obscurity", if someone does gain access to the box they won't instantly know where to go to find the websites. Of course this will only slow them down by about 60 seconds, and security through obscurity is worse than no security.

share|improve this answer
It will also stop almost all of the dumb scripts which put data in INETPUB. It is also a good way to seperate data & (OS) code, putting the sites on a different drive. – LapTop006 Jan 1 '10 at 7:41
Actually there's some very useful scripts under inetpub/adminscripts – Mark Henderson Jan 1 '10 at 8:35

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.