Re: Remote WMI scripting problems

I suspect a privilege issue. I know this is common when backing up SQL
Server databases, where the actual backup process uses the server computer
credentials. I don't know how BackupEventLog works, but either you, the
client, or the remote computer needs backup privileges. I don't know if this
link helps:

http://msdn2.microsoft.com/en-us/library/aa390430.aspx

The privilege is called wbemPrivilegeBackup. I can't find better
documentation.

--
Richard Mueller
Microsoft MVP Scripting and ADSI
Hilltop Lab - http://www.rlmueller.net
--

"J Ford" <JFord@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6C8DD400-5194-4526-BAA2-8BD5EA60221E@xxxxxxxxxxxxxxxx
It appears that the ".BackupEventLog" method doesn't like UNC or Network
shares, almost as if it exec's it with SYSTEM credentials.

"Richard Mueller [MVP]" wrote:

There are many things that can go wrong with WMI. Check the
troubleshooting
links I posted earlier.

--
Richard Mueller
Microsoft MVP Scripting and ADSI
Hilltop Lab - http://www.rlmueller.net
--

"lyott" <lyott@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:AFCE800C-11E3-403B-9768-7B73C1FECEBF@xxxxxxxxxxxxxxxx
Thank you for the help so far!
I tried adding in:
Set objWMIService = GetObject("winmgmts:" _ &
"{impersonationLevel=impersonate,authenticationLevel=Pkt,(Backup)}!\\"
& _
strComputer & "\root\cimv2")
For some reason it still failed to retrieve the event logs from remote
computers. Are there any other possible problems that could be causing
this?
I'll try having another system administrator run it, in case they have
priviledges I'm not aware of, but is there any other potential cause to
this
error?

"Richard Mueller [MVP]" wrote:

Some time ago I researched how to connect to remote computers with WMI
and
found the following:

1. You cannot connect to computers running XP Home.
2. An NT computer cannot connect to OS later than W2k.
3. A W2k3 computer cannot connect to Win9x.
4. To connect to W2k Server SP4 you must set impersonation level to
Impersonate.
5. W2k computers must have SP2 to connect to XP or above.
6. W2k3 can only connect to Win9x and NT if credentials supplied.
7. To connect to XP or W2k3 you must set authentication level to Pkt.

I determined this before Vista came out, so I need to add to the list.

--
Richard Mueller
Microsoft MVP Scripting and ADSI
Hilltop Lab - http://www.rlmueller.net
--








.

Relevant Pages

  • Re: Backup Exec 11d - weird System Account credential failures, maybe SQL issue
    ... but the first backup job ... "Authentication failed on connection to the server - make sure tha ... "successful - used server credentials" ... like 30 seconds - but is successful) ...
    (microsoft.public.backoffice.smallbiz)
  • Re: Backup Exec 11d - weird System Account credential failures, maybe SQL issue
    ... but the first backup job ... It turns out that BE has a nifty feature - Select Volume Credentials - for ... something weird - the top icon (server) says "a communications failure has ... 'SQL Browser - 'the config of the AdminConnection\TCP protocol in the SQL ...
    (microsoft.public.windows.server.sbs)
  • Backup Exec 11d - weird System Account credential failures, maybe SQL issue
    ... but the first backup job ... It turns out that BE has a nifty feature - Select Volume Credentials - for ... something weird - the top icon (server) says "a communications failure has ... 'SQL Browser - 'the config of the AdminConnection\TCP protocol in the SQL ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Server down. what would you do?
    ... into laptops with cached credentials for days - probably over a week. ... a guess as to what will happen with the server. ... they can while the SBS is available, other than things hosted on the SBS ... I do not have a backup server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Forcing Process to Run With Ordinary User Authority
    ... I don't want to have to supply any credentials. ... The best approach is generally to use runas only for increasing the privilege level, ... If you try to run a privileged application from a non-privileged account using runas, if the alternate account lacks the required privilege level, you will be unable to use the application for actions requiring privilege. ...
    (microsoft.public.windows.server.security)