RE: E2K Store

  • From: "Mulnick, Al" <Al.Mulnick@xxxxxxxxxx>
  • To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
  • Date: Wed, 6 Apr 2005 09:05:02 -0400

That would be mostly normal and expected behavior.  Exchange will take as
many resources as it can get during run time.  It will then give back those
resources when asked by other applications (mostly.) 

Al 

-----Original Message-----
From: Simon Bound [mailto:simon.bound@xxxxxxxxxxxxxxxxxxxx] 
Sent: Wednesday, April 06, 2005 9:05 AM
To: [ExchangeList]
Subject: [exchangelist] E2K Store

http://www.MSExchange.org/

I have a client with a W2K fully patched SBS server. The server has 1.5gb
RAM. The number of Exchange users is around 10. When Exchange store.exe
loads initially resources in task manager are of 10,000k range, however this
rises over a number of days to around 850,000k and stays at that level. I am
wondering if this is "normal" given that W2K SBS does not use the /3gb
switch in boot.ini. AV checking is correctly excluding drive M:
and specific Exchange folders.

Any observations or additional things to check ?

thanks
Simon

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com Leading
Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security
Resource Site: http://www.windowsecurity.com/ Network Security Library:
http://www.secinf.net/ Windows 2000/NT Fax Solutions:
http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this MSEXchange.org Discussion List as:
al.mulnick@xxxxxxxxxx To unsubscribe visit
http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Report abuse to listadmin@xxxxxxxxxxxxxx


Other related posts: