Windows 7 Deployment FOG- SAD2 Driver tool
-
[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)
-
[quote=“drjam, post: 17922, member: 16842”]
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![/quote]
See the above about easily adding your own driverpacks to your image. I wouldn’t give up, even if you spend another month getting it right, it’s still worth it given the time it saves.
-
Hi Guys!
Dell Latitude E6330 cannot boot pxe / fog server? any kernel for this laptop?
-
I am in the process of getting this all setup (FOG/VMware/Win7 Image) and I am to the last part with the SAD2 driver tool installation. Every time I try to install it Vipre removes it stating its virus/generic trojan. Is anyone else experiencing this issue. I have gotten the files from [url]http://www.mediafire.com/download/3e8ee9fpo7s6ek4/SAD3-130627.7z[/url] but each time I try to open it it is flagged and deleted.
Any help would be appreciated.
Chad -
I could be wrong in my thinking Chad, but I don’t think this is the file you should be downloading. It probably does contain a virus which means your antivirus is doing the right thing.
-
Request,
is the newest version of Driverpack tools compatible with the DP install tool of this tutorial? or do i need edit the new DP_Install_Tool
if i need to edit it, can some one explain what i need to edit / remove -
[quote=“raimon93, post: 24319, member: 22311”]Request,
is the newest version of Driverpack tools compatible with the DP install tool of this tutorial? or do i need edit the new DP_Install_Tool
if i need to edit it, can some one explain what i need to edit / remove[/quote][quote=“Chad Lecraft, post: 23368, member: 22087”]I am in the process of getting this all setup (FOG/VMware/Win7 Image) and I am to the last part with the SAD2 driver tool installation. Every time I try to install it Vipre removes it stating its virus/generic trojan. Is anyone else experiencing this issue. I have gotten the files from [url]http://www.mediafire.com/download/3e8ee9fpo7s6ek4/SAD3-130627.7z[/url] but each time I try to open it it is flagged and deleted.
Any help would be appreciated.
[SIZE=13px][FONT=Tahoma][COLOR=#141414]Chad[/COLOR][/FONT][/SIZE][/quote]
Guys I’ve updated the guide, please see the Step 8 on the first page of this thread. That post has the file attached as a .zip so you can just unzip and place the folder in C:\ and then add your driver packs as per instructions.
-
Thanks! also what can be the problem of this? got an error, i tried the image in VMware checking if its correct but got this error:
[url]https://www.dropbox.com/s/qelairrkreko9ts/2014-03-21 14.51.47.jpg[/url]
-
[quote=“raimon93, post: 24563, member: 22311”]Thanks! also what can be the problem of this? got an error, i tried the image in VMware checking if its correct but got this error:
[URL=‘https://www.dropbox.com/s/qelairrkreko9ts/2014-03-21 14.51.47.jpg’]https://www.dropbox.com/s/qelairrkreko9ts/2014-03-21 14.51.47.jpg[/URL][/quote]
It looks like windows hasn’t loaded properly yet, it’s still logging on. I think mine does that too but can you test a fresh install of win 7, then run the driver packs manually while logged on as admin?
-
oke, after another VM image it worked, meby the problem was that somthing wasend loaded. but after a while it worked flawless!
Thanks for support
-
I was able to use the SAD3-130627 tool to extract and install the drivers just like the SAD2 tool. I had to modify the DP-Install_Tool.cmd with code from the originally modified SAD2 .cmd. I will upload what I have done. There are switches in the beginning of the code that you can change to do reboot or shutdown, delete drivers, ect. It explains it in the notes in the code. Mine reboots and leaves the drivers as it only amounts to a gig of space. I also had to modify the command that is put in the sysprep script folder to use SAD3-130627 instead of SAD2-111118. Other then that it ran the same. Add the 7zip file just like in the tutorial.
Just open the attached txt file in notepad and save it as a .cmd.[url=“/_imported_xf_attachments/0/615_DP_Install_Tool.txt?:”]DP_Install_Tool.txt[/url]
-
Sooo… I have used the instructions from the initial post with great success many times though apparently I haven’t done so since November. My VMWare Workstation snapshots from November work fine but if I upload an image after taking a new snapshot and then deploy it to any machine I get a blue screen stop error and the computer boot loops at the “Starting Windows” screen.
Unfortunately I can’t recall exactly what changed around that time. I first noticed trouble when I started to experiment creating 64bit images last winter. I mistakenly thought it was an issue with my x64 imaging process which wasn’t critical so I didn’t think much of it. As I am trying to update my 32 bit image from last November I finally realized that the issue extends to all VMWare Workstation images EXCEPT those with snapshots that go back to November and before.
I did upgrade from VMWare Workstation 9 to VMWare workstation 10. I thought that was in September or October but it might have been around the time of the problem. My next plan is to roll back to VMWare Workstation 9.
Anyone experienced anything like this and found a solution?
-
Fog is a great tool. question: Any idea why SAD 2 is not running silently ? I am prompted every step of the way. Used the DP_Install_tool posted here and still no silent install. should c:\windows\setup\scripts\setupcomplete.cmd have “/s” added to the end of this line ? START C:\Drivers\SAD2-111118\DP_Install_Tool.cmd
-
This topic is still a bit hard to understand when i used SAD 2 for more than a year and now SAD 3 !
I added to SAD a FOG configuration generator based on network IP and DNS suffix and a Windows OEM Activator based on brands but it’s far from perfection so i don’t use them anymore.
But if some people are interested to improve my script, i can share them.To use SAD 2 or 3 in silent, you have to add the /S to the .cmd of SAD and run something like this in the “FirstLogonCommands” of the sysprep :
C:\SAD3-130627\DP_Install_Tool.cmd /SThere is no problem to keep this kind of image under VMware Workstation 10 even after making with an older version.
Mine was made in 2013 and i keep updating it since. -
[quote=“jmeyer, post: 32276, member: 6537”]
There is no problem to build this image under VMware Workstation 10.
Mine was made in 2013 and i keep updating it since.[/quote]Thanks for confirming this.
I’m thinking this could be a problem with my configuration of VMWare Workstation configuration or the hardware/OS it is running on. I would question the settings I’m using when creating the VM guest images but older snapshots work fine on VMs created in November 2013 or before. I tried starting from scratch with a fresh install of Workstation 9 and still end up with unbootable deployments. The file system transfers fine and partitioning looks good but still won’t boot.
Are there any recent Windows updates known to break VMWare V2P? My workstation 10 is Windows 8 x64(not 8.1) on an HP 6200 Pro while Workstation 9 is Windows 7 x64 on an HP 6000 Pro. P2V is well documented but the reverse not so much.
We are an HP shop with 6000/6200/6300 pro and will be adding 600 G1 shortly. Aside from the 6000 not wanting to step through the boot order when a PXE server is not found these machines have worked well for us until now.
I’m quickly running out of ideas so any thoughts are welcome. Reports of success with similar hardware will also help me feel more hopeful.
Thanks
Eli
-
There were something about disabling SCSI (scsi0.present = “FALSE”) and put drive as IDE but i haven’t edit vmx file under Workstation 10 for a new image version so i’m not sure it’s something to check.
I don’t understand what you try to do when you speak of P2V for HP home computers.
-
I do set the drives as IDE but I have not edited the VMX file to disable SCSI. It is a good thought that I will try to tomorrow and report results.
P2V is shorthand for the process of capturing a physical machine to a virtual machine. This is not what I’m trying to do but my point was there is plenty of documentation of that process. V2P is essentially what we are doing when we are preparing virtual machine images with VMWare Workstation for deployment to physical machine with FOG.
