Questions[application-pools](server)

We are about to deploy a bunch of sites to some new servers. I have the following questions about application pools:

1. It seems advisable to have one application pool per website. Are there any caveats to this approach? Will one application pool hog all the CPU, Memory, Etc...?

2. When should you allow multiple worker processes in an application pool? When should you not?

3. Can private memory limit be used to prevent one application pool from interfering with another? Will setting it too low cause valid requests to recycle the application pool without getting a valid response?

4. What is the difference between private and virtual memory limits?

5. Are there compelling reasons NOT to run one application pool per site?

I have an application in one of my application pools that has a virtual path of /Site/login.aspx. I want to remove it but it no longer exists on my computer and it's causing me issues setting up AppFabric.

I understand that you can remove these phantom applications by recreating the application in IIS and then hitting Remove. That will get rid of the application from the pool but in this case I can't recreate the application due to the /login.aspx in the virtual path

Any ideas how I remove this erroneous entry?

I have a small ASP.NET test script that opens a connection to a SQL Server database on another machine in the domain. It isn't working in all cases.

Setup:

IIS 7.5 under W2K8R2 trying to connect to a remote SQL Server 2008 R2 instance. All machines are in the same domain.

Using the ApplicationPoolIdentity for the web site it fails to connect to the SQL Server with the following:

Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

However if I switch the Process Model Identity to NETWORK SERVICE or my domain account the database connection is successful.

I've granted the \$ access in SQL Server.

I am not doing any sort of authentication on the web site, it is just a simple script to open a connection to a database to make sure it works.

I have Anonymous Authentication enabled and set to use the Application pool identity.

How do I make this work? Why is the ApplicationPoolIdentity trying to use ANONYMOUS LOGON? Better yet, how do I make it stop using the Anonymous logon?

In the vein of this question.

Other questions have touched on this, but let's get a complete answer down:

1. What specific permissions are necessary for a generic IIS 7 site with a domain user as the app pool identity?

2. What specific permissions are necessary for an ASP.NET IIS 7 site with a domain user as the app pool identity?

3. Are there any tricks/shortcuts to applying these permissions?

I have multiple web sites hosted with IIS 6.0 on Windows Server 2003. Some of them use the .Net 1.1 framework while the others use .Net 2.0. I currently have application pools set up for each framework. Are there any other reasons to add additional application pools?