WMI with SP2


G

Guest

I had a SP1 project that ran some WMI scripts at first boot. These scripts
ran fine. When the project was upgraded to SP2 the scripts all failed with
error:-
"Unable to connect to WMI service Error 0x80041001 Generic failure ".
Does anyone know what may be causing this?

Thanks.
PaulM
 
Ad

Advertisements

K

KM

Paul,

Obviously, make sure your scripts are run at FBA phase later that WMI core gets installed and registered.
Check out \windows\fba\FBAlog.txt log to know if WMI is not installed yet when your commands are launched.

Also, for testing purposes turn off Firewall in your image (in Configuration in TD).

KM
 
G

Guest

The scripts get run well after the WMI components have been registered. There
is no firewall component at the moment. As I said before this setup worked
before being upgraded to SP2.

Could there be some security settings in SP2 that are not allowing scripts
to be run?
 
K

KM

Paul,
The scripts get run well after the WMI components have been registered. There
is no firewall component at the moment.
There is no firewall component? IIRC, the firewall components would be brouhgt in Configuration automatically if you include network
stack.
Did you turn off Autoresolve dependencies in TD?
As I said before this setup worked before being upgraded to SP2.
That woud be an issue [bug] if you have all the components autoresolved. However, I started think this is not the case with your
image.
Could there be some security settings in SP2 that are not allowing scripts to be run?
Well.. In SP2 there have been a number of security fixes. It is hard to tell which one is causing problems for you becuase it would
compltely depend on what you have got in the WMI scripts.

Did you:
- try the WMI scripts after FBA? If it works there, please verify thee FBALog.txt to make sure WMI Core gets installed before
you launch the scripts.
- try on XP Pro SP2. You would know than if your WMI scripts are compatible with SP2 in general.
[/QUOTE]
 
G

Guest

KM,

You are correct I had turned off Autoresolve dependencies in TD. I have done
a build with all the dependencies resolved. It made no difference except that
during FBA it complained about firewall.cpl (not 100% sure of extension).

I remember at one stage adding the component with firewall.cpl and that did
not work either.

Regards,
Paul.


KM said:
Paul,
The scripts get run well after the WMI components have been registered. There
is no firewall component at the moment.
There is no firewall component? IIRC, the firewall components would be brouhgt in Configuration automatically if you include network
stack.
Did you turn off Autoresolve dependencies in TD?
As I said before this setup worked before being upgraded to SP2.
That woud be an issue [bug] if you have all the components autoresolved. However, I started think this is not the case with your
image.
Could there be some security settings in SP2 that are not allowing scripts to be run?
Well.. In SP2 there have been a number of security fixes. It is hard to tell which one is causing problems for you becuase it would
compltely depend on what you have got in the WMI scripts.

Did you:
- try the WMI scripts after FBA? If it works there, please verify thee FBALog.txt to make sure WMI Core gets installed before
you launch the scripts.
- try on XP Pro SP2. You would know than if your WMI scripts are compatible with SP2 in general.
 
G

Guest

Slobodan,

I have run one of the scripts on an XPpro PC with SP2 and it does work.
Here is the command line:
C:\WINDOWS\system32\cscript.exe C:\WINDOWS\System32\prncnfg.vbs -t -p "HP
LaserJet 4M" +direct.

I have also reported a problem with the SMS client. This appears to be the
same issue with WMI.

Regards,
Paul.
 
Ad

Advertisements

K

KM

Paul,

You may need "Windows Firewall Control Panel" component.

Btw, is it 32 or 64 bit processor used on your target?

--
Regards,
KM, BSquare Corp.

KM,

You are correct I had turned off Autoresolve dependencies in TD. I have done
a build with all the dependencies resolved. It made no difference except that
during FBA it complained about firewall.cpl (not 100% sure of extension).

I remember at one stage adding the component with firewall.cpl and that did
not work either.

Regards,
Paul.


KM said:
Paul,
The scripts get run well after the WMI components have been registered. There
is no firewall component at the moment.
There is no firewall component? IIRC, the firewall components would be brouhgt in Configuration automatically if you include network
stack.
Did you turn off Autoresolve dependencies in TD?
As I said before this setup worked before being upgraded to SP2.
That woud be an issue [bug] if you have all the components autoresolved. However, I started think this is not the case with your
image.
Could there be some security settings in SP2 that are not allowing scripts to be run?
Well.. In SP2 there have been a number of security fixes. It is hard to tell which one is causing problems for you becuase it would
compltely depend on what you have got in the WMI scripts.

Did you:
- try the WMI scripts after FBA? If it works there, please verify thee FBALog.txt to make sure WMI Core gets installed before
you launch the scripts.
- try on XP Pro SP2. You would know than if your WMI scripts are compatible with SP2 in general.

