Comments on: Automating Outlook’s Inbox Repair Tool (ScanPST) http://opindian.com/blog/2008/09/02/automating-outlooks-inbox-repair-tool-scanpst/ One Indian's Opinion Sat, 17 Jul 2010 16:59:07 -0400 hourly 1 http://wordpress.org/?v=3.0.1-beta By: Mark http://opindian.com/blog/2008/09/02/automating-outlooks-inbox-repair-tool-scanpst/comment-page-1/#comment-199 Mark Sun, 11 Jul 2010 19:46:31 +0000 http://opindian.com/blog/?p=236#comment-199 I like your second solution (text file with names of PST); this is something I would probably run once or twice a year as I DO perform the occasional search in those files for some email or attachment (and thus a risk for corruption).<br><br>Thank you for your insight and clever solutions!<br><br>Mark I like your second solution (text file with names of PST); this is something I would probably run once or twice a year as I DO perform the occasional search in those files for some email or attachment (and thus a risk for corruption).

Thank you for your insight and clever solutions!

Mark

]]> By: Mark http://opindian.com/blog/2008/09/02/automating-outlooks-inbox-repair-tool-scanpst/comment-page-1/#comment-213 Mark Sun, 11 Jul 2010 18:46:00 +0000 http://opindian.com/blog/?p=236#comment-213 I like your second solution (text file with names of PST); this is something I would probably run once or twice a year as I DO perform the occasional search in those files for some email or attachment (and thus a risk for corruption). Thank you for your insight and clever solutions! Mark I like your second solution (text file with names of PST); this is something I would probably run once or twice a year as I DO perform the occasional search in those files for some email or attachment (and thus a risk for corruption).

Thank you for your insight and clever solutions!

Mark

]]> By: ahpatel http://opindian.com/blog/2008/09/02/automating-outlooks-inbox-repair-tool-scanpst/comment-page-1/#comment-198 ahpatel Sun, 11 Jul 2010 17:38:16 +0000 http://opindian.com/blog/?p=236#comment-198 You can have multiple locations on the same cmdscan line... So your cmdscan statement can look like:<br>cmdscan D:DOCSOUTLOOKSCANPST.exe D:DOCSOUTLOOKcovetMay.pst C:Location2Outlook*.pst D:Location3*.pst > D:DOCSOUTLOOKautopst.tmp<br><br>The only issue with that is that if any one of your 37 files have errors, the script would rescan ALL of them!<br><br>Alternatively, you could create a file that lists all 37 PSTs and then use each line as an input into a for loop that runs 37 times. And, if any instance of the loop sends the "Error Found" message, rerun that same line before moving to the next PST.<br><br>But, honestly, it you don't regularly use/open all 37 PSTs, it seems unnecessary to make them part of your regular scans. I have a dozen old PSTs backed up as well, but I hardly ever scan them because I don't keep them open in Outlook and seldom reference them. You can have multiple locations on the same cmdscan line… So your cmdscan statement can look like:
cmdscan D:DOCSOUTLOOKSCANPST.exe D:DOCSOUTLOOKcovetMay.pst C:Location2Outlook*.pst D:Location3*.pst > D:DOCSOUTLOOKautopst.tmp

The only issue with that is that if any one of your 37 files have errors, the script would rescan ALL of them!

Alternatively, you could create a file that lists all 37 PSTs and then use each line as an input into a for loop that runs 37 times. And, if any instance of the loop sends the “Error Found” message, rerun that same line before moving to the next PST.

But, honestly, it you don't regularly use/open all 37 PSTs, it seems unnecessary to make them part of your regular scans. I have a dozen old PSTs backed up as well, but I hardly ever scan them because I don't keep them open in Outlook and seldom reference them.

]]> By: Mark http://opindian.com/blog/2008/09/02/automating-outlooks-inbox-repair-tool-scanpst/comment-page-1/#comment-197 Mark Sun, 11 Jul 2010 17:05:41 +0000 http://opindian.com/blog/?p=236#comment-197 I have 37 PST files going back to early days of Outlook. As someone else has pointed out, if PST isn't in default location, wildcard (*.PST) doesn't work in batchfile. So my options are move PST back to default folder (ugh!) or do 37 different errorlevel loops.... unless you provide more inspiration! <G><br>Thanks for your help and guidance.<br>Mark I have 37 PST files going back to early days of Outlook. As someone else has pointed out, if PST isn't in default location, wildcard (*.PST) doesn't work in batchfile. So my options are move PST back to default folder (ugh!) or do 37 different errorlevel loops…. unless you provide more inspiration! <G>
Thanks for your help and guidance.
Mark

]]> By: ahpatel http://opindian.com/blog/2008/09/02/automating-outlooks-inbox-repair-tool-scanpst/comment-page-1/#comment-214 ahpatel Sun, 11 Jul 2010 16:38:00 +0000 http://opindian.com/blog/?p=236#comment-214 You can have multiple locations on the same cmdscan line... So your cmdscan statement can look like:<br>cmdscan D:DOCSOUTLOOKSCANPST.exe D:DOCSOUTLOOKcovetMay.pst C:Location2Outlook*.pst D:Location3*.pst > D:DOCSOUTLOOKautopst.tmp<br><br>The only issue with that is that if any one of your 37 files have errors, the script would rescan ALL of them!<br><br>Alternatively, you could create a file that lists all 37 PSTs and then use each line as an input into a for loop that runs 37 times. And, if any instance of the loop sends the "Error Found" message, rerun that same line before moving to the next PST.<br><br>But, honestly, it you don't regularly use/open all 37 PSTs, it seems unnecessary to make them part of your regular scans. I have a dozen old PSTs backed up as well, but I hardly ever scan them because I don't keep them open in Outlook and seldom reference them. You can have multiple locations on the same cmdscan line… So your cmdscan statement can look like:
cmdscan D:DOCSOUTLOOKSCANPST.exe D:DOCSOUTLOOKcovetMay.pst C:Location2Outlook*.pst D:Location3*.pst > D:DOCSOUTLOOKautopst.tmp

The only issue with that is that if any one of your 37 files have errors, the script would rescan ALL of them!

Alternatively, you could create a file that lists all 37 PSTs and then use each line as an input into a for loop that runs 37 times. And, if any instance of the loop sends the “Error Found” message, rerun that same line before moving to the next PST.

But, honestly, it you don’t regularly use/open all 37 PSTs, it seems unnecessary to make them part of your regular scans. I have a dozen old PSTs backed up as well, but I hardly ever scan them because I don’t keep them open in Outlook and seldom reference them.

]]> By: ahpatel http://opindian.com/blog/2008/09/02/automating-outlooks-inbox-repair-tool-scanpst/comment-page-1/#comment-196 ahpatel Sun, 11 Jul 2010 16:14:09 +0000 http://opindian.com/blog/?p=236#comment-196 Thanks for the update Mark. I will edit my script and remove the ().<br><br>Let me know if you think of any additional optimizations/enhancements! Thanks for the update Mark. I will edit my script and remove the ().

Let me know if you think of any additional optimizations/enhancements!

]]> By: Mark http://opindian.com/blog/2008/09/02/automating-outlooks-inbox-repair-tool-scanpst/comment-page-1/#comment-215 Mark Sun, 11 Jul 2010 16:05:00 +0000 http://opindian.com/blog/?p=236#comment-215 I have 37 PST files going back to early days of Outlook. As someone else has pointed out, if PST isn't in default location, wildcard (*.PST) doesn't work in batchfile. So my options are move PST back to default folder (ugh!) or do 37 different errorlevel loops.... unless you provide more inspiration! <G> Thanks for your help and guidance. Mark I have 37 PST files going back to early days of Outlook. As someone else has pointed out, if PST isn’t in default location, wildcard (*.PST) doesn’t work in batchfile. So my options are move PST back to default folder (ugh!) or do 37 different errorlevel loops…. unless you provide more inspiration!
Thanks for your help and guidance.
Mark

]]> By: Mark http://opindian.com/blog/2008/09/02/automating-outlooks-inbox-repair-tool-scanpst/comment-page-1/#comment-195 Mark Sun, 11 Jul 2010 16:02:20 +0000 http://opindian.com/blog/?p=236#comment-195 FIXED:<br>IF %errorlevel% == 0 GOTO RESCAN FIXED:
IF %errorlevel% == 0 GOTO RESCAN

]]> By: ahpatel http://opindian.com/blog/2008/09/02/automating-outlooks-inbox-repair-tool-scanpst/comment-page-1/#comment-216 ahpatel Sun, 11 Jul 2010 15:14:00 +0000 http://opindian.com/blog/?p=236#comment-216 Thanks for the update Mark. I will edit my script and remove the (). Let me know if you think of any additional optimizations/enhancements! Thanks for the update Mark. I will edit my script and remove the ().

Let me know if you think of any additional optimizations/enhancements!

]]> By: Mark http://opindian.com/blog/2008/09/02/automating-outlooks-inbox-repair-tool-scanpst/comment-page-1/#comment-217 Mark Sun, 11 Jul 2010 15:02:00 +0000 http://opindian.com/blog/?p=236#comment-217 FIXED: IF %errorlevel% == 0 GOTO RESCAN FIXED:
IF %errorlevel% == 0 GOTO RESCAN

]]>