Ghost Solution Suite

So I just started another ghostcast session to clone 31 computers. On those computers, some works A1, some have the cloning agent crashed and some have nothing loaded... This is a ghost cloning session using the automated partition. I included the pictures. 

Version 3.0, 1252, Hotfix 1

Those computers are all the same. 

Thank you.

I have locked your previous thread since you have started a new one on the same issue.

Are you really unable to discuss the settings of your switches with anyone in your environment?.  IGMP snooping was a fundamental requirement in Ghost 2.5 if you wanted to multicast, so without checking this out, how do you hope to make progress with your issue?

Are you able to categorically state that all bioses on your machines are at the same revision and all have identical settings?  What make and model are your machines?  Is the UEFI bios enabled on these machines?

I've been using GSS 2.5 since A LOT a years. Multicast is working. That lab is 100% same computers with the same components and the same BIOS. Computers are Lenovo M93p (10A8S20700).

No UEFI since those were previously ghosted with GSS 2.5

I changed my task for a manual multicast (boot with a CD, check attached file). The multicast starts for 10 sec, then hangs.

I'm really starting to believe that GSS 3.0 has been released too soon. How can this thing can have so many problems? None of the deployment (50+) I've done so far were 100% succesfull.

If you were to look back over the threads detailing the development and release history of Ghost 3, Symantec have never made a secret of the fact that the releases would be staged. Users were crying out for some basic updates to the core files which form the hub of the new release, but there is a lot of ongoing development work to add functionality based on user feedback, much of which was received during the public beta testing that preceded the release.

In respect of your cloning activities, are you deploying an old image created under version 2.5 or is this a new image created under Ghost 3.0?  Has the operating system changed in the new image?  Although the bioses may be the same, are the settings the same also?  For example, is AHCI enabled for the hard disk(s) or are the bios settings for compatibility mode? This would naturally affect the requirement for WinPE to have the appropriate SATA drivers installed.  In your testing, are you getting consistent results with the machine inventory - ie, do the same machines always fail, or is pass/fail a random distribution?

At this point, I would suggest giving Symantec support a call so that you can discuss your problems in more detail.

Thanks for your reply. My image is a Ghost 3 file. It comes from a virtual machine (vmware).

As I mentionned earlier, if I'm deploying using a boot CD and starts a manual multicast session, it works. If I'm deploying 100% using the console (like i'ts meant to be) that it's not working. So instead of taking me 2 min to start my ghostcast session, I have to visit every single computer with my boot cd.