Windows could not finish configuring the system. To attempt to resume configuration, restart the computer

[Migration User]

I am using GSS 3.1 MP4.  This behavior started just a few weeks ago but i thought it was the type of computer i was imaging.  I didnt realize this issue was larger until i tried to image a different make/model.

Ive used all of the video resources to get GSS up and running and create/deploy images to my machines.  I came from Altiris DS 6.9 so i am familiar with the process.

In a lab with all of the same make/model computer, when i take an image of a computer, choosing the option to Prepare using Sysprep - Congifure and putting in my sysprep options of Win 7 Pro x64 and use exisiting key (which is a KMS key activating with my on premisis server) and entering my domain admin information, i get the aformentioned error in my title upon the image creation complete and the computer rebooting.  My computer is fully updated with all of the latest MS updates.  I saw Symantecs article TECH158464 about applying the MS Hotfix, but that is not applicable since i am fully updated.  I did a search through the forums and could not find anything.

I saw that there are "fixes" out there people have done but they invovle touching each machine which defeats the purpose of what i am using GSS for.  Any help would be greatly appreciated as i cannot create and thus deploy any images.

One other thing to note, if i deploy an image that i successfully built maybe 2 or so months ago, they deploy fine.  It seems to be the computer itself after image creation.  The created image is broken as well.  If i deploy that image, the machines the image is deployed to will display the same error.

[Migration User]

Timothy,

If I am to understand correctly you are receiving this error when trying to create a sysprepped image?

 

Sysprep Creating Image

1. Ghost Solution Suite sends a file/script to your client machine that will start sysprep using the parameters that you entered. The administrator user and password entered is used to elevate the sysprep run command on the client machine.

2. Client machine runs sysprep from "C:\windows\system32\sysprep\sysprep.exe"

3. Client Machine reboots and then Ghost Solution Suite creates an image

 

Sysprep Deploying Image

4. Ghost Solution Suite deploys sysprepped image to your new machine

5. Client machine reboots and the unattend.xml file is used to configure client machine

6. If a Ghost Solution Suite dagent is present on the sysprepped image, the client machine will boot up to production, check back in with the GSS sever and finish the configuration process, changing the computer name.

 

At which step in the Sysprep process are you experiencing an issue?

[Migration User]

Between setp 5 and 6.  Once the image is downloaded to the target machine, the machine reboots and goes through discovering devices and turning services on.  During the turning services on stage, the message pops up.

 

I think it might have more to do with the image or sysprep rather than GSS.  After i get the error message, if i reboot into safe mode, it will display the same error again during a safemode boot, but then after rebooting back to normal, it completes.

[Migration User]

Timothy,

You are correct at that point it would be in Windows hands and not ghost. Are you using a custom unattend.xml file or the one created by GSS?

[Migration User]

I apologize for the late response.  To answer the above, it is the default unattend file created by GSS.  The issue definately lies on the windows side and not the GSS side.