Ghost Solution Suite

When imaging a computer and running a configuration task to join the computer to the domain we receive an error and the task fails. The error is "The user name or password is incorrect" If I click on the failed task and tell it to retry it then completes without error.

I have reentered and verified the domain account used to join the domain. weh have had no problems running the tasks when we had version 3.0 - HF4. This problem started to occur right after we updated to Version 3.1 from Ver 3.0 HF4.

Has anyone elase seen this problem?

It sounds like a timing issue. Can you add a delay into the configuration task?

That was one thought I had as well but not sure how I can add a delay. The configuration is occuring as part of the Distribute Disk Image task in the job.

I have checked to "Automatically perform configuration task after completing this imaging task" and "Boot to production to complete configuration task"

If I uncheck those boxes and add a Configuration task I lose the computer name.

I'm getting the same issue when deploying an image or just trying to change the configuration.

It changes the computer name but does not join the domain. I tried two different Domain Admin accounts.

Albion, Did this problem occur after you updated to 3.1?

I opened a support ticket with Symantec but it went nowhere. They claim I am the only one with this problem and seem to think it is a sysprep or network issue. The problem is everything was working great until we updated.

Have you tried to retry the task after it fails? It fails for us the first time thru but then if I retry the task it completes OK.

We had experienced same issue, and my co-worker found out that the dagent running on the clients did not have right version and GSS server fails to upgrade them automaticly.

After we replaced the client from 3.1 express share on clients, the problem solved.

Same solution I came across as well.

Issue happened after the upgrade to 3.1

Noticed the Agent Update task was in the task log of the computer but never ran. After I ran it, it was able to do the configuration without issue.

An out of date dagent was the last thing support mentioned before closing the ticket. This makes sense now because when I retry the task and it completes successfully the dagent has updated itself. Below is what they said:

If you have a 3.0 version dagent included in your image, then as soon as it is booted into the OS after deploy, the first thing it would do is contact the server. If the server detects an incorrect version, the first thing it does is update the dagent so communication can continue. For most people that isn't an issue. it generally finishes before it does the join domain. It is possible for some reason the join domain part is running while the server is updating the dagent. If it takes a fraction of a second longer in your environment than we expect, it may derail communication to join the domain. If this is the case, then the only thing to guarantee it will work every time the first time is to get new images with the 3.1 dagent included.

So this sounds like the issue is the dagent. All of our images have been created with the old agent on them. To rebuild every image with a new agent is going to take some time. Sounds like a poor design that the old agent can't talk to the GSS Server and complete a basic task.

I wonder if there would be a way to force the agent update earlier or manually add the new agent to the existing image.