Posts made by fogmania

@sebastian-roth

I had the same issue with the slow Erasing current MBR/GPT table. I followed @Tom-Elliott advise of downgrading the kernel to 4.15.2 and now it is working without issues.

@wayne-workman

I re created the accounts and now they are working for quick deployment.

But the image history still shows that the user that is logged in is the one that made all imagings. Any idea?

Thanks Wayne,

Updated to Fog 1.5.4
Still can’t do quick image. Another thing I found since creating additional users is that it does not show it properly in image history.

If I login with my username, image history says that only I did all the imaging of this host. If I user another account, going to same host, image history says that he did all imaging of the same host…

The idea of adding users was to have more control over who imaged what computer.

I’m using a storage node that is working well but it has not been updated to the last version. Should I do this too?

Hi guys, I’m using Fog 1.5.0 here and everything is working well.
As of yesterday I had only 1 user used to login to the web management and to make quick images. I decided to create 2 more users from web management and now I can’t do quick images with none of them. To image computers I have to login into web management and create a basic task for each one of them.

Any insights?

@george1421

Found the culprit!!!
One laptop was contacting one of the DHCP servers and and the other was contacting the other one.

It was an issue related to server replication, now everything is working at the moment.

Tanks again George, I really appreciate your help.

@george1421

I have rechecked everything and it looks good to me. I’m also having 2 different responses from 2 identical computers. I checked in wireshark and everything looks the same except that one of the computers gets undionly.kpxe and the other gets ipxe.efi.

IP’s are on same subnet, DHCP server is responding and fog server too. I deleted all policies and filters and created only the filter and policy for the 00007 NIC. Still one gets UEFI, the other does not.

I checked and safe mode is disabled in both laptops. UEFI is enabled in both laptops. Both laptops have the same Architecture according to Wireshark.

I thank you George for your efforts anyway, keep up your good job, it is invaluable to me and this community.

@george1421 Thanks George,

I had a look at it as you said and I’m getting an offer from the DHCP server with an IP address on the same subnet. The next server IP address is the FOG server but I don’t know why the boot file name is still undionly.kpxe.

With the other identical laptop I’m getting the same results but that other laptop is getting the ipxe.efi, I’m scratching my head a lot as to why this would be happening with two identical laptops.

I’m going to have a look at it again closely today and get back to you. I hope it is not too much bothering from my part.

@george1421

Here are the results:

Acording to the documentation, I need to use ipxe7156.efi but I don’t have it in the tftpboot folder.

This is how I have the DHCP scope policy now: I created a policy for each architecture just in case:

@george1421

Thanks George,

I did create a policy for each definition. Funnily, One of the X1 Yoga is now booting to UEFI having this config. The other one is still getting the NBP file message.

Why could this be happening? They are connected to the same switch, the Lenovo X240 is also getting the NBP file message.

Option 66 is currently with my Fog Server’s IP.
I feel I’m getting there but I’m stuck at the moment, I’m no expert in Fog.

@george1421

Here is the screenshot with the scope options for the subnet mentioned:

@tom-elliott Thanks for your reply.

I did make the change and it worked. thanks for that.

Thing is that I want to be able to use both boot files in my environment as we still have some legacy computers at the school.

I tried the steps from the website mentioned before about coexistence of BIOS and UEFI but it didn’t work, undionly.kpxe is still coming up as the bootfile as per the screenshot.

@george1421

Thanks for your reply. The PC and the DHCP are not in the same subnet. Here you have the screenshot:

As I said, it is working well for BIOS but not for UEFI. I’m not an expert in this I have to say, I’m just trying to understand and figure things out.

Hi guys,

I hope I’m not late to the party. We got new machines here at the school and I have decided to install the latest version of FOG to make it work with UEFI. The old version still works but with BIOS only.

The new fog server is working well in BIOS mode with the new laptops but not in UEFI mode.

I followed the steps from here https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy but it doesn’t work.

I also tried changing the default boot from BIOS to UEFI in the DHCP server to see whether the laptops could boot with no success. Secure boot has been disabled on the laptops.

I’m wondering if I have to add something to the .fogsettings file? I only see undionly.kpxe as the bootfilename.

Our DHCP server is a Windows Server 2012 R2.

I also tried with an old Lenovo X240 with no success.