--
Regards,
KM, BSquare Corp.
Paul,

Obviously, make sure your scripts are run at FBA phase later that WMI core gets installed and registered.
Check out \windows\fba\FBAlog.txt log to know if WMI is not installed yet when your commands are launched.

Also, for testing purposes turn off Firewall in your image (in Configuration in TD).

KM

I had a SP1 project that ran some WMI scripts at first boot. These scripts
ran fine. When the project was upgraded to SP2 the scripts all failed with
error:-
"Unable to connect to WMI service Error 0x80041001 Generic failure ".
Does anyone know what may be causing this?

Thanks.
PaulM
 
G

Guest

KM,

It is a 32 bit VIA C3 processor.

Regards,
Paul.

KM said:
Paul,

You may need "Windows Firewall Control Panel" component.

Btw, is it 32 or 64 bit processor used on your target?

--
Regards,
KM, BSquare Corp.

KM,

You are correct I had turned off Autoresolve dependencies in TD. I have done
a build with all the dependencies resolved. It made no difference except that
during FBA it complained about firewall.cpl (not 100% sure of extension).

I remember at one stage adding the component with firewall.cpl and that did
not work either.

Regards,
Paul.


KM said:
Paul,

The scripts get run well after the WMI components have been registered. There
is no firewall component at the moment.

There is no firewall component? IIRC, the firewall components would be brouhgt in Configuration automatically if you include network
stack.
Did you turn off Autoresolve dependencies in TD?

As I said before this setup worked before being upgraded to SP2.

That woud be an issue [bug] if you have all the components autoresolved. However, I started think this is not the case with your
image.

Could there be some security settings in SP2 that are not allowing scripts to be run?

Well.. In SP2 there have been a number of security fixes. It is hard to tell which one is causing problems for you becuase it would
compltely depend on what you have got in the WMI scripts.

Did you:
- try the WMI scripts after FBA? If it works there, please verify thee FBALog.txt to make sure WMI Core gets installed before
you launch the scripts.
- try on XP Pro SP2. You would know than if your WMI scripts are compatible with SP2 in general.

--
Regards,
KM, BSquare Corp.

Paul,

Obviously, make sure your scripts are run at FBA phase later that WMI core gets installed and registered.
Check out \windows\fba\FBAlog.txt log to know if WMI is not installed yet when your commands are launched.

Also, for testing purposes turn off Firewall in your image (in Configuration in TD).

KM

I had a SP1 project that ran some WMI scripts at first boot. These scripts
ran fine. When the project was upgraded to SP2 the scripts all failed with
error:-
"Unable to connect to WMI service Error 0x80041001 Generic failure ".
Does anyone know what may be causing this?

Thanks.
PaulM
 
K

KM

Paul,

Just for testing purposes, ould you make sure DEP is turned off on your SP2 image?
The easiest way would be to add /NoExecute=AlwaysOff switch to the boot.ini.

Read it more about DEP on SP2 here: http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr.mspx

The reason I have a concern about DEP is that even on XP Pro SP2 system I was getting a bunch of crashes from some MS components
including WSH until I turned off DEP for them.

Let us know if it would help.

KM
KM,

It is a 32 bit VIA C3 processor.

Regards,
Paul.

KM said:
Paul,

You may need "Windows Firewall Control Panel" component.

Btw, is it 32 or 64 bit processor used on your target?

--
Regards,
KM, BSquare Corp.

KM,

You are correct I had turned off Autoresolve dependencies in TD. I have done
a build with all the dependencies resolved. It made no difference except that
during FBA it complained about firewall.cpl (not 100% sure of extension).

I remember at one stage adding the component with firewall.cpl and that did
not work either.

Regards,
Paul.


:

Paul,

The scripts get run well after the WMI components have been registered. There
is no firewall component at the moment.

There is no firewall component? IIRC, the firewall components would be brouhgt in Configuration automatically if you include network
stack.
Did you turn off Autoresolve dependencies in TD?

As I said before this setup worked before being upgraded to SP2.

That woud be an issue [bug] if you have all the components autoresolved. However, I started think this is not the case with
your
image.

Could there be some security settings in SP2 that are not allowing scripts to be run?

Well.. In SP2 there have been a number of security fixes. It is hard to tell which one is causing problems for you becuase it would
compltely depend on what you have got in the WMI scripts.

Did you:
- try the WMI scripts after FBA? If it works there, please verify thee FBALog.txt to make sure WMI Core gets installed before
you launch the scripts.
- try on XP Pro SP2. You would know than if your WMI scripts are compatible with SP2 in general.

