Windows 7 Deployment FOG- SAD2 Driver tool
I hope it can help you out, if you have problems just ask and I will help if I can! I might clean up the formatting in this thread tomorrow and I will no doubt make changes/additions as I continue to test this into the future.
great article, I myself have been going through similar process based on this guide [URL=‘http://blog.ibuddy.info/index.php/2011/05/fog-29-my-windows-7-guide-3264-bit-docv1/’]http://blog.ibuddy.info/index.php/2011/05/fog-29-my-windows-7-guide-3264-bit-docv1/ [/URL](just what you have done but with VirtualBox) my next stage was to look into the automation of drivers, which you have covered.
Thanks for sharing :D will definitely help me and others, a few of my new machines network cards are not detected by Win 7 so cannot auto join domain until I manually installed the driver
UPDATE: just implemented this into a test image, and it works great, now it will install missing NIC driver and allow fog to continue with AD joining. Cheers
[B]Step 9: FOG service and sysprepping/fogprepping[/B]
Now the final steps should be to:
- Install the FOG service, navigate to:
And install the FOG client service. [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.
- Download and Run “FOG Prep”- This is important for uploading windows 7 machines.
The virtual image almost ready to upload to FOG. The last step is to run the system preparation too. If you closed it you can access it in:
Before doing the below, I strongly suggest to take a snapshot! It’s likely you will want to re-upload the image many times before you are happy with it. Plus you can then easily add updates/changes from that snapshot position.
Have the cleanup action to go into OOBE mode, and tick generalize. Set the shutdown option to “shutdown”, then hit OK. Sysprep will start working. Once finished the machine will then shutdown. Now the next time it powers on we want to upload FOG before windows starts again. You can also take a snapshot before you run sysprep and then let it reboot without capturing it, to make sure everything works on the next boot up before uploading it to FOG.
Step 10: Creating the image in FOG
Select “Image management” in the FOG console. Then choose “new image”. Name the image-and select “Single Partition” (NTFS Only, Resizable).
Now go to your host and reference the newly made host image to your registered host machine.
Then choose “Basic Tasks” from the menu to the left. Choose “upload Image”>“Upload image”. The task will start. Fog will automatically resize the partition for upload.
Now you just need to turn your virtual machine back on, and hit F12 to ensure it network boots. If it PXE boots then FOG will grab the image and upload it! If windows starts then you have not successfully PXE booted and you need to return to your snapshot- and re run sysprep. My Final image size was approx 10GB.
You are finished!
That’s pretty much it. Now you can deploy the image to other psychical machines by the standard process. Thanks to the SAD2 tool drivers are a breeze, that said, Windows 7 and Sysprep will handle the majority of the essential drivers, but it’s nice to get the correct drivers from SAD2.
I have deployed this on many machines. Most recent machine I was testing was a Lenovo desktop, CPU i5 quad, 4GB ram, onboard graphics and I put an SSD in it and it imaged in two minutes dead (I tried another with the original mechanical drive, and it managed two minutes- five seconds)… It finished the windows deployment in another 2 minutes approx. It auto logged on and deployed SAD2 and installed drivers in around 4 minutes, then rebooted, joined the domain and renamed. All up it was probably done in around 15 minutes max.
I hope this guide will help you in some small way. I don’t think it’s possible to make a ‘one guide fits all’ for win 7 deployment, because there are just so many variables, but I hope this might help get you started. Thanks for reading!
Please feel free to comment etc below.
- A. Hingston 2012
- Install the FOG service, navigate to:
[B]Step 5: Customizing windows installation- Free for all[/B]
Ok this section is really up to you. Here you can make any changes you want to windows for when it is deployed. I will list some of the things I have done to give you an idea of what you might like to do. I’m sure you will come up with your own idea for how you want to customize windows 7. I suggest making snapshots as you go along.
Installed VNC 1.0.9 set password - This allows us to remote control machines across the network for support reasons.
Enabled Remote desktop (windows)- As a backup to VNC.
Upgraded IE to 9
Disabled System restore- Not needed, FOG is our system restore :)
Set boot animation custom- I made my own custom windows boot animation- I animated our company logo- instead of the normal win 7 startup animation. It’s not hard to do, and you can download a neat tool to do it very easily here:
Your animation has to be 105 frames long- and it is 7 seconds long- running at 15/fps. The first 4 seconds play then the last 3 seconds loop until the machine starts up.
IMPORTANT NOTE: Some third party tools like can really ruin your day- I used another program to change the startup sound for win 7 and after a lot of trouble shooting figured out it was the cause of a problem I was having where the imaged machines were not working properly. That said I have fully tested the above boot animation changer tool and it works flawlessly.
Set Desktop background
Set win 7 basic theme as default
Set log on backgrounds in regedit- Here you can create custom logon screens. This is the screen before you logon. You can make one for each common resolution- and also set a default background for when it can’t find the right resolution.
- Start registry editor (Start>Regedit)
Click on background- and Create a new 32 bit DWORD called “useOEMBackground”. Set the value to “1”.
EDIT: I found that while this does work, it won’t use your other dimensions, only background default. You should actually modify this registry key:
[INDENT=1][COLOR=#333333][FONT=Arial][SIZE=13px]HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\Background Now in right-side pane, change value of [B][SIZE=13px]OEMBackground[/SIZE][/B] to [B][SIZE=13px]1[/SIZE][/B][/SIZE][/FONT][/COLOR][/INDENT]
Now you have to create the folders in C:\Windows\System32\oobe\info\backgrounds
Now place all of your background files in that folder. You have to name them in this fashion:
background1024x768, background1920x1080 etc. The images you make should be the correct dimensions or they won’t work. Also they can’t be over 250 kilobytes or they won’t work. I use Photoshop’s save for web feature which cuts the size down of images greatly.
Now users will see a custom background when they get to the log on screen.
Set a few local accounts for our company that we use
Set default user account picture
Local Group policies
Load specific theme
Prevent users changing theme (can still change background/window colours etc)
Allowed users to install print drivers/usb hub drivers
Set screen to 15 min Lock out
Prevent changing screen saver/password on wake up
(SECPOL) Behaviour of the elevation prompt for admins in admin approval mode: Evaluate without prompting
(SECPOL) Interactive Logon hide last user
(SECPOL) Switch to the secure desktop prompt for elevation: disabled
Windows Defender off
Power options: never turn off hard disk
Remove windows media centre
Turn off all warning messages in windows action centre
Set OEM information via regedit- Here you can customize what it says when viewing system properties. You can do this via a regedit. Just copy and paste the below into a .reg file and edit the field I mark in red.
Windows Registry Editor Version 5.00
You also need to create a .bmp file in the location C:\Windows\System32\ called “oemlogo.bmp”, it should be no bigger than 115x115 pixels.
X64 ICON RESTORER
Windows Updates- We pointed our image to our WSUS server, and installed as many updates as possible before upload.
Again, the above is just an example, you don’t have to follow these steps if you don’t want- that said I will make a couple of exceptions and say that the secpol (secpol.msc) changes really are necessary and you should do them. If not you can cause problems with snapins prompting for approval, instead of being fully unattended.
[B]Step 6: An important thing to do[/B]
Now you need to place your unattend.xml file in it’s location. This location is the same for both x64 and x86 images:
Your unattended file will be processed during sysprep.
[B]Step 7: First log on script- This is important![/B]
After FOG has imaged your computer and setup has run, windows will run a script that we will now make. You need to make a folder called “scripts” in the C:\Windows\setup\ directory:
In the scripts folder you need to create a .cmd script called “setupcomplete.cmd”. Copy and paste the below into this script.
del /Q /F c:\windows\system32\sysprep\unattend.xml
del /Q /F c:\windows\panther\unattend.xml
This script will perform three critical things: It will delete your unattend.xml file from the original location and the location it is copied to during sysprep, and it will also call the wonderful SAD2 driver install tool to run. I will explain more about the SAD 2 drivers tool in the next step.
[B]Step 8: Drivers- SAD2[/B]
This is the method this guide uses to install drivers on any machine after the initial imaging.
Essentially after install on first logon, the “setupcomplete.cmd” script will call the “SAD2” driver tool to run. The SAD2 driver tool was made by community members of the driverpacks.net forums.
[B]UPDATE:[/B] There is some confusion on which version to use, how to modify it, where to download it, etc, so I’m making it very simple.
You can download the folder which has the SAD2 script already modified and the correct folder structure setup. There is no need to download the latest version of the SAD2 script from driver packs forums.
[B]DOWNLOAD THE FILE AT THE BOTTOM OF THIS POST.[/B]
[COLOR=#000000][SIZE=3][FONT=Open Sans]If you can’t download it from there PM me and I will email it to you.[/FONT][/SIZE][/COLOR]
First, extract the .zip archive and you will get a folder called “Drivers”.
Put this folder “drivers” in root of C:\
Then download the driver packs you want from here:
If it is [B]x64 bit image[/B] you are making, put driver packs here:
Or [B]here for x86:[/B]
This is what SAD2 looks like:
So in the x64 image you only put the 64 bit drivers into the x64 folder, and for the x86 image you only put the 32bit drivers into the x86 folder.
I made a few changes to the “DP_Install_Tool” to make it fully unattended, and also so that it restarts the PC after the drivers have been installed, and deletes the driver packs from the image.
I suggest creating another snapshot and testing that the tool runs correctly. You can also try the tool out manually. Just manually run the DP_Install_tool.cmd and it will install required drivers for your machine.
[B]STEP 4: Making an unattend.xml[/B]
Now we are going to create an answer file. What you do here will vary depending on what you want automated. An answer file is responsible for automating the setup stage of windows 7 once deployed to a machine from FOG. This part is difficult to write a tutorial for, as it is complicated to explain- but is actually very simple once you have looked into it for a while.
You should have downloaded AIK tools and installed. From your physical machine start menu launch “Windows system image manager”.
NOTE: If you need more detailed information on the Answer file process check here:
You will need to have your .ISO or win 7 DVD mounted/inserted. Choose “File>Select windows image”. Choose the win 7 DVD iso. You now need to choose a .clg file. In this case choose “install_windows 7 PROFESSIONAL.clg”
What this does is give you the “catalogue” options for that version of Windows 7.
Now make a new answer file. Go “New> Answer file”. Be sure to save this now- call it “unattend.xml”.
IMPORTANT: If you are making an X86 and X64 version, you must make two different answer files. Make one after the other. You will need to unmount the first DVD and then select the other, and re open the .clg catalogue files as explained above. I suggest making a folder called “unattend files”-then making one sub folder for your X86 and one for your x64. Note the difference between 86 and 64:
Now basically you can add “components” to the file, by dragging and dropping things you want into the answer file. I will detail what I have added to my answer file- you may want to customize your own further.
Add “x86_Microsoft-Windows-Setup_Nuetral” or “amd64_Microsoft-Windows -Setup_neutral”.
Set "Use ConfigurationSet to “true”.
Add “x86_Microsoft-Windows-Security-SPP_neutral” or “amd64_ Microsoft-Windows-Security-SPP_neutral”- Set value to “1”. This will skip the windows licensing program.
Add these three components. Substitute x86 or amd64 depending on which answer file you are doing.
c) _Microsoft Windows-Shell-Setup_neutral
I will now show what to add for each above component.
Right click and “Insert new Runsyncronouscommand”.
Set the options below. This will activate the built in administrator account during setup.
Set to “true”. This will skip automatic activation.
c) _Microsoft Windows-Shell-Setup_neutral
I set computer name to “RENAME”- Fog will rename when first logged on, or you can do it manually.
Set copy profile to “true”- this will copy your administrator account profile as the default profile for other users, including domain users.
You can put a dummy product key in to make sure it skips this during setup. You can set the real license key later. A full list of keys is below.
Operating System Edition
Windows 7 Professional
Windows 7 Professional N
Windows 7 Enterprise
Windows 7 Enterprise N
Windows 7 Enterprise E
Set “show windows live” to False.
Set your time zone.
- OOBE System
Set your language settings here, mine is for En-Au (English:Australia)
Under “autoLogon” set enabled to: true (this will set windows to automatically log on after imaging)
Set logon count to 3 (this means it will automatically log on three times to the local admin account after deploying image from FOG)* I have since dropped this to 2, because I’ve found I don’t need 3 for my setup.
Set username to “administrator”
Then add the administrator password also.
Under “OOBE” set the options as follow:
Under “User account” set the administrator password.
Now you need to add something extra here to the Shell setup. Go back to components and to the Shell setup neutral component. By default, shell setup won’t add local accounts as an option. You have to drill down like below then drag local accounts across under shell setup.
Now configure the local administrator account as below:
…and don’t forget to set a password. This will be the account windows uses to log on the first time after install.
Ok that’s it for the unattend file. As mentioned above make sure you have a x86 and x64 unattend.xml if you are making both SOE.