@tom-elliott sorry! I meant last deployed date. Is there a way for me to see per host when it was? I am just looking to get an output of that via some sort of command line. I use Powershell currently with the FOG API.

@esmatos You might provide more detailed information on what steps exatly you took and what error occurred (pictures of error on screen!!). Otherwise we won’t be able to help.

@tehcnique DNSMASQ can be installed on the same server as FOG or on a different linux server. It will work well in either case as long as the target pxe bootng computers are on the same subnet as the dnsmasq server. If the pxe booting computers are on a different subnet then you must make a change on your router to make it work.

What configuration file are you using for dnsmasq? It would be helpful if you put it in your post. DNSMASQ can do a lot of things so the configuration file is important to have it correct.

@tom-elliott said in How to use QNAP NAS for image storage?:

@exworker9to5 Or this:
https://wiki.fogproject.org/wiki/index.php?title=NAS_Storage_Node

https://wiki.fogproject.org/wiki/index.php?title=Use_FOG_with_FreeNAS

https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node/1

Thank you!

@jona will you show us the output of this command
ls -la /var/www/html/fog/service/ipxe it almost sounds like your install did not complete correctly. You should have a file called init.xz that is the virtual hard drive for the kernel bzImage. Your kernel panic is saying the kernel doesn’t understand the virtual hard drive.

Where did you get the bzImge you added to stop the first error?

@tom-elliott Hi, thanks for the reply.

Im getting the following errors : in CMD :

curl: (6) Could not resolve host: NjhmN2VkNmFiZWVmZGQ4NjNhNGYyMzAwYmEyZGY4MWMwYzdhZGFmZjQyZjI0Yzc0Mjc1NzNmYWE1MjVlMzBjODM5MTE2YjZlODJhNjNhZmFiMzg1NGU3NmM1MjQzMDc4M2FjYTU0NGExMWQ2NWQxxxxMWJlZjQ’
curl: (6) Could not resolve host: MTM3OWM1YjczZjI3OGZlNmVjNjk0MWQwYTUzOTljNTFjOTc0YmE0OWRiMjQ5MzhhOGE0ZGM4ODRjZjFkOWI2MzI3NjNlYzMxYTY4MWJhNjEzOTFmMWY3OTEwMDJmNTUwM2Q1NTNjMjlhZTA5NmQ3xxxxNDU’

and in powershell console :

Invoke-WebRequest : Cannot bind parameter ‘Headers’. Cannot convert the "fog-api-token:

But nevermind, thanks for the support but im throwing in the towel. Guess this is just 1 of those things thats to complicated for me. Hoped it was simple, but im getting errors left and right. Thanks for your time. Dont waste anymore on me 🙂

@cwgcad As George said this looks like a response packet. With source port 80 this must be the case I would think. So please figure out what the other IP is!

Matching the alerts with httpd log in the FOG server is a great idea.

You didn’t mention your process, but if you are using sysprep and have your reference unattend.xml file in the right locaiton it should work.

Look over this thread, it give you a sanitized unattend.xml file as well as the sysprep switches.

FWIW I use the unattend.xml file to name the PC and connect it to the domain and not the fog client, so I know this route works.

@aheerds said in "Enabling apache and fpm services on boot" failed:

I got much further in the installation by changing to debian:latest and not ubuntu:20.04.

Now I am stuck at this :

insserv: FATAL: service mountdevsubfs has to exists for service hwclock insserv: FATAL: service mountkernfs has to exists for service procps insserv: exiting now!

Currently working on it, but FOG has started and it’s running. But there is still something wrong …

@matthieu-jacquart Sorry I can only write in english.

Its best if you DO NOT connect your mother/master image to active directory before you capture the image. I’m sure my environment is different than you, but we use MDT to create the golden image, sysprep then capture with FOG. At no time is the golden image connected to AD before capture with FOG. The first time the target computer image is connected to AD is on the final hardware.

@cello said in Client should deploy everyday an do a autostart:

Why can’t I synchronize the computer and then immediately boot from the hard disk? The menu always appears and I then have to select the option to start again.

Which menu do you mean? The FOG boot menu has a default option to chainload the OS from disk, pretty much what you want from what I understand.

@george1421 well no also is an awnser 😉 I really appriciate the time you spend on it for me! Thanks a lot!!

@ntex
Nevermind, I’m too tired clearly, fixed the original configuration has another prefix= to empty.
So this line was creating a conflict with one above.

3195ca99-f8a5-45c8-b390-a2ad984f0f78-image.png

Time to rest for today. 😊 long day, thanks anyways!!

@george1421 Checking for the folder /sys/firmware/efi works perfectly so far on the systems we are testing.

If the folder exists we assign it the UEFI image, if it doesn’t exist it gets assigned the BIOS image.

@kyl said in Multiple PXE Servers:

Currently I am using chain to point menu items to the pxe boot files residing on another server. I know that this isn’t what FOG is made for, but it’s working for me and that’s all I can ask for.

That is the beauty of FOG and open source software. FOG is flexible enough to support doing things that it was never designed to do. Case in point the articles related to pxe booting your fav OS installer. That’s not related to FOG, but can be done with a little skill.

@sebastian-roth as you suspected, this ISO image did boot both legacy and EFI. Which has been a boon.

I have used this ISO four times this week, and it has been a huge time-saver.

@wasps-d You can automate the domain join with FOG by using the so called fog-client software. Installed in the master host before you capture the image. After the image is deployed to one or several other machines it boots into Windows, fog-client service is started, host rename, reboot and domain join happen automatically (if everthing is setup correctly). To be clear, whatever method of booting you use (PXE or USB), the domain join/rename will still work.

That said I would still advise you to talk to your admin as many PXE systems can chainload from one to the other. I am not sure about PVS but it’s worth to take a look because it would make deployment of 500 PCs so much more convenient.

@londonfog You’ve probably seen my post in your other topic: https://forums.fogproject.org/post/143080

I managed to PXE boot it using NFS instead of the url=...iso option. So I have not played with the ISO option. See my post and give it a try using the NFS method.

Now bacl to the point of you saying that it does work with other machines but not with Dell Precision 5750 in UEFI mode. Do you have other machines that PXE boot in UEFI mode and loading this fine? I mean, is it just that Dell Precision 5750 causing the problem or potentially any UEFI mode machine?

@Jacques-Olivier What is TZ INFO (FOG Configuration -> FOG Settings -> General Settings) set to?

As well you might need to look into PHP-FPM timezone information. As we don’t know much about your setup yet (Linux OS and version) it’s hard to give further instructions. This command should help you find if there is a timezone set in PHP on your system or not:

find /etc/ -type f -exec grep "date.timezone" {} /dev/null \;

Make sure you adjust the value for and restart PHP-FPM service (not PHP cli or PHP apache module).

@sebastian-roth Because we are using VMs that are thin provisioned, Windows only optimizes, which we tried and the same result and behavior happened. Increasing the value of how much space to use https://forums.fogproject.org/topic/15416/out-of-disk-space-fog-capture-error/7#, did fix our issue and we only had to increase the value from 5 to 8 for a successful capture.

Thank you for your help!