Application Pools are available only for IIS 6 or newer. For previous versions of IIS, any application pool related settings are ignored.
You can set a condition for the installation of this application pool. The condition will be evaluated during maintenance as well. Edit this field using Smart Condition Edit Control.
Use the following recommended condition so that application pools can get removed or installed during maintenance depending on how the user sets their feature states:
(!AppPoolFeature = 3 AND &AppPoolFeature <> 2) OR (&AppPoolFeature = 3)
Where AppPoolFeature is the identifier of the feature containing the required resources.
- On Demand - the application worker process is started the moment a request is received
- Always Running - the application worker process is started by IIS the moment the server itself is started.
Having it set to “On Demand“ reduces the resources comsumption on the server but might result in longer waiting times for the request to get a reply. Using the option “Always Running“ will make the application respond faster to the requests received, at the expense of hardware resources being occupied when the application is running without any user requesting it.
Start application pool immediately
If this option is checked, the Advanced Installer IIS configuration tool will attempt to start the associated worker process for the newly created pool when the installation is completed.
ASP.NET (IIS 7 or newer)
.NET Framework version
Select the .Net Framework version that will be loaded by this application pool. An application pool can only load one .NET Framework version; all applications in the application pool must use the same version.
- <default> - use the default .NET version for new application pools on the target machine
- v2.0 - specifies that the application pool will use .NET Framework 2.0, 3.0 or 3.5
- v4.0 - specifies that the application pool will use .NET Framework 4.0
- No Managed Code - select this option if the applications that you want to assign to this application pool do not contain managed code
Managed pipeline mode
Select one of the following values from the list to specify how IIS processes requests for managed content:
- Integrated - IIS processes requests for managed content with the integrated IIS and ASP.NET request-processing pipeline.
- Classic - IIS processes requests for managed content with the separate IIS and ASP.NET request-processing pipelines. Use this mode only when the applications in the application pool cannot run in Integrated mode.
Enable 32-bit applications on 64-bit Windows
If you check this option, on 64-bit versions of Windows the worker process(es) serving the application pool will be in WOW64 mode. Processes in WOW64 mode are 32-bit processes that can load only 32-bit applications.
Action if duplicate
Select the desired IIS configuration tool behavior when a duplicate Application Pool is found on the target server.
- Skip item installation - when a duplicate Application Pool is found the installer will automatically skip the item's installation and continue the setup.
- Rollback installation - when a duplicate Application Pool is found the installation will rollback with an error message.
- Prompt user to skip item or rollback installation - when a duplicate Application Pool is found the user will be prompted to choose whether to continue the installation skipping that item or to abort.
- Prompt user to overwrite item or rollback installation - when a duplicate Application Pool is found the user will be prompted to choose whether to continue the installation overwriting that item or to abort.
The overwrite operation cannot be undone by uninstall or rollback !
You can read more about application pools in this article.