Ghost Solution Suite

Hi, I am trying to create an image of a laptop that I set up.  I followed the instructions detailed in the help file to do so, but whenever I finally executed the image creation, it made the laptop restart (laptop is plugged in and using wired networking) and it loaded up in pc dos.  Afterword it made a series of colored L's go across the screen, but on the server, it eventually failed.  Now I cannot get the laptop to return to windows.  It remains in pc dos outputing:

time laptopsipadress:11346 polling for bound server servername

I have tried restarting the computer, changing boot sequences, restarting the execution of the image create, but nothing I do allows the laptop to even return to windows.

So if anyone can tell me what to do to get the laptop back to windows, or to get the image fully created, I would be very thankful.


Edit:

I forgot to say that the networking card is a Realtek RTL8169/8110

Message Edited by hcaelxxam on 08-09-200708:14 AM

Thank you, That was exactly what I needed and it worked perfectly, however now I am at the issue as to why it is failing.  Here is a step by step recreation of what I did:

1. go to configuration recources > Images > Laptops  (folder)
2. right click > New Image
3. Name: Laptops, Location D:\Images\laptops, OK
4. Tasks > Laptops   (folder)
5. right click > New Image Create Task
6. General:
-----Name: Laptops
-----Source Machine: tpm102 - maleach      (network username)
-----Source drive: 1
-----Image Name: Laptops
-----Compression: Fast
-----Everything else unselected
7. Network/Sysprep - nothing changed
8. OK, Execute


After that tpm102, the computer I'm trying to image recognizes that ghost is working, puts up an informative box saying that an administrative process is occuring, it eventually restarts into pc dos outputing what I wrote above, and then the task on the ghost server fails with the log saying:

Client -------------------- Adapter Address ------------------ Step
tpm102 - maleach.......Not known...................................Update DOS system files
tpm102 - maleach.......Not known...................................Update DOS Network Drivers
tpm102 - maleach.......Not known...................................To Virtual Partition


I've even turned off the firewall on the server when I tried this to see if it was a port problem, but it still failed, so right now I am at a loss for what to do.

Hi,

You can try UNDI driver instead of the one the Ghost console picked for you out of inventory request. If you go to machine properties in Ghost Console you can change network driver to Universal network driver (UNDI). See whether this helps. Another thing is to look for DOS driver updates from the network card provider. GSS 2.0 was shipped with a lot of DOS network drivers but they are now up to 10 months old and some manufactures may have already provided fixes. One of the most recent ones that springs to mind is Marvel Yukon card.

Also, please note what messages you get when DOS network driver starts up. It may report some errors that will lead you to the root of the problem. It maybe as simple as interrupt conflict. Also, can Ghost agent communicate back with the server, ie. do you see usual "heart beat" messages (acknowledgment) going up and down the link?

ok, thanks, that fixed that problem, but now we have new problems

Now I can't get ghost to actually write the image file.

In my images folder on the server where I want the image to be written I have sharing on, with everyone having full control, as well as seurity where everyone has full control in an attempt to fix this problem.

In my Images folder under configuration recources, I have Image is located on the Client Machine unchecked.  And the location field is set to D:\symghost\laplaptopimages\test.gho.   (symghost is the folder where the permissions for full control are set)

As I said before the servers firewall is completely off, and the network card is now working in pc dos.

I have tried resetting D:\symghost\..... to \\cad-server\symghost\..... hoping that having a network name would fix the problem rather than a drive name.

I can indeed get the image to attempt to write to a thumb drive plugged into the laptop, but given that its a thumdrive, Its not big enough to hold the image so it fails there, and Ghost won't let me write the image to the computers C drive because that is the drive being imaged.  Regardless, the images need to be written to the server for efficiency, and writing to a local drive was really just a test to make sure it was actually trying to write.

Here is the error I get whenever I try to create the image with the location being D:\symghost\....

10030 unable to establish contact with session <cadserverpull45>
Check that the ghostcasting server application is ready to accept clients!
c:\ghost\ghost.exe - z2 - clone, src=1 mode=create,dst=@mccadserverpull48 -batch -igb -sgt
time ipaddress polling bound for cadserver


I have tried to open up GhostCast server and create my own seccion, but I can't figure out how to get clients to connect so I'm stuck on that attempt as well.

When you are using create image task from console and specify local drive d:\blah, this means local drive on the server. Ghost.exe sends image to Ghostcast server who then stores it on local d: drive. For that reason you do not need to make it an open share and grant everyone permissions to it.
Currently, when create image task is run from the Console, there exist no way for you to specify that your image will reside on a real network share. But you can create boot disk with ghost networking and network share access and then run ghost manually and store image on some network share.

Coming back to your problem. I cannot guess what is the issue here but if you can post ghosterr.txt contents. Also check that the session name that is run on the Ghostcast server is same as the ghost receives from the Console. In your example ghost tries to connect to session "cadserverpull45" but Ghostcast server runs on "carserverpull48", which arent going to work. Try running Ghostcast sever manually with any session name and then run ghost.exe on the client manually and connect to that session just to verify that connection between server and client is happy.