Ghost Solution Suite

Hello all, 

We currently started purchasing Dell XPS 9570s and 9370s. We are running GSS 3 in a test VM before we put it into production and I am running into an issue that I cant figure out. I have pushed automation folders to the client PCs that I am trying to capture a backup image from. I can get them to boot into automation using a wait job and they are getting an IP from the DHCP server and they are mapping to the M: which is where we want the images to save. The issue is if I run an image job I cannot get ghost to launch, the PC will reboot back to windows. I even tried manually running a command to launch it by doing the following: M:\ cd ghost, and then ghost\ghost64.exe. When I do this 1 of 2 things happens, it will either reboot into windows 10 and take me to the login screen or it will sit there and do nothing. I been working with a gentlemen from Symantec and even he has run out of ideas. Just to bring everyone up to speed, Ive installed a clean copy of windows 10 pro on this machine and deleted all the factory Dell partitions. I would really like to get this into production soon, so any help is highly appreciated.

1. You are using WinPE x86 or x64? Did you try to manually start Ghost64.exe or Ghost32.exe on affected client computer while it is loaded in WinPE? What it shows?
2. What show Ghost logs on client side (it should be stored in WinPE, just boot in WinPE and check logs from cmd line) Also check logs on GSS side eXpress\LOG\

As Igor mentioned, you need to be using Win PE 64 bit - the 32 bit version will not work with Ghost64.exe.
Your WinPE edition must also contain the 64 bit drivers for both the NIC and the SATA chipsets on the machine you are booting. If you intend to use any USB-3 ports during imaging, you will need the correct USB-3 drivers as well.

Igor, 

As mentioned, I have tried running ghost manuallu while loaded in winPE and the outcome is either nothing happens or the client PC reboots to the windows 10 login screen. 

Some background.   It isn't that nothing happens and it reboots.   Ghost64.exe is crashing and this caused winpe to reboot to production OS.   Because ghost64 is crashing there aren't any ghost logs even to review.   It is also crashing on execution not part way through creating or restoreing an image.   So when ghost64 is indexing the hardware some thing causes it to crash. 

From the production OS Ghost64 is able to be executed and does not crash it only crashes when run from the 64bit Win pe environment.    


While in win PE the MS diskpart tool can be executed and the hard drive is able to be seen by the winpe environment.  The system in question does have a M2 drive if I recall and there have been delays in the past with getting up to speed with newer solid state drives.     But even with Ghost development delays gennerally if the drive can be seen in win PE by disk part then genneraly ghost can succeed with imageing.        

Not having access to this hardware I am not able to help much further.   We do know that the PE that is imported and the ghost suite as installed is working because we can test on a VM and all the steps expected work as expected.   This is limited to this specific hardware if any one has these systems that they have pointers on it would be appreciated.    Additional Sata chipset drivers have not been added to the winpe but the NIC drivers were needed.   That might be the next thing to try.    The firmware was updated just as a test and same results. 

Cheers

May also be worth updating to the 1903 ADK version of WinPE as MS tend to add support for newer hardware.