WMI cache?

Question

0.00/5 (No votes)

See more:

.NET2.0

Hi,

I am having a issue with WMI. I am starting a process on a remote computer using it. First I copy the application(.exe/.NET 2.0) and then I use WMI and Win32_Process Create method to start it. And, it starts, it runs correctly, but there is one problem. I make changes to my deployed application from time to time. But for some reason the process that starts on the remote system is the outdated one. It runs the 'old' version. The file that is copied remotely is 100% the new one (I check the date attribute).

Can anyone help with this one? How to force WMI run the 'fresh' deployed application?

Many thanks,
Marius Jigoreanu

Posted 21-Dec-09 2:41am

majig

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

majig · Answer 1 · 2009-12-21T22:14:00

Hi,

I got it. I was testing the tool in two different ways. With psexec and WMI. psexec copies the file to system32 and with the WMI I copy it to windows(admin$) folder. It seems that WMI was trying to executing the file found at system32 first (not always the updated one), so it ignored the one in windows folder. If the file in system32 is missing, then it executes the one in windows folder.

Thanks for the ones who took a look at this one,

Cheers,
Marius Jigoreanu