Ghost Cloning Error

[AnonGod]

Alright, just starting to pull my hair out on this.
Still working on it, but outside input would definately be appreciated. I will post back what I find as well.
Symantec is a joke when it comes to support, KB only. It's times like this when I know NAI has their act together - phone support for the life of your contract.

Background:
-Ghost 7.5 Server/Client
-Sysprep 1.1 (5.00.2195.2104)
-Running sysprep manually, not through ghost console (see Symantec KB, Document ID: 2002021914065725 - says console can only run sysprep 1.1 - 5.00.2195.1 only)
-Pulling image by boot disk and GhostCast
-Image gets placed on new machines just fine
-On exit of the ghostcast cloning operation, error 40102 display's for half a second before rebooting.
-Machine stalls on reboot, in DOS, trying to contact the ghost server

-Error 40102 points to either an older ghost client installed, or no ghost client installed. Post configuration fails.
-But Ghost 7.5 Client is installed in image.

Now, I can send a config update task to the machine while it is stuck looking for the server, it receives it fine and reboots. But the task reports as failed.
Machine reboots and gets into windows, and goes through the sysprep setup. Reboots and you are now in the machine, but without your config.
I send the same config update task to the machine, and it completes successfully.

Where is my error?
-Sysprep?, pulling the image?, cloning?, config?

Personal experiences with using Ghost are welcome.
Thanks!

[TAG]
anongod@hotmail.com
"Drawing on my fine command of language, I said nothing."

 

[Zelandakh]

What apps and OS are on the ghost image you are pulling down? What network card are you using?

If it every machine affected with same problem from the one image or all images?

This sounds like a pulling the image issue, but need to confirm the above. Have you tried copying the ghost to the local machine and implementing it manually?

 

[AnonGod]

I actually found the answers i was looking for and more.
Symantec is not the most helpful, but there are many other users with posts out here.
here's my link

http://servicenews.symantec.com/cgi...ct=symghost&mini_version=symghost_75&tpre=ent

[TAG]
anongod@hotmail.com
"Drawing on my fine command of language, I said nothing."

 

[retep37]

I have this exact same issue currently. I believe that I will simply need to dump my image one more time, update the client even though it is 7.5 to begin with! Perhaps just a config refresh before I run sysprep and dump again. I am using the exact same procedure as outlined in the original post and I am using the updated sysprep.exe due to issues with the "-clean" command.

AnonGod, if you make it back to this thread, please elaborate on your statement:
"I actually found the answers i was looking for and more"

I did not find much on this topic. Thanks for any help.

Peter