Windows 7 Deployment FOG- SAD2 Driver tool
-
this is an ace tutorial!!! i’ve just got two tedious issues that i can’t seem to solve and no searches on the net have came up with any answers (i suppose it is because it is REALLY trivial)
-
when opening IE after sysprep it asks “do you want to make IE your default browser?” even though all other customisations have been kept from making changes in audit mode and i made sure IE was the default in audit mode also tried adding ie settings in unattend.xml, still no luck
-
Desktop icon layout - it’s hard to explain so i’ve took a before and after example to show you… i know this is picky but soo annoying…
[IMG]http://img833.imageshack.us/img833/1241/desktopissue.png[/IMG]
i’ve tried everything i can in the registry, i’ve even set the layout for every resolution in vmware incase this was the cause (diff resolutions) - refreshed desktop after setting for every resolution and noticed keys were being set for each resolution under: [HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Bags\1\Desktop] and the keys still exist after sysprep but don’t seem to keep the layout (although they do before sysprep) i’m pulling my hair out because it really is tedious but i’d like to solve it lol.
-
-
[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.[/quote]
Were you able to figure this one out, Kendall? I am experiencing the same “Unable to extract” error.
-
[quote=“boon, post: 5642, member: 833”]Were you able to figure this one out, Kendall? I am experiencing the same “Unable to extract” error.[/quote]
It was this line that was causing the Unable to extract error message: [CODE]Start /wait /separate /high “” “%cur%\bin\un7zip.exe” “%cur%\bin\dpinst32.7z” %SystemDrive%\D[/CODE]The more recent versions of SAD2 have this file renamed to dpinst.7z, and located in C:\Drivers\SAD2\bin\32
-
I, thanks for the tuto. I use fog for my own. ( about 10 computers at home ) It’s the second time i made an image of Win 7 using VM and Fog. This really really usefull. It’s only take about 15 min for building a new computer. The unattend file is the only point that can be difficult.
I’ve not implemented drivers solution. I’ve made a folder a the root of C$. Inside there are drivers for different motherboards I own.
MAny software are installed, like Itunes, Fraps , Avast …
Thanks for this tuto
Jigsaw
-
Hey all,
So I was following the guide and I have set up my Win 7 VM (using VirtualBox) but I guess I went over my initial 30 days, so now I’m in non-genuine mode. I never installed Security Essentials, so I’d like to do that, but I can’t until I activate. What should I do? And even using the VM snapshot method, won’t it always jump back to non-genuine after the 30 day non-activated period is up?
-
[quote=“John Deery, post: 5769, member: 46”]Hey all,
So I was following the guide and I have set up my Win 7 VM (using VirtualBox) but I guess I went over my initial 30 days, so now I’m in non-genuine mode. I never installed Security Essentials, so I’d like to do that, but I can’t until I activate. What should I do? And even using the VM snapshot method, won’t it always jump back to non-genuine after the 30 day non-activated period is up?[/quote]
Yeah mine does this to. For me it isn’t a problem as we use our own anti virus etc. Once a machine is imaged it gets another 30 days to activate it.
I suppose that’s one way… you could deploy it to another virtual machine, then put that machine back into sysprep, and re add your unattend xml etc.
Perhaps you could also change the date somehow in the ‘bios’ of the virtual machine.
-
[quote=“andyroo54, post: 7825, member: 267”]Yeah mine does this to. For me it isn’t a problem as we use our own anti virus etc. Once a machine is imaged it gets another 30 days to activate it.
I suppose that’s one way… you could deploy it to another virtual machine, then put that machine back into sysprep, and re add your unattend xml etc.
Perhaps you could also change the date somehow in the ‘bios’ of the virtual machine.[/quote]
I decided to just reinstall… tied in with ninite, it goes pretty quickly. Thanks for the amazing guide, btw!
-
Something I noticed looking at the DP_Install_Tool.cmd… the line
[CODE]Start /wait /separate /high “” “%cur%\bin\un7zip.exe” “%cur%\bin\dpinst64.7z” %SystemDrive%\D[/CODE]
Looking at the SAD2 structure, the folders are \bin[32 or 64]\dpinst.7z
Should this be updated in the DP_Install_Tool.cmd example? Or maybe just a note to put the modified commands for the RemoveD.cmd at the bottom of the DP_Install_Tool.cmd that is provided with the release?
-
Thank you very much for this guide, the sad tool works perfect in our environment.
I am stuck with one problem, our new laptops have some display drivers that are not included in the driver packs, so my idea was to add these drivers to the 7zip archive under mobile display drivers, but it doesnt work.
The laptop models is a Fujitsu lh 532 with both nvidia 620 and Intel 300 driver, and a lenovo Lh530 with Intel 3000 display driver. -
I’d like to add for updating the drivers in SAD2 for the drivers that won’t install, you can use MDT along with WAIK which both are free from microsoft and build your out of box drivers, then go to your deployment share then open out of box folder and use 7zip to add those extracted drivers to your NT6 folder in SAD2.
-
[quote=“viggo, post: 9248, member: 457”]Thank you very much for this guide, the sad tool works perfect in our environment.
I am stuck with one problem, our new laptops have some display drivers that are not included in the driver packs, so my idea was to add these drivers to the 7zip archive under mobile display drivers, but it doesnt work.
The laptop models is a Fujitsu lh 532 with both nvidia 620 and Intel 300 driver, and a lenovo Lh530 with Intel 3000 display driver.[/quote]I have never modfied the driver packs, however there are tutorials over at driverpacks.net
-
Okay i have one issue and sure it is my fault. I am having trouble understanding
[BE SURE TO REPLACE YOUR “Hostnamechanger.dll” or your
machine won’t rename and add to domain after imaging". Replace this after FOG client is installed.can we go into more detail on this process as I am not understanding it at all. The tutorial is great and works fine. I just can not get the computer to be renamed during imaging . It stays at rename so i am sure it is me missing a step.
-
can anyone explain to me the issue ?
-
[quote=“mmoore5553, post: 9311, member: 2685”]can anyone explain to me the issue ?[/quote]
Hi,
you should disregard that step, you shouldn’t need to change it, read back earlier in this thread because others have mentioned it. -
Oh i am sorry maybe i am not explaining. The computer name is not being renamed. It is not changing it at all. It stays as renamed. I change it manually . I did not run fog sysprepping as i thought that was no longer needed.
-
This got a bit messy, I just downloaded the deployment cabs from Dell and made a DVD, then included those folders in my image going forward.
-
Guys, I used FOG server along with SAD2 scripts and the driver pack, but then I realized that some of the drivers from driverpack causes issued on some of our computers.
then started to look for a better solution to make it possible only use the manufacture’s drivers. and lot more.
The solution I found was the MDT2012 ( microsoft Deployment toolkit ) which is a free product that can be run on a windows 7 machine with tones of capblity includin injecting drivers during image deployemnt, post install apps and more…thanks
-
This is perhaps a dumb question… I want to follow your tutorial step by step, but I have not yet downloaded FOG. Should I install it has a virtual machine? Or do I just install it on a standalone server on our network?
Thanks
Jason
-
[quote=“jasonaedwards, post: 10076, member: 3147”]This is perhaps a dumb question… I want to follow your tutorial step by step, but I have not yet downloaded FOG. Should I install it has a virtual machine? Or do I just install it on a standalone server on our network?
Thanks
Jason[/quote]
Hi, you can follow the guide without having fog, you can still create your image etc, and get it all ready, just make sure to use lots of snapshots along the way.
But to fully test the deployment you will need FOG.
You could run the sysprep and turn the machine off, then ghost the hard drive to test it in another machine. But I would just get fog working anyway.
-
I love this tutorial. Everything works perfect. I made myself a Universal Windows 7 x86 image out of a VirtualBox (ver. 4.2.6) virtual guest in my ArchLinux. I deployed it on some “metal” it takes about 30 minutes – 10 min. for image deploy (12GB) and 20 minutes unattended install and SAD2 drivers installation. One issue with the Video Card driver in the real hardware – “Device manager” says driver error: “Not enough resources”… or something similar, maybe because my video uses just 8MB of RAM (shared memory) and there is no option to increase it in BIOS even with the latest bios flashed. Though Microsoft site says that this error is related to Interrupts been occupied by other device. NOTE: There is a scenario which is very important for me: I want to deploy this image to previously installed and used PCs (some kind of reinstall) and just deploy it on the first partition e.g.
drive and leave 
drive intact, because there are some user’s saved files, mainly office documents, pictures etc. but I don’t know how to do it, the only suggestion that I found was that I had to create multipartition image (single disk) and basically delete from /images/image-name/ directory the not needed partition of the drive. Because my Golden Image is one partition only (and one 100MB for special win7 needs) so it wipes all my D drive of the computer on which the image is deployed. Any suggestions? How can I save the data of my precious drive?
