@neiliob1973 “The best solution” depends on your situation. In a perfect world, you shut down other DHCP servers and let FOG handle it all and it will work out of the box basically.

However due to policies, preferences or certain restrictions sometimes you are stuck with another DHCP server, this is where dnsmasq comes in with proxy mode. (basically piggybacks the other DHCP server and sends only the PXE boot info)

I do think this may struggle or not work as expected if the original DHCP server is also sending PXE boot info, from what I remember anyway. And certain clients for some reason don’t like it very much either.

I think they just return the exitcode of whatever it is you’re trying to snapin.

@Tom-Elliott facepalms in Microsoft’s general direction

@aborn I am unsure if the FTP client would be able to move the images, but you can change the chmod comment using a postinit script.

It might work fine if you chown -R fog:fog first, though.

At any rate in /images/dev/postinitscripts/fog.postinit try adding the following:

sed -i -e "s#chmod -R 777#chmod -R 774#gi" /usr/share/fog/lib/funcs.sh

The permissions are set twice, once before imaging (so files can be put there) and once after imaging (in case the files are created with different permissions for some reason).

You’ll have to test which permissions actually work yourself.

I don’t really see the issue here. There is tons of products that only have a single update a year or fewer. People seem to expect FOG to pump out updates on a daily basis.

@Shadow00Caster Any news on this?

This is a known problem on Ubuntu (the database moving when changing to mariadb)

You will likely find your fog database in /var/lib/mysql-5.7

Currently, FOG does not try to move to mariadb on Ubuntu for this reason.

If possible, going back to mysql would be the best option I reckon.

@astrugatch Looks like there would be an edge case if you answered ‘no’ to php/apache reinstall during update where it would just carry on with the ‘packages’ line from .fogsettings and thus cause no problems.

https://wiki.fogproject.org/wiki/index.php?title=Multicasting#Kill_Multitasking

Although it would be interesting and useful to know why this is happening. Does anything show up in the Apache error log when you create multicast sessions perhaps?

Resize doesn’t work for Apple partitions, it’s not a “validResizeOS”

You have to use one of the unresizable image types.

Perhaps an idea for the devs is to simply hide the resizable option for OS it won’t work for anyway?

/dev/mapper are Logical Volumes, part of LVM.

It says it is currently using 1% of the 88GB

@TomBagley What’s the output of http://192.168.150.10/fog/service/ipxe/boot.php ?

As an aside, Linux kernel 5.3 has added native support for keyboard in these models.

@baessens I’m going to take a guess, but is the disk a “dynamic virtual disk” by any chance?

@george1421 OP is using a USB NIC since it doesn’t have one built-in. It also has a sort of keyboard dock which I’m guessing is what OP is talking about when he says it doesn’t respond.

@gutter Microsoft actually provides an executable that tries to convert MBR to GPT

https://www.tenforums.com/tutorials/81502-convert-windows-10-legacy-bios-uefi-without-data-loss.html

Your mileage may vary; I’ve used it only once (still works fine to this day), but I’m not sure it’s going to be exactly the same as a clean GPT install, that would still be your best bet imo.

In VBOX you can create an image in EFI, turn off the VM, switch off EFI, boot to PXE in legacy, capture the image and now you have an EFI image ready to go.

Key aspect to remember is that the mode PXE boots in is irrelevant to the image.

@alismayilov Can you give a couple of model names on which it’s failing?

Actually, thinking about this some more, I think I’ve seen this on virtual machines quite often during upload.

Try adding the following to FOG Configuration -> FOG Settings -> General settings -> FOG_KERNEL_ARGS

nolapic_timer

Reset encryption data for that host/group in the Web UI

@mclapper68 You need to install the correct rpm for your version. For your version it’s probably http://rpms.remirepo.net/fedora/remi-release-24.rpm

Fedora 24 wiki article

I’m not overly familiar with Fedora, but I think the complete error log might be more useful.

What happens if you do a simple dnf update -y ?

@Buzer1 I spot login failed.

https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP#Credentials_.2F_Passwords