Re: WMI not working
From: Peter L (pl_at_compmatters_at_yahoo.co.uk)
Date: 09/17/04
- Next message: PJ: "CPU Temperature code example"
- Previous message: Gabriel GHIZILA [MSFT]: "Re: Win32_StartupCommand not showing everything?"
- In reply to: Gerry Hickman: "Re: WMI not working"
- Next in thread: Gerry Hickman: "Re: WMI not working"
- Reply: Gerry Hickman: "Re: WMI not working"
- Messages sorted by: [ date ] [ thread ]
Date: 17 Sep 2004 03:58:43 -0700
Gerry Hickman <gerry666uk@yahoo.co.uk> wrote in message news:<#fI7WbomEHA.3876@TK2MSFTNGP15.phx.gbl>...
> Hi,
>
> You need to break this down into component parts and test each in turn.
> You appear to be trying three things at once:
>
> 1. "WMI scripts" are for managing remote machines, nothing to do with
> logging on.
>
> 2. Scriptomatic?? What's that? Maybe you need the scriptomatic newsgroup
> to deal with issues relating to it?
>
> 3. Logging on, what does this have to do with WMI?
>
> At a wild guess, it may be that you've tried to create some fancy logon
> script that tries to do something the user is not allowed to do.
>
> You need to clarify, I don't see how any of this relates to "WMI not
> working".
>
> [snip]
I'm not very au fait with WMI so maybe I confused terminology of WMI
Scripting and WMI Filters. My situation is that I was getting errors
relating to the use of WMI Filters being applied to Group Policy
Objects on a Windows Server 2003. These GPOs are applied as part of
user logon processing hence the link between WMI and logon. Of course
in this instace the WMI is being used for simple WMI Filter controls
rather than full on WMI scripting.
Scriptomatic is the free tool from the MS Scripting guys to enable
everyone to try out and get used to whats available from WMI. Because
I was getting errors during the WMI Filter processing that happened at
user logon, I thought I would try to reproduce the problem in a more
specific situation that I could control and debug more easily -
separate from the logon process. Hence I tried running one of the
simple WMI Scripts automatically generated from Scriptomatic.
This then led me to the "Class doesnt support Automation" error at
which point I was stumped as to whether I was hitting a WMI error or a
VB Script error. Hence the post.
Anyway... to cut a long story short... I have now solved my original
problem. The permissions in the registry on the server had been
corrupted. I reset Everyone group to have Full Control over the
HKEY_CLASSES_ROOT hive and this resolved the problem!
- Next message: PJ: "CPU Temperature code example"
- Previous message: Gabriel GHIZILA [MSFT]: "Re: Win32_StartupCommand not showing everything?"
- In reply to: Gerry Hickman: "Re: WMI not working"
- Next in thread: Gerry Hickman: "Re: WMI not working"
- Reply: Gerry Hickman: "Re: WMI not working"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|