--
Regards,
KM, BSquare Corp.

Paul,

Obviously, make sure your scripts are run at FBA phase later that WMI core gets installed and registered.
Check out \windows\fba\FBAlog.txt log to know if WMI is not installed yet when your commands are launched.

Also, for testing purposes turn off Firewall in your image (in Configuration in TD).

KM

I had a SP1 project that ran some WMI scripts at first boot. These scripts
ran fine. When the project was upgraded to SP2 the scripts all failed with
error:-
"Unable to connect to WMI service Error 0x80041001 Generic failure ".
Does anyone know what may be causing this?

Thanks.
PaulM
 
G

Guest

KM,
I shall try this but exactly where in boot.ini should I add
"NoExecute=AlwaysOff". Under which key?

Thanks,
Paul.

KM said:
Paul,

Just for testing purposes, ould you make sure DEP is turned off on your SP2 image?
The easiest way would be to add /NoExecute=AlwaysOff switch to the boot.ini.

Read it more about DEP on SP2 here: http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr.mspx

The reason I have a concern about DEP is that even on XP Pro SP2 system I was getting a bunch of crashes from some MS components
including WSH until I turned off DEP for them.

Let us know if it would help.

KM
KM,

It is a 32 bit VIA C3 processor.

Regards,
Paul.

KM said:
Paul,

You may need "Windows Firewall Control Panel" component.

Btw, is it 32 or 64 bit processor used on your target?

--
Regards,
KM, BSquare Corp.


KM,

You are correct I had turned off Autoresolve dependencies in TD. I have done
a build with all the dependencies resolved. It made no difference except that
during FBA it complained about firewall.cpl (not 100% sure of extension).

I remember at one stage adding the component with firewall.cpl and that did
not work either.

Regards,
Paul.


:

Paul,

The scripts get run well after the WMI components have been registered. There
is no firewall component at the moment.

There is no firewall component? IIRC, the firewall components would be brouhgt in Configuration automatically if you include
network
stack.
Did you turn off Autoresolve dependencies in TD?

As I said before this setup worked before being upgraded to SP2.

That woud be an issue [bug] if you have all the components autoresolved. However, I started think this is not the case with
your
image.

Could there be some security settings in SP2 that are not allowing scripts to be run?

Well.. In SP2 there have been a number of security fixes. It is hard to tell which one is causing problems for you becuase it
would
compltely depend on what you have got in the WMI scripts.

Did you:
- try the WMI scripts after FBA? If it works there, please verify thee FBALog.txt to make sure WMI Core gets installed
before
you launch the scripts.
- try on XP Pro SP2. You would know than if your WMI scripts are compatible with SP2 in general.

--
Regards,
KM, BSquare Corp.

Paul,

Obviously, make sure your scripts are run at FBA phase later that WMI core gets installed and registered.
Check out \windows\fba\FBAlog.txt log to know if WMI is not installed yet when your commands are launched.

Also, for testing purposes turn off Firewall in your image (in Configuration in TD).

KM

I had a SP1 project that ran some WMI scripts at first boot. These scripts
ran fine. When the project was upgraded to SP2 the scripts all failed with
error:-
"Unable to connect to WMI service Error 0x80041001 Generic failure ".
Does anyone know what may be causing this?

Thanks.
PaulM
 
K

KM

Paul,

You can add it to the current ARC path that is set up for your XPe image.

Under [operating systems] you probably have got something like:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Embedded" /fastdetect
Change it to:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Embedded" /fastdetect /NoExecute=AlwaysOff

KM
KM,
I shall try this but exactly where in boot.ini should I add
"NoExecute=AlwaysOff". Under which key?

Thanks,
Paul.

KM said:
Paul,

Just for testing purposes, ould you make sure DEP is turned off on your SP2 image?
The easiest way would be to add /NoExecute=AlwaysOff switch to the boot.ini.

Read it more about DEP on SP2 here: http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr.mspx

The reason I have a concern about DEP is that even on XP Pro SP2 system I was getting a bunch of crashes from some MS components
including WSH until I turned off DEP for them.

Let us know if it would help.

KM
KM,

It is a 32 bit VIA C3 processor.

Regards,
Paul.

:

Paul,

You may need "Windows Firewall Control Panel" component.

Btw, is it 32 or 64 bit processor used on your target?

--
Regards,
KM, BSquare Corp.


KM,

You are correct I had turned off Autoresolve dependencies in TD. I have done
a build with all the dependencies resolved. It made no difference except that
during FBA it complained about firewall.cpl (not 100% sure of extension).

I remember at one stage adding the component with firewall.cpl and that did
not work either.

Regards,
Paul.


:

