That is correct, also I verified the “default exit mode” and it is set to REFIND_EFI. Would a Windows, bios or driver update have this affect?

Internet access is behind a proxy. I downloaded the latest Fog via git.

BIOS updated to v1.35 (Latest) Kernal 4.19.64 still does not work. Custom Kernal still does not work

I might be wrong, but when testing FOG configurations myself, I noticed that using dynamic VHD, and LVM FOG did not want to work. After thorough investigation, I noticed the disks were attempting to grow, but just creating unused space, without expanding the partition itself. I ended up booting into Parted Magic to get a graphic representation of the Disks, and finished expanding them manually. (For some reason, it did not display unused space in Ubuntu Server 18.04 for me) If the @george1421 's solution does not work, I would Live boot a Linux Distro with a GUI and investigate the partition layout using the Disk Management tool (Forgot what its really called).

@Lee-Rowlett said in Access Control Plugin: removehosteditgen.hook.php Lee, I searched everywhere for that file and cannot find it.

@george1421 Ok, good thing is we got a programmer in our team that can php. I’ll talk with him about that and maybe we can contribute it too.

@Sebastian-Roth hi. the password is correct, it is the same one with which I opened the ftp with a client (filezilla)

@george1421 I had time to spin up two new fog servers in my test area, one for imaging and one for client interaction. The client interaction one is set to connect to the DB of the imaging one. I also imported the certs from my production machine to both. Unfortunately I ran out of time before I could actually test anything. Holding pattern until Monday I suppose.

@Testers Anyone able to replicate this?

@george1421 said in Capture problem: I have noticed an uptick in people reporting this invalid storage group. Aß mentioned in my last post it’s not the same error message everytime. A couple of times we hat the “Invalid Storage Node” but this one is not.

@jtappen From what you wrote it seems like you are on the right track with this - Active Directory Defaults in the FOG settings should be the was to go. So which way do you actually register your clients? Our Fog is on versoin 1.5.6 This is not the latest version. I cannot say for sure we have found und fixed in the latest but if we find this to be a bug I need you to update to the very latest version.

@ibivibiv Ok I was correct! I think maybe there is a more clever way to update the grub directory contents (grub update command etc.) but basically if I do the following I find myself with a fairly close to working system: dd the MBR file to /dev/sda sfdisk the partitions to /dev/sda partclone restore d1p1.img to /dev/sda1 Take the grub contents from the original machine and overwrite them onto sda1 partclone restore d1p6.img to /dev/sda6 mkswap to /dev/sda5 with the uuid from the orig uuid file This drops me into the grub menu and after the timeout it boots as normal. Not too bad, and hopefully it helps anybody else that asks this question. I saw it gets brought up sometimes.

@Brad-Schumann From what you wrote so far I am fairly sure this is a different issue than we had before. Please open a new topic and post more details on when this is exactly happening. When there is a task scheduled or if you try to register the host or what?

@Fernando-Gietz Possible bug in the location plugin. What do you think?

@chris-lynn said in New latitude E7400. No internal NIC, Boot to USB-C Puck NIC. Gets IP from DHCP but does not connect to Fog.: We have since updated our FOG DHCP boot file to ipxe.efi FWIW: If the fog server IS your dhcp server for imaging and you had FOG install and configure the dhcp server, it should automatically manage the right boot file based on the pxe booting computer. You should not have to change anything. If you have a MS Windows dhcp server then there are somethings you can do to make it dynamic.

@astrugatch The link is in my signature. Testing is suspended by request of @Sebastian-Roth until the 20th of this month. The last test results can be seen on the site.

@darkxeno In the dell firmware switch the disk controller from Raid-on to AHCI mode. Unless you have more than one disk connected in a raid configuration raid-on mode doesn’t help you. There is a document issues between linux and intel controllers in raid-on mode. Once you have imaged with fog you can switch back to raid-on mode or leave it in ahci mode. It doesn’t matter to windows.

@Middle Unfortunately, aside from the latency kernel argument there isn’t anything else we can do from our side as far as I’m aware. Unfortunately manufacturers don’t always check how their stuff works on linux…

@Celena said in I have a problems! I need your help: he computer reboots before Windows has a chance to set up completely. This is probably because you didn’t follow the guidance on the wiki about disabling the fog service on your reference image and then enabling it in your setupcomplete.cmd batch file. https://wiki.fogproject.org/wiki/index.php/FOG_Client#FOG_Client_with_Sysprep (but that’s just a guess)