We are using ZCM 10.1.3 (SLES 10) for imaging new Vista computers. Where we have students handling this task we elected to invoke a series of installation scripts.

- create a samba share on your SLES box containing the installation scripts.
- within the settings.txt file (/srv/tftp/boot) mount, copy your scripts to the local machine, and then umount the directory
- our installation scripts can then be run from the local machine. In our case students CD into dell or lenovo directory and run the corresponding installation script according to model type such as;


This script looks like the following;

/sbin/reboot -f

Each of these scripts reference the image (base of addon) to come down to the machine;

/bin/img -rp sysprep/sysprep-vistasp1-x86-107-1TB.zmg

In any event the end result. Is a completely modular Vista Imaging approach. The scripts can be edited with Notepad++ from a windows box without needing to mount and modify the 'root' image. Changes can be made on the fly.. and all the installs happen within the sysprep (audit phase) of Vista.

Big thing to note here.. is that simply running the scripts from the samba share is a bad thing.. as img apparently writes temporary files to disk which later are removed once imaging is complete. (imgcode/imglog/imglogr) You can end up having several machines attempting to write to identical files.. and causing chaos. Compying locally works like a charm.

Just one way of doing things.. but seems to work well for us. We could do autodetection and all that jazz, but sometimes we prefer not to have total automation.. there is job security to think of.

Feel free to share your procedures.. ideas.. or if there are any other tricks your organization is doing which you think may be of benefit.