Re: backup a remote host's event logs
- From: "Michael Harris \(MVP\)" <mikhar.at.mvps.dot.org>
- Date: Wed, 13 Jun 2007 12:39:34 -0700
Adam Sandler wrote:
On Jun 12, 5:28 pm, "Michael Harris \(MVP\)" <mikhar.at.mvps.dot.org>
wrote:
Look in the C:\Temp folder on each of the servers...
Once the event log is backed up, you can use a UNC path reference
\\server\c$\temp to copy the *.evt file and then delete them from the
server.
My script has this line:
backupLog = log.BackupEventLog(sFileName)
and
sFileName has "C:\Temp\" in it... somehow the scripting engine thinks
this is the local (to each host) temp dir and NOT the dir from where
the script was run??? ...
That is the way *remote* WMI automation is designed to work, it has nothing
to do with script host/engine executing on your machine.
... How about if I put your \\server\c$\temp
suggestion in sFileName and since I've then been explicit about the
location I can avoid having to copy afterwards?
Remote WMI automation runs in an impersonated security context, meaning that
it can't access other remote resources like UNC paths.
--
Michael Harris
Microsoft.MVP.Scripting
.
- References:
- backup a remote host's event logs
- From: Adam Sandler
- Re: backup a remote host's event logs
- From: Michael Harris \(MVP\)
- Re: backup a remote host's event logs
- From: Adam Sandler
- backup a remote host's event logs
- Prev by Date: Re: WshShell.Run and long command
- Next by Date: Re: ADO stored proc
- Previous by thread: Re: backup a remote host's event logs
- Next by thread: Re: Generating a HTML file with accentuated characters?
- Index(es):
Relevant Pages
|
