Windows 7 Deployment FOG- SAD2 Driver tool
-
After a few trial runs, here is what I did:
Modify the sysprep.inf file (with setupmgr.exe) so that:
1 - Completely Unattended = NO
2 - Additional commands = startup.cmd (Add this command, this will create a CMDLINES.TXT file under \sysprep\i386$oem$include in [I][B]\sysprep\i386$oem$[/B][/I] as [I][B]startup.cmd[/B][/I]:
[B]cd %SystemDrive%\Drivers\SAD[/B]
[B]call DP_Install_Tool.cmd[/B]in [I][B]\Drivers\SAD[/B][/I], edit [B][I]DP_Install_Tool.CMD[/I][/B]:
just after these lines:
[B]popd[/B]
[B]endlocal[/B]include:
[CODE]ECHO @ECHO OFF > %SystemDrive%\Drivers\RemoveD.cmd
ECHO reg add HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce /v CMD0 /t REG_SZ /d “rd /s /q %SystemDrive%\Drivers” >> %SystemDrive%\Drivers\RemoveD.cmd
ECHO rd /s/q %SystemDrive%\D >> %SystemDrive%\Drivers\RemoveD.cmd
ECHO DEL /F /S /Q /A “%SystemDrive%\Drivers\SAD” >> %SystemDrive%\Drivers\RemoveD.cmd
ECHO rd /s/q %SystemDrive%\Drivers\SAD >> %SystemDrive%\Drivers\RemoveD.cmd
ECHO EXIT >> %SystemDrive%\Drivers\RemoveD.cmdshutdown -r -c “Drivers Installed! Machine will now restart…”
call C:\Drivers\RemoveD.cmd
NET START “Fog Service”[/CODE]
The RunOnce key added will delete the \Drivers\SAD directory on next reboot, since RemoveD.cmd can’t do it after erasing itself. But since the FOG service is restarted just after RemoveD.cmd, the FOG service will restart the computer (to rename it).
Tried many times and works like a charm!
Hope it helps!
-
small correction:
on:
[FONT=Consolas][CODE]ECHO reg add HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce /v CMD0 /t REG_SZ /d “rd /s /q %SystemDrive%\Drivers” >> %SystemDrive%\Drivers\RemoveD.cmd[/CODE][/FONT]
[FONT=Consolas]should be: [/FONT]
[FONT=Consolas][CODE]ECHO reg add HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce /v CMD0 /t REG_SZ /d “cmd /c rd /s /q %SystemDrive%\Drivers” >> %SystemDrive%\Drivers\RemoveD.cmd[/CODE][/FONT] -
After some more testing, I found out the REG line, after /d instead of:
[FONT=Consolas]“cmd /c rd /s /q %SystemDrive%\Drivers”[/FONT]
SHOULD be:
[FONT=Consolas]“cmd /c “”“rd /s /q %SystemDrive%\Drivers””"[/FONT]
[FONT=Consolas](Yes 3 quotes to escape a single quote). That works magic! [/FONT][FONT=Consolas] [/FONT]
-
Are you able to add your own drivers to the list as well and do they have to be compressed?
-
Could someone please upload SAD2-111118(tuturial version) again, the download link is giving me the following error.
Sorry, the time limit of this canvas has expired and the original media fire link no longer works
Thanks for any help -
[quote=“andyroo54, post: 10394, member: 267”]Sorry I thought I replied to this.
The problem appears to be with your unattend file. In particular something you have specified possibly in shell setup module. If you could upload the file we can have a look, you may need to zip the file first.[/quote]
The image above is not showing, but the error message is:
Windows could not parse or process the unattend answer file for pass [specialize] blah blah
Microsoft-Windows-Shell-SetupThe the VM says “fine, im gunna reboot and fix it.” but it just loops reboot with same errors.
Im having this issue too.
Ive read that it can be:
[LIST]
[]A Space in the ComputerName field (I dont have a space, ive called mine RENAME)
[]Bad product Key (I used the one from this post, should be good)
[/LIST]
I have no idea what to do from here… heeeeelp? -
[quote=“drjam, post: 17863, member: 16842”]The image above is not showing, but the error message is:
Windows could not parse or process the unattend answer file for pass [specialize] blah blah
Microsoft-Windows-Shell-SetupThe the VM says “fine, im gunna reboot and fix it.” but it just loops reboot with same errors.
Im having this issue too.
Ive read that it can be:
[LIST]
[]A Space in the ComputerName field (I dont have a space, ive called mine RENAME)
[]Bad product Key (I used the one from this post, should be good)
[/LIST]
I have no idea what to do from here… heeeeelp?[/quote]ok the “fix” is to delete the entire key: Microsoft-Windows-Shell-Setup
pretty crap fix. I hope to find the reason why this didnt work on a vanilla Windows 7 Pro SP1 OEM install on an ESXi VM machine.
But if anyone can… it will be superman. or steve. -
[quote=“andyroo54, post: 4019, member: 267”]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…[/quote]
Were you ever able to upload your unattend.xml? I’m having issues following along the tutorial, things are all appearing different then the screenshots included on the original tutorial.
Thanks,
Knight. -
[quote=“Knight, post: 17910, member: 17014”]Were you ever able to upload your unattend.xml? I’m having issues following along the tutorial, things are all appearing different then the screenshots included on the original tutorial.
Thanks,
Knight.[/quote]What is appearing differently? Are you using windows 7 pro SP1? Or a different DVD?
-
[quote=“andyroo54, post: 17911, member: 267”]What is appearing differently? Are you using windows 7 pro SP1? Or a different DVD?[/quote]
[url]http://prntscr.com/1wbrjg[/url]Things aren’t nested the same way, and I can’t seem to insert anything into “3 generalize”.
I’m using Windows 7 Pro x86, Not SP1.
ISO MD5Sum is: D8F675AAEB48057452666B0CD686D7F5
Btw, thanks for the awesome tutorial.
Knight.
-
[quote=“Knight, post: 17910, member: 17014”]Were you ever able to upload your unattend.xml? I’m having issues following along the tutorial, things are all appearing different then the screenshots included on the original tutorial…
[/quote]Same, what is different? Maybe at what point is it first different?
Ive had some MAJOR issues getting fog itself running, as well as a nice sys-prepped VM working.
Id love to share my learning curve with you here, in the interests of common learning!I followed this thread for my setup, and ended up scrapping the SAD2 drivers totally as they didn’t seem to make any difference when rolling it onto a physical box.
So now ive dumped a lot of motherboard drivers into a folder on the VM called “Drivers” and will do that by hand after each image deployment.
I will be searching here and googleing there…to find a way to script the driver installs, even if its just making a bat file to daisy-chain the drivers install per motherboard model.
I run a PC business…this will be useful for our pc builds.
-
[quote=“drjam, post: 17914, member: 16842”]Same, what is different? Maybe at what point is it first different?
Ive had some MAJOR issues getting fog itself running, as well as a nice sys-prepped VM working.
Id love to share my learning curve with you here, in the interests of common learning!I followed this thread for my setup, and ended up scrapping the SAD2 drivers totally as they didn’t seem to make any difference when rolling it onto a physical box.
So now ive dumped a lot of motherboard drivers into a folder on the VM called “Drivers” and will do that by hand after each image deployment.
I will be searching here and googleing there…to find a way to script the driver installs, even if its just making a bat file to daisy-chain the drivers install per motherboard model.
I run a PC business…this will be useful for our pc builds.[/quote]
I find the SAD2 drivers tool works great for us, but it’s good you found a way that works for your own setup. The main point of this was deploying windows 7, the drivers are just a bonus really.
[quote=“Knight, post: 17912, member: 17014”][url]http://prntscr.com/1wbrjg[/url]
Things aren’t nested the same way, and I can’t seem to insert anything into “3 generalize”.
I’m using Windows 7 Pro x86, Not SP1.
ISO MD5Sum is: D8F675AAEB48057452666B0CD686D7F5
Btw, thanks for the awesome tutorial.
Knight.[/quote]
That would explain why the screen shots I took don’t look the same for you. Every version of windows 7 has diff options for configuring the XML file. For example the XML file I created for windows 7 Sp1 x64 is different to the one I created for windows 7 Sp1 x86, and so it will be different again to yours because you aren’t using SP1 even.
Here is another guide:
[url]http://www.mockbox.net/windows-7/149-windows-7-autounattend-example.html[/url]
Remember my guide will work if you are following it exactly, since you aren’t using the same DVD then I’m afraid you will need to figure out the unattend xml, you will need to read guides, there is now even more info out there compared to back when I wrote this guide.
-
[quote=“andyroo54, post: 17915, member: 267”]I find the SAD2 drivers tool works great for us, but it’s good you found a way that works for your own setup. The main point of this was deploying windows 7, the drivers are just a bonus really.
That would explain why the screen shots I took don’t look the same for you. Every version of windows 7 has diff options for configuring the XML file. For example the XML file I created for windows 7 Sp1 x64 is different to the one I created for windows 7 Sp1 x86, and so it will be different again to yours because you aren’t using SP1 even.
Here is another guide:
[url]http://www.mockbox.net/windows-7/149-windows-7-autounattend-example.html[/url]
Remember my guide will work if you are following it exactly, since you aren’t using the same DVD then I’m afraid you will need to figure out the unattend xml, you will need to read guides, there is now even more info out there compared to back when I wrote this guide.[/quote]
I appreciate the suggestions. At this point I’m more then willing to slipstream in sp1 just so I can use your unattended.xml. I’m also trying to do Professional, at this point anyway, just to get things going, once I’ve got it going, I can start doing different images.
[quote=“drjam, post: 17914, member: 16842”]I run a PC business…this will be useful for our pc builds.[/quote]
This is the exact same reason I’m wanting to do this also, however I’m more repair, then building a new machine. So I’ll have to figure out the best way to allow me to manually enter legit license codes, etc. I haven’t even gotten to the SAD2 part yet, lol. -
[quote=“Knight, post: 17917, member: 17014”]
This is the exact same reason I’m wanting to do this also, however I’m more repair, then building a new machine. So I’ll have to figure out the best way to allow me to manually enter legit license codes, etc. I haven’t even gotten to the SAD2 part yet, lol.[/quote]
If you follow my guide, it does not activate the license key, it is a dummy key (legitimate). Once the computer is imaged etc, we manually enter our volume license key. So the same process will work for you. I did consider a license server for our VLK but decided it wasn’t worth the hassle. Plus if we have an OEM desktop/laptop then we enter the windows license it comes with to save activations on our VLK.
-
[quote=“andyroo54, post: 17918, member: 267”]If you follow my guide, it does not activate the license key, it is a dummy key (legitimate). Once the computer is imaged etc, we manually enter our volume license key. So the same process will work for you. I did consider a license server for our VLK but decided it wasn’t worth the hassle. Plus if we have an OEM desktop/laptop then we enter the windows license it comes with to save activations on our VLK.[/quote]
I did seem to recall reading that somewhere, I suspect in your tutorial.
-
[quote=“Knight, post: 17910, member: 17014”]I’m having issues following along the tutorial, things are all appearing different then the screenshots included on the original tutorial.[/quote]
Alright… I feel like an idiot. I re-read the tutorial, about 50 times, and finally realized I was using the “Windows System Image Manager” incorrectly to make my auto answer file, unattend.xml. I was incorrectly going to the top and clicking on “insert > add synchronous command”, then cutting and pasting the name of the component into the program. This isn’t the right way… The right way is in the bottom left, under “Windows Image”, expand the “Components” folder, then drag and drop the items listed in the tutorial over to the right middle of the program, under the “Answer File” section.
-
[quote=“Knight, post: 17917, member: 17014”]…
This is the exact same reason I’m wanting to do this also, however I’m more repair, then building a new machine. So I’ll have to figure out the best way to allow me to manually enter legit license codes, etc. I haven’t even gotten to the SAD2 part yet, lol.[/quote]If you’re a sole-trader handling break-fix pcs for users who dont appreciate your time, effort and patience talking to them, then yes, we are similar lol!!!
[quote=“andyroo54, post: 17915, member: 267”]I find the SAD2 drivers tool works great for us, but it’s good you found a way that works for your own setup. The main point of this was deploying windows 7, the drivers are just a bonus really.
[/quote]Yeah i was hoping that I could build a single image and roll it out using your really-bang-on procedure man. It would save SO much time with pcs!! My issue said ‘hulloo’ to me in the form of LAN drivers on a standard AMD FM2 Gigabyte mobo. The driverpack (i used the latest of all the stuff on that site, totalled over 1.something gig) in all its glory didnt find the LAN and add the driver.
I figured this didnt work because of MY noobness at work with this setup, but after all the time ive spent so far, i couldnt spend another week learning code, scripting driver packaging, hunting and testing. AAHHHH!!
I love this forum btw…thanks for being alive!
-
Hi,
thank you for the great guide. Unfortunately the drivers are not current. Does any one where i can get current drivers?
Thanks! -
Hi Warrender,
Google “Easy Driver Packs”, these are almost up-to-date.
-
[quote=“Warrender, post: 20887, member: 17068”]Hi,
thank you for the great guide. Unfortunately the drivers are not current. Does any one where i can get current drivers?
Thanks![/quote]Another option is to add your own to the existing driver packs. I found that the latest dell latitude laptops, the driver packs do not have the current drivers.
So I just downloaded the CAB files for the laptop from Dell. I’m lucky because we always get Dell Latitude laptops, and Dell desktops now too.
You can very easily create driver packs. They are basically just drivers that have been zipped up into certain folders. That’s it.
Here is a guide:
[url]http://forum.driverpacks.net/viewtopic.php?id=5[/url]
Once you’ve made it just put it in the corresponding sections of the SAD2 folders. (64bit or 32bit)