Windows 7 Deployment FOG- SAD2 Driver tool
-
thank you, your guide is truly awesome!!
-
Andyroo54 would you be kind enough to go back to the original post in the thread and add the DP_Install_Tool.txt to the first entry? This will keep the thread uniform and simple to manage.
Also… if you could please upload an example of your .xml answer file for the community. Just a thought
p.s. i’m working on a tutorial for XP as well for all those legacy users holding out
–ssx–
-
Hi all ive recently looked into this guide and use the dpinstall and sad tool, now for me the drivers get uncompressed with no problem at all, the issue i get is the drivers dont actually get installed in device manager, i have to click through to install each device driver any body got a trick to get this to work??
-
[quote=“Darren George, post: 2711, member: 375”]Hi all ive recently looked into this guide and use the dpinstall and sad tool, now for me the drivers get uncompressed with no problem at all, the issue i get is the drivers dont actually get installed in device manager, i have to click through to install each device driver any body got a trick to get this to work??[/quote]
Hi Darren,I’d suggest testing the DPinstall tool on a PC that’s just been loaded with win 7 fresh, and running it manually. Get the version I specify in the guide I think it’s 1.111118, and run it. I’ve never had the problem where the drivers won’t install, so perhaps its a policy setting you’ve changed or something else, hence why you should try it on a totally fresh install of win 7.
-
hey there guys, great guide but i have a problem with trying to boot into pxe, i get anerror stating that it cant read the hard drive size. it tells me to unmount the hard drive 1st. not sure what this means
PLEASE help
-
This post is deleted! -
This post is deleted! -
[quote=“iphunt3r1, post: 2862, member: 932”]hey there guys, great guide but i have a problem with trying to boot into pxe, i get anerror stating that it cant read the hard drive size. it tells me to unmount the hard drive 1st. not sure what this means
PLEASE help[/quote]
Make sure you set your virtual machines’s HDD to IDE and not SCSI, for some reason FOG won’t pick up SCSI. Other than that, you might have more luck starting a thread in the help section. -
Is it possible to use VMPlayer instead of workstation for this? Thanks in advance!
-
I don’t believe so. Player only plays existing VM’s, you need to build one from scratch.
Look into Virtual Box as a free alternative - [url]https://www.virtualbox.org/[/url]
-
this is what I did;
I created a RunOnce registry input which will call the DP_install the first time that windows boots.
Example: DrvIns.reg
C:\Drivers\SAD2-111118\DP_Install_Tool.i have uploaded the file, please remember to rename it to drvins.reg
thx[url=“/_imported_xf_attachments/0/102_Drvins.TXT?:”]Drvins.TXT[/url]
-
This post is deleted! -
I wish I’d found this guide about a week ago. Thanks to Andyroo54 for the hard work to get it together and the willingness to share it.
I’ve done essentially the same thing, but without the DP_Install_Tool. I do have a fundamental question on the efficacy of the process. I apologize in advance if I’ve misunderstood any of what’s been documented here. Just point out my error. So here’s what I think I understand:
[LIST=1]
[]This whole process is an attempt to make an image that will work on a wide array of hardware platforms?
[]OS is installed
[]drivers are copied to a drivers dir on the machine prior to imaging (driver packs).
[]system is sysprep’d
[]System is uploaded
[]image is sent to some other PC, boots, sysprep runs, reboots, etc
[*]of the first logon on the new machine, DP_Install_Tool runs, with your defined alterations and drivers are installed, unused stuff is deleted.
[/LIST]
If all of the above is true, how does the OS boot the first time if the image knows nothing about critical chipset or mass storage drivers that are normally required to boot the OS? DP_Install_Tool runs after the first boot. It seems like a chicken and egg issue. How can the OS boot in the first place.
I’m sure I’ve got something wrong. If I don’t, the result would be the same as sysprep’ing XP without [OEMMassStorage] and all the effort that required to extract PnP IDs. In this scenario, a freshly imaged PC would deploy correctly, all drivers would load for new NICs, sound cards, graphics cards, etc., if and only if the chipset (almost all were) and the disk subsystem were supported by whatever was on the original MS OS CD (often a problem).
The process I’ve just started to use I believe solves this problem by “injecting” drivers into the image using DISM from a Winbuilder or WinPE boot CD. This is done between steps 4 and 5 above - post sysprep, pre-upload. The step uses the same driver packs, but extracted to a second ISO or run from a network share. Getting DISM to work correctly in a Winbuilder CD was the tough part. This step seems to require the OS drive not be in use.
If the guide give us a process that works for all devices, including mass storage, I’d rather us it than the one I’m using since it adds a different type of support cd and make the process a little more difficult. I’m just getting started on this, so the right direction really matters
Please advise.
Jim Graczyk -
[quote=“Jim Graczyk, post: 3147, member: 931”]I wish I’d found this guide about a week ago. Thanks to Andyroo54 for the hard work to get it together and the willingness to share it.
I’ve done essentially the same thing, but without the DP_Install_Tool. I do have a fundamental question on the efficacy of the process. I apologize in advance if I’ve misunderstood any of what’s been documented here. Just point out my error. So here’s what I think I understand:
[LIST=1]
[]This whole process is an attempt to make an image that will work on a wide array of hardware platforms?
[]OS is installed
[]drivers are copied to a drivers dir on the machine prior to imaging (driver packs).
[]system is sysprep’d
[]System is uploaded
[]image is sent to some other PC, boots, sysprep runs, reboots, etc
[*]of the first logon on the new machine, DP_Install_Tool runs, with your defined alterations and drivers are installed, unused stuff is deleted.
[/LIST]
If all of the above is true, how does the OS boot the first time if the image knows nothing about critical chipset or mass storage drivers that are normally required to boot the OS? DP_Install_Tool runs after the first boot. It seems like a chicken and egg issue. How can the OS boot in the first place.[/quote]It can boot because Windows starts in OOBE, which is the process when you are installing windows 7 manually, for example, once windows is copied it says “Windows will now restart and installation will continue”. Windows then starts again, it scans the hardware and “installs devices” then “starting services”.
With the process I’ve outlined, the image is copied to the C drive of the new PC, and then windows starts in OOBE mode which is what I just outlined above.
You don’t need driver packs, windows 7 will install basically all essential drivers for pretty much an PC living or dead. I use driver packs after install, because occasionally windows 7 may not install a mass storage, or a wifi driver for example. Using driver packs after the OS is installed solves that problem.
I hope that clears that up, but remember, there is no right way to do it with FOG, this is just a guide that I made, based on one way that does work.
-
Thanks for the clarification. I guess I’ll just have to get over my distrust that MS would actually correctly deal with all hardware platforms. This has never been the case and I’ve been doing this for 20 years, so it’s quite a leap for me. I like your solution since it leaves the drivers in the packs, making the image smaller. For mine process, I have to expand them.
Jim
-
I have followed this through step by step on a virtual machine. I have made the image and captured the image in fog. I then setup a different VM and registered it in FOG. I deployed the image to the new machine. When the machine boots after the image is copied I get a Windows Boot Manager error.
[QUOTE]Windows failed to start. A recent hardware or software change might be the cause. To fix the problem
- Insert your windows installation disc a restart your computer.
- Choose your language settings and then click “Next”.
- CLick “Repair your computer”.
If you do not have the disc, contact your system administrator or computer manufacturer for assistance
File: \Windows\systme32\winload.exe
Status: 0xc000000e
Info: The selected entry could not be loaded because the application is missing or corrupt[/QUOTE]
Any ideas where to start?
-
[quote=“Kendall Eley, post: 3916, member: 1270”]I have followed this through step by step on a virtual machine. I have made the image and captured the image in fog. I then setup a different VM and registered it in FOG. I deployed the image to the new machine. When the machine boots after the image is copied I get a Windows Boot Manager error.
Any ideas where to start?[/quote]
your virtual machine hard drives are set to IDE?
-
[quote=“falko, post: 3945, member: 48”]your virtual machine hard drives are set to IDE?[/quote]
They were not. I added an IdE Hard Disk and choose the existing disk attached to this machine. I then deleted the existing disk under the sata controller. I restarted and got the same error. SHould I reimage or do I have to change the disk on the original VM that I created the image from and recreate the image? -
Change disk on original one, mine is set to ide. I’m using virtualbox
-
Thanks. I will do that. After I change the type to IDE, will I need to rebuild the whole machine?
