Windows 7 Deployment FOG- SAD2 Driver tool
-
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?
-
Yes start from scratch
-
I am using Oracle VM virtualbox Manger v 4.1.16 Everytime a create a new VM, it creates a sata drive. If I delete that one, change to a ide, then it will not boot. I get back to the same screen as before. How do I create a drive with a ide drive from the beginning? Am I missing something?
-
hmm, yeah it will always create a sata drive you just need to delete it and add and ide one, sounds like your doing it right,
-
[quote=“Kendall Eley, post: 3955, member: 1270”]Thanks. I will do that. After I change the type to IDE, will I need to rebuild the whole machine?[/quote]
It’s better just do rebuild the whole thing yes. It doesn’t take long since you have done it before. I have rebuilt mine three times.
-
I have built my image. I got all updates to the OS and installed Microsoft Office, Adober Reader, FLash, Java and a few others similare programs. (Note I had an error in my unattend file, so I recreated it after installing everything and then copied it over to the proper location) I then captured it to FOG. I then deployed it back to the VM. When it boots, I am asked to accept the license terms of Win 7 Pro Service Pack 1. If I accept, I am then prompted to choose how to deploy updates. I choose recommended settings. It then proceeds to finalizing settings (which is still running after 30 minutes) Any ideas on what I have done wrong?
-
[quote=“Kendall Eley, post: 4010, member: 1270”]I have built my image. I got all updates to the OS and installed Microsoft Office, Adober Reader, FLash, Java and a few others similare programs. (Note I had an error in my unattend file, so I recreated it after installing everything and then copied it over to the proper location) I then captured it to FOG. I then deployed it back to the VM. When it boots, I am asked to accept the license terms of Win 7 Pro Service Pack 1. If I accept, I am then prompted to choose how to deploy updates. I choose recommended settings. It then proceeds to finalizing settings (which is still running after 30 minutes) Any ideas on what I have done wrong?[/quote]
Are you sure you have copied the guide correctly? Have you run sysprep correctly? I’d suggest to strongly re read the instructions and try again with your xml file. Use snapshots, which will reduce your time. I know my guide is long and in some cases can be difficult to interpret due to language differences, but you will find that everyone does this differently so you may come across diff problems. I will try to upload my unattend xml tomorrow for you to try…
-
I have gotten my image to deploy to a virtual machine. When the DP_Install tool begins extracting, it stops and prompts me with a message box No files to Extract. I click ok and it begins extracting fine.
Also, how do I add drivers? I have an HP Elitebook 8560 with several devices that did not have drivers installed. I have the drivers downloaded from HP, but I am not sure how to inject them into the base image
-
[quote=“Kendall Eley, post: 4246, member: 1270”]I have gotten my image to deploy to a virtual machine. When the DP_Install tool begins extracting, it stops and prompts me with a message box No files to Extract. I click ok and it begins extracting fine.
Also, how do I add drivers? I have an HP Elitebook 8560 with several devices that did not have drivers installed. I have the drivers downloaded from HP, but I am not sure how to inject them into the base image[/quote]
re-read [B]STEP 8[/B] you need to download the driver packs and copy them to the necessary folder
-
Followed step 8 exactly. When the machine reboots, It has many unknown devices such as video card, NIc (both wired and wireless), Card reader, and others. I have since found those drivers. Is there a way to inject those drivers into the script in step 8?
-
what other drives are you missing i find that the driverpacks has them all for my setup. and then windows update will finish it off
-
I did not have the Network card driver for that machine, The wireless card, and several others. The network card is the most pressing, because obviously Windows can not access the internet without that.
