There is no question here, but I imagine a couple of questions:
is this normal ? if not, how to fix it ?
Also, there is not enough information to provide an accurate answer.
If this is related to an Exchange server running on a Windows 2003 server cluster, then this could help:
<a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;843546">Increased CPU usage and poor performance may occur when Outlook Web Access uses an SSL connection to a Exchange Server 2003 computer in a cluster that is running Windows Server 2003</a>
---------------------
Last Wiki Answer Submitted: May 5, 2010 3:05 pm by carlosdl63,535 pts.
If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
Thanks Carlosdl for Your reply and you have guessed the exact question. I have tried this answer and but already i have SP2 so i am not able to install this hotfix. i am guessing Microsoft has added this into Sp2.
It is normal that lsass.exe uses more CPU when SSL is enabled, as all SSL processing is done by this service. If the amount of CPU time being used by this process is not causing problems, I would not worry.
Just make sure it is related to SSL, as some malware could be causing this as well.
I don’t have more suggestions, but there are at least a couple of Exchange experts here in the community, and I hope they take a look at this question.
Thanks Carlosdl for Your reply and you have guessed the exact question. I have tried this answer and but already i have SP2 so i am not able to install this hotfix. i am guessing Microsoft has added this into Sp2.
Do you have any other suggestion.
Yes that fix is included in SP2.
It is normal that lsass.exe uses more CPU when SSL is enabled, as all SSL processing is done by this service. If the amount of CPU time being used by this process is not causing problems, I would not worry.
Just make sure it is related to SSL, as some malware could be causing this as well.
I don’t have more suggestions, but there are at least a couple of Exchange experts here in the community, and I hope they take a look at this question.