Categories

  • 12k Topics
    114k Posts
    V

    I originally posted here and hoping for more feedback.

    I am imaging a Dell laptop (Windows 11) using FOG. The laptop has two identical hard drives identified by FOG as /dev/nvme0n1 and /dev/nvme1n1

    I imaged one of the drives a couple times, first using GParted to delete any existing partitions on any of the drives (not formatting). I recall one time after imaging Windows logged in after OOBE (the image was syspreped) and after restarting I got a Windows Inaccessible Boot Device Error. I had options to go into Windows recovery modes. I recall subsequent imaging and restart went ok.

    At one point I decided to try imaging the other drive (again deleting any existing partitions first). After FOG finished its imaging and Windows started its setup, the computer started up Dell Diagnostics automatically (which happens on this laptop when both drives have their partitions erased). Subsequent imaging resulted in the imaging completing and Windows logging in as before though after restarting the Inaccessible Boot Device Error occured. I tried deleting the Windows Boot Manager entry in the firmware between reimaging however this did not resolve the issue.

    I don’t see any option in the firmware to disable a drive. I physically removed the second drive and it imaged fine, about 4-5 reimages, and restarting Windows caused no issues.

    Is this a UEFI/NVRAM issue or something else? Would there be anything I could try instead of having to remove one of the drives?

  • 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
    L

    Hello,

    We are preparing a lab with 44 MacBooks (Apple M4, 16 GB RAM).

    Currently, we have not implemented any imaging solution yet. At the moment, we only use our Samba Active Directory domain for user authentication (LDAP/Kerberos) on the Macs.

    All machines have the exact same hardware configuration, and we need a way to create a standardized macOS image and replicate it across all devices. This deployment process is performed once every semester, so we are looking for a reliable and repeatable solution.

    We are evaluating the FOG Project as a possible solution, but we are unsure whether it supports cloning and deploying macOS images on Apple Silicon devices (M4).

    We would like to ask:

    Is FOG suitable for capturing and deploying macOS images on Apple Silicon Macs?
    How does the cloning process for macOS work in this scenario?
    If FOG is not recommended, what tools or best practices would you suggest for mass macOS deployment and domain integration with Samba AD?

    Thank you for your guidance.

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

    @Tom-Elliott Thanks for the clarification! I’ll try upgrading to the latest stable version, I was planning on doing this anyway.

    I’ll look into the Persistent Groups plugin and see how it works!

104

Online

12.7k

Users

17.6k

Topics

156.5k

Posts