J
J.S.
Hi,
by tracking down my WPA problem on small footprint images I learned that
it seems to be necessary to have WMI on board. I installed several WMI
components (that one I found in my correctly running "big" XPE-Image***)
but result is the same: no WPA-PSK and no list of configured wireless
networks after reopening the WZC dialog.
But now I notice accesses to the wbem databases in the
repository\FS-directory. And I get errors in wbemprox.log showing this:
(Thu Jan 18 16:48:00 2001.3717535) : NTLMLogin resulted in hr = 0x8004100e
According to MSDN this seems to be an invalid namespace problem
(WBEM_E_INVALID_NAMESPACE)
What's missing here? Where can I put my fingers on to go one step
further? I have no idea where to go on next. Maybe there's some help out
there...
*** installed components are:
WMI Core
WMI Correlation
WMI Filter
WMI Management Snapins
WMI SNMP Provider
WMI Win32 Provider
WMI Windows Installer provider
(as I said these components are also available in a correctly running
"full blown" image)
by tracking down my WPA problem on small footprint images I learned that
it seems to be necessary to have WMI on board. I installed several WMI
components (that one I found in my correctly running "big" XPE-Image***)
but result is the same: no WPA-PSK and no list of configured wireless
networks after reopening the WZC dialog.
But now I notice accesses to the wbem databases in the
repository\FS-directory. And I get errors in wbemprox.log showing this:
(Thu Jan 18 16:48:00 2001.3717535) : NTLMLogin resulted in hr = 0x8004100e
According to MSDN this seems to be an invalid namespace problem
(WBEM_E_INVALID_NAMESPACE)
What's missing here? Where can I put my fingers on to go one step
further? I have no idea where to go on next. Maybe there's some help out
there...
*** installed components are:
WMI Core
WMI Correlation
WMI Filter
WMI Management Snapins
WMI SNMP Provider
WMI Win32 Provider
WMI Windows Installer provider
(as I said these components are also available in a correctly running
"full blown" image)