Page 1 of 1

PXE boot PK 4.5 not reflecting customisations [SOLVED]

Posted: 17 Nov 2017, 04:45
by rans_au
Hi,

I'm working on deploying Porteus Kiosk [PK] 4.5 via PXE from Windows Server 2012 R2.
I'm able to get the client to successfully PXE boot, and load PK, however none of the customizations made via the wizard are reflected in the PXE boot image. It simply boots chrome (the selected browser) to the http://porteus-kiosk.org/ homepage.
I've tried (multiple times) to create ISOs via the wizard, and upload them to online storage, unpack, then transfer to the PXE server for deployment. However no matter what changes are made, none are retained upon PXE boot.
If I burn the ISO created to HDD/USB, the changes are reflected.
Hopefully I'm missing something simple?
Any help appreciated.

Thanks,
rans.

PXE boot PK 4.5 not reflecting customisations

Posted: 17 Nov 2017, 14:14
by fanthom
Hi rans,

1) Did you update 'http_server=' parameter in /unpacked_kiosk_ISO/boot/pxelinux.cfg/default? I guess yes otherwise kiosk would not boot at all over PXE.
2) Is your http server hosting all files from /unpacked_kiosk_ISO folder? It must host /boot, /docs and /xzm folders and all files/subfolders which are present in them.

Thanks

PXE boot PK 4.5 not reflecting customisations

Posted: 21 Nov 2017, 23:18
by rans_au
Hi Fanthom,

Thanks for your prompt reply, however I've managed to figure this one out!
My issue had to do with the configuration of the http server, specifically setting the mime types for .xz and .sgn files, which were not present by default in IIS (I had previously set one for .xzm files, if I hadn't done this I suspect the thing wouldn't have booted at all).
Once I configured these as file/download mimetypes, PK was able to access these files, and picked up the remote management file configuration.
So thanks for the reply, but it was a problem with my http server configuration, not PK.

Regards,
rans.

PXE boot PK 4.5 not reflecting customisations [SOLVED]

Posted: 22 Nov 2017, 00:03
by rans_au
For those who ran into these problems as well, I also had to configure (for the relevant folder) in IIS :
- Enable Directory Browsing
- Add another mimetype for .* - application/octet-stream (this is for those files that have no file extension)

rans