RE: lsass.exe question

2008-02-06 Thread Ziots, Edward
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>  ~


RE: lsass.exe question

2008-02-06 Thread Kent, Larry CTR USA IMCOM
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>  ~


RE: lsass.exe question

2008-02-05 Thread Michael B. Smith
With cached mode, that's certainly true.

 

It's a competitive feature. Even with its limited applicability it is
unlikely to be removed.

 

Regards,

 

Michael B. Smith

MCSE/Exchange MVP

http://TheEssentialExchange.com

 

From: Greg Olson [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 6:02 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

I think even in the org it's pretty much zero chance it will work. 

 

 

From: Salvador Manzo [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 2:55 PM
To: NT System Admin Issues
Subject: Re: lsass.exe question

 


The Recall This Message function really needs to go away, considering how
close to useless it is.


On 2/5/08 1:18 PM, "Michael B. Smith" <[EMAIL PROTECTED]>
wrote:


I just meant - are you aware that there is zero chance that recall will work
once it has left your internet boundary?
 

Regards,
 
Michael B. Smith
MCSE/Exchange MVP
http://TheEssentialExchange.com
 

From: Ziots, Edward [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 4:15 PM
To: NT System Admin Issues
Subject: RE: Recall: lsass.exe question

 
Nope I aint..
 
I am at least somewhat respectful of Shooks Privacy, even if TVK wasn't to
trample all over it J 
 
Z
 

Edward E. Ziots
Netwok Engineer
Lifespan Organization
MCSE,MCSA,MCP,Security+,Network+,CCA
Phone: 401-639-3505
-Original Message-
From: Michael B. Smith [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 4:12 PM
To: NT System Admin Issues
Subject: RE: Recall: lsass.exe question

 
You gotta be kidding!
 

Regards,
 
Michael B. Smith
MCSE/Exchange MVP
http://TheEssentialExchange.com
 

From: Ziots, Edward [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 4:08 PM
To: NT System Admin Issues
Subject: Recall: lsass.exe question

 
The sender would like to recall the message, "lsass.exe question". 



















 
 











 







 













---
Salvador Manzo  [ 620 W. 35th St - Los Angeles, CA 90089  e. [EMAIL PROTECTED] ]

Auxiliary Services IT, Datacenter
University of Southern California
818-612-5112
In matters of style, swim with the current; in matters of principle, stand
like a rock. Thomas Jefferson

 














 
 


 

 







 


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

RE: lsass.exe question

2008-02-05 Thread Greg Olson
I think even in the org it's pretty much zero chance it will work. 

 

 

From: Salvador Manzo [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 2:55 PM
To: NT System Admin Issues
Subject: Re: lsass.exe question

 


The Recall This Message function really needs to go away, considering
how close to useless it is.


On 2/5/08 1:18 PM, "Michael B. Smith" <[EMAIL PROTECTED]>
wrote:


I just meant - are you aware that there is zero chance that recall will
work once it has left your internet boundary?
 

Regards,
 
Michael B. Smith
MCSE/Exchange MVP
http://TheEssentialExchange.com
 

From: Ziots, Edward [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 4:15 PM
To: NT System Admin Issues
Subject: RE: Recall: lsass.exe question

 
Nope I aint..
 
I am at least somewhat respectful of Shooks Privacy, even if TVK wasn't
to trample all over it J 
 
Z
 

Edward E. Ziots
Netwok Engineer
Lifespan Organization
MCSE,MCSA,MCP,Security+,Network+,CCA
Phone: 401-639-3505
-Original Message-
From: Michael B. Smith [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 4:12 PM
To: NT System Admin Issues
Subject: RE: Recall: lsass.exe question

 
You gotta be kidding!
 

Regards,
 
Michael B. Smith
MCSE/Exchange MVP
http://TheEssentialExchange.com
 

From: Ziots, Edward [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 4:08 PM
To: NT System Admin Issues
Subject: Recall: lsass.exe question

 
The sender would like to recall the message, "lsass.exe question". 



















 
 











 







 














---
Salvador Manzo  [ 620 W. 35th St - Los Angeles, CA 90089  e.
[EMAIL PROTECTED] ] 
Auxiliary Services IT, Datacenter
University of Southern California
818-612-5112
In matters of style, swim with the current; in matters of principle,
stand like a rock. Thomas Jefferson

 





 


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

Re: lsass.exe question

2008-02-05 Thread Salvador Manzo
The Recall This Message function really needs to go away, considering how
close to useless it is.


On 2/5/08 1:18 PM, "Michael B. Smith" <[EMAIL PROTECTED]>
wrote:

>  
> I just meant ­ are you aware that there is zero chance that recall will work
> once it has left your internet boundary?
>  
> 
> Regards,
>  
> Michael B. Smith
> MCSE/Exchange MVP
> http://TheEssentialExchange.com
>  
> 
> From: Ziots, Edward [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 05, 2008 4:15 PM
> To: NT System Admin Issues
> Subject: RE: Recall: lsass.exe question
>  
>  
> Nope I aint..
>  
> I am at least somewhat respectful of Shooks Privacy, even if TVK wasn¹t to
> trample all over it J
>  
> Z
>  
> 
> Edward E. Ziots
> Netwok Engineer
> Lifespan Organization
> MCSE,MCSA,MCP,Security+,Network+,CCA
> Phone: 401-639-3505
> -Original Message-
> From: Michael B. Smith [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 05, 2008 4:12 PM
> To: NT System Admin Issues
> Subject: RE: Recall: lsass.exe question
>  
>  
> You gotta be kidding!
>  
> 
> Regards,
>  
> Michael B. Smith
> MCSE/Exchange MVP
> http://TheEssentialExchange.com
>  
> 
> From: Ziots, Edward [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 05, 2008 4:08 PM
> To: NT System Admin Issues
> Subject: Recall: lsass.exe question
>  
>  
> The sender would like to recall the message, "lsass.exe question".
> 
>  
>  
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  
>  
> 
>  
>  
> 
> 
> 
> 
> 
> 
> 
> 
>  
> 
>  
>  
> 
> 
> 
> 
>  
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ---
> Salvador Manzo  [ 620 W. 35th St - Los Angeles, CA 90089  e. [EMAIL 
> PROTECTED] ]
> Auxiliary Services IT, Datacenter
> University of Southern California
> 818-612-5112
> In matters of style, swim with the current; in matters of principle, stand
> like a rock. Thomas Jefferson


~ Upgrade to Next Generation Antispam/Antivirus with Ninja!~
~   ~

RE: OT (was RE: lsass.exe question)

2008-02-05 Thread Tim Vander Kooi
Just to be clear, no offense was intended to the estimable Mrs.
Shookiemonster (who is above all reproach). All offense was intended
solely for the Shookster himself.  :-P

 

From: David Lum [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 3:07 PM
To: NT System Admin Issues
Subject: OT (was RE: lsass.exe question)

 

 

When my wife was pregnant we joked to people that "we'll be excited when
we find out who the mother is" J

 

From: Tim Vander Kooi [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 12:54 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

He'll be happier once they figure out who the father is...

 

From: Ziots, Edward [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 2:49 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

Let me ask my  Exchange Admin here what he used to track it down. 

 

How your Wife doing. 

 

I bet you happy to be a Daddy for the 3rd time

 

How you digging VMware so far? 

 

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 3:41 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question
Importance: High

 

 

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

 

 

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]
<mailto:[EMAIL PROTECTED]>  

 

 

 










 










 
 










 










 
 










 










 
 










 










 
 
 










 










 
 










 










 
 










 










 
 










 










 
 
 
 


 

 










 










 
 










 










 
 










 










 
 










 










 
 
 
 


 

 










 










 
 










 










 
 
 


 

 










 










 
 
 


 

 










 
 


 

 





 


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

RE: lsass.exe question

2008-02-05 Thread John Cook
NO! you can't have it back!

John W. Cook
System Administrator
Partnership For Strong Families
315 SE 2nd Ave
Gainesville, Fl 32601
Office (352) 393-2741 x320
Cell (352) 215-6944
Fax (352) 393-2746
MCSE, MCTS, MCP+I,CompTIA A+, N+

From: Ziots, Edward [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 05, 2008 4:08 PM
To: NT System Admin Issues
Subject: Recall: lsass.exe question
Importance: High




The sender would like to recall the message, "lsass.exe question".













~ Upgrade to Next Generation Antispam/Antivirus with Ninja!~
~   ~

RE: lsass.exe question

2008-02-05 Thread Tim Vander Kooi
Is that the same line you crossed with my Momma years ago??? :-P

 

From: Andy Shook [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 3:00 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

 

 

There's the line, you crossed it.

 

Andy



From: Tim Vander Kooi [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 3:54 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

He'll be happier once they figure out who the father is...

 

From: Ziots, Edward [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 2:49 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

Let me ask my  Exchange Admin here what he used to track it down. 

 

How your Wife doing. 

 

I bet you happy to be a Daddy for the 3rd time

 

How you digging VMware so far? 

 

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 3:41 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question
Importance: High

 

 

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

 

 

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]
<mailto:[EMAIL PROTECTED]>  

 

 

 










 










 
 










 










 
 










 










 
 










 










 
 
 










 










 
 










 










 
 










 










 
 










 










 
 
 
 


 

 










 










 
 










 










 
 










 










 
 










 










 
 
 
 


 

 










 










 
 










 










 
 
 


 

 










 










 
 
 


 

 










 
 


 

 





 


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

OT (was RE: lsass.exe question)

2008-02-05 Thread David Lum
When my wife was pregnant we joked to people that "we'll be excited when
we find out who the mother is" J

 

From: Tim Vander Kooi [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 12:54 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

He'll be happier once they figure out who the father is...

 

From: Ziots, Edward [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 2:49 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

Let me ask my  Exchange Admin here what he used to track it down. 

 

How your Wife doing. 

 

I bet you happy to be a Daddy for the 3rd time

 

How you digging VMware so far? 

 

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 3:41 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question
Importance: High

 

 

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

 

 

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]
<mailto:[EMAIL PROTECTED]>  

 

 

 










 










 










 










 
 










 










 










 










 
 
 


 

 










 










 










 










 
 
 


 

 










 










 
 


 

 










 
 


 

 





 


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

RE: lsass.exe question

2008-02-05 Thread Fogarty, Richard R Mr CTR USA USASOC
Congrats.

 

From: Andy Shook [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 3:52 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

Dang, Z.  Thanks for bringing the whole freakin' list into my personal life.
Sheesh.

 

Oh well, 

Wife is doing as good as to be expected for being 8.5 months preggers

 

Shookie #3 (a girl-Ava Riley) is being induced on 2/13 due to size.  My son
was 10lbs even at one week early and she is measuring bigger than that.

 

VMWare is still awesome, really enjoying it.  

 

Shook

http://www.linkedin.com/in/andyshook  

  _  

From: Ziots, Edward [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 3:49 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

Let me ask my  Exchange Admin here what he used to track it down. 

 

How your Wife doing. 

 

I bet you happy to be a Daddy for the 3rd time..

 

How you digging VMware so far? 

 

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 3:41 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question
Importance: High

 

 

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

 

 

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-  <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]


 

 

 














 














 














 














 
 














 














 














 














 
 
 


 

 














 














 














 














 
 
 


 

 














 














 
 


 

 














 
 


 

 







 


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

RE: lsass.exe question

2008-02-05 Thread Andy Shook
 

 

There's the line, you crossed it.

 

Andy



From: Tim Vander Kooi [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 3:54 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

He'll be happier once they figure out who the father is...

 

From: Ziots, Edward [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 2:49 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

Let me ask my  Exchange Admin here what he used to track it down. 

 

How your Wife doing. 

 

I bet you happy to be a Daddy for the 3rd time

 

How you digging VMware so far? 

 

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 3:41 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question
Importance: High

 

 

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

 

 

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]
<mailto:[EMAIL PROTECTED]>  

 

 

 










 










 










 










 
 










 










 










 










 
 
 


 

 










 










 










 










 
 
 


 

 










 










 
 


 

 










 
 


 

 





 


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

Re: lsass.exe question

2008-02-05 Thread Salvador Manzo
Also interested.  Haven¹t been able to  hammer down if my performance issues
are Windows Mobile related, Entourage related or an indexing service.


On 2/5/08 12: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
>  
>  
> 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 sharesS.
>  
> 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] <mailto:[EMAIL PROTECTED]>
>  
>  
>  
> 
> 
> 
> 
> 
> 
> 
> 
>  
> 
>  
>  
> 
> 
> 
> 
>  
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ---
> Salvador Manzo  [ 620 W. 35th St - Los Angeles, CA 90089  e. [EMAIL 
> PROTECTED] ]
> Auxiliary Services IT, Datacenter
> University of Southern California
> 818-612-5112


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

RE: lsass.exe question

2008-02-05 Thread Tim Vander Kooi
He'll be happier once they figure out who the father is...

 

From: Ziots, Edward [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 2:49 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

Let me ask my  Exchange Admin here what he used to track it down. 

 

How your Wife doing. 

 

I bet you happy to be a Daddy for the 3rd time

 

How you digging VMware so far? 

 

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 3:41 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question
Importance: High

 

 

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

 

 

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]
<mailto:[EMAIL PROTECTED]>  

 

 

 




















 




















 
 


 

 




















 
 


 

 










 


 

 





 


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

RE: lsass.exe question

2008-02-05 Thread Andy Shook
Dang, Z.  Thanks for bringing the whole freakin' list into my personal
life.  Sheesh.

 

Oh well, 

Wife is doing as good as to be expected for being 8.5 months preggers

 

Shookie #3 (a girl-Ava Riley) is being induced on 2/13 due to size.  My
son was 10lbs even at one week early and she is measuring bigger than
that.

 

VMWare is still awesome, really enjoying it.  

 

Shook

http://www.linkedin.com/in/andyshook  



From: Ziots, Edward [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 3:49 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

Let me ask my  Exchange Admin here what he used to track it down. 

 

How your Wife doing. 

 

I bet you happy to be a Daddy for the 3rd time

 

How you digging VMware so far? 

 

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 3:41 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question
Importance: High

 

 

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

 

 

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]
<mailto:[EMAIL PROTECTED]>  

 

 

 




















 




















 
 


 

 




















 
 


 

 










 


 

 





 


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

Re: lsass.exe question

2008-02-05 Thread Micheal Espinola Jr
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-4B7C-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>  ~


RE: lsass.exe question

2008-02-05 Thread Ziots, Edward
Let me ask my  Exchange Admin here what he used to track it down. 

 

How your Wife doing. 

 

I bet you happy to be a Daddy for the 3rd time

 

How you digging VMware so far? 

 

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 3:41 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question
Importance: High

 

 

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

 

 

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]
<mailto:[EMAIL PROTECTED]>  

 

 

 










 










 
 


 

 










 
 


 

 





 


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

RE: lsass.exe question

2008-02-05 Thread Andy Shook
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

 

 

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]
<mailto:[EMAIL PROTECTED]>  

 

 

 










 


 

 





 


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

RE: lsass.exe question

2008-02-05 Thread Ziots, Edward
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]
  

 

 

 





 


~ Upgrade to Next Generation Antispam/Antivirus with Ninja!~
~   ~

RE: lsass.exe question

2008-02-05 Thread Bob Fronk
I guess you know that lsass.exe will give some problems when Exchange is
installed on a DC, especially at shutdown.  (long delay at shutdown is
the most noticed)

 

My guess would be another application causing it, maybe google indexing
as you suspect.

 

From: Andy Shook [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 3:03 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

No.

 

Andy



From: Bob Fronk [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 2:58 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

Symantec on it?

 

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]
<mailto:[EMAIL PROTECTED]>  

 

 

 










 










 
 
 


This email and any attached files are confidential and intended solely
for the intended recipient(s). If you are not the named recipient you
should not read, distribute, copy or alter this email. Any views or
opinions expressed in this email are those of the author and do not
represent those of the Davis H. Elliot Company . Warning: Although
precautions have been taken to make sure no viruses are present in this
email, the company cannot accept responsibility for any loss or damage
that arise from the use of this email or attachments.

 

 










 
 


 

 





 




This email and any attached files are confidential and intended solely for the 
intended recipient(s). If you are not the named recipient you should not read, 
distribute, copy or alter this email. Any views or opinions expressed in this 
email are those of the author and do not represent those of the Davis H. Elliot 
Company company. Warning: Although precautions have been taken to make sure no 
viruses are present in this email, the company cannot accept responsibility for 
any loss or damage that arise from the use of this email or attachments.
~ Upgrade to Next Generation Antispam/Antivirus with Ninja!~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

RE: lsass.exe question

2008-02-05 Thread Andy Shook
No.

 

Andy



From: Bob Fronk [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 05, 2008 2:58 PM
To: NT System Admin Issues
Subject: RE: lsass.exe question

 

 

Symantec on it?

 

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]
<mailto:[EMAIL PROTECTED]>  

 

 

 










 
 


This email and any attached files are confidential and intended solely
for the intended recipient(s). If you are not the named recipient you
should not read, distribute, copy or alter this email. Any views or
opinions expressed in this email are those of the author and do not
represent those of the Davis H. Elliot Company . Warning: Although
precautions have been taken to make sure no viruses are present in this
email, the company cannot accept responsibility for any loss or damage
that arise from the use of this email or attachments.

 

 





 


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

RE: lsass.exe question

2008-02-05 Thread Bob Fronk
Symantec on it?

 

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]
  

 

 

 





 




This email and any attached files are confidential and intended solely for the 
intended recipient(s). If you are not the named recipient you should not read, 
distribute, copy or alter this email. Any views or opinions expressed in this 
email are those of the author and do not represent those of the Davis H. Elliot 
Company company. Warning: Although precautions have been taken to make sure no 
viruses are present in this email, the company cannot accept responsibility for 
any loss or damage that arise from the use of this email or attachments.
~ Upgrade to Next Generation Antispam/Antivirus with Ninja!~
~   ~