Paul,

The scripts get run well after the WMI components have been registered. There
is no firewall component at the moment.

There is no firewall component? IIRC, the firewall components would be brouhgt in Configuration automatically if you
include
network
stack.
Did you turn off Autoresolve dependencies in TD?

As I said before this setup worked before being upgraded to SP2.

That woud be an issue [bug] if you have all the components autoresolved. However, I started think this is not the case
with
your
image.

Could there be some security settings in SP2 that are not allowing scripts to be run?

Well.. In SP2 there have been a number of security fixes. It is hard to tell which one is causing problems for you becuase
it
would
compltely depend on what you have got in the WMI scripts.

Did you:
- try the WMI scripts after FBA? If it works there, please verify thee FBALog.txt to make sure WMI Core gets installed
before
you launch the scripts.
- try on XP Pro SP2. You would know than if your WMI scripts are compatible with SP2 in general.

--
Regards,
KM, BSquare Corp.

Paul,

Obviously, make sure your scripts are run at FBA phase later that WMI core gets installed and registered.
Check out \windows\fba\FBAlog.txt log to know if WMI is not installed yet when your commands are launched.

Also, for testing purposes turn off Firewall in your image (in Configuration in TD).

KM

I had a SP1 project that ran some WMI scripts at first boot. These scripts
ran fine. When the project was upgraded to SP2 the scripts all failed with
error:-
"Unable to connect to WMI service Error 0x80041001 Generic failure ".
Does anyone know what may be causing this?

Thanks.
PaulM
 
Ad

Advertisements

G

Guest

KM,

Sorry this did not fix the problem. A good idea though.

KM said:
Paul,

You can add it to the current ARC path that is set up for your XPe image.

Under [operating systems] you probably have got something like:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Embedded" /fastdetect
Change it to:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Embedded" /fastdetect /NoExecute=AlwaysOff

KM
KM,
I shall try this but exactly where in boot.ini should I add
"NoExecute=AlwaysOff". Under which key?

Thanks,
Paul.

KM said:
Paul,

Just for testing purposes, ould you make sure DEP is turned off on your SP2 image?
The easiest way would be to add /NoExecute=AlwaysOff switch to the boot.ini.

Read it more about DEP on SP2 here: http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr.mspx

The reason I have a concern about DEP is that even on XP Pro SP2 system I was getting a bunch of crashes from some MS components
including WSH until I turned off DEP for them.

Let us know if it would help.

KM

KM,

It is a 32 bit VIA C3 processor.

Regards,
Paul.

:

Paul,

You may need "Windows Firewall Control Panel" component.

Btw, is it 32 or 64 bit processor used on your target?

--
Regards,
KM, BSquare Corp.


KM,

You are correct I had turned off Autoresolve dependencies in TD. I have done
a build with all the dependencies resolved. It made no difference except that
during FBA it complained about firewall.cpl (not 100% sure of extension).

I remember at one stage adding the component with firewall.cpl and that did
not work either.

Regards,
Paul.


:

Paul,

The scripts get run well after the WMI components have been registered. There
is no firewall component at the moment.

There is no firewall component? IIRC, the firewall components would be brouhgt in Configuration automatically if you
include
network
stack.
Did you turn off Autoresolve dependencies in TD?

As I said before this setup worked before being upgraded to SP2.

That woud be an issue [bug] if you have all the components autoresolved. However, I started think this is not the case
with
your
image.

Could there be some security settings in SP2 that are not allowing scripts to be run?

Well.. In SP2 there have been a number of security fixes. It is hard to tell which one is causing problems for you becuase
it
would
compltely depend on what you have got in the WMI scripts.

Did you:
- try the WMI scripts after FBA? If it works there, please verify thee FBALog.txt to make sure WMI Core gets installed
before
you launch the scripts.
- try on XP Pro SP2. You would know than if your WMI scripts are compatible with SP2 in general.

--
Regards,
KM, BSquare Corp.

Paul,

Obviously, make sure your scripts are run at FBA phase later that WMI core gets installed and registered.
Check out \windows\fba\FBAlog.txt log to know if WMI is not installed yet when your commands are launched.

Also, for testing purposes turn off Firewall in your image (in Configuration in TD).

KM

I had a SP1 project that ran some WMI scripts at first boot. These scripts
ran fine. When the project was upgraded to SP2 the scripts all failed with
error:-
"Unable to connect to WMI service Error 0x80041001 Generic failure ".
Does anyone know what may be causing this?

Thanks.
PaulM
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

WMI 1
WMI 0
WMI Question 1
wmi problem 1
WMI problem 1
WMI Component 1
wmi initialization failed 9
WMI Script Issue 3

Top