OHH I like the B-Slap comment, layin down the LAW> 

Z

Edward E. Ziots
Netwok Engineer
Lifespan Organization
MCSE,MCSA,MCP,Security+,Network+,CCA
Phone: 401-639-3505

-----Original Message-----
From: Kent, Larry CTR USA IMCOM [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 06, 2008 12:20 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

Also if you have SMS you can determine who has Google Desktop installed
and use Group Policy to stop it from running.  Then B1tchslap the
culprit... 

-----Original Message-----
From: Micheal Espinola Jr [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 3:50 PM
To: NT System Admin Issues
Subject: Re: lsass.exe question

You should be able to nail this down with the Exchange Server User
Monitor tool:

http://www.microsoft.com/Downloads/details.aspx?familyid=9A49C22E-E0C7-4
B7C-ACEF-729D48AF7BC9&displaylang=en

More info:

http://msexchangeteam.com/archive/2005/04/06/403409.aspx


On Feb 5, 2008 3:41 PM, Andy Shook <[EMAIL PROTECTED]>
wrote:
>
>
>
> Any advice on how I can find out the user (I have an idea but it's a 
> C-level and I'll need documentation)?
>
>
>
>
> Andy
> ________________________________
>
>
> From: Ziots, Edward [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 05, 2008 3:38 PM
>
> To: NT System Admin Issues
> Subject: RE: lsass.exe question
>
> To: NT System Admin Issues
> Subject: RE: lsass.exe question
>
>
>
>
>
>
>
>
> Google Desktop has caused spikes in Exchange 2003 here also, with the 
> indexing operations and its constant communications with the Exchange 
> server, so that very well might be your issue.  We just flat out ban 
> Goog Earth/Desktop and all that now, due to the issues.
>
>
>
> Z
>
>
>
>
> Edward E. Ziots
>
> Netwok Engineer
>
> Lifespan Organization
>
> MCSE,MCSA,MCP,Security+,Network+,CCA
>
> Phone: 401-639-3505
>
> -----Original Message-----
> From: Andy Shook [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 05, 2008 1:44 PM
> To: NT System Admin Issues
> Subject: lsass.exe question
>
>
>
>
>
> Above mentioned process ran away and buried my Exchange server a few 
> minutes ago.  Still reviewing event logs but I'm wondering if someone 
> install google desktop search and it started to index his mail file 
> would that cause the lsass.exe spike?  Server is 2003 std. with 
> Exchange 2003 std SP2 + all patches and is a DC\GC DNS and a few
shares....
>
>
>
> Andy Shook, IT Manager
>
> Decision Support LLC
>
> 624 Matthews-Mint Hill Road
>
> Matthews, NC 28105
>
> p-704.844.1828
>
> f-704.847.4875
>
> e- [EMAIL PROTECTED]
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>



--
ME2

~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

Reply via email to