What is wrong with a 1.9GB mailbox? Why are you rehashing old threads? Do you have a name, or shall we assign you one?
William -----Original Message----- From: dp To: MS-Exchange Admin Issues Sent: 11/3/01 9:21 PM Subject: RE: Eseutil Hot fixes, make sure no one is running a 1.9 gig Mailbox -----Original Message----- From: Scott Schnoll [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 12:05 To: MS-Exchange Admin Issues Subject: Re: Eseutil MessageIMHO, this statement is wrong: "The best maintance [sic] for Exchange is apply service packs. other then that nothing needs to be done." There is a lot more to maintaining Exchange than applying service packs. You should also regularly review your event logs (daily, if not more frequently). There are some good tools out there that can automate this for you. You should also regularly collect and monitor performance data. You also need to watch mail queues for build-up, verify that your Exchange-aware antivirus software is working and keeping up-to-date, monitor disk space, and perform a whole other slew of tasks that combine to form your Exchange maintenance practices. Don't think for a minute that applying service packs is all you need to do to keep your servers up longer. There are lots of other factors that affect uptime and availability and they should not be overlooked. My $.02. -Scott ----- Original Message ----- From: Kevin Miller To: MS-Exchange Admin Issues Sent: Wednesday, October 31, 2001 8:24 AM Subject: RE: Eseutil Most the people here who use it on a monthly basis would have a very difficult time explaining what the log files are, what they are used for, and why they are there. don't go by them. Listen to people who know what they are talking about. DON'T TOUCH eseutil unless you are on the phone with PSS or know what you are doing and have a very good backup. The best maintance for Exchange is apply service packs. other then that nothing needs to be done. The longer a server is up the better. Kevinm M WLKMMAS, UCC+WCA, CKWSE -----Original Message----- From: Dimitri Limanovski [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 8:13 AM To: MS-Exchange Admin Issues Subject: RE: Eseutil So what is the best practice with defragmentation? MS says that "ESEUITL is not considered a tool for regular maintenance and should only be used in case of emergency after contacting Microsoft Technical Support". On the other hand, there're people here that use it on monthly basis! So, to use or not to use? -----Original Message----- From: Kopec, David [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 10:41 AM To: MS-Exchange Admin Issues Subject: RE: Eseutil This statement is NOT entirely accurate. Try the following syntax and you can direct wherever you want including mapped drives. For example, C:\exchsrver/bin>eseutil /d /ispriv /tf:\tempedb.edb. Notice, there is no space between the /t and the drive you wish to defrag on. -----Original Message----- From: Abercrombie, Sherry [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 9:23 AM To: MS-Exchange Admin Issues Subject: RE: Eseutil I'm not familiar with E2K, but on 5.5 I regularly (read monthly) run eseutil. I run it because that is the ONLY way to regain space in the Exchange DB that has been freed up by messages being deleted etc. If I did not do this on a regular basis I would hit the Exchange 5.5 IS limit. I would guess that it would be /t f:/tempedb.edb or what ever you plan to use for the defrag. It may not work, it doesn't work in 5.5 when you try to redirect the temp database, it must run on the same physical drive that it is stored. Good luck. Sherry -----Original Message----- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 31, 2001 7:34 AM To: MS-Exchange Admin Issues Subject: RE: Eseutil List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
