In our Excahnge 2003 environment, we are attempting to balance the load of our OWA connections between 2 virtual servers, Mail1 and Mail2.We use Quest Spotlight on Messaging (SLOM)for monitoring our 2 node Exchange cluster.Both servers have IIS configured to host OWA sessions.SLOM gives an alarm everyday as our OWA connnections grow in number to more than 45 or so on one of the Virtual servers (Mail2).I am not sure whether the alarm is something to be concerned about but since we have performance issues I am addressing this.Is there a standard number of OWA sessions that an Virtual Exchange Exchange server can handle from a best practices point of view?The other Virtual server (Mail1) only hosts about a maximum of 17 OWA sessions andthe numbernever getshigher than that.My thinking is that the users with stores on Mail2 are the gaining OWA more frequently and this is assocaited with this large number OWA connections on Mail2.Thus to balance it, I need to move some of the stores of users using OWA to Mail1 and then I can balance the load of the OWA connections.

Hi,Did you configure NLB?MCSE,CCNA,VCP,APP

Hi,Base on my experience, we only can set timeout value on OWA session.For the number of OWA connection, I think if may base on the IIS server performance, especially the hardware.For the alarm, there should be a rule set in SLOM to be triggered when the connection is more than 45. Please try to connect SLOM support to get more information on it.Besides, I recommend you to configure NLB for CAS role to archive the high availability. More information to share with you: How to harden the TCP/IP stack against denial of service attacks in Windows http://support.microsoft.com/default.aspx/kb/324270 Event ID 9646 is logged in the application event log of your Exchange Server http://support.microsoft.com/kb/842022 Regards, Xiu