Command not working from script

[gorbisloth]

I've written a script to handle imaging a Win7 machine with ghost. The script works up to the point where it attempts to contact the ghost server to connect to the session. It basically times out. Now the reason I'm looking for assistance from you instead of from Symantec is that if I run the exact same command from the command line it works perfectly.

The command needed to connect to the Ghost session is "Ghost32.exe -CLONE,mode=restore,src=@MCc,dst=1 -sure". When this is entered from a WinPE prompt it starts Ghost, connects to the session and completes successfully.

The line in my script that runs this command is:

Runwait(@ComSpec & " /c "& "Ghost32.exe -CLONE,mode=restore,src=@MCc,dst=1 -sure",@WindowsDir,@SW_SHOW)

Is there something wrong with my code that would cause this to not work when run from my script?

[DicatoroftheUSA]

Try loading your run string into clip and run it yourself and see what happens.

[BrewManNH]

Where is the Ghost.exe program file located? If it's not in the Windows directory, you should specify the working directory to be the directory where Ghost is located.

[gorbisloth]

Where is the Ghost.exe program file located? If it's not in the Windows directory, you should specify the working directory to be the directory where Ghost is located.

The Ghost exe file is located in the system32 folder. Does it even need a working directory?

[BrewManNH]

It probably doesn't need a working directory, but you included one on your RunWait command, so I figured if you're including it it should point to the right place. Otherwise it might not work correctly. Also, have you tried surrounding the ghost command with quotes?

[gorbisloth]

After some testing it appears that a working directory has to be specified. If that option is left out the command won't execute at all. The ghost command is in quotes. I've tried both single and double quotes and doesn't seem to matter which you use it does the same thing.

[BrewManNH]

When I mentioned putting it in quotes I meant something like this.

Runwait(@ComSpec & " /c "& '"Ghost32.exe -CLONE,mode=restore,src=@MCc,dst=1 -sure"',@SystemDir,@SW_SHOW)

In the above, the Ghost command line is surrounded by first a single and then a double quote so when @ComSpec sees it, it sees it like this, "Ghost32.exe -CLONE,mode=restore,src=@MCc,dst=1 -sure", I'm not sure if it will make any difference, but can't hurt to try.

[John]

If it is a working directory issue you need to change @WindowsDir to @SystemDir, since you say it's in the system32 folder. Shouldn't make much difference on the path that way, but that can also depend on Ghost32.exe.

[gorbisloth]

Working directory doesn't seem to matter. I've tried windowsdir, systemdir and tempdir. All come back with the same problem.

Could McAfee be blocking this from running somehow? Like I said earlier if you run the ghost command from the command prompt it connects fine but if it's run from the AutoIT executable it doesn't work. Could McAfee, which is running on the server, see that the network requests are coming from the AutoIT executable and be blocking it?

[Tripredacus]

I don't think McAfee can see what is running on the WinPE, since there is an internal firewall that should be enabled. I'd run it with a /K to see if there is any valuable information that shows up in that cmd.

[gorbisloth]

I was thinking more of McAfee running on the server than in WinPE actually. It doesn't look like the Host Intrusion part is installed on the server anyway so not likely an issue.

[gorbisloth]

Well seems to be the firewall in WinPE that's causing the problem. Disabled that with "wpeutil disable firewall" and Ghost picked up without a problem. Going to do some further testing but that seems to have been the problem.