Can you ensure that the timezone listed in the FOG settings is correct, as well as the timezone listed in the /etc/php.ini config file? Lastly ensure the linux clock on the FOG server is accurate.

@Dino_Nerd Were you able to complete the steps that Sebastian requested

@Dino_Nerd Can you access/download the picture (http://192.168.0.15/fog/service/ipxe/bg.png) or the kernel (http://192.168.0.15/fog/service/ipxe/bzImage) from your browser?

If you can then the web bits are in place and correct.

Just to be sure you did set selinux to permissive right?

In regards to #1 when you installed 1.4.3 you will have the latest kernel. There is no need to download again. That doesn’t address your issue, but know that you have the latest kernel.

I have to ask you, did you make any changes to the linux user called fog this is not the default web ui user account, this is the linux account. That account is an internal account used by the FOG application. I’ve seen people attempt to use/change the password on that linux account and use it for system administration. Doing so will break FOG.

As for your isc-dhcp config file, we really need to see it to identify what’s wrong. There is a great example of what the config file needs to be if you review this document (example 1) : https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

@msnyder If I understand Sebastian’s post correctly. The source size of the disk doesn’t matter much since FOG can shrink the disk image. The issue is fog can’t expand it because of the HFS format.

I can tell you before we switched to FOG 1.3.x, 1.2.0 didn’t expand disks (in windows) very well at all. What we would do is build our reference image on a 40GB VM and then capture and deploy that. That 40GB disk was smaller than any hardware that we would deploy to. Then in windows there is a batch file that gets run after windows setup completes call setupcomplete.cmd. Inside there we would run the diskpart commands to expand the deployed C: drive size to the entire size of the physical disk. This method worked well, but now it works much better that we don’t need to do that anymore.

You may have to do something similar for MacOS.

@msnyder said in Mac capture and deploy solutions:

MacOS partitions are not resizable << @Developers opinion please??

First let me say, we do have people who are successful deploying MacOS. I can also say I have no practice experience imaging Mac computers. You have got over the initial hump of being able to boot into the FOG menu. That is where most are getting hung up.

Are you saying that you captured the master image as single disk resizeable and its not resizing after deployment?

@msnyder You will need to capture the images again (or be sneeky and move the /images/dev/<mac_name> to /images/<image_name> as the <image_name> is exactly defined in the image configuration. mv /images/dev/<mac_name> /images/<image_name> The capture is complete it just needs to be parked in the right location.

@msnyder Make sure your permissions are set correctly for /images

They should be owned by user fog:root right or wrong the file permissions are 777

@FiSi said in Blank page on web interface:

Please tell me it is possible to do that with fog 1.4.3

After all of this, sorry its not possible…

Just kidding, yes Win10 is possible both in legacy (bois) mode and uefi modes. UEFI modes are a little problem but is more on the hardware side than win10. Many new win10 systems are not coming with ethernet ports built in, so this means you must use an approved usb ethernet adapter to make it work.

One last comment. It is possible to setup root with a password as long as the password in the .fogsettings file is the same exact as what you set root’s password to. If you change then you need to rerun the fog installer.

@FiSi What I was trying to find out is if

1. You changed the password for root
2. The /opt/fog/.fogsettings had the correct password to access the database.

The ALTER USER 'root'@'127.0.0.1' IDENTIFIED WITH mysql_native_password BY '' command from the developers post should have reset root’s password back to nothing. If you followed this then the root password should be nothing <blank>. The fogsettings file must be set correctly. If it is not or the .fogsettings file is not accurate to what is needed to login, please fix it so its correct and rerun the installer.