Ghost Solution Suite

Hey All!

I need some help on an issue.  I have Ghost Solution Suite 3.0, and I am running into an issue at the end of the Image creation process.  I am NOT able to start pulling the image... I really need some specific info, there is just to much info in the symantec website which is not.
 

- All Ghost Suite programs running on the Windows 2012 server.

- We are working with Fujitsu ESPRIMO Q920

I need some fast help, this is an internship project for me at the RIVM

"System error 1223 has occurred" suggests that the account details in the WinPE boot disk are wrong. Another common problem nowadays is when you try and map an F: drive it fails because there is an internal card reader set of drives that get given F:, G:, H: etc. Modern practice is to use W: to map the eXpress share.

Hello Andy!

Thanks for your fast reply.

 

I've added the WinPE bootdisk from C:\Program Files (x86)\Windows Kits\8.1

But how can I manage my account details settings? ( I'm kinda new with Windows ADK ) Do I need to boot my WinPE and add account settings and change the mapping to another drive letter? I dont know how to boot from the Windows Kits map.

Looking forward to ur reply!

From the Ghost console go to Tools > PXE Configuration Utility. Select the Boot option your job is using and "Edit" then "Edit Boot Image". Once the "Boot Disk Creator" screen opens press "Edit" at the bottom and then you can step forward to step 5 of 12 and add account information.

Thank you Andy!

This helped for me!

Now Ghost booted from the network with automation, it makes 30GB images, is it possible to make it smaller?

 

In the "Create Disk Image" Job there is an Advanced options button where you can select "Optimize for Size" which will increase the compression used. Is it a sysprepped image you are taking? You can run the cleanup tool automatically on Windows 7 before you take an image, you can also clean up leftovers from superseded Windows patches by installing KB2852386, this KB also give the instructions for running cleanup automatically: https://support.microsoft.com/en-gb/kb/2852386 If you run cleanup after installing this patch it will create a log file under c:\windows\logs\cbs\deepclean.log; the end of this log will tell you any patches that you have installed in your image that are superseded and can be removed from your image build process.

The option to compress and optimise for size was broken in early 3.0 and then removed at some service pack (I think 3) and then now is back in the product with 3.1 MP 1.  Check out the release notes for 3.1 MP1 it notes this as a new feature and a known issue so I don't yet know what that tells us. 

http://www.symantec.com/docs/DOC9253