Categories

  • 12.3k
    Topics
    113.4k
    Posts

    A

    Hello,
    I’m having a problem with the Windows 11 24H2 deployment. I got a blue screen after deploying the image. I tried it on several models but without success. I realized it was related to Bitlocker. I tried this trick: After the Sysprep, I added these three lines to the WINDIR%\Setup\Scripts\SetupComplete.cmd script:

    bcdedit -set {current} osdevice partition=C:
    bcdedit -set {current} device partition=C:
    bcdedit -set {memdiag} device partition=\Device\HarddiskVolume1

    This works for the master computer, but as soon as I deploy the image with this modification, the blue screen returns.

    Do you have a solution that works?

  • Get the latest news on what's happening.
    Security Advisories
    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.
    General Tutorials
    2.4k
    Topics
    18.5k
    Posts

    B

    @george1421 Just seeing if anyone else has had issues.

    Haven’t purchased the new models yet.

    Was hoping to confirm they’re compatible with FOG first, so thought I’d reach out and ask around.

    Thank you!

  • Report bugs, request features, or get the latest progress.
    General Feature Request Bug Reports
    2.3k
    Topics
    20.9k
    Posts

    rogalskijR

    Requesting a feature addition in the “FOG Settings > FOG Email Settings” section that would allow an admin to test whether or not email is working. This would be similar to other programs that have a “test email” button with a box of who to send the test email to.

    Or perhaps some built in logic to test if postfix or other email prereqs that FOG needs to send email post image deployment.

246

Online

12.1k

Users

17.3k

Topics

155.3k

Posts