Exchange 2010 SP1 CAS Server running at 100% CPU - Autodiscover Issue
We're currently running Exchange 2010 SP1 on Windows 2008 R2. We have 2 servers with a mailbox role and 2 servers with a combined CAS and Hub Transport role. One of our CAS servers is constantly running at 100% cpu on the w3wp.exe and lsass.exe services. If you dig deeper into the process through Process Explorer, it looks like it's the MSExchangeAutodiscoverAppPool that's causing the processing issue and IIS logs confirm that every one of our Outlook 2007 clients continue to poll for AutoDiscover settings--almost every second. For example: 2010-09-23 15:25:24 10.12.224.165 POST /Autodiscover/Autodiscover.xml - 443 - 10.12.225.111 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6535;+Pro) 401 1 2148074254 280 2010-09-23 15:25:24 10.12.224.165 POST /Autodiscover/Autodiscover.xml - 443 - 10.12.225.150 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6535;+Pro) 401 1 2148074254 265 Autodiscover works setting up the Outlook client for the first time, testexchangeconnectivity.com shows autodiscover is working correctly from the outside and an outlook client on the internal side running a "Test E-mail AutoConfiguration" looks to be correct as well. What might be causing Outlook to poll autodiscover so much? All of the internal url settings on all of the CAS and AutoDiscover setup seem ok to me but maybe I missed something? Or is this an Outlook issue?
September 23rd, 2010 1:25pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics