The Windows 7 Kiosk’s have been doing well over the last year, but have proven to be a bit of a pain with updates. Each month I set a reminder to perform Windows & AV updates. AV was fine (We use SEP) but Windows would always hang on a few .NET updates or cumulative roll ups for no reason. So I decided to look in to Porteus Kiosk once more and spend a bit more time customising it. The end result is a much easier to deploy and manage Kiosk. I have not gone down the path of setting up the server component for them yet which would be nice, due to the fact that we only have 2 and there is not much management needed. I may tinker with this sometime soon.
So to begin just download the standard ISO from the Porteus website
I wanted to change the default home page to be the same one used on the Windows 7 Kiosks, as well as the default wallpaper. So it was necessary to customise the ISO and rebuild it on a Linux machine.
Porteus uses modules in the .xzm format to house it’s file structure. After some research I decided it would be easiest to just modify one of the existing modules and add my files to it. Referring to the manual customisation page this is quite easy
On a Linux machine (I used a standard Ubuntu desktop) follow the customise process as described in the link above. Copy the standard Porteus ISO to the /tmp directory, then from the terminal create the kiosk_ISO directory, mount it, copy the files and unmount.
Inside the xzm directory I chose the 003-settings.xzm file to alter. To make changes you first need to unsquash the package, places your files in the folder structure where you need them (I placed my custom homepage in /opt/kiosk-home.), and resquash it again. All described in the modules page
Once you are done with your customisations, move the xzm module back to the xzm directory of the kiosk_ISO folder. Now run the make_iso.sh script to create the .ISO file again.
Simply burn that to a CD and put it in the intended Kiosk machine.
My additional customisations of the install itself are as follows. This is generated after you run through the wizard. The critical one for my needs was the wallpaper (needs to be a web address where it is downloaded and applied during install) and enable_file_protocal=yes. This allows referencing the local file structure for the home page with file://
additional_components=09-x11vnc.xzm uefi.zip 08-ssh.xzm 07-java.xzm 05-flash.xzm