How to instal Drivers on source image
-
prince,
While I don’t mind assisting you, there are at least two, if not more, threads explaining how to do this, but both go in depth about sysprepping/generalizing the image. Why? Because if the OS isn’t generalized, is still going to think it has all the information of the original host. The drivers, even if loaded into the Windows Driver store, will not load up properly. Sysprepping and generalizing an image removes all host specific associations of drivers and on the first load out, windows re-detects all the new systems components and installs/uses the drivers that are required (if it has them.)
That all said, we’re not here to help you build your image, we’re here to make sure you are able to image. With that all said, we’ve already created quite a few posts in the tutorial thread to explain HOW to do what you’d like to do, though they do require sysprepping.
Is there a particular reason you’re against sysprepping?
-
This post is deleted! -
[INDENT]hi sir Thank you…
but no… I just dont want the UNATTENDED installation unattend.xml
but I want to sysprep generalize my sourceImage… sorry if I dont clear that on my first post…
I want to generalize/sysprep my SourceImage because Im deploying it to different machine hardwares
but I dont want to make it Unattended installation[/INDENT]
-
I already know how to sysprep my source image by reading some post and tutorials here…
but I cant find a good guide on how exactly Im supposed to prepare my SourceImage about the DRIVERS…how to properly install driverpacks on my sourcePC and my clonePCs will accept and happily use it.,so I dont have to install drivers manually on my clonedPCs
-
-
Thank you… I’ve done reading the 2nd link…
Ill try the first link…
=------
“1) Install the FOG service, navigate to:
[url]http://fogserver/fog/client/[/url]
And install the FOG client service. [BE SURE TO REPLACE YOUR “Hostnamechanger.dll” [COLOR=#ff0000][B]Where can I locate this hostnamechanger.dll? and what will I enter as replacement?[/B][/COLOR]
or your machine won’t rename and add to domain after imaging”. Replace this after FOG client is installed.- Download and Run “FOG Prep”- This is important for uploading windows 7 machines." [B][COLOR=#ff0000]Can I skip this if the machine is Windows8 and Xp? this apply only in windows 7?[/COLOR][/B]
-
Step one is needed for your own needs to update your FOGCrypt information and to gain some more capabilities. It’s not really necessary to do that step.
Step two is really only needed on older versions of FOG, from 0.29 I believe. FOGPrep is not really needed on any system anymore. That said, It’s already telling you that you would need to use it on Windows 7, so if you’re not using Windows 7, I think it kind of explains itself.
The relevant parts for you needs, if you’re already aware of how to sysprep your system, is really getting the driverpacks loaded and the SAD2 tools itself.
-
[quote=“Tom Elliott, post: 36379, member: 7271”]Step one is needed for your own needs to update your FOGCrypt information and to gain some more capabilities. It’s not really necessary to do that step.
[/quote] OK so I’ll just skip this one.[quote=“Tom Elliott, post: 36379, member: 7271”]S
Step two is really[B] only needed on older versions of FOG[/B], from 0.29 I believe. FOGPrep is [COLOR=#0000ff]not really needed on any system anymore.[/COLOR] That said, It’s already telling you that [COLOR=#ff0000]you would need to use it on Windows 7,[/COLOR] so if you’re not using Windows 7, I think it kind of explains itself.[/quote] Im just confused here sir… sorry…[B]only needed on older versions of FOG > [/B]Im using FOG 1.2.0
[COLOR=#808080]not really needed on any system anymore [/COLOR]
[COLOR=#ff0000]you would need to use it on Windows 7 >> [COLOR=#0000ff]I need to do the step 2 in Windows7 image even if im using a newer and latest FOG? just to clarify sir… Thanks again…[COLOR=#000000]yes I’ll check the [/COLOR][/COLOR][/COLOR][COLOR=#000000]SAD2 tools. Thanks[/COLOR]
-
You do not need to do step 2.
-
Thank you sir…
-
You can close this thread sir… please… Thanks
-
I downloaded the sad tool from this post [url]http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380/[/url]
then I follow the instructions…
I now have Drivers folder on C:\
I put my DriverPacks
my question is…
Do i have to RUN [B]DP_Install_Tool? [/B]or I just simply put my driverpacks on the corresponding folder (x86/x64) ?
Thanks again
-
Do i have to RUN [B]DP_Install_Tool? [/B]or I just simply put my driverpacks on the corresponding folder (x86/x64) ?
-
Do i have to RUN [B]DP_Install_Tool? [/B]or I just simply put my driverpacks on the corresponding folder (x86/x64) ?
Do i have to RUN [B]DP_Install_Tool before imaging, or RUN IT AFTER imaging on the destination/imaged PC/Host? [/B]
-
Be careful with pre-installing drivers. You can bloat the registry and break the image if you pre-install too many.
-
so the better way is… put the drivers on the folder, then clone/image it… then on run the SADtool on the cloned/destination host?
is that correct ?
-
A simple method is to create a folder in “c:\windows\inf” . I use “c:\windows\inf\xinf”.
Because Windows 7 recursively searches folders for drivers, and since Windows 7 searches “c:\windows\inf” by default, there is no configuration required other than to drop each extracted driver into its own folder inside “c:\windows\inf\xinf”.
Be aware, that some drivers are coded for both x86 and x64. Some will load x64 when x86 is required or vice versa, causing a failure of varying degree.
Some drivers for some versions of hardware will load the wrong version and brick the system. I’m looking at you Intel USB 3.0 eXtensible Host Controller (series 7 vs series 8).
I’ve dropped x86 and x64 drivers that play nice together into my xinf folder. I then use a vb script called from sysprep that detects specific needs for specific make/models that we have in service, that then performs installations and configurations, all the while using auto-logon.
Importantly, I disable and set to manual, the FOG Service before I close an image with sysprep. Reactivating the FOG service is the last thing my script does because the FOG Service will ungracefully interrupt any running scripts and force a restart when an image is deployed with naming and domain-joining enabled.
