@Sebastian-Roth
Thanks, looks promising.
Will set up a test.

@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.

@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.

@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

@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.

@tom-elliott Many thanks!! I used now the internal ip address of the AD server … This was the whole problem.
A vaild domain name here did not work.

Normally this AD server is reachable with this fqdn YYYY.XXXX.com (it’s not the real domain). I can’t type public this domain here for security reasons.

I can now login with users from my AD into FOG.

@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.

@MasterOfUs Now that I have had a good sleep I figured that proposing to use SSH is just raising the hurdle once more but not solving the concern. Why? Because some kind of secret (probably SSH key) needs to be included in the FOS inits to authenticate when connecting. Even if this is done properly (random generated key pair) we can not prevent an attacker from loading the FOS init manually and extracting the secret, right?

So making it secure would mean the user needs to enter a connect passphrase manually on each deploy/capture.

@TraverseTheFOG First I suggest you check the free disk space on your FOG server. Connect via SSH and run: df -h

Copy the full output here or take a screenshot and post that here in the forums.

@rodluz Para MAC

@thedark5776 I can read your post in 2 ways. I answered previously in the most common way you ask. If I did not answer your question correctly then clarify if your original disk contains 2 partitions (like C and D) but you only want to deploy the C partition to the target computer).

@thedark5776 Licensing is out of scope in regards to FOG. But you will need to have 1 license for every target computer you deploy an image to. This is not a FOG requirement (because its open source) but your operating system you send to the target computer.

You did not mention the operating system you deploy to the target computer, but if you use MS Windows then you will need an enterprise activation license. The windows OEM license does not support imaging cloning. This is a microsoft EULA issue.

@sebastian-roth Perfect.
I’ll look at getting a test version up and running and see how it goes.
My work has made internet more clunky to get proxies working so I’ll have to test that as well.