@plegrand UEFI implementations can be a real pain. It’s meant to be Kind of universal but everyone is just doing his/her own thing. So some UEFI clients work great while others just don’t want to play nicely. There is not much we can do about it. Well, you can try using rEFInd and start playing with the config file. If you are lucky it’s justa matter of finding the right options.

@mparlette said in Date off in dashboard #253 - Github: CentOS 7 w/ FOG 1.5.4 /etc/php.ini date.timezone entry was commented out. corrected with: date.timezone =“America/Vancouver” Technically that may not help you. In a normal world it would. But in FOG’s case its using php-fpm which has its own opinion of things and if you have php 7.x installed then the /etc/php.ini file is typically not referenced since php 7 has this file in a different path. But having the OS and fog menus in agreement should get you to where you want to be. So good job!!

@george1421 Here is a post and a thread (with developer supplied code) that will hot patch the registration file. This thread was actually someone wanting to create a custom registration process. https://forums.fogproject.org/topic/9754/custom-full-host-registration-for-1-3-4/45

@mparlette @george1421 Thanks. I’m not sure what the issue was, but I believe it to have been network related. I didn’t realize it initially when I posted but the pings I was doing, showed dropped packets galore (even while some were successful). I’m working my way through the install guide after creating a new VM, and so far it’s looking alright. No packet loss on an initial test ping. We’ll see what happens when I start the FOG installer! EDIT: SUCCESS!

@vascomorais Do you have a good link for this ISO?

@tom-elliott DEXTER is the storage group i created. Well after looking in the storage group it was not added in the storage group field, after adding it their it appears to be gathering. I appreciate and thank you sir. I’m sure i will have more coming soon :)

I tired options ‘Windows 10’ as well as ‘other’. None of them worked. I even tired DD method for cloning it showed the same errors.

@varun-r Please provide: A screenshot or well-focused photograph of the error. FOG Version FOG OS Information about your DHCP setup - like what OS is doing it, any current special settings, etc. Model of the hardware you’re trying to capture/deploy. Have you had FOG working in any capacity prior to this?

@pa_fog_man I think we have a bit of confusion here (and the 390 is not helping with clarification). First let me say that the Dell’s will let you dynamically boot in the other mode without changing the firmware (where it gets its default value). You can do this dynamic switching from the F12 boot menu. The other issue with the 390s (I can’t speak for personal experience with the 390s, but we have 790s in our fleet) the 790s were the first generation to support UEFI mode. But as far as I know, the 790s don’t support pxe booting in uefi mode. The 7010s was the first generation to support pxe booting in uefi mode. To pxe boot on the 7010s you would have to enable the uefi network stack on the network adapter settings in the bios. Otherwise you would not get ipv4 and ipv6 entries under uefi on the F12 boot menu. Back on point. You MUST select the proper boot kernel for the target system bios mode (legacy/bios or UEFI). If you sent the wrong boot file to the system you will not see the FOG iPXE boot menu. for bios mode you can use ipxe.pxe or undionly.kpxe for uefi mode you can use ipxe.efi or snponly.efi The bold text above are the typical kernels to set for dhcp option 67. You can not mix the boot kernels. This isn’t a FOG issue, but rather a firmware one.

Couple of things to check: Is the original machine in BIOS or UEFI mode? Is the target machine in BIOS or UEFI mode? If both are in UEFI mode, you may have to manually add the boot option in the UEFI of the target machine.

@p4cm4n also, tried cmd and batch from sfx archives, specifically 7zip sfx maker which threw an error trying to run on my own machine and winrar sfx maker. Rar is crappier compression but oh well. One of those worked can’t remember which…but things like wifi configs using it didnt.

@victorsantiago Sorry if I seem ignorant but I just don’t get what you are trying to do. What is/are project installers? You seem to have played with FOG a fair bit and also adjusted code to suit your need. Please tell us more about it and I am sure we can help you. Post your custom code (which worked in 1.4.4) for example.

Not necessarily the same problem, but I had to work around a certificate error by adding this to my setupcomplete.cmd file that is run after Windows Installs: certutil -delstore "Root" "FOG Server CA" certutil -delstore "Root" "FOG Project" certutil -addstore "Root" "%windir%\System32\Sysprep\fog.ca.cer" certutil -addstore "Root" "%windir%\System32\Sysprep\ca.cert.der" And of course add the certificate files to the folder referenced above.

well, what i needed was the french keyboard for the registration/capture/deploy. I followed Quazz advice (General settings / keymap : azerty) and all is good now ! thanks :)

@reese I am having the same issue. How did you safely downgrade back to 1.4.4. I had no issues there but can’t image an entire lab anymore. Just locks up. Hints on the downgrade process would be appreciated!

@jmg74 said in dell optiplex 3050 avec windows 10 UEFI: @verdierr : have you tried different options in your host config in Fog website, about “Host Bios/EFI Exit Type” ? [FR : As-tu tenté différentes options, pour ton hôte (via le site web de FOG), concernant “Host Bios/EFI Exit Type” ?] we tried every possible combination but none worked. for option 60, we have legacy computers and to try the uefi, we saw on the web that you have to activate option 60?

Has there been any progress with this issue. I am having the issue where the “_” flashes but goes no further and I have been searching for a solution for the past 3 days. In my case, I am attempting to boot a WinPE Environment to run a 3rd party application. I tried both clean boot.wim files from Win7 and Win10, both fail. But when booted from a USB Drive or CD the application boots. Everything worked perfectly when I was running 1.5.0 but no longer in 1.5.4. Dell PowerEdge 910 Windows Server 2016 DHCP ** Option 66 - IP of CentOS 7 Server Running Fog ** Option 67 - undionly.kpxe DNS Hyper-V ** CentOS 7 ** Fog 1.5.4 ** 16 Cores ** 128GB Ram It will sit here forever.

One other possible solution is Veeam Backup Agent (free). This will do a full system backup with bare metal restore. You can back up to a NAS, Veeam B&R Server ($$), or other network storage device. If you have a system failure, you boot from the linux boot cdrom, connect to your storage device and then restore your system. This is one way to protect your fog server. There may be native (Ubuntu) options like Bacula too.

there isn’t anything there yet: anthony@fogserver2:/opt$ ls 1.5.4.tar.gz fogproject-1.5.4