> On Mar 18, 9:15 am, "Tom K" <thomas.DOTk...@ThighmarkDOT.com> wrote: >> This line in our logon script...
>> Set oWMIService = >> GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")
>> ...returns an error code 80041002 on some systems.
>> Anyone have ideas what might be causing it?
>> Thanks,
>> Tom
> Are these WinNT systems? That error is WBEM_E_NOT_FOUND according to > a search at MSDN. IIRC, NT does not have WMI installed, though it can > run it.
> If they are not NT, then the problem must presumably be related to a > fault in the WMI installation.
> In any case, it would appear to be a configuration problem, not a > scripting fault. You may get more help at the WMI or a sys admin > group.
Thanks for the quick reply, Tom. These are all fully patched Windows XP SP2 systems that are displaying the problem. I forgot to include the WMI group on my OP so I've added them now. Hopefully those wizards will have something for me.
The $65,000 question is what is the quickest and easiest way to rebuild the WMI installation?
>>> Set oWMIService = >>> GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")
>>> ...returns an error code 80041002 on some systems.
>>> Anyone have ideas what might be causing it?
>>> Thanks,
>>> Tom
>> Are these WinNT systems? That error is WBEM_E_NOT_FOUND according to >> a search at MSDN. IIRC, NT does not have WMI installed, though it can >> run it.
>> If they are not NT, then the problem must presumably be related to a >> fault in the WMI installation.
>> In any case, it would appear to be a configuration problem, not a >> scripting fault. You may get more help at the WMI or a sys admin >> group.
> Thanks for the quick reply, Tom. These are all fully patched Windows XP > SP2 systems that are displaying the problem. I forgot to include the WMI > group on my OP so I've added them now. Hopefully those wizards will have > something for me.
> The $65,000 question is what is the quickest and easiest way to rebuild > the WMI installation?
> Tom
When WMI is busted, and the answer is not obvious, this is the first place I turn. It has helped me many times. This tool is also the biggest VB Script I have ever seen.
>>>> Set oWMIService = >>>> GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")
>>>> ...returns an error code 80041002 on some systems.
>>>> Anyone have ideas what might be causing it?
>>>> Thanks,
>>>> Tom
>>> Are these WinNT systems? That error is WBEM_E_NOT_FOUND according to >>> a search at MSDN. IIRC, NT does not have WMI installed, though it can >>> run it.
>>> If they are not NT, then the problem must presumably be related to a >>> fault in the WMI installation.
>>> In any case, it would appear to be a configuration problem, not a >>> scripting fault. You may get more help at the WMI or a sys admin >>> group.
>> Thanks for the quick reply, Tom. These are all fully patched Windows XP >> SP2 systems that are displaying the problem. I forgot to include the WMI >> group on my OP so I've added them now. Hopefully those wizards will have >> something for me.
>> The $65,000 question is what is the quickest and easiest way to rebuild >> the WMI installation?
>> Tom
> When WMI is busted, and the answer is not obvious, > this is the first place I turn. It has helped me many times. > This tool is also the biggest VB Script I have ever seen.
After research I found the following regarding connecting to remote computers with WMI:
1. You cannot connect to computer 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.
> After research I found the following regarding connecting to remote > computers with WMI:
> 1. You cannot connect to computer 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.
|
