Application Server Structure

[powlaz]

I am stuck for ideas and can't find much in Google about how to organize an application server. 

Currently programs with very limited access that are run from the server are installed to a directory in a mapped drive F:.  The F: drive also contains restricted files for the same group of users.

Programs that can be run by everyone from the server are installed in a mapped drive G:  The G: drive also contains all of the rest of the company files.

I expected to leave F: and G: for files and create a P: drive for programs.  The problem I am having is:

1.  Is it commonplace for everyone in a company to be able to see the install directory of a program?
2.  I need to keep most every user from parusing the restricted programs' installation directories.

Maybe I just worked this out.  If it's not a bad thing to have the entire company mapped to the P: drive then I could Share this drive with Everyone and then lock down the various directories accordingly.  Also, now that I think about it, using advanced permissions I should be able to fix it so authorized users have full access to the directories but are not capable of moving or deleting them, right?

If my realization is right I guess my big concern is with how most companies structure their application servers - are the program directories visible?  If not, how are they kept from the user's sight but still available to use?

Thanks for the help,

Po

[Spero-T]

http://livedocs.adobe.com/dreamweaver/8/using/wwhelp/wwhimpl/common/html/wwhelp.htm?context=LiveDocs_Parts&file=25_weba4.htm

Man not sure but thats all i could find on google..

[mektek]

Start with what server program you are using. They all operate "slightly" different.

Server2000 Small enterpise? Server 2003 Enterprise? Appache?

[powlaz]

Thanks for the replies guys.  I didn't check the link yet.  Just wanted to give more information: 

We have Windows 2003 Standard R2 SP2 servers.  What more information can I give you that's relevant?

Po