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

    Add drivers problem

    Scheduled Pinned Locked Moved Unsolved
    Windows Problems
    3
    3
    866
    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.
    • C
      ciic
      last edited by

      Hi,

      Hello everyone,

      I come to you with the following problem.
      I created a custom image of W10 by performing regular snapshots before and after sysprep.
      But I can not properly add the drivers for the 4 different computers that the company has.
      I recovered the drivers via the dual driver software. I recovered the exact models of the computers.
      But I do not understand, some talk about a post fog script, others just add a few lines in the unattend.xml file.
      In the hypothesis where I add the few lines
      <settings pass = “offlineServicing”>
      <component name = “Microsoft-Windows-PnpCustomizationsNonWinPE” processorArchitecture = “amd64” publicKeyToken = “31bf3856ad364e35” language = “neutral” versionScope = “nonSxS” xmlns: wcm = "http://schemas.microsoft.com/WMIConfig/2002/ State “xmlns: xsi =” http://www.w3.org/2001/XMLSchema-instance ">
      <DriverPaths>
      <PathAndCredentials wcm: action = “add” wcm: keyValue = “1”>
      <Path> 😄 \ Drivers </ Path>
      </ PathAndCredentials>
      </ DriverPaths>
      </ Component>
      </ Settings>

      Reading:
      The structure should be built to match the variables used in the script fog.drivers.

      The structure should be built to match the variables used in the fog.drivers script.

      /images
      ├─/drivers
      ├─$machine
      ├─$osn
      └─$arch
      or translated into real values (note that the space has been removed for “Optiplex 7040” to this Optiplex7040. There is a clean up line above that removes spaces in the product name. While linux supports spaces in path names (like Windows) its bad practice to use them because some utilities will see the space as a parameter delimiter.

      /images
      ├─/drivers
      ├─Optiplex7040
      ├─win7
      └─x86
      └─x64
      ├─win10
      └─x64
      ├─Optiplex7050
      …

      Is there anything to do? I do not understand, it seems a little simplistic at first.

      Can you help me?

      george1421G 1 Reply Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @ciic
        last edited by

        @ciic Let me ask a basic question first. Are the proper drivers making it to the target computer? If yes then the entire fog server side is solved and working. Once we know IF the correct drivers are being copied to the target computer we can look at next steps.

        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
        • M
          mikmatcr
          last edited by

          Hello, I managed to do the insertion of drivers following the method mentioned by @george1421 , I followed the steps of this link: Using FOG Postinstall scripts for Windows Driver injection 2017 ed.

          I hope it works

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

          124

          Online

          12.1k

          Users

          17.3k

          Topics

          155.3k

          Posts
          Copyright © 2012-2024 FOG Project