Ghost Solution Suite

We just upgraded from Ghost 8 to GSS 2. The upgrade went smooth. However there seems to be a problem when rolling out images we created previously in ghost 8. In the tasks window the status shows that it "failed". However the image does deploy and function on the client. This is only occurring with images we had created in ghost 8. New images we have created since upgrading to GSS 2 deploy fine and show "finished" instead of "failed". We are just a bit curious why the console is showing "failed" when the image deploys and functions.

The images that you deploy, if built with the older console, will likely have the the old Ghost client embedded in them. Now, the console should be trying to upgrade them as soon as possible after deployment, and if you look at the detail of the task log the reason for the program may be in that upgrading process.

You need to inspect the step-by-step detail of the task log for the task that failed, and find the description of the specific step within the task that had a problem. If you find a specific step that fails, often there is some more detail of the failure there too.

Thanks for the response Nigel. The last step is what is failing. The "step" is "configuration" in the Event Log from the "failed" roll-out.

Tomorrow I'll try rolling out one of these and see how it behaves upon booting up. I had not thought about the old ghost client being on those images - the ones created with the previous version of ghost.

Ah, thanks. I've just taken a look at how the tasks are sequenced, and basically forever what we've done is run the upgrade after checking the configuration status. That's because in every single version ever (up until GSS2), the configuration was done in the newly-imaged system by device drivers contained in the imaged system, and upgrading the client before checking the results thus made no sense.

In GSS2, the bulk of the configuration settings are actually applied in DOS by a program called GhConfig.exe, and the old post-configuration drivers never actually run any more (which ends up meaning that the old version of the client has no result from them to retrieve, which ends up in an error).

It's a subtle detail that we seem to have missed, but in GSS2 we should upgrade the client earlier in the task process after going into the imaged system.