Speak of the devil, this was just posted yesterday: http://gsexdev.blogspot.com/2004/10/listing-file-sizes-of-all-exchange.h tml -----Original Message----- From: Harding, Devon [mailto:dharding@xxxxxxxxxxxxxxxx] Sent: Tuesday, October 12, 2004 1:31 PM To: [ExchangeList] Subject: [exchangelist] Information Store size? http://www.MSExchange.org/ Is there any way to find the size of a remote Exchange server's Information Store (.edb)? Any scripts out there that can do this? Devon Harding Windows Systems Engineer Southern Wine & Spirits - GSD 954-602-2469 ----------------------------------------- __________________________________ This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use or distribution of the information included in the message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank You. ------------------------------------------------------ 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: michael@xxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx
