How to see if an image being deployed was properly sysprepped (4281139)

If the image is a Kimage, you can open up the image detail page,
click on “browse files” and go to folder “C:\windows\system32\config”. Then download the file “system” but rename it “temp_system” and save it to a temp folder (c:\temp for my example).
Open a command prompt and change directories into the temp folder and run the following commands.
               reg load HKLM\TEMP_SYSTEM c:\temp\temp_system
               reg query HKLM\TEMP_SYSTEM\setup /v Systemsetupinprogress /s

               reg query HKLM\TEMP_SYSTEM\setup /v clonetag /s
               reg unload HKLM\TEMP_SYSTEM

If the image has been properly sysprepped then the SystemSetupInProgress key should return a value of 1.
             SystemSetupInProgress reg_dword  0x1
If the return is 0
             SystemSetupInProgress reg_dword  0x0
The image is not syspreped and the windows setup will not run at system boot to install any drivers.

Likewise, a properly sysprepped image must contain a value for clonetag.
clonetag   reg_multi_sz   DATE   (the date sysprep was run)

If the clonetag entry is missing then the image has not been properly syspreped and the windows setup will not run at system boot to install any drivers.

If the image is a WIM,  it is more difficult to access the registry so the Mid level task “Image sysprep check “ can be used to check the registry entries at deployment time. This task will work for WIM or Kimages.

There are two versions of this task: one for K2000 3.5 and one for K2000 3.6 and later. Please ensure you install the correct version for your K2000.

Installation: Unzip the file and copy the pkg and xml files to \\k2\\restore
On the K2 Web UI click | settings & maintenance | Package Management | Import K2000 Packages
Find the Image sysprep check PO task on the list and check the box (on the left side of the page )
go to the drop down box and select “Import Selected”

How it works:

This is a Mid-level task, so drop it into the top of the mid-level task section of the detail page of the image to be deployed.
When the deployment runs, a log file will be written  (\\k2\petemp\sysprepcheck.log).
This log will show the image information such as name, image ID, etc and also the values of registry keys
HKEY_LOCAL_MACHINE\System\Setup
SystemSetupInProgress
and
clonetag

if the image has been properly sysprepped then the SystemSetupInProgress key should return a value of 1
                SystemSetupInProgress reg_dword  0x1
if the return is 0
                SystemSetupInProgress reg_dword  0x0
Then the image is not syspreped and the windows setup will not run at system boot to install any drivers.

Likewise a properly sysprepped image must contain a value for clonetag
                clonetag   reg_multi_sz   DATE   (the date sysprep was run)

If the clonetag entry is missing then the image has not been properly syspreped and the windows setup will not run at system boot to install any drivers.

Note: this task is for debugging purposes so it will write to the same log no matter what image it is run from. If it finds a previous text file called “sysprepcheck.log” it will overwrite it with results of the latest run.