Re: Unattended ISINTEG
- From: PL <plecki2@xxxxxxxxxxx>
- Date: Fri, 05 May 2006 10:13:47 -0700
Hi all, thanks for your responses.
The reason why I'm trying to run ISINTEG unattended is because the
store has to be dismounted in order to do so and I can only do this in
off-hours, when I'd rather be sleeping. It is recommended to run
ISINTEG at least once a month whether you're experiencing specific
problems with the store or not. You could be just compounding simple
problems if not fixed right away and pretty soon you've got a bigger
problem than it should have been. Furthermore, I don't believe that
ISINTEG is a dangerous (potentially destructive) tool, such as the
ESEUTIL, which I always run on raw db files copied to another machine.
I also realize that ISINTEG has to be often ran several times to fix
all issues, but I can pipe the results to a log file that I can later
review to see if I need to run the utility again.
Even though I can call it from a batch file, I can't run it because it
seems to be an interactive app, can't find a way to tell it which
store to process by passing a command line argument or something like
that.
Peter.
On Thu, 04 May 2006 17:38:56 -0700, PL <plecki2@xxxxxxxxxxx> wrote:
Is it possible to run ISINTEG unattended? I found a way to dismount
and mount stores from command line which means I can schedule it for
off-hours, but it's not much use if I can't run ISINTEG after the
dismount.
Thanks,
Peter.
.
- Follow-Ups:
- Re: Unattended ISINTEG
- From: PL
- Re: Unattended ISINTEG
- From: Susan
- Re: Unattended ISINTEG
- From: Ben M . Schorr - MVP
- Re: Unattended ISINTEG
- From: Andy David - MVP
- Re: Unattended ISINTEG
- References:
- Unattended ISINTEG
- From: PL
- Unattended ISINTEG
- Prev by Date: Re: Attachments Stripped
- Next by Date: Re: Event ID: 8231 and 8213 in exchange 2003
- Previous by thread: Re: Unattended ISINTEG
- Next by thread: Re: Unattended ISINTEG
- Index(es):
Relevant Pages
|