Modifying the Managed Pipeline Mode in IIS 7.0
Topic Last Modified: 2009-02-27
If you are running Communicator Web Access (2007 R2 release) under Internet Information Services (IIS) 7.0, your users might experience lengthy logon times and you might discover that your servers are unable to handle more than a few hundred simultaneous connections. (Communicator Web Access should be able to accommodate around 6,500 simultaneous users.) This is due to the way that IIS 7.0 allocates memory for IIS applications. To avoid this issue, you should create your Communicator Web Access virtual servers, and then, for each virtual server on each computer running Communicator Web Access, change the IIS Managed Pipeline Mode. Use the following procedure to change the pipeline mode.
To configure Managed Pipeline Mode in IIS 7.0
Log on to a computer running Communicator Web Access as a member of the local Administrators group.
Note
You need to perform this task on each computer that hosts a Communicator Web Access virtual server.
Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
In the IIS Manager, expand the name of your IIS server, and then click Application Pools.
Under Application Pools, locate the name of one of the applications created for you when you created your Communicator Web Access virtual server (for example, W3SVC175074822 - Communicator Web Access), right-click the application, and then click Advanced Settings.
In the Advanced Settings dialog box, click the Managed Pipeline Mode list, select Classic, and then click OK.
Repeat steps 4 and 5 for any other Communicator Web Access applications running on the computer, and then close IIS Manager.
Click Start, and then click Run.
In the Run dialog box, type cmd, and then click OK.
In the command window, type iisreset to stop IIS and then restart IIS.
Close the command window.