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

Making a single, hardware-independent image

Scheduled Pinned Locked Moved
Windows Problems
4
12
4.0k
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.
  • M
    mcgonigiggle
    last edited by Sep 22, 2015, 6:50 PM

    What’s the best way to create one master image and be able to deploy it to different hardware sets? This is what I hope to be able to do:

    *Make one image
    *Add all software
    *Add drivers for Hardware Set B (Dell Inspiron 1545) to an image being created on Hardware Set A (Dell Latitude D630) (i.e., the EXE files to setup the drivers)
    *Have Windows 7 Pro x64 be able to find the appropriate drivers in the folders specified and install them with as little administrative overhead as possible.

    Any suggestions are highly appreciated. I’m not even sure when to begin with this and Google hasn’t been helpful.

    Thanks in advance!

    1 Reply Last reply Reply Quote 0
    • D
      d4rk3
      last edited by d4rk3 Sep 22, 2015, 1:15 PM Sep 22, 2015, 6:55 PM

      (This works on Vista/7/8/8.1/10 and Server 2008 R2/2012/2012 R2)

      All you need to do for drivers in images is this:

      1. Put all desired drivers in a folder. I use “C:\Drivers”.

      2. Run this in an elevated command prompt (if you want to use a different directory simply replace the bolded C:\Drivers with your driver directory):

      reg add “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion” /v “DevicePath” /t “REG_SZ” /d “%SystemRoot%\inf;C:\Drivers” /f

      1. Profit???
      1 Reply Last reply Reply Quote 0
      • M
        mcgonigiggle
        last edited by Sep 22, 2015, 6:58 PM

        Is it really that simple? Man I overthink things way too much! Thanks for the fast reply; I shall let you know how it goes!

        D 1 Reply Last reply Sep 22, 2015, 6:59 PM Reply Quote 0
        • D
          d4rk3 @mcgonigiggle
          last edited by Sep 22, 2015, 6:59 PM

          @mcgonigiggle It is really that simple 🙂 enjoy the many hours you’ll save with this trick ;D

          M 1 Reply Last reply Sep 22, 2015, 7:08 PM Reply Quote 1
          • D
            d4rk3
            last edited by d4rk3 Sep 22, 2015, 1:05 PM Sep 22, 2015, 7:04 PM

            I should mention that the Dell .exe driver packages will not work as-is. Make sure you extract them first.

            This is the driver folder structure I use for all of my images:

            AHCI
            Audio
            Chipset
            LAN
            Video
            WiFi

            W 1 Reply Last reply Sep 23, 2015, 3:51 PM Reply Quote 1
            • M
              mcgonigiggle @d4rk3
              last edited by Sep 22, 2015, 7:08 PM

              You are way too good to me. Where did you obtain all the drivers from?

              D 1 Reply Last reply Sep 22, 2015, 7:12 PM Reply Quote 0
              • D
                d4rk3 @mcgonigiggle
                last edited by d4rk3 Sep 22, 2015, 1:14 PM Sep 22, 2015, 7:12 PM

                @mcgonigiggle The manufacturer’s site, silly 😛

                If you’re only using those two Dell models just grab the drivers for both, extract them to your folder, run the reg add command and you’re done.

                1 Reply Last reply Reply Quote 1
                • M
                  mcgonigiggle
                  last edited by Sep 22, 2015, 7:18 PM

                  Well I figured that one, silly! 😛 I was hoping you had zipped files! XD

                  I wish your user name was “Ferris Bueller” so I could appropriately say, “Ferris Bueller, you’re my hero.”

                  D 1 Reply Last reply Sep 22, 2015, 9:10 PM Reply Quote 1
                  • S
                    sudburr
                    last edited by Sep 22, 2015, 9:04 PM

                    See: https://technet.microsoft.com/en-us/library/cc753716.aspx

                    Inclusion of a driver package in a folder referenced by the DevicePath registry entry does not remove any prompts created by the signature on the package. If the package is not signed, or signed by an unknown or untrusted publisher, then the user is still presented with dialog boxes to accept the publisher. Inclusion of the certificate used to sign the driver in the Trusted Publishers certificate store removes this additional prompt. For more information, see the documentation about signing device drivers on the Microsoft Web site

                    https://msdn.microsoft.com/en-us/library/windows/hardware/ff544865(v=vs.85).aspx
                    https://technet.microsoft.com/en-us/library/dd919238(v=ws.10).aspx

                    Unsigned drivers are one of my many banes.

                    [ Standing in between extinction in the cold and explosive radiating growth ]

                    1 Reply Last reply Reply Quote 0
                    • D
                      d4rk3 @mcgonigiggle
                      last edited by Sep 22, 2015, 9:10 PM

                      @mcgonigiggle I don’t have any right now, but I know a guy…

                      Just download 7zip and then right click any Dell driver .exe file and extract 🙂

                      1 Reply Last reply Reply Quote 0
                      • W
                        Wayne Workman @d4rk3
                        last edited by Sep 23, 2015, 3:51 PM

                        @d4rk3 said:

                        I should mention that the Dell .exe driver packages will not work as-is. Make sure you extract them first.

                        This is the driver folder structure I use for all of my images:

                        AHCI
                        Audio
                        Chipset
                        LAN
                        Video
                        WiFi

                        I do something similar already - but I have other folders too… like
                        Smartboard
                        NiNite
                        NAPS2
                        eStudio_Drivers
                        FOG
                        CannoScan
                        Insight

                        and so on.

                        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!
                        Daily Clean Installation Results:
                        https://fogtesting.fogproject.us/
                        FOG Reporting:
                        https://fog-external-reporting-results.fogproject.us/

                        D 1 Reply Last reply Sep 23, 2015, 5:06 PM Reply Quote 0
                        • D
                          d4rk3 @Wayne Workman
                          last edited by Sep 23, 2015, 5:06 PM

                          @Wayne-Workman Yep, the sky’s the limit as far as drivers go 🙂 Customize your little heart out lol…

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

                          193

                          Online

                          12.1k

                          Users

                          17.3k

                          Topics

                          155.3k

                          Posts
                          Copyright © 2012-2024 FOG Project