When Web Interfaces sites or Program Neighborhood Agent sites are part of a large deployment and are the primary method of accessing applications for an organization, you might consider isolating each Web Interface site or Program Neighborhood Agent site into their own IIS Application Pool.
Background
Each separate Application Pool provides a process boundary so that when a Web Interface site or Program Neighborhood Agent site is assigned to one application pool, problems in other application pools do not affect the application. This ensures that if a Web Interface site or Program Neighborhood Agent site fails, it does not affect the other Web Interface or Program Neighborhood Agent sites running in other application pools.
The process to create an Application Pool for Web Interface or Program Neighborhood Agent site is as follows:
Note: Before performing these changes, ensure that no users are accessing the Web Interface or Program Neighborhood Agent sites because their access will get interrupted.
Windows 2003:
- Open IIS manager.
- Right click on the Application Pools node, click on New > Application Pool:
- Add a descriptive name to the Application pool ID textbox and select Use existing application pool as template, then pick the already existing Citrix*AppPool:
The Application Pool should now exist:
- Assign the Web Interface or Program Neighborhood Agent site to the newly created Application Pool (see screen shot below).
The Web Interface or Program Neighborhood Agent site will begin to use the new application pool for all its functionality from this moment on.
Windows 2008:
- Open IIS Manager.
- Right click on the Application Pools node, click on Add Application Pool:
- Add a descriptive name to the name of the application pool, and choose Classic for the managed pipeline mode:
Once the application pool is created, you need to make a few changes to mimic the application pool of the existing Web Interface application pool.
- Right click on the new Application pool and choose Advance Settings:
- The following settings need to be change based on the original Web Interface Application pool:
- Under General, Enable 32-Bit Applications to True.
- Under Process Model, Identity to NetworkService. Idle Time-out (minutes) to 0 (zero). Load User Profile to False.
- Under Recycling: Regular Time Interval (minutes) to 0 (zero). Specific Times to add entry for 2 hours.
- Assign the Web Interface or Program Neighborhood Agent site to the newly created Application Pool:
- Click on the site itself and choose Advance settings… then change the Application Pool under General.
The Web Interface or Program Neighborhood Agent site will begin to use the new application pool for all its functionality.
Read the original post here on the Citrix knowledgebase.