@gandzioreek said in Boot Porteus Kiosk iso from fog pxe menu:

I tried, didn’t worked

What didn’t work? What did you see?

While this thread is 2 years old, I just looked at the Porteus Kiosk iso image again, and it looks pretty much the same, so the menu settings I recommended previously should still work.

If it wasn’t for the details most things would work right out of the box.

@george1421

@george1421 said in FOG With more than 1 subnet:

What host OS is the fog server running?

I’m using debian.

After some searching on internet, i found this steps(https://gist.github.com/troyfontaine/59ace875a951154f881bfe3d297d1a10) to configure PFSense with VLAN and TFTP Server. After configuring the step 3, now i can boot on the other vlan(172) but it’s more slowly than the vlan 200 to receive the boot file. But it works!! I don’t really know yet if this is the problem, but it worked haha. Now i’ll make some tests and see if the imaging it’s working correctly.

Thank you.

@sega Yes, though I think it’s specific to the multicast sessions bandwidth capability and limited at the storage node level (if my memory serves correctly)

@Sebastian-Roth Thanks Sabastian.

@typotony That’s Great to hear!
Glad you got it working and that it was as easy as intended.

Is your AD configured as SSL only connections? This could be part of the problem but I’m just grabbing at straws with this thought.

@george1421 I tried entering a hostname after the prefix was appended, for example I entered “TestVM” thinking the full registered hostname would be “NCIT-TestVM”, but the device was registered as “TestVM”.

@george1421 Thanks Guyz !!

@plegrand Correct

@René_Sig Hey René,

we have solved the problem with delete the tasks on the mysql database.

mysql -u root
use fog
delete from tasks where taskState = 0;

@george
the “Programs” folder is not part of winPE, it stays back on the CDrom iso on the Y: drive. If you boot the ISO thru a console - you get to keep the Y: drive. If you boot the ISO thru PXE, control is turned over to Hiren winPE process and you lose access to the Y: drive.
To make the Y: drive available from a PXE boot: I edit Hiren’s boot process inside the boot.wim file and map the Y: drive to a network share after winpe initialize but before Hiren process initializes. You must copy folder ‘Program’,‘CustomDrivers’, and HBCD_PE.ini to the network share.

@brakcounty According to the installer code, it’s in $sslpath/CA/*. It also appears in your /opt/fog/.fogsettings file, under sslpath=.

By default, the installer drops it all into /opt/fog/snapins/ssl (lib/common/functions.sh L#1879)

@rizingknight72 You ahve to create an image definition and assign it to the host.

Zero touch just means that the image you’re using doesn’t require the machine to be touched after imaging.

Please review the FOG Documents as this is one of the first things discussed when dealing with FOG.

@brent I don’t recommend this solution.

But I did test something similar many years ago: https://forums.fogproject.org/topic/6941/windows-server-as-fog-storage-node-proof-of-concept-blog

There is also this method: https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node

Another choice is to create an iscsi target and connect the fog server to that iscsi target to the /images directory on the fog server.

But FOG Project only supports using a linux computer with the FOG Storage node configured loaded as valid.

@jmeyer said in How to Use FOG to PXE Boot MultiBoot 2k10 Unofficial:

chain memdisk iso raw

Just adding a bit of a caveat here.

memdisk is a BIOS boot loader only. There is currently not an equivalent function for UEFI based systems.

The iso image you boot from must be less than 2GB in size (remember 32bit address space) AND the booting computer must have at least 2 times the memory of the 2GB iso to function. So in the case of a 2GB ISO image, your computer needs to have 4GB of RAM.