Torgeek
- Should application pools be set to run as application pool identity?
- What is the difference between application pool identity and custom account in IIS?
- What is the best practice for virtual memory limit in IIS?
Should application pools be set to run as application pool identity?
It is recommended that Application Pools be set to run as ApplicationPoolIdentity unless there is an underlying reason that the application pool needs to run as a specified end user account. One example where this is needed is for web farms using Kerberos authentication.
What is the difference between application pool identity and custom account in IIS?
Application Pool Identity - runs the Orchestrator website under the default identity of the application pool. Custom account - runs the Orchestrator website under an existing Windows or Domain identity.
What is the best practice for virtual memory limit in IIS?
We recommend leaving this as the default of 1740 to ensure that memory stays defragmented. Virtual Memory Usage: By default IIS sets this to 0, which means there is no limit to the virtual memory it can use. Because virtual memory cannot so easily be exhausted, there is usually no reason to set a limit on this.
