Categories

  • 13k Topics
    115k Posts
    A

    For anyone else struggling with this, I finally figured it out. FYI this is not a fog issue, it’s a Windows secureboot UEFI issue.

    Once I image a machine, I need to make sure secure boot is disabled, boot windows, and run these commands from an elevated command prompt:

    mountvol s: /s
    del s:*.* /f /s /q
    bcdboot %systemroot% /s S:

    That will rebuild the EFI partition files.

    I did this, rebooted to the bios, re-enabled secureboot, and Windows successfully booted. Hooray.

    My only issue now is that I can’t do unattended reimaging with secureboot enabled. If I push my golden image back to this system with secureboot enabled, Windows will fail to boot again until I make it rebuild the EFI partition files. What’s so weird to me is that I don’t have this problem on Wyse 5070 thin clients - I can leave secureboot enabled all day, reimage a system, and Windows boots just fine. But these Dell Optiplex 3000s sure don’t like it.

  • Get the latest news on what's happening.
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    2k Topics
    19k Posts
    Tom ElliottT

    @ahaeder No:

    The idea of fog client is to rename the host based on what you name the computer within FOG, not the other way around.

    If you want it to be a specific name, and you have the FOG Client installed, set the wanted name in the FOG UI, and the host will change automatically.

  • Report bugs, request features, or get the latest progress.
    2k Topics
    21k Posts
    Tom ElliottT

    @scottrayr I’m not able to replicate the issue you’re seeing.

62

Online

12.8k

Users

17.6k

Topics

157.1k

Posts