Ghost Solution Suite

Greetings,

While attempting to schedule a New Image Create Task on a machine in a separate domain, I am receiving the following the message from the Symantec Ghost Console:

"Can not save changes.  Can not save schedule definition file."

Nothing in the Event Viewer.  Not sure what's going on, but I'm wondering if it isn't credentials-based?

The administrator credentials on the separate domain aren't the same as the one that the Ghost Console Server resides in, therefore I must change them while scheduling the task.  The credentials have an extremely strong password with a special character in it (a symbol that can only be created by using an ALT+key combination).  Would this cause any problems for Ghost? 

Although I am experiencing this error, if I close the window representing the error and view the scheduled tasks, I see that the task did indeed schedule for the time I input, however the credentials show our default domain and administrator account, not the separate domain administrator account (they have different names).

A search of Google and the Symantec Knowledge Base showed nothing related to this error.  There is no error code to be found; at least not where I know to look.

Thanks in advance for any assistance!

Cheers, Jack Dorsey

I don't think this is related to your password.

The Ghost console scheduler relies on windows scheduled tasks for some of the functionality it provides. The root cause of the "Can not save changes" "Can not save schedule definition file" messages can be seen by attempting to create a task in windows task scheduler using the same credentials.

For instance when attempting something similar I'm getting: "Task Scheduler" : "An error has occured while attempting to set task account information. The specific error is: 0x80041310: Unable to establish existence of the account specified. Ensure the account name specified is valid."

In my case the message occurs beacuse there is no trust relationship defined between the domain my console machine is installed on and the domain where the user credentials provided are stored.

The good news though is that this trust relationship probably isn't needed. If your console is able to manage the remote machines anyway, you only need to supply credentials sufficient to exectute the console task.

Unless you are doing something really tricky like using console task scheduler on Console A, to execute tasks on Console B?

Can you let me know the error code and text of the message you are see when using windows task scheduler?

Thanks,
Xan

Message Edited by Xan Todd on 05-17-200703:13 PM

Hi Xan,

Thanks for the knowledgeable reply!  I'm not honestly not sure what was wrong, but after a reboot of the remote client I was able to get the task to perform.

Cheers, Jack

Hi Stormfront,

In my case I never found out what exactly was wrong, however after a reboot of the remote client the situation was resolved.

Does any of the information that Xan provided help?

In Jack's case I'd guess a hanging windows trust relationship caused the credentials he chose to use to be rejected. The restart would have resolved/re-established this trust relationship.

Really though, you only need to provide credentials valid to execute the task on the GSS server.

If your domain (or the authenication path to your domain) is often up and down you may wish to consider executing the task using local (gss server) credentials.

Note: To view the security required to execute a particular GSS defined scheduled task, head to Control Panel -> Scheduled Tasks -> [Taskname] -> Security.

If you were to say we could make this a whole lot clearer and provide better error messages in this area - I would agree. We will discuss this.

Thanks,
Xan

Message Edited by Xan Todd on 06-12-200711:59 AM