Engineering has updated the way sysprep integration works with post install tasks in 2.3.9670 and greater versions. The changes put less emphasis on the version of sysprep used or how it is used. In past versions of the K1000 appliance sysprep integration, the C:\sysprep\i386\$oem$\cmdlines.txt was used to trigger the post install task by setting the registry’s RunOnce section to install the applications. This was largely unreliable since the version of sysprep used was the difference between post install tasks working or not. This also meant customers that already had sysprep based images, in many cases, could not use then if they were planning post image installations of applications. This new enhancement is not deploy.cab version dependent and thus works consistently.
Here is how it works:
Just as before, the application source files were copied to C:\KACE\Applications directory after the image deployment and post_install.bat kicked off the installs. However, in the updated version, the batch file installs the application rather than telling the registry to do it. In addition, cmdlines.txt was not used but rather the sysprep.inf file was appended with a [GuiRunOnce] section and the command, “C:\kace\applications\post_install.bat”. The only requirement to automate the process is setting “AutoLogon” in the sysprep.inf file.
[GuiUnattended]
AutoLogon=Yes
AutoLogonCount=1
Trouble shooting the feature is easy.
- Verify your K2000 appliance is version 2.3.19670 - 3.2.31608.
- Verify the application source is in C:\kace\applications.
- Verify that “C:\kace\applications\post_install.bat” is added to C:\sysprep\sysprep.inf.
Here are some tested sysprep files for all service pack levels for XP and also some information on Vista sysprep. We also have a FAQ on creating sysprep images. This has been newly modified for the newest version of the K2000 appliance.
From version 3.3.xxxx and on, syprep integration is automatic and this FAQ should not be followed.