Subcategories

  • Technical help directly related to FOG.
    9k Topics
    86k Posts
    L

    @Tom-Elliott

    Thanks Tom, I tested #2122 and it does what you described.

    I applied the two src files of the PR by hand on top of the patches channel (schema 465, agent 0.1.28) and reproduced the same situation with test-bios. First Deploy (16928): the agent asked for the directory join and the plan went to awaiting_reboot (attempt 12f448e3…, trigger_task_id 16928). Before it rebooted I powered the VM off and queued a second Deploy (16929), which completed normally. The agent enrolled by itself after that (rebind, approved via deploy).

    For a while the old plan was still in hdRejoinState, still awaiting_reboot with trigger 16928, so right after queuing the Deploy nothing had changed. Once the machine booted the new Windows and the agent checked in, FOG replaced it on its own. A minute later there was a new attempt (3e64f53…, trigger 16929, awaiting_reboot). I didn’t touch “Clear directory operation review” or edit anything in the database. After one reboot the host was verified, hdJoined=1, hdKind=ad, secure_channel: healthy.

    So the old attempt is dropped after the new Deploy and the first boot, not at the moment the Deploy is created, which matches what you wrote. It only looks odd if you check the host in between and still see the old plan. No problem on my side, just mentioning it in case anyone else notices the same thing.

    One idea, only if you think it’s worth it: a checkbox in the Deploy task form, something like “discard every pending task of this host”, unchecked by default. The automatic rules are safer for the normal case, but sometimes the admin knows everything left over from the previous install is dead (queued tasks, snapins, a pending directory join) and wants to force a clean start right when the Deploy is queued, without waiting for the first boot and without the “Clear directory operation review” box. In our case, when a machine misbehaves it often keeps snapin tasks queued, and today you have to open the host, work out which tasks it has and delete them one by one. In a big fleet that is slow and easy to get wrong, whereas one box on the Deploy would clean the slate in a single step.

    I’ll drop my manual patch when #2122 reaches patches.

  • Problems with specific computer models.
    713 Topics
    8k Posts
    R

    @Tom-Elliott

    Thanks so much for your help with this. Happy to feed back any info I can so please do let me know if there’s anything else you need me to test. Will be on annual leave for a couple of weeks after this and have no access to the systems but I think this confirms your suspicion. Please see results below from a Dell OptiPlex 3070:

    Addresses on this machine:

    NIC: 01:00.0 (Realtek RTL8168h)
    Root port: 00:1c.0

    UEFI mode:

    setpci -s 01:00.0 CAP_EXP+10.w = 0142 (last digit 2 = L1 enabled)
    setpci -s 00:1c.0 CAP_EXP+10.w = 0c42 (last digit 2 = L1 enabled)

    Legacy/CSM mode:

    setpci -s 01:00.0 CAP_EXP+10.w = 0040 (last digit 0 = ASPM off)
    setpci -s 00:1c.0 CAP_EXP+10.w = 0c40 (last digit 0 = ASPM off)

    Dell’s UEFI firmware enables L1 on both the NIC and root port. The Legacy/CSM path leaves both off. The only difference between the two readings is those two ASPM bits. Everything else in the register is identical.

    Thanks for the nudge to run these. Anything else needs testing please do let me know. We love using FOG and it’s invaluable in our set of schools that we work in at least so please do keep up the great work!

  • Technical help related to a Windows Problem.
    1k Topics
    8k Posts
    Tom ElliottT

    Glad you have a workaround. I think the cause is the Windows boot manager certificate change, not the image.

    Your golden Optiplex installed Windows with Secure Boot on. Windows servicing then added the “Windows UEFI CA 2023” certificate to that machine’s db, and switched the boot files to a boot manager signed with it. The other Optiplex 3000s only trust the 2011 Microsoft certificates, so they reject that boot manager. bcdboot works because it copies the older 2011-signed boot manager.

    Can you confirm with two checks, in admin PowerShell, on the golden machine and on one target?

    [Text.Encoding]::ASCII.GetString((Get-SecureBootUEFI db).bytes) -match 'Windows UEFI CA 2023' mountvol S: /s (Get-AuthenticodeSignature S:\EFI\Microsoft\Boot\bootmgfw.efi).SignerCertificate.Issuer

    If the golden machine says True and the target says False, that is the cause. A newer Dell BIOS may include the 2023 certificate in its default keys. I am also looking at having FOS add it during the Secure Boot enrollment task.

  • Technical help related to a Linux Problem.

    730 Topics
    6k Posts
    Mr_____TM

    @JasonNaughton

    Hi, I noticed that this was unresolved after so long. Wonder if you have solved it?
    I recently stumbled across the man page for dhcpcd.conf. In there is a denyinterfaces (pattern) should solve the issue for you. It tells dhcpd to ignore the nic interfaces listed in pattern. Just was wondering if you found the fix otherwise hope this helps.

  • Technical help related to a Mac Problem.

    81 Topics
    943 Posts
    Bristow 0B

    Hello everyone,

    As I work at a secondary school, I was able to get hold of some Catalina iMacs (iMac 14.3).
    I already use FOG to deploy Windows and Linux images on PCs.

    I would like to deploy a LinuxMint image on these iMacs.

    However, I am unable to boot into PXE on them with FOG, and I do not know what is wrong.

    I modified my DHCP server as follows:

    ## FOG class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.efi"; } class "UEFI-64-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008"; filename "ipxe.efi"; } class "UEFI-64-3" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009"; filename "ipxe.efi"; } class "Apple-Intel-Netboot" { match if substring (option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386"; option dhcp-parameter-request-list 1,3,17,43,60; if (option dhcp-message-type = 8) { option vendor-class-identifier "AAPLBSDPC"; if (substring(option vendor-encapsulated-options, 0, 3) = 01:01:01) { # BSDP List option vendor-encapsulated-options 01:01:01:04:02:80:00:07:04:81:00:05:2a:09:0D:81:00:05:2a:08:69:50:58:45:2d:46:4f:47; } elsif (substring(option vendor-encapsulated-options, 0, 3) = 01:01:02) { #BSDP Select option vendor-encapsulated-options 01:01:02:08:04:81:00:05:2a:82:0a:4e:65:74:42:6f:6f:74:30:30:31; # filename "i386-efi/ipxe.efi"; filename "snp.efi"; } } } class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } ### END FOG

    I tested ipxe.efi in 64-bit and 32-bit, as well as snp.efi, but it still doesn’t work. I get some kind of spinning planet when I try to boot.

    I admit I don’t fully understand the documentation page: https://wiki.fogproject.org/wiki/index.php/FOG_on_a_MAC

    Thanks in advance!

  • General Developer questions relating to FOG.
    691 Topics
    5k Posts
    Tom ElliottT

    @IgniWarlock Must’ve been a github issue that was temporary as I’m seein ghte page load just fine now.

    Thanks!

51

Online

12.8k

Users

17.7k

Topics

157.5k

Posts