Become a Columnist |  Microsoft Exchange Site | Microsoft Support Site | MSDN Exchange Site

Subscribe to OutlookExchange What's New Columnist Anderson Patricio Ann Mc Donough Bob Spurzem Brian Veal Catherine Creary Cherry Beado Colin Janssen Collins Timothy Mutesaria Drew Nicholson Fred Volking Glen Scales Goran Husman Guy Thomas Henrik Walther Jason Sherry Jayme Bowers John Young Joyce Tang Justin Braun Konstantin Zheludev Kristina Waters Kuang Zhang Mahmoud Magdy Martin Tuip Michael Dong Michele Deo Mitch Tulloch Nicolas Blank Pavel Nagaev Ragnar Harper Ricardo Silva Richard Wakeman Russ Iuliano Santhosh Hanumanthappa Steve Bryant Steve Craig Todd Walker Tracey J. Rosenblath Development Microsoft Scripting Center Code Example Page Outlook Object Model Constants More Resources White Papers Microsoft Sites Documentation Help Files Sample Apps Tools & Addons Books Other Sites FAQ's Programming With Outlook Slipstick Systems Other Sites of Interest Software Exchange Server Downloads Other Links Exchange Training Exchange/Outlook FAQs

Scripting Solutions Reader comments compiled by Mitch Tulloch Hi Mitch, Ever a firm believer in simplicity, I use 3 scripts. The main script calls a Stop Exchange script (NET STOP commands), copies the files onto another server, and then calls a Start Exchange script (NET START commands). This is scheduled to go off at 4AM – I used WINAT from the resource kit cos its friendly J - with the output redirected to a simple text file. Next, WINAT is scheduled to email the log file to me using BLAT (a command line mailer). Short, sweet and best of all cheap. Oops! I meant to say cost-effective J Steve Pullinger – Intel Certified Integration Specialist Director, Sentinet Computing Ltd Email: steve.pullinger@sentinetcomputing.com Web: http://www.sentinetcomputing.com Send me feedback on this article. Back to Mitch Tulloch's column on OutlookExchange Disclaimer: I hope that the information in these pages is valuable to you. Your use of the information contained in these pages, however, is at your sole risk. All information on these pages is provided "as -is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by me. I shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

Disclaimer: Your use of the information contained in these pages is at your sole risk. All information on these pages is provided "as is", without any warranty, whether express or implied, of its accuracy, completeness, fitness for a particular purpose, title or non-infringement, and none of the third-party products or information mentioned in the work are authored, recommended, supported or guaranteed by Stephen Bryant or Pro Exchange. OutlookExchange.Com, Stephen Bryant and Pro Exchange shall not be liable for any damages you may sustain by using this information, whether direct, indirect, special, incidental or consequential, even if it has been advised of the possibility of such damages.

Copyright Stephen Bryant 2008