I like Sysinternals contig.exe to do my 'on the spot' defragmentation. It is just simply a defragmenter so other applications, like Defraggler, would surely find some space to add value.
The note about Outlook being closed is still valid concerning contig: Outlook locks OSTs and PSTs when it opens them. -----Original Message----- From: Sam Cayze [mailto:sam.ca...@rollouts.com] Sent: Wednesday, October 21, 2009 10:55 PM To: NT System Admin Issues Subject: RE: Outlook 2007, constant hard disk thrashing. I've been testing Defraggler file-level defrag for OST's (Mine range from 2GB to 15GB for our users). We have NO issues with Outlook speed, but I figured it might help and be good measure. It's hard to really gauge the benefit... df.exe C:\Users\Sam\AppData\Local\Microsoft\Outlook\outlook.ost /large Will defrag just that file, and move it to the end of the drive. Obviously it would have to run when outlook isn't open. (Startup script). http://docs.piriform.com/defraggler Sam -----Original Message----- From: Ben Scott [mailto:mailvor...@gmail.com] Sent: Wednesday, October 21, 2009 8:30 PM To: NT System Admin Issues Subject: Re: Outlook 2007, constant hard disk thrashing. On Wed, Oct 21, 2009 at 5:43 PM, Matthew W. Ross <mr...@ephrataschools.org> wrote: > These PST/OST files, they are located on the Client, or on the Server? Joe Tinney answered this pretty well, I'll just add that starting with Outlook 2003, by default, the OST (Offline Store) is used to keep a cached copy of the server mailbox even when nominally online. Outlook uses that cache for most operations, and only sync's it to the server every few minutes or so. > But each client with a spare partition for a Mail > client's database file... that sounds ridiculous. It is severely annoying, to be sure. We only do it for those with the giant mondo mailboxes, basically anything over 2 GB in size. What we really need is an archiving solution, but haven't been able to get money for one yet. Exchange 2010 is supposed to have a basic solution in that area, and I'm hoping that will be good for us. Again, we're talking a single file, several GB in size, that gets highly fragmented. I don't really put too much blame on Outlook here. While I suspect Outlook could probably be more efficient, there's only so much you can do under those conditions. Clients that never leave the LAN have cached mode disabled. They always talk to the server then. Exchange performs very well, even with a 70 GB plus server database in a single file that's probably more fragmented than I want to think about. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
