Windows 7 Deployment FOG- SAD2 Driver tool
-
[quote=“andyroo54, post: 5349, member: 267”]Sounds like a problem with your xml file and your sysprep. I would strongly suggest to scrap your image, and rebuild from scratch, following each step very closely. If there’s something you don’t understand then post in this thread. You will probably have to try a few times to get the sysprep/unattend file correct. But if you follow my guide it will work.[/quote]
I had a few issues:
- I didn’t encrypt my AD passwords using Fogcrypt.
- I ran across a problem where Sysprep would fail, due to me removing the Windows Media Center. This requires the manual disabling of the Windows Media Player Network Sharing Service. (I don’t know why, that’s just what punching in the error said to do, and it worked.)
- The whole section on changing the hostnamechange.dll threw me for a loop. First because I was looking for hostnamechanger.dll, and when I did figure out what I was looking for, started to panic about having to compile. In the end it looked as if you only have to compile if you want to change the default key-passphrase combo built into Fogcrypt.
The only thing that I still have a problem with is that when the system boots up to the desktop it uses the default one in addition to the nicely laid out administrator one I made, and used the default taskbar icons. In addition the system couldn’t detect some of the hardware on my new systems. Not a show stopper, but something I’ll have to figure out.
-
Ok, I finally got mine working, scrapped the whole “gold image” build from VirtualBox. When I did it baremetal - it worked. However, I can’t tell if my SAD2 install worked with the drivers, since I have network, ide, etc but have a few with the notorious yellow question mark for (base, and something else) Not sure if there’s a pause in the script to allow something else to finish or what. I know it’s always a work in progress, so maybe once I’ve figured it all out - for good, I can draft a nice step by step with pretty pictures.
-
[quote=“Leroy Brown, post: 5431, member: 1560”]Ok, I finally got mine working, scrapped the whole “gold image” build from VirtualBox. When I did it baremetal - it worked. However, I can’t tell if my SAD2 install worked with the drivers, since I have network, ide, etc but have a few with the notorious yellow question mark for (base, and something else) Not sure if there’s a pause in the script to allow something else to finish or what. I know it’s always a work in progress, so maybe once I’ve figured it all out - for good, I can draft a nice step by step with pretty pictures.[/quote]
I’d suggest to test the SAD tool by itself first, by installing win 7 vanilla on some hardware, then manually running the sad tool. This is how I got it to work initially… but if you get the same version I used and use the scripts I uploaded then it should work.
-
Has anyone been able to successfully build a “gold” image on VirtualBox then lay it on a baremetal machine? I can create successfully from a machine, to Fog, and back down, but from VB up and then down to baremetal doesn’t work. I did make sure its set to IDE.
-
[quote=“Leroy Brown, post: 5551, member: 1560”]Has anyone been able to successfully build a “gold” image on VirtualBox then lay it on a baremetal machine? I can create successfully from a machine, to Fog, and back down, but from VB up and then down to baremetal doesn’t work. I did make sure its set to IDE.[/quote]
yeah I build a ‘master/gold’ image in Virtualbox, I’m not the only one either
-
okay so you can upload but not deploy.
once you have sysprepped your Gold Vbox and uploaded it. just turn on the Virtual machine and let it run through sysprep see if that works.
p.s. don’t forget to take a snapshot before sysprep
-
also when you install windows 7 how do you do it?
100mb boot partition + os partition or 1 single partition?
-
I did in fact do the sysprep, then the fogprep too, even tho they say in .32 you don’t have too. problem is there’s too many “this says that” and “then this way”. Like a nice, concise step by step is what I’ll have to put together. Not to take away from all andyroo54’s hard work. we can just make it even better. ill test and try again, but…(dual partitions, etc)
-
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.
