Ghost Solution Suite

We need Ghost to be running almost like a server where it accepts connections and we are able to ghost computers up or down to it. Without having someone there to turn on the ghostcast server portion. Is this possible.


Thanks

The short answer is no, right now it's not possible. Sorry.

The longer answer is "keep asking for it". I actually do have a program that works exactly that way, but it's just at the "some code I wrote" stage, not actual product with a user interface. Getting from a rough command-line tool that works on one developer's machine to something polished that has been tested to survive thousands of cycles on hundreds of machines takes lots of time.

As soon as GSS2 actually ships to manufacturing I do want to return to that and try and get it turned into a proper piece of the product. The more people who ask for it the more likely it is to get done.

Alright thats sound about right....what is the START SERVER function in the ghost console under FILE. What does that do?

right now I have a server setup and in the startup it runs a batch file that opens up about 13 ghostcast servers to do various jobs, they restart after a ghostcast. As long as the server is up and has been logged into, it will push down images.

One of my batch statements looks like this:
start c:\images\ghostsrv c:\image.gho session5 -N5 -R -UU

It starts ghostcast server with session name session5, it waits til 5 pcs are connected to it and pushes image and then resets and waits for 5 more.

This is fine if you are just re-imaging but if you are creating image, this will obviously not help, as the images would always be overwritten.

I am wondering if I can run these ghostcast sessions as a service and not even have to login to get them started?

I too need something like this for unattended/scripted re-imaging jobs as part of our automated testing.
-G

There is a capability to use client initiated tasks. So you can set up predefined tasks and then from the client initiate those tasks.

In the console --> Tools --> Client tab --> Enable Client User Interface
Then for the properties for the specific task --> General tab --> Allow Client Initiation and then you can set a password so that only specific persons are allowed to execute that task.

The downside is that the tasks are completely setup ahead of time and the targets are as well. SO you might think that you only want the client that initiated it to be the "target", which you can't. But if the targets and the settings are always the same this might work for you.