Ghost Solution Suite

Sup guys,

 I'm seeing some strange thing when trying to issue ghost command to clients after they were booted into PE

So I kept the start.bat in WinPE at default, which looks like this:

---

set path=%path%;x:\ghost

x:
cd \ghost
rem --- This will remove any traces of virtual partition from hard drive ---
gdisk32.exe /revert  >> x:\ghost\startlog.txt

rem --- This will create primary OS drive configuration ---
ghost32.exe /setosdrives /blind >> x:\ghost\startlog.txt
start /w cmd.exe
start ngctw32.exe -console

---

I created a simple ghost task and executed on target client (see attached pic)
When client boot into PE and launched ngctw32, a task command was issued to client (see attached pic). The command issued to client was: Ghost32.exe -clone,mode=restore,src=@mcvista,dst=1 -sure
As a result, client launched ghost32 and automatically joined cast session and began cloning; but cloning always failed in less than 10 seconds and forced a system reboot!!



So far, the only way I could get around this problem is to explicitly specify the ghost32 command in start.bat, which is documented on a KB article:

---

@ECHO OFF
set path=%path%;x:\ghost

x:
cd \ghost
gdisk32.exe gdisk32 /diskwipe /disk:system
rem ECHO press any key to continue...
pause
rem --- This will create primary OS drive configuration ---
ghost32.exe /setosdrives /blind >> x:\ghost\startlog.txt
rem ECHO press any key to continue...
pause
ghost32.exe -clone,mode=restore,src=@MCvista,dst=1 -sure

---

In fact, I can chop down my start.bat further and it also worked:

---

@ECHO OFF
set path=%path%;x:\ghost

x:
cd \ghost
ghost32.exe -clone,mode=restore,src=@MCvista,dst=1 -sure

---

The problem is that I really do not want to edit my start.bat and I would like to leave it the way it is originally.  So that the clone command is saved in my tasks instead of hard coded into start.bat.  Could someone share some light?

Is there any progress shown in your ghost cast server?
Again, Is it failing exactly at the same point everytime ?

yes, the progress bar do show progress on both cast server and ghost client.  And yes, I've tried this on two different models of computer in my company, it is failed at the same point every time.  Sorry I cannot capture any crash dump or logs because computer always reboot on it's own at 8% into cloning.

 Did the image that you use pass the integrity check?

To perform integrity check, do the following:

Go to My Computer->Local Disk (c): ->Program Files ->Symantec->Ghost->Ghost32.exe
Open Ghost32.exe   ->choose Local ->Check->Image File-> open your image file

In some cases, the image file might get corrupted and can cause issues while ghosting. Verify the same.

Yes, the images passed the integrity check. But my method of cloning continues to fail

Hi starlog,

Check the available memory space in your destination drive. You can get this error due to low disk space too.\

Again,

If this is a ghost console task, on the bottom of console window,you can see red "x" mark for failed tsk. right click and select event log
In the event log window, chck where it fails and right click the same..select event details....this will give you more details about the cause....


Dilip

Hi there,

Try running GDISK32 without any switches, as this will list the disks. What I have seen sometimes is that the utility partition will show as a physical disk. The behavior described could be Ghost successfully cloning a very,very small "disk" that isn't active. Note the disk numbers and size that GDISK32 tells you and make sure you are cloning what you expect to be cloning. 

Thank you,

Randy