Ghost Solution Suite

Dear,

I need a little clarification:

When I create an Image with Sysprep in GSS 2.5 the Master-PC is sysprepped and the the image is created. That
- leaves the Master-PC behind as a sysprepped (Non-Configured) PC after Image-Creation
- allows me to distribute this new image even with a manual Ghost-Cast-Session (no Automation)

In GSS 3.1 this seems to be done in two steps?

When I create an Image with Sysprep in GSS 3.1 the Master-PC seems to be not sysprepped before/after/during the creation of the image. In fact the Master-PC come´s up almost "untouched" (still Configured) after the Image-Creation.

When I distribute that Image with a GSS 3.1-Job an DO NOT activate the two checkboxes "Configuration-Task after Imaging" and "Reboot to Production" the new PC comes up with the same Name, IP-Adress and even Domain-Membership the Master-PC has had.

So: What does exactly happen on what PC (Master/Target) on which Point of the process?!

Thanks in vorward!

TJ

P.S.:

Just tested: Distribute my above mentioned Image with Sysprep with manual Ghost-Cast to another PC: Same IP, same Name, seems like no Sysprep has been done, although I checked the Boxes when Creating the Image.

When I distribute exact this Image with a GSS 3.1-Job, also with checked Sysprep-Boxes, the Traget-Machine ends up as sysprepped.

So it seems to me that Sysprep is only done during the Distribution-Process but not during the Creation-Process of the image?
If this ist the Case: For what reason I have Sysprep-Checkboxes in the Image-Creation-Taks? Confused...

It sounds like sysprep's not running. Check your logs under C:\windows\panther or c:\windows\system32\sysprep

Dear,

thank you!

I will check.
Does this mean, that creating a sysprepped Image with GSS 3 leaves the PC behind sysprepped (unconfigured) like it was in GSS 2.5?
And if it does not, Sysprep did not "happen"?

TJ

The "boxes" you speak of during the deployment job are the configuration tasks, if not running a manual task you will want to use the automatically perform config task option.

The configuration task is what changes the name of a pc, re joins the domain etc... after sysprep. The only reason you sysprep is to get the out of box experience, change the SID on the image and deploy a generalized image to new machines.

Please see Microsofts doc on sysprep

https://technet.microsoft.com/en-us/library/cc721940(v=ws.10).aspx

It doesn't matter how you run sysprep, if it's run successfully it will leave the PC in a generalised unconfigured state ready for cloning.