Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

GhostCast prompts for next segment on some clients, but not others

Updated: 21 May 2010 | 2 comments
KeithBrownGDC4S's picture
0 0 Votes
Login to vote

I am using Ghost Solution Suite 2.5, with all the latest updates.  (This includes GhostCast Server 11.5.0.2113.)

I have been loading this image onto several machines using a simple boot disk and manually starting the GhostCast session on the client.  Now I am trying to automate it all by adding the necessary switches to the Ghost32 command line on the boot disk. 

I thought I had all the same switches, but on machines using my original boot disks, the image loads just fine.  However, on a machine using my new boot disk (connected to the exact same GhostCast session from the server), it stops and prompts for the next segment.  Of course, I cannot get to the next segment because I'm using GhostCast; if I cancel on that machine, the other machines continue on their merry way.

Here is the manual steps I was doing on the original boot disks:

  1. I had the -noide switch built into the command to start Ghost.
  2. When Ghost starts, I go into options and enable the following:
  3. * Spanning (-span) is on by default
  4. * AutoName (-auto) is on by default
  5. * Reboot (-rb) I turn on
  6. Then I select GhostCast -> Multicast, put in the session name, destination, etc.

So for my new boot disk, I just added the following switches to the Ghost32 command:
-noide -rb -span -auto -clone,MODE=restore,SRC=@MCsessionname,DST=1


I also tried adding the -nofile switch in front of the -clone switch.

Is there something I'm missing?  I wouldn't think it is something on the server, since the exact same session works with the original boot disks but not the new ones.

Thanks

Comments

Randall Newnham's picture
17
Nov
2009
0 Votes 0
Login to vote

Filenames

Keith,

The issue is likely with your naming convention for your files. I often see this when numbers are used in the filename. It often causes images to be segmented differently. Try recompiling the image file with the Ghost Explorer to have a new name without numbers.

Thank you,

Randy

KeithBrownGDC4S's picture
17
Nov
2009
0 Votes 0
Login to vote

Found a solution, but unsure why it works

Actually, I added the -batch switch, and that seems to fix it for some reason.

I do actually have a number in the filename:  ABCD1.GHO, ABCD1001.GHS, etc.  Would that cause it to behave differently when a GhostCast session is joined manually vs. via a command-line argument?

Thanks.