Ghost Solution Suite

I have created 3 tasks that allow a user to easily backup any PC where the Dagent is installed.

First task installs the automation folder in the client (WinPE), second task backups the entire drive onto the server to a folder with the computer's name.

Third task is to be run in Automation and allows the PC to get the right backup by name to restore it's content and it's actually working fine with one odd issue only.

The script doesn't run at in Automation.

If I send the command using the "Execute" option it works fine as long as "Run with default credentials" is selected. Try it with "console user session" or send it via a Job with Run Script and it's ignored, with "error 1" if it's sent with a script.

This problem happens with any command at all, whether it's just "echo test", "notepad" or anything at all. Drive mapping is working perfectly well so it can't be due to that either.

Of note is that, whenever a command is sent and ends up not running at all, I do see a command window opening and closing abruptadly.

Perhaps this is a problem with the SYSTEM ACCOUNT of WinPE but other uses seem able to send Scripts onto their Automation Folders so I am at a loss as to why it refuses to do so but has no problem if I send "Execute" with default credentials.

Any help would be apreciated, I'm only one step away to make an idiot-proof automated solution, just missing this final step (since CTRL+C, CTRL+V might be too hard for some people. I'm serious)

HI Koriath.

Is there any error message in the script task?

Have you tried to run the script one command at time? If I were you, I would open the cms and run one command at time to validate if everything is happening as planned in the script.

Regards,

It's just "Error 1", the famous one.

I've tried a script that's literally just "notepad" or "echo hi", a single command that still doesn't go through. But using the "Execute" option to send it instead does work, as long as "Default Credentials" are used, not the console user session, which got me thinking it might be something about what user is, well... Used to send a script since, unlike Production, I can't specify it for Automation.

Run script for WinPe should all be left as default. (Do not specify any account or logged on user)

Cause in WinPe there is no logged on user session, Thus they will alway's fail and never work.

You already where on correct track :)

I'm not sure what you mean, is it straight up impossible to run scripts in WinPE do to lacking a user account? Or is there a way to run scripts in WinPE?

Or are we simply not supposed to run scripts in WinPE, relying on startup.bat to do whatever needs to be done?

Because I can send individual commands with Execute from the RMB menu and they run just fine, it's only running scripts with Jobs that causes the Error 1.

I mostly want it done this way so I can use a script with %COMPNAME% that fetches the right image for the PC I drag said task to automatically, but this script would need to be sent when the PC is in Automation.

It is possible to use run script task in WinPE.

But we need to make sure that under advanced options of run script the radio button for System account is selected, not use logged on user or specified user