• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Inject drivers via Fog

    Scheduled Pinned Locked Moved
    Tutorials
    2
    2
    77
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      diogo.seabra
      last edited by

      Hello All,

      I new user in FOG Project and i want inject drivers in my deployments.

      I following the link: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

      But I don’t understand where I should do this in this configuration:
      264895a9-84ac-41f1-9f4e-b606e749a2ad-image.png

      Can help-me with this step?

      Thanks Team

      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @diogo.seabra
        last edited by

        @diogo-seabra

        post taken from this thread: https://www.elevenforum.com/t/automated-windows-11-installation-with-post-installation-script.28219/

        "The normal sequence for Windows Post-Setup:

        • Exit specialize pass, and run OOBE​
        • Run C:\Windows\Setup\Scripts\SetupComplete.cmd, except when Windows finds an OEM license key and it’s skipped entirely​
        • Begin user provisioning for the first logon user​
        • Run RunOnce or Run registry tasks​

        SetupComplete.cmd would be ideal for you, it’s right after OOBE but before any user profiles are provisioned. But the problem is Windows deliberately skips SetupComplete when it detects an OEM setup."

        There are several ways to do the injection the most correct place is the setupcomplete.cmd file. But if you have an OEM licensed install that file is skipped.

        The other option is to add the driver injection (only one call to pnputil is really needed in my experience) is if/when you use the unattend.xml file. There is a first run section where you can call applications at first login, but you must couple that step with autoadminlogin function, so as soon as OOBE finishes autoadminlogin logs in the administrator account once to run the firstrun section of the unattend.xml file. This way is a bit more complicated to setup. If you can get the setupcomplete.cmd file to run its much easier of a setup

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        1 Reply Last reply Reply Quote 0
        • 1 / 1
        • First post
          Last post

        155

        Online

        12.2k

        Users

        17.3k

        Topics

        155.5k

        Posts
        Copyright © 2012-2024 FOG Project