FOG Project - User contributions [en]

Auto driver Install

2015-02-18T21:21:18Z

Andrew.single: /* Install Script */

Auto driver Install

2015-02-18T21:01:15Z

Andrew.single: /* Install Script */

File:Machinedrivers.txt

2015-02-18T20:58:12Z

Andrew.single: Andrew.single uploaded a new version of "File:Machinedrivers.txt": .3 Alpha

Script for auto driver install with FOG 1.2.0

File:Machinedrivers.txt

2015-02-18T20:56:39Z

Andrew.single: Andrew.single uploaded a new version of "File:Machinedrivers.txt": v .3alpha

Script for auto driver install with FOG 1.2.0

Auto driver Install

2015-02-18T18:07:08Z

Andrew.single: /* Adding Windows Device Drivers */

Auto driver Install

2015-02-18T16:39:05Z

Andrew.single: /* Adding Windows Device Drivers */

Auto driver Install

2014-11-03T01:03:01Z

Andrew.single: /* Install Script */

File:Driverinstall.txt

2014-11-03T01:02:19Z

Andrew.single: Auto Driver install script for FOG 1.2.0

Auto Driver install script for FOG 1.2.0

File:Machinedrivers.txt

2014-11-03T01:00:05Z

Andrew.single: Script for auto driver install with FOG 1.2.0

Script for auto driver install with FOG 1.2.0

Auto driver Install

2014-11-03T00:20:31Z

Andrew.single: /* Install Script */

Overview: The Auto Driver install script is an addition for FOG that allows you to build a hardware independent Windows 7 image. Devices on the system will be detected by FOG, and drivers inserted into C:\Drivers from a repository on the FOG server. Windows will then use that as an additional driver search path when doing Sysprep first run.

Why do this? When you're managing thousands of machines from a variety of models with differing driver requirements making a single image that has everything you need is nearly impossible. In the past we would make images specific to each model of computer, but it means that we maintained about 10 different images. That means that updating the image was a lot of work, and simply didn't get done very often. By separating the image from the drivers, you gain a lot of flexibility, and can respond to changes very quickly.

For example, let's say a new model of desktop comes your way. With this system, all you do is image it once as is, take a look at Device manager to see what drivers it needs, and then place those drivers on the FOG server. Now all machines with the same hardware will have the drivers installed during the sysprep process. Another common scenario is that some machines have a special card added to them. Maybe it's a video card, or firewire card. Rather than building a new image, or multiple new images, simply include the driver, and any system with that card present will pull it post imaging.

==Setup Repository==
*Create a folder inside of /images named drivers
mkdir /images/drivers
*Create a Common folder for drivers/scripts you want on all systems.
mkdir /images/drivers/Common
*Create a SetupComplete.cmd file. (See: http://technet.microsoft.com/en-ca/library/cc766314%28v=ws.10%29.aspx)
*This is a script, that when copied to C:\Windows\Setup\Scripts is executed at the end of the SysPrep process. The Frontier script stops the FOG service, runs a netsh command to push out a wlan profile, deletes the profile xml file, the sysprep.xml and fixes the permissions on the C:\drivers folder. It's a quite useful tool to use. I recommend at least having:
net STOP "Fog Service"
start "Reset C:\Drivers Perms" /wait "icacls" C:\drivers /reset /T >>"C:\FOGDrivers.log" 2>&1

===Adding Windows Device Drivers===
*The script currently detects three categories of Drivers: PCI, USB & ACPI.
*The first step is to identify the device that you want to install. On an imaged Windows 7 machine, go to device Manager.
**Right click the device, and go to Properties.
**Click the details tab, and go to the Hardware IDs dropdown.
**You'll see something like PCI\VEN_XXXX&Dev_YYYY&SUBSYS_ZZZZ.... or USB\VID_XXXX&PID_YYYY or ACPI\XXXXXXXXX
***You take the driver for that device, and place it in a folder of /images/drivers/XXXX/YYYY.
For Example, a driver for Intel Video with a device ID of PCI\VEN_8086&DEV_5A3C would be in the folder /images/drivers/8086/5a3c **Note that it's lower case.
***In the case of a drivers that contains drivers for multiple devices (Ie: Chipset) you don't need to break out each individual device. You can simply make the folder match one of the devices.
***ACPI devices don't have a vendor/ID value, but only contain a single value. ACPI/PNP devices should be placed in /images/pnp/XXXXXX.
For Example, a driver for the Dell Freefall sensor is ACPI\SMO8810 in Device Manager. Place the driver in /images/pnp/SMO8810.

*Tip for keeping driver folders reasonably sized: Very often drivers are bloated and come with a lot more than what Windows minimally needs to get the device working. Often there's an executable that installs a tray application, etc. As for the actual driver, it's often found inside of a subfolder like \Win7\driver\x64. When adding a driver, you can usually just grab the subfolder that contains the files you need. You can test this by putting that folder on a USB stick, and going to a system that's missing the driver. In Device Manager, point to the folder and see if it will update successfully. ("Real" driver folders contain .inf, .cat, .sys, .man files)

===Adding Silent Install drivers===
*Drivers that require an executable to be run can also be included in this method provided the driver has a silent install option with no user interaction.
*If there is a drvinstall.bat file inside the driver folder, the script will take the contents of the bat file and add it to the end of the SetupComplete.cmd file to be executed at the end of the sysprep process. See the example contents of:
echo Driver for SMO8810
start/wait C:\drivers\pnp\SMO8810\setup.exe /s
*This is handy for devices that aren't detected by Device Manager's Update Driver. Devices that operate this way for us have been some sound cards, freefall sensors, touchscreen calibration tools, etc.

==Install Script==
*There are two files you'll need to add to /images/postdownloadscripts/
*machinedrivers.sh
#!/bin/bash
#machineinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#http://www.fogproject.org/wiki/index.php/Auto_driver_Install
#Andrew Single - Frontier School Division (Frontier loves FOG!)

oIFS=$IFS;
getDeviceName()
{
# echo "lspci -mm -d $1";
local devnamefull=`lspci -mm -d $1`;
devnamefull=${devnamefull//\" \"/¤};
IFS=¤;
pciDescr=($devnamefull);
IFS=$oIFS;
}
#Read PCI Device strings
pci=`lspci -n |cut -c 15-23`;
usb=`lsusb |cut -c 23-32`;
last="";
for device in $pci
do
#filter for unique devices
if [ "$device" != "$last" ]; then
last=$device;
#Split up vendor & Device IDs
dMfg=${device:0:4};
dDev=${device:5:4};
# echo "Device: $device";
# echo "Mfg: $dMfg - Dev: $dDev";
# sleep 1;
drvLoc="/images/drivers/$dMfg/$dDev";
#Does the driver folder exist?
if [ -d $drvLoc ];then
#Copy files
# echo $device;
getDeviceName $device;
echo -n " * Copying ${pciDescr[4]} ";
#Does the vendor folder exist?
if [ -d /ntfs/Drivers/$dMfg ]; then
cp -r $drvLoc /ntfs/Drivers/$dMfg
else
mkdir /ntfs/Drivers/$dMfg
cp -r $drvLoc /ntfs/Drivers/$dMfg
fi
if [ -f $drvLoc/drvinstall.bat ]; then
cat $drvLoc/drvinstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
fi
echo "Done.";
fi
fi
done
IFS='
';

#enumerate PNP devices
pnpdevices=`dmesg |grep IDs`;
for pnp in $pnpdevices
do
pnp=${pnp#*IDs };
pnp=${pnp:0:7};
#filter for unique devices
if [ "$pnp" != "$last" ]; then
last=$pnp;
drvLoc="/images/drivers/pnp/$pnp";
#Does the driver folder exist?
if [ -d $drvLoc ];then
#Copy files
echo -n " * Copying PnP Device $pnp ........";
#Does the folder exist?
if [ -d /ntfs/Drivers/pnp ]; then
cp -r $drvLoc /ntfs/Drivers/pnp
else
mkdir /ntfs/Drivers/pnp
cp -r $drvLoc /ntfs/Drivers/pnp
fi
if [ -f $drvLoc/drvinstall.bat ]; then
cat $drvLoc/drvinstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
fi
echo "Done.";
fi
#echo "No driver for $device.";
fi

done

IFS=$oIFS;
usb=`lsusb |cut -c 23-32`;
for device in $usb
do
#filter for unique devices
if [ "$device" != "$last" ]; then
last=$device;
#Split up vendor & Device IDs
dMfg=${device:0:4};
dDev=${device:5:4};
drvLoc="/images/drivers/$dMfg/$dDev";
#Does the driver folder exist?
if [ -d $drvLoc ];then
#Copy files
echo -n " * Copying USB Device Driver ........";
#Does the vendor folder exist?
if [ -d /ntfs/Drivers/$dMfg ]; then
cp -r $drvLoc /ntfs/Drivers/$dMfg
else
mkdir /ntfs/Drivers/$dMfg
cp -r $drvLoc /ntfs/Drivers/$dMfg
fi
if [ -f $drvLoc/drvinstall.bat ]; then
cat $drvLoc/drvinstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
fi
echo "Done.";
fi
#echo "No driver for $device.";
fi
done

*And driverinstall.sh
#!/bin/sh
#driverinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#Andrew Single - Frontier School Division (Frontier loves FOG!)

win7sys="/dev/sda2";
mkdir /ntfs 2>/dev/null

echo -n " * Mounting Windows File System...................";
mount.ntfs-3g $win7sys /ntfs 2>/tmp/mntfail
mntRet="$?";
if [ ! "$mntRet" = "0" ]
then
echo "Failed to mount C:";
echo "";
echo -n " * ";
cat /tmp/mntfail
echo "";
sleep 2;
else #Mount successful
echo "Done.";
mkdir /ntfs/Drivers 2>/dev/null
echo "";
echo -n " * Copying Common Drivers.........................";
cp -r /images/drivers/Common /ntfs/Drivers
if [ -d /ntfs/Windows/Setup/Scripts ]; then
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
else
mkdir /ntfs/Windows/Setup/Scripts
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
fi
#Needs to be exectued with bash
bash /images/postdownloadscripts/machinedrivers.sh
echo " ";
echo " * Driver copy completed.";
umount /ntfs
sleep 5;
fi
*Make them executable with
chmod a+x *.sh
*Finally, edit the fog.postdownload file and the following to the end of the file:
${postdownpath}/driverinstall.sh

==Building the Universal Image==
*The script requires a sysprepped Windows 7 image to work. If you're not using Sysprep, this process won't work.
*Include driver search path to C:\Drivers (See: http://technet.microsoft.com/en-ca/library/cc753716.aspx)

==Notes for Andrew Single==
In Progress: Documentation for adding the Auto Driver install script from Frontier School Division.
Script To Do:
*Make device ID's all lower case so PNP devices don't require upper case folder names & are consistent with all lower case.

Auto driver Install

2014-11-03T00:20:15Z

Andrew.single: /* Install Script */

Auto driver Install

2014-11-03T00:04:43Z

Andrew.single: /* Install Script */

Overview: The Auto Driver install script is an addition for FOG that allows you to build a hardware independent Windows 7 image. Devices on the system will be detected by FOG, and drivers inserted into C:\Drivers from a repository on the FOG server. Windows will then use that as an additional driver search path when doing Sysprep first run.

Why do this? When you're managing thousands of machines from a variety of models with differing driver requirements making a single image that has everything you need is nearly impossible. In the past we would make images specific to each model of computer, but it means that we maintained about 10 different images. That means that updating the image was a lot of work, and simply didn't get done very often. By separating the image from the drivers, you gain a lot of flexibility, and can respond to changes very quickly.

For example, let's say a new model of desktop comes your way. With this system, all you do is image it once as is, take a look at Device manager to see what drivers it needs, and then place those drivers on the FOG server. Now all machines with the same hardware will have the drivers installed during the sysprep process. Another common scenario is that some machines have a special card added to them. Maybe it's a video card, or firewire card. Rather than building a new image, or multiple new images, simply include the driver, and any system with that card present will pull it post imaging.

==Setup Repository==
*Create a folder inside of /images named drivers
mkdir /images/drivers
*Create a Common folder for drivers/scripts you want on all systems.
mkdir /images/drivers/Common
*Create a SetupComplete.cmd file. (See: http://technet.microsoft.com/en-ca/library/cc766314%28v=ws.10%29.aspx)
*This is a script, that when copied to C:\Windows\Setup\Scripts is executed at the end of the SysPrep process. The Frontier script stops the FOG service, runs a netsh command to push out a wlan profile, deletes the profile xml file, the sysprep.xml and fixes the permissions on the C:\drivers folder. It's a quite useful tool to use. I recommend at least having:
net STOP "Fog Service"
start "Reset C:\Drivers Perms" /wait "icacls" C:\drivers /reset /T >>"C:\FOGDrivers.log" 2>&1

===Adding Windows Device Drivers===
*The script currently detects three categories of Drivers: PCI, USB & ACPI.
*The first step is to identify the device that you want to install. On an imaged Windows 7 machine, go to device Manager.
**Right click the device, and go to Properties.
**Click the details tab, and go to the Hardware IDs dropdown.
**You'll see something like PCI\VEN_XXXX&Dev_YYYY&SUBSYS_ZZZZ.... or USB\VID_XXXX&PID_YYYY or ACPI\XXXXXXXXX
***You take the driver for that device, and place it in a folder of /images/drivers/XXXX/YYYY.
For Example, a driver for Intel Video with a device ID of PCI\VEN_8086&DEV_5A3C would be in the folder /images/drivers/8086/5a3c **Note that it's lower case.
***In the case of a drivers that contains drivers for multiple devices (Ie: Chipset) you don't need to break out each individual device. You can simply make the folder match one of the devices.
***ACPI devices don't have a vendor/ID value, but only contain a single value. ACPI/PNP devices should be placed in /images/pnp/XXXXXX.
For Example, a driver for the Dell Freefall sensor is ACPI\SMO8810 in Device Manager. Place the driver in /images/pnp/SMO8810.

*Tip for keeping driver folders reasonably sized: Very often drivers are bloated and come with a lot more than what Windows minimally needs to get the device working. Often there's an executable that installs a tray application, etc. As for the actual driver, it's often found inside of a subfolder like \Win7\driver\x64. When adding a driver, you can usually just grab the subfolder that contains the files you need. You can test this by putting that folder on a USB stick, and going to a system that's missing the driver. In Device Manager, point to the folder and see if it will update successfully. ("Real" driver folders contain .inf, .cat, .sys, .man files)

===Adding Silent Install drivers===
*Drivers that require an executable to be run can also be included in this method provided the driver has a silent install option with no user interaction.
*If there is a drvinstall.bat file inside the driver folder, the script will take the contents of the bat file and add it to the end of the SetupComplete.cmd file to be executed at the end of the sysprep process. See the example contents of:
echo Driver for SMO8810
start/wait C:\drivers\pnp\SMO8810\setup.exe /s
*This is handy for devices that aren't detected by Device Manager's Update Driver. Devices that operate this way for us have been some sound cards, freefall sensors, touchscreen calibration tools, etc.

==Install Script==
*There are two files you'll need to add to /images/postdownloadscripts/
*machinedrivers.sh
#!/bin/bash
#machineinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#http://www.fogproject.org/wiki/index.php/Auto_driver_Install
#Andrew Single - Frontier School Division (Frontier loves FOG!)

oIFS=$IFS;
getDeviceName()
{
# echo "lspci -mm -d $1";
local devnamefull=`lspci -mm -d $1`;
devnamefull=${devnamefull//\" \"/¤};
IFS=¤;
pciDescr=($devnamefull);
IFS=$oIFS;
}
#Read PCI Device strings
pci=`lspci -n |cut -c 15-23`;
usb=`lsusb |cut -c 23-32`;
last="";
for device in $pci
do
#filter for unique devices
if [ "$device" != "$last" ]; then
last=$device;
#Split up vendor & Device IDs
dMfg=${device:0:4};
dDev=${device:5:4};
# echo "Device: $device";
# echo "Mfg: $dMfg - Dev: $dDev";
# sleep 1;
drvLoc="/images/drivers/$dMfg/$dDev";
#Does the driver folder exist?
if [ -d $drvLoc ];then
#Copy files
# echo $device;
getDeviceName $device;
echo -n " * Copying ${pciDescr[4]} ";
#Does the vendor folder exist?
if [ -d /ntfs/Drivers/$dMfg ]; then
cp -r $drvLoc /ntfs/Drivers/$dMfg
else
mkdir /ntfs/Drivers/$dMfg
cp -r $drvLoc /ntfs/Drivers/$dMfg
fi
if [ -f $drvLoc/drvinstall.bat ]; then
cat $drvLoc/drvinstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
fi
echo "Done.";
fi
fi
done
IFS='
*And driverinstall.sh
#!/bin/sh
#driverinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#Andrew Single - Frontier School Division (Frontier loves FOG!)

win7sys="/dev/sda2";
mkdir /ntfs 2>/dev/null

echo -n " * Mounting Windows File System...................";
mount.ntfs-3g $win7sys /ntfs 2>/tmp/mntfail
mntRet="$?";
if [ ! "$mntRet" = "0" ]
then
echo "Failed to mount C:";
echo "";
echo -n " * ";
cat /tmp/mntfail
echo "";
sleep 2;
else #Mount successful
echo "Done.";
mkdir /ntfs/Drivers 2>/dev/null
echo "";
echo -n " * Copying Common Drivers.........................";
cp -r /images/drivers/Common /ntfs/Drivers
if [ -d /ntfs/Windows/Setup/Scripts ]; then
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
else
mkdir /ntfs/Windows/Setup/Scripts
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
fi
#Needs to be exectued with bash
bash /images/postdownloadscripts/machinedrivers.sh
echo " ";
echo " * Driver copy completed.";
umount /ntfs
sleep 5;
fi
*Make them executable with
chmod a+x *.sh
*Finally, edit the fog.postdownload file and the following to the end of the file:
${postdownpath}/driverinstall.sh

==Building the Universal Image==
*The script requires a sysprepped Windows 7 image to work. If you're not using Sysprep, this process won't work.
*Include driver search path to C:\Drivers (See: http://technet.microsoft.com/en-ca/library/cc753716.aspx)

==Notes for Andrew Single==
In Progress: Documentation for adding the Auto Driver install script from Frontier School Division.
Script To Do:
*Make device ID's all lower case so PNP devices don't require upper case folder names & are consistent with all lower case.

Auto driver Install

2014-11-03T00:04:25Z

Andrew.single: /* Adding Windows Device Drivers */

Overview: The Auto Driver install script is an addition for FOG that allows you to build a hardware independent Windows 7 image. Devices on the system will be detected by FOG, and drivers inserted into C:\Drivers from a repository on the FOG server. Windows will then use that as an additional driver search path when doing Sysprep first run.

Why do this? When you're managing thousands of machines from a variety of models with differing driver requirements making a single image that has everything you need is nearly impossible. In the past we would make images specific to each model of computer, but it means that we maintained about 10 different images. That means that updating the image was a lot of work, and simply didn't get done very often. By separating the image from the drivers, you gain a lot of flexibility, and can respond to changes very quickly.

For example, let's say a new model of desktop comes your way. With this system, all you do is image it once as is, take a look at Device manager to see what drivers it needs, and then place those drivers on the FOG server. Now all machines with the same hardware will have the drivers installed during the sysprep process. Another common scenario is that some machines have a special card added to them. Maybe it's a video card, or firewire card. Rather than building a new image, or multiple new images, simply include the driver, and any system with that card present will pull it post imaging.

==Setup Repository==
*Create a folder inside of /images named drivers
mkdir /images/drivers
*Create a Common folder for drivers/scripts you want on all systems.
mkdir /images/drivers/Common
*Create a SetupComplete.cmd file. (See: http://technet.microsoft.com/en-ca/library/cc766314%28v=ws.10%29.aspx)
*This is a script, that when copied to C:\Windows\Setup\Scripts is executed at the end of the SysPrep process. The Frontier script stops the FOG service, runs a netsh command to push out a wlan profile, deletes the profile xml file, the sysprep.xml and fixes the permissions on the C:\drivers folder. It's a quite useful tool to use. I recommend at least having:
net STOP "Fog Service"
start "Reset C:\Drivers Perms" /wait "icacls" C:\drivers /reset /T >>"C:\FOGDrivers.log" 2>&1

===Adding Windows Device Drivers===
*The script currently detects three categories of Drivers: PCI, USB & ACPI.
*The first step is to identify the device that you want to install. On an imaged Windows 7 machine, go to device Manager.
**Right click the device, and go to Properties.
**Click the details tab, and go to the Hardware IDs dropdown.
**You'll see something like PCI\VEN_XXXX&Dev_YYYY&SUBSYS_ZZZZ.... or USB\VID_XXXX&PID_YYYY or ACPI\XXXXXXXXX
***You take the driver for that device, and place it in a folder of /images/drivers/XXXX/YYYY.
For Example, a driver for Intel Video with a device ID of PCI\VEN_8086&DEV_5A3C would be in the folder /images/drivers/8086/5a3c **Note that it's lower case.
***In the case of a drivers that contains drivers for multiple devices (Ie: Chipset) you don't need to break out each individual device. You can simply make the folder match one of the devices.
***ACPI devices don't have a vendor/ID value, but only contain a single value. ACPI/PNP devices should be placed in /images/pnp/XXXXXX.
For Example, a driver for the Dell Freefall sensor is ACPI\SMO8810 in Device Manager. Place the driver in /images/pnp/SMO8810.

*Tip for keeping driver folders reasonably sized: Very often drivers are bloated and come with a lot more than what Windows minimally needs to get the device working. Often there's an executable that installs a tray application, etc. As for the actual driver, it's often found inside of a subfolder like \Win7\driver\x64. When adding a driver, you can usually just grab the subfolder that contains the files you need. You can test this by putting that folder on a USB stick, and going to a system that's missing the driver. In Device Manager, point to the folder and see if it will update successfully. ("Real" driver folders contain .inf, .cat, .sys, .man files)

===Adding Silent Install drivers===
*Drivers that require an executable to be run can also be included in this method provided the driver has a silent install option with no user interaction.
*If there is a drvinstall.bat file inside the driver folder, the script will take the contents of the bat file and add it to the end of the SetupComplete.cmd file to be executed at the end of the sysprep process. See the example contents of:
echo Driver for SMO8810
start/wait C:\drivers\pnp\SMO8810\setup.exe /s
*This is handy for devices that aren't detected by Device Manager's Update Driver. Devices that operate this way for us have been some sound cards, freefall sensors, touchscreen calibration tools, etc.

==Install Script==
*There are two files you'll need to add to /images/postdownloadscripts/
*machinedrivers.sh
#!/bin/bash
#machineinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#http://www.fogproject.org/wiki/index.php/Auto_driver_Install
#Andrew Single - Frontier School Division (Frontier loves FOG!)

oIFS=$IFS;
getDeviceName()
{
# echo "lspci -mm -d $1";
local devnamefull=`lspci -mm -d $1`;
devnamefull=${devnamefull//\" \"/¤};
IFS=¤;
pciDescr=($devnamefull);
IFS=$oIFS;
}
#Read PCI Device strings
pci=`lspci -n |cut -c 15-23`;
usb=`lsusb |cut -c 23-32`;
last="";
for device in $pci
do
#filter for unique devices
if [ "$device" != "$last" ]; then
last=$device;
#Split up vendor & Device IDs
dMfg=${device:0:4};
dDev=${device:5:4};
# echo "Device: $device";
# echo "Mfg: $dMfg - Dev: $dDev";
# sleep 1;
drvLoc="/images/drivers/$dMfg/$dDev";
#Does the driver folder exist?
if [ -d $drvLoc ];then
#Copy files
# echo $device;
getDeviceName $device;
echo -n " * Copying ${pciDescr[4]} ";
#Does the vendor folder exist?
if [ -d /ntfs/Drivers/$dMfg ]; then
cp -r $drvLoc /ntfs/Drivers/$dMfg
else
mkdir /ntfs/Drivers/$dMfg
cp -r $drvLoc /ntfs/Drivers/$dMfg
fi
if [ -f $drvLoc/drvinstall.bat ]; then
cat $drvLoc/drvinstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
fi
echo "Done.";
fi
fi
done
IFS='
*And driverinstall.sh
#!/bin/sh
#driverinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#Andrew Single - Frontier School Division (Frontier loves FOG!)

win7sys="/dev/sda2";
mkdir /ntfs 2>/dev/null

echo -n " * Mounting Windows File System...................";
mount.ntfs-3g $win7sys /ntfs 2>/tmp/mntfail
mntRet="$?";
if [ ! "$mntRet" = "0" ]
then
echo "Failed to mount C:";
echo "";
echo -n " * ";
cat /tmp/mntfail
echo "";
sleep 2;
else #Mount successful
echo "Done.";
mkdir /ntfs/Drivers 2>/dev/null
echo "";
echo -n " * Copying Common Drivers.........................";
cp -r /images/drivers/Common /ntfs/Drivers
if [ -d /ntfs/Windows/Setup/Scripts ]; then
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
else
mkdir /ntfs/Windows/Setup/Scripts
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
fi
#Needs to be exectued with bash
bash /images/postdownloadscripts/machinedrivers.sh
echo " ";
echo " * Driver copy completed.";
umount /ntfs
sleep 10;
fi
*Make them executable with
chmod a+x *.sh
*Finally, edit the fog.postdownload file and the following to the end of the file:
${postdownpath}/driverinstall.sh

==Building the Universal Image==
*The script requires a sysprepped Windows 7 image to work. If you're not using Sysprep, this process won't work.
*Include driver search path to C:\Drivers (See: http://technet.microsoft.com/en-ca/library/cc753716.aspx)

==Notes for Andrew Single==
In Progress: Documentation for adding the Auto Driver install script from Frontier School Division.
Script To Do:
*Make device ID's all lower case so PNP devices don't require upper case folder names & are consistent with all lower case.

Auto driver Install

2014-11-02T23:50:33Z

Andrew.single:

Overview: The Auto Driver install script is an addition for FOG that allows you to build a hardware independent Windows 7 image. Devices on the system will be detected by FOG, and drivers inserted into C:\Drivers from a repository on the FOG server. Windows will then use that as an additional driver search path when doing Sysprep first run.

Why do this? When you're managing thousands of machines from a variety of models with differing driver requirements making a single image that has everything you need is nearly impossible. In the past we would make images specific to each model of computer, but it means that we maintained about 10 different images. That means that updating the image was a lot of work, and simply didn't get done very often. By separating the image from the drivers, you gain a lot of flexibility, and can respond to changes very quickly.

For example, let's say a new model of desktop comes your way. With this system, all you do is image it once as is, take a look at Device manager to see what drivers it needs, and then place those drivers on the FOG server. Now all machines with the same hardware will have the drivers installed during the sysprep process. Another common scenario is that some machines have a special card added to them. Maybe it's a video card, or firewire card. Rather than building a new image, or multiple new images, simply include the driver, and any system with that card present will pull it post imaging.

==Setup Repository==
*Create a folder inside of /images named drivers
mkdir /images/drivers
*Create a Common folder for drivers/scripts you want on all systems.
mkdir /images/drivers/Common
*Create a SetupComplete.cmd file. (See: http://technet.microsoft.com/en-ca/library/cc766314%28v=ws.10%29.aspx)
*This is a script, that when copied to C:\Windows\Setup\Scripts is executed at the end of the SysPrep process. The Frontier script stops the FOG service, runs a netsh command to push out a wlan profile, deletes the profile xml file, the sysprep.xml and fixes the permissions on the C:\drivers folder. It's a quite useful tool to use. I recommend at least having:
net STOP "Fog Service"
start "Reset C:\Drivers Perms" /wait "icacls" C:\drivers /reset /T >>"C:\FOGDrivers.log" 2>&1

===Adding Windows Device Drivers===
*The script currently detects three categories of Drivers: PCI, USB & ACPI.
*The first step is to identify the device that you want to install. On an imaged Windows 7 machine, go to device Manager.
**Right click the device, and go to Properties.
**Click the details tab, and go to the Hardware IDs dropdown.
**You'll see something like PCI\VEN_XXXX&Dev_YYYY&SUBSYS_ZZZZ.... or USB\VID_XXXX&PID_YYYY or ACPI\XXXXXXXXX
***You take the driver for that device, and place it in a folder of /images/drivers/XXXX/YYYY.
For Example, a driver for Intel Video with a device ID of PCI\VEN_8086&DEV_5A3C would be in the folder /images/drivers/8086/5a3c **Note that it's lower case.
***In the case of a drivers that contains drivers for multiple devices (Ie: Chipset) you don't need to break out each individual device. You can simply make the folder match one of the devices.
***ACPI devices don't have a vendor/ID value, but only contain a single value. ACPI/PNP devices should be placed in /images/pnp/XXXXXX.
For Example, a driver for the Dell Freefall sensor is ACPI\SMO8810 in Device Manager. Place the driver in /images/pnp/SMO8810.

===Adding Silent Install drivers===
*Drivers that require an executable to be run can also be included in this method provided the driver has a silent install option with no user interaction.
*If there is a drvinstall.bat file inside the driver folder, the script will take the contents of the bat file and add it to the end of the SetupComplete.cmd file to be executed at the end of the sysprep process. See the example contents of:
echo Driver for SMO8810
start/wait C:\drivers\pnp\SMO8810\setup.exe /s
*This is handy for devices that aren't detected by Device Manager's Update Driver. Devices that operate this way for us have been some sound cards, freefall sensors, touchscreen calibration tools, etc.

==Install Script==
*There are two files you'll need to add to /images/postdownloadscripts/
*machinedrivers.sh
#!/bin/bash
#machineinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#http://www.fogproject.org/wiki/index.php/Auto_driver_Install
#Andrew Single - Frontier School Division (Frontier loves FOG!)

oIFS=$IFS;
getDeviceName()
{
# echo "lspci -mm -d $1";
local devnamefull=`lspci -mm -d $1`;
devnamefull=${devnamefull//\" \"/¤};
IFS=¤;
pciDescr=($devnamefull);
IFS=$oIFS;
}
#Read PCI Device strings
pci=`lspci -n |cut -c 15-23`;
usb=`lsusb |cut -c 23-32`;
last="";
for device in $pci
do
#filter for unique devices
if [ "$device" != "$last" ]; then
last=$device;
#Split up vendor & Device IDs
dMfg=${device:0:4};
dDev=${device:5:4};
# echo "Device: $device";
# echo "Mfg: $dMfg - Dev: $dDev";
# sleep 1;
drvLoc="/images/drivers/$dMfg/$dDev";
#Does the driver folder exist?
if [ -d $drvLoc ];then
#Copy files
# echo $device;
getDeviceName $device;
echo -n " * Copying ${pciDescr[4]} ";
#Does the vendor folder exist?
if [ -d /ntfs/Drivers/$dMfg ]; then
cp -r $drvLoc /ntfs/Drivers/$dMfg
else
mkdir /ntfs/Drivers/$dMfg
cp -r $drvLoc /ntfs/Drivers/$dMfg
fi
if [ -f $drvLoc/drvinstall.bat ]; then
cat $drvLoc/drvinstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
fi
echo "Done.";
fi
fi
done
IFS='
*And driverinstall.sh
#!/bin/sh
#driverinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#Andrew Single - Frontier School Division (Frontier loves FOG!)

win7sys="/dev/sda2";
mkdir /ntfs 2>/dev/null

echo -n " * Mounting Windows File System...................";
mount.ntfs-3g $win7sys /ntfs 2>/tmp/mntfail
mntRet="$?";
if [ ! "$mntRet" = "0" ]
then
echo "Failed to mount C:";
echo "";
echo -n " * ";
cat /tmp/mntfail
echo "";
sleep 2;
else #Mount successful
echo "Done.";
mkdir /ntfs/Drivers 2>/dev/null
echo "";
echo -n " * Copying Common Drivers.........................";
cp -r /images/drivers/Common /ntfs/Drivers
if [ -d /ntfs/Windows/Setup/Scripts ]; then
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
else
mkdir /ntfs/Windows/Setup/Scripts
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
fi
#Needs to be exectued with bash
bash /images/postdownloadscripts/machinedrivers.sh
echo " ";
echo " * Driver copy completed.";
umount /ntfs
sleep 10;
fi
*Make them executable with
chmod a+x *.sh
*Finally, edit the fog.postdownload file and the following to the end of the file:
${postdownpath}/driverinstall.sh

==Building the Universal Image==
*The script requires a sysprepped Windows 7 image to work. If you're not using Sysprep, this process won't work.
*Include driver search path to C:\Drivers (See: http://technet.microsoft.com/en-ca/library/cc753716.aspx)

==Notes for Andrew Single==
In Progress: Documentation for adding the Auto Driver install script from Frontier School Division.
Script To Do:
*Make device ID's all lower case so PNP devices don't require upper case folder names & are consistent with all lower case.

Auto driver Install

2014-11-02T23:43:22Z

Andrew.single: /* Building the Universal Image */

In Progress: Documentation for adding the Auto Driver install script from Frontier School Division.
Script To Do:
*Make device ID's all lower case so PNP devices don't require upper case folder names & are consistent with all lower case.

Overview: The Auto Driver install script is an addon for FOG that allows you to build a hardware independent Windows 7 image. Devices on the system will be detected by FOG, and drivers inserted into C:\Drivers. Windows will then use that as an additional driver search path when doing Sysprep first run.

==Setup Repository==
*Create a folder inside of /images named drivers
mkdir /images/drivers
*Create a Common folder for drivers/scripts you want on all systems.
mkdir /images/drivers/Common
*Create a SetupComplete.cmd file. (See: http://technet.microsoft.com/en-ca/library/cc766314%28v=ws.10%29.aspx)
*This is a script, that when copied to C:\Windows\Setup\Scripts is executed at the end of the SysPrep process. The Frontier script stops the FOG service, runs a netsh command to push out a wlan profile, deletes the profile xml file, the sysprep.xml and fixes the permissions on the C:\drivers folder. It's a quite useful tool to use. I recommend at least having:
net STOP "Fog Service"
start "Reset C:\Drivers Perms" /wait "icacls" C:\drivers /reset /T >>"C:\FOGDrivers.log" 2>&1

===Adding Windows Device Drivers===
*The script currently detects three categories of Drivers: PCI, USB & ACPI.
*The first step is to identify the device that you want to install. On an imaged Windows 7 machine, go to device Manager.
**Right click the device, and go to Properties.
**Click the details tab, and go to the Hardware IDs dropdown.
**You'll see something like PCI\VEN_XXXX&Dev_YYYY&SUBSYS_ZZZZ.... or USB\VID_XXXX&PID_YYYY or ACPI\XXXXXXXXX
***You take the driver for that device, and place it in a folder of /images/drivers/XXXX/YYYY.
For Example, a driver for Intel Video with a device ID of PCI\VEN_8086&DEV_5A3C would be in the folder /images/drivers/8086/5a3c **Note that it's lower case.
***In the case of a drivers that contains drivers for multiple devices (Ie: Chipset) you don't need to break out each individual device. You can simply make the folder match one of the devices.
***ACPI devices don't have a vendor/ID value, but only contain a single value. ACPI/PNP devices should be placed in /images/pnp/XXXXXX.
For Example, a driver for the Dell Freefall sensor is ACPI\SMO8810 in Device Manager. Place the driver in /images/pnp/SMO8810.

===Adding Silent Install drivers===
*Drivers that require an executable to be run can also be included in this method provided the driver has a silent install option with no user interaction.
*If there is a drvinstall.bat file inside the driver folder, the script will take the contents of the bat file and add it to the end of the SetupComplete.cmd file to be executed at the end of the sysprep process. See the example contents of:
echo Driver for SMO8810
start/wait C:\drivers\pnp\SMO8810\setup.exe /s
*This is handy for devices that aren't detected by Device Manager's Update Driver. Devices that operate this way for us have been some sound cards, freefall sensors, touchscreen calibration tools, etc.

==Install Script==
*There are two files you'll need to add to /images/postdownloadscripts/
*machinedrivers.sh
#!/bin/bash
#machineinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#http://www.fogproject.org/wiki/index.php/Auto_driver_Install
#Andrew Single - Frontier School Division (Frontier loves FOG!)

oIFS=$IFS;
getDeviceName()
{
# echo "lspci -mm -d $1";
local devnamefull=`lspci -mm -d $1`;
devnamefull=${devnamefull//\" \"/¤};
IFS=¤;
pciDescr=($devnamefull);
IFS=$oIFS;
}
#Read PCI Device strings
pci=`lspci -n |cut -c 15-23`;
usb=`lsusb |cut -c 23-32`;
last="";
for device in $pci
do
#filter for unique devices
if [ "$device" != "$last" ]; then
last=$device;
#Split up vendor & Device IDs
dMfg=${device:0:4};
dDev=${device:5:4};
# echo "Device: $device";
# echo "Mfg: $dMfg - Dev: $dDev";
# sleep 1;
drvLoc="/images/drivers/$dMfg/$dDev";
#Does the driver folder exist?
if [ -d $drvLoc ];then
#Copy files
# echo $device;
getDeviceName $device;
echo -n " * Copying ${pciDescr[4]} ";
#Does the vendor folder exist?
if [ -d /ntfs/Drivers/$dMfg ]; then
cp -r $drvLoc /ntfs/Drivers/$dMfg
else
mkdir /ntfs/Drivers/$dMfg
cp -r $drvLoc /ntfs/Drivers/$dMfg
fi
if [ -f $drvLoc/drvinstall.bat ]; then
cat $drvLoc/drvinstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
fi
echo "Done.";
fi
fi
done
IFS='
*And driverinstall.sh
#!/bin/sh
#driverinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#Andrew Single - Frontier School Division (Frontier loves FOG!)

win7sys="/dev/sda2";
mkdir /ntfs 2>/dev/null

echo -n " * Mounting Windows File System...................";
mount.ntfs-3g $win7sys /ntfs 2>/tmp/mntfail
mntRet="$?";
if [ ! "$mntRet" = "0" ]
then
echo "Failed to mount C:";
echo "";
echo -n " * ";
cat /tmp/mntfail
echo "";
sleep 2;
else #Mount successful
echo "Done.";
mkdir /ntfs/Drivers 2>/dev/null
echo "";
echo -n " * Copying Common Drivers.........................";
cp -r /images/drivers/Common /ntfs/Drivers
if [ -d /ntfs/Windows/Setup/Scripts ]; then
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
else
mkdir /ntfs/Windows/Setup/Scripts
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
fi
#Needs to be exectued with bash
bash /images/postdownloadscripts/machinedrivers.sh
echo " ";
echo " * Driver copy completed.";
umount /ntfs
sleep 10;
fi
*Make them executable with
chmod a+x *.sh
*Finally, edit the fog.postdownload file and the following to the end of the file:
${postdownpath}/driverinstall.sh

==Building the Universal Image==
*The script requires a sysprepped Windows 7 image to work. If you're not using Sysprep, this process won't work.
*Include driver search path to C:\Drivers (See: http://technet.microsoft.com/en-ca/library/cc753716.aspx)

Auto driver Install

2014-11-02T23:41:11Z

Andrew.single: /* Setup Repository */

In Progress: Documentation for adding the Auto Driver install script from Frontier School Division.
Script To Do:
*Make device ID's all lower case so PNP devices don't require upper case folder names & are consistent with all lower case.

Overview: The Auto Driver install script is an addon for FOG that allows you to build a hardware independent Windows 7 image. Devices on the system will be detected by FOG, and drivers inserted into C:\Drivers. Windows will then use that as an additional driver search path when doing Sysprep first run.

==Setup Repository==
*Create a folder inside of /images named drivers
mkdir /images/drivers
*Create a Common folder for drivers/scripts you want on all systems.
mkdir /images/drivers/Common
*Create a SetupComplete.cmd file. (See: http://technet.microsoft.com/en-ca/library/cc766314%28v=ws.10%29.aspx)
*This is a script, that when copied to C:\Windows\Setup\Scripts is executed at the end of the SysPrep process. The Frontier script stops the FOG service, runs a netsh command to push out a wlan profile, deletes the profile xml file, the sysprep.xml and fixes the permissions on the C:\drivers folder. It's a quite useful tool to use. I recommend at least having:
net STOP "Fog Service"
start "Reset C:\Drivers Perms" /wait "icacls" C:\drivers /reset /T >>"C:\FOGDrivers.log" 2>&1

===Adding Windows Device Drivers===
*The script currently detects three categories of Drivers: PCI, USB & ACPI.
*The first step is to identify the device that you want to install. On an imaged Windows 7 machine, go to device Manager.
**Right click the device, and go to Properties.
**Click the details tab, and go to the Hardware IDs dropdown.
**You'll see something like PCI\VEN_XXXX&Dev_YYYY&SUBSYS_ZZZZ.... or USB\VID_XXXX&PID_YYYY or ACPI\XXXXXXXXX
***You take the driver for that device, and place it in a folder of /images/drivers/XXXX/YYYY.
For Example, a driver for Intel Video with a device ID of PCI\VEN_8086&DEV_5A3C would be in the folder /images/drivers/8086/5a3c **Note that it's lower case.
***In the case of a drivers that contains drivers for multiple devices (Ie: Chipset) you don't need to break out each individual device. You can simply make the folder match one of the devices.
***ACPI devices don't have a vendor/ID value, but only contain a single value. ACPI/PNP devices should be placed in /images/pnp/XXXXXX.
For Example, a driver for the Dell Freefall sensor is ACPI\SMO8810 in Device Manager. Place the driver in /images/pnp/SMO8810.

===Adding Silent Install drivers===
*Drivers that require an executable to be run can also be included in this method provided the driver has a silent install option with no user interaction.
*If there is a drvinstall.bat file inside the driver folder, the script will take the contents of the bat file and add it to the end of the SetupComplete.cmd file to be executed at the end of the sysprep process. See the example contents of:
echo Driver for SMO8810
start/wait C:\drivers\pnp\SMO8810\setup.exe /s
*This is handy for devices that aren't detected by Device Manager's Update Driver. Devices that operate this way for us have been some sound cards, freefall sensors, touchscreen calibration tools, etc.

==Install Script==
*There are two files you'll need to add to /images/postdownloadscripts/
*machinedrivers.sh
#!/bin/bash
#machineinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#http://www.fogproject.org/wiki/index.php/Auto_driver_Install
#Andrew Single - Frontier School Division (Frontier loves FOG!)

oIFS=$IFS;
getDeviceName()
{
# echo "lspci -mm -d $1";
local devnamefull=`lspci -mm -d $1`;
devnamefull=${devnamefull//\" \"/¤};
IFS=¤;
pciDescr=($devnamefull);
IFS=$oIFS;
}
#Read PCI Device strings
pci=`lspci -n |cut -c 15-23`;
usb=`lsusb |cut -c 23-32`;
last="";
for device in $pci
do
#filter for unique devices
if [ "$device" != "$last" ]; then
last=$device;
#Split up vendor & Device IDs
dMfg=${device:0:4};
dDev=${device:5:4};
# echo "Device: $device";
# echo "Mfg: $dMfg - Dev: $dDev";
# sleep 1;
drvLoc="/images/drivers/$dMfg/$dDev";
#Does the driver folder exist?
if [ -d $drvLoc ];then
#Copy files
# echo $device;
getDeviceName $device;
echo -n " * Copying ${pciDescr[4]} ";
#Does the vendor folder exist?
if [ -d /ntfs/Drivers/$dMfg ]; then
cp -r $drvLoc /ntfs/Drivers/$dMfg
else
mkdir /ntfs/Drivers/$dMfg
cp -r $drvLoc /ntfs/Drivers/$dMfg
fi
if [ -f $drvLoc/drvinstall.bat ]; then
cat $drvLoc/drvinstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
fi
echo "Done.";
fi
fi
done
IFS='
*And driverinstall.sh
#!/bin/sh
#driverinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#Andrew Single - Frontier School Division (Frontier loves FOG!)

win7sys="/dev/sda2";
mkdir /ntfs 2>/dev/null

echo -n " * Mounting Windows File System...................";
mount.ntfs-3g $win7sys /ntfs 2>/tmp/mntfail
mntRet="$?";
if [ ! "$mntRet" = "0" ]
then
echo "Failed to mount C:";
echo "";
echo -n " * ";
cat /tmp/mntfail
echo "";
sleep 2;
else #Mount successful
echo "Done.";
mkdir /ntfs/Drivers 2>/dev/null
echo "";
echo -n " * Copying Common Drivers.........................";
cp -r /images/drivers/Common /ntfs/Drivers
if [ -d /ntfs/Windows/Setup/Scripts ]; then
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
else
mkdir /ntfs/Windows/Setup/Scripts
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
fi
#Needs to be exectued with bash
bash /images/postdownloadscripts/machinedrivers.sh
echo " ";
echo " * Driver copy completed.";
umount /ntfs
sleep 10;
fi
*Make them executable with
chmod a+x *.sh
*Finally, edit the fog.postdownload file and the following to the end of the file:
${postdownpath}/driverinstall.sh

==Building the Universal Image==
*Include driver search path to C:\Drivers (Detect it in the script maybe and add the reg entry if it's missing?)

Auto driver Install

2014-11-02T23:40:04Z

Andrew.single: /* Install Script */

In Progress: Documentation for adding the Auto Driver install script from Frontier School Division.
Script To Do:
*Make device ID's all lower case so PNP devices don't require upper case folder names & are consistent with all lower case.

Overview: The Auto Driver install script is an addon for FOG that allows you to build a hardware independent Windows 7 image. Devices on the system will be detected by FOG, and drivers inserted into C:\Drivers. Windows will then use that as an additional driver search path when doing Sysprep first run.

==Setup Repository==
*Create a folder inside of /images named drivers
mkdir /images/drivers
*Create a Common folder for drivers/scripts you want on all systems.
mkdir /images/drivers/Common
*Create a SetupComplete.cmd file. This is a script, that when copied to C:\Windows\Setup\Scripts is executed at the end of the SysPrep process. The Frontier script stops the FOG service, runs a netsh command to push out a wlan profile, deletes the profile xml file, the sysprep.xml and fixes the permissions on the C:\drivers folder. It's a quite useful tool to use. I recommend at least having:
net STOP "Fog Service"
start "Reset C:\Drivers Perms" /wait "icacls" C:\drivers /reset /T >>"C:\FOGDrivers.log" 2>&1

===Adding Windows Device Drivers===
*The script currently detects three categories of Drivers: PCI, USB & ACPI.
*The first step is to identify the device that you want to install. On an imaged Windows 7 machine, go to device Manager.
**Right click the device, and go to Properties.
**Click the details tab, and go to the Hardware IDs dropdown.
**You'll see something like PCI\VEN_XXXX&Dev_YYYY&SUBSYS_ZZZZ.... or USB\VID_XXXX&PID_YYYY or ACPI\XXXXXXXXX
***You take the driver for that device, and place it in a folder of /images/drivers/XXXX/YYYY.
For Example, a driver for Intel Video with a device ID of PCI\VEN_8086&DEV_5A3C would be in the folder /images/drivers/8086/5a3c **Note that it's lower case.
***In the case of a drivers that contains drivers for multiple devices (Ie: Chipset) you don't need to break out each individual device. You can simply make the folder match one of the devices.
***ACPI devices don't have a vendor/ID value, but only contain a single value. ACPI/PNP devices should be placed in /images/pnp/XXXXXX.
For Example, a driver for the Dell Freefall sensor is ACPI\SMO8810 in Device Manager. Place the driver in /images/pnp/SMO8810.

===Adding Silent Install drivers===
*Drivers that require an executable to be run can also be included in this method provided the driver has a silent install option with no user interaction.
*If there is a drvinstall.bat file inside the driver folder, the script will take the contents of the bat file and add it to the end of the SetupComplete.cmd file to be executed at the end of the sysprep process. See the example contents of:
echo Driver for SMO8810
start/wait C:\drivers\pnp\SMO8810\setup.exe /s
*This is handy for devices that aren't detected by Device Manager's Update Driver. Devices that operate this way for us have been some sound cards, freefall sensors, touchscreen calibration tools, etc.
==Install Script==
*There are two files you'll need to add to /images/postdownloadscripts/
*machinedrivers.sh
#!/bin/bash
#machineinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#http://www.fogproject.org/wiki/index.php/Auto_driver_Install
#Andrew Single - Frontier School Division (Frontier loves FOG!)

oIFS=$IFS;
getDeviceName()
{
# echo "lspci -mm -d $1";
local devnamefull=`lspci -mm -d $1`;
devnamefull=${devnamefull//\" \"/¤};
IFS=¤;
pciDescr=($devnamefull);
IFS=$oIFS;
}
#Read PCI Device strings
pci=`lspci -n |cut -c 15-23`;
usb=`lsusb |cut -c 23-32`;
last="";
for device in $pci
do
#filter for unique devices
if [ "$device" != "$last" ]; then
last=$device;
#Split up vendor & Device IDs
dMfg=${device:0:4};
dDev=${device:5:4};
# echo "Device: $device";
# echo "Mfg: $dMfg - Dev: $dDev";
# sleep 1;
drvLoc="/images/drivers/$dMfg/$dDev";
#Does the driver folder exist?
if [ -d $drvLoc ];then
#Copy files
# echo $device;
getDeviceName $device;
echo -n " * Copying ${pciDescr[4]} ";
#Does the vendor folder exist?
if [ -d /ntfs/Drivers/$dMfg ]; then
cp -r $drvLoc /ntfs/Drivers/$dMfg
else
mkdir /ntfs/Drivers/$dMfg
cp -r $drvLoc /ntfs/Drivers/$dMfg
fi
if [ -f $drvLoc/drvinstall.bat ]; then
cat $drvLoc/drvinstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
fi
echo "Done.";
fi
fi
done
IFS='
*And driverinstall.sh
#!/bin/sh
#driverinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#Andrew Single - Frontier School Division (Frontier loves FOG!)

win7sys="/dev/sda2";
mkdir /ntfs 2>/dev/null

echo -n " * Mounting Windows File System...................";
mount.ntfs-3g $win7sys /ntfs 2>/tmp/mntfail
mntRet="$?";
if [ ! "$mntRet" = "0" ]
then
echo "Failed to mount C:";
echo "";
echo -n " * ";
cat /tmp/mntfail
echo "";
sleep 2;
else #Mount successful
echo "Done.";
mkdir /ntfs/Drivers 2>/dev/null
echo "";
echo -n " * Copying Common Drivers.........................";
cp -r /images/drivers/Common /ntfs/Drivers
if [ -d /ntfs/Windows/Setup/Scripts ]; then
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
else
mkdir /ntfs/Windows/Setup/Scripts
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
fi
#Needs to be exectued with bash
bash /images/postdownloadscripts/machinedrivers.sh
echo " ";
echo " * Driver copy completed.";
umount /ntfs
sleep 10;
fi
*Make them executable with
chmod a+x *.sh
*Finally, edit the fog.postdownload file and the following to the end of the file:
${postdownpath}/driverinstall.sh

==Building the Universal Image==
*Include driver search path to C:\Drivers (Detect it in the script maybe and add the reg entry if it's missing?)

Auto driver Install

2014-11-02T23:38:11Z

Andrew.single: /* Install Script */

In Progress: Documentation for adding the Auto Driver install script from Frontier School Division.
Script To Do:
*Make device ID's all lower case so PNP devices don't require upper case folder names & are consistent with all lower case.

Overview: The Auto Driver install script is an addon for FOG that allows you to build a hardware independent Windows 7 image. Devices on the system will be detected by FOG, and drivers inserted into C:\Drivers. Windows will then use that as an additional driver search path when doing Sysprep first run.

==Setup Repository==
*Create a folder inside of /images named drivers
mkdir /images/drivers
*Create a Common folder for drivers/scripts you want on all systems.
mkdir /images/drivers/Common
*Create a SetupComplete.cmd file. This is a script, that when copied to C:\Windows\Setup\Scripts is executed at the end of the SysPrep process. The Frontier script stops the FOG service, runs a netsh command to push out a wlan profile, deletes the profile xml file, the sysprep.xml and fixes the permissions on the C:\drivers folder. It's a quite useful tool to use. I recommend at least having:
net STOP "Fog Service"
start "Reset C:\Drivers Perms" /wait "icacls" C:\drivers /reset /T >>"C:\FOGDrivers.log" 2>&1

===Adding Windows Device Drivers===
*The script currently detects three categories of Drivers: PCI, USB & ACPI.
*The first step is to identify the device that you want to install. On an imaged Windows 7 machine, go to device Manager.
**Right click the device, and go to Properties.
**Click the details tab, and go to the Hardware IDs dropdown.
**You'll see something like PCI\VEN_XXXX&Dev_YYYY&SUBSYS_ZZZZ.... or USB\VID_XXXX&PID_YYYY or ACPI\XXXXXXXXX
***You take the driver for that device, and place it in a folder of /images/drivers/XXXX/YYYY.
For Example, a driver for Intel Video with a device ID of PCI\VEN_8086&DEV_5A3C would be in the folder /images/drivers/8086/5a3c **Note that it's lower case.
***In the case of a drivers that contains drivers for multiple devices (Ie: Chipset) you don't need to break out each individual device. You can simply make the folder match one of the devices.
***ACPI devices don't have a vendor/ID value, but only contain a single value. ACPI/PNP devices should be placed in /images/pnp/XXXXXX.
For Example, a driver for the Dell Freefall sensor is ACPI\SMO8810 in Device Manager. Place the driver in /images/pnp/SMO8810.

===Adding Silent Install drivers===
*Drivers that require an executable to be run can also be included in this method provided the driver has a silent install option with no user interaction.
*If there is a drvinstall.bat file inside the driver folder, the script will take the contents of the bat file and add it to the end of the SetupComplete.cmd file to be executed at the end of the sysprep process. See the example contents of:
echo Driver for SMO8810
start/wait C:\drivers\pnp\SMO8810\setup.exe /s
*This is handy for devices that aren't detected by Device Manager's Update Driver. Devices that operate this way for us have been some sound cards, freefall sensors, touchscreen calibration tools, etc.
==Install Script==
*There are two files you'll need to add to /images/postdownloadscripts/
*machinedrivers.sh
#!/bin/bash
#machineinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#http://www.fogproject.org/wiki/index.php/Auto_driver_Install
#Andrew Single - Frontier School Division (Frontier loves FOG!)

oIFS=$IFS;
getDeviceName()
{
# echo "lspci -mm -d $1";
local devnamefull=`lspci -mm -d $1`;
devnamefull=${devnamefull//\" \"/¤};
IFS=¤;
pciDescr=($devnamefull);
IFS=$oIFS;
}
#Read PCI Device strings
pci=`lspci -n |cut -c 15-23`;
usb=`lsusb |cut -c 23-32`;
last="";
for device in $pci
do
#filter for unique devices
if [ "$device" != "$last" ]; then
last=$device;
#Split up vendor & Device IDs
dMfg=${device:0:4};
dDev=${device:5:4};
# echo "Device: $device";
# echo "Mfg: $dMfg - Dev: $dDev";
# sleep 1;
drvLoc="/images/drivers/$dMfg/$dDev";
#Does the driver folder exist?
if [ -d $drvLoc ];then
#Copy files
# echo $device;
getDeviceName $device;
echo -n " * Copying ${pciDescr[4]} ";
#Does the vendor folder exist?
if [ -d /ntfs/Drivers/$dMfg ]; then
cp -r $drvLoc /ntfs/Drivers/$dMfg
else
mkdir /ntfs/Drivers/$dMfg
cp -r $drvLoc /ntfs/Drivers/$dMfg
fi
if [ -f $drvLoc/drvinstall.bat ]; then
cat $drvLoc/drvinstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
fi
echo "Done.";
fi
fi
done
IFS='
*And driverinstall.sh
#!/bin/sh
#driverinstall.sh
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#Andrew Single - Frontier School Division (Frontier loves FOG!)

win7sys="/dev/sda2";
mkdir /ntfs 2>/dev/null

echo -n " * Mounting Windows File System...................";
mount.ntfs-3g $win7sys /ntfs 2>/tmp/mntfail
mntRet="$?";
if [ ! "$mntRet" = "0" ]
then
echo "Failed to mount C:";
echo "";
echo -n " * ";
cat /tmp/mntfail
echo "";
sleep 2;
else #Mount successful
echo "Done.";
mkdir /ntfs/Drivers 2>/dev/null
echo "";
echo -n " * Copying Common Drivers.........................";
cp -r /images/drivers/Common /ntfs/Drivers
if [ -d /ntfs/Windows/Setup/Scripts ]; then
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
else
mkdir /ntfs/Windows/Setup/Scripts
cp /images/drivers/Common/SetupComplete.cmd /ntfs/Windows/Setup/Scripts/
cat /images/drivers/Common/commoninstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
echo "Done.";
fi
#Needs to be exectued with bash
bash /images/postdownloadscripts/machinedrivers.sh
echo " ";
echo " * Driver copy completed.";
umount /ntfs
sleep 10;
fi

==Building the Universal Image==
*Include driver search path to C:\Drivers (Detect it in the script maybe and add the reg entry if it's missing?)

Auto driver Install

2014-11-02T23:35:42Z

Andrew.single: /* Install Script */

In Progress: Documentation for adding the Auto Driver install script from Frontier School Division.
Script To Do:
*Make device ID's all lower case so PNP devices don't require upper case folder names & are consistent with all lower case.

Overview: The Auto Driver install script is an addon for FOG that allows you to build a hardware independent Windows 7 image. Devices on the system will be detected by FOG, and drivers inserted into C:\Drivers. Windows will then use that as an additional driver search path when doing Sysprep first run.

==Setup Repository==
*Create a folder inside of /images named drivers
mkdir /images/drivers
*Create a Common folder for drivers/scripts you want on all systems.
mkdir /images/drivers/Common
*Create a SetupComplete.cmd file. This is a script, that when copied to C:\Windows\Setup\Scripts is executed at the end of the SysPrep process. The Frontier script stops the FOG service, runs a netsh command to push out a wlan profile, deletes the profile xml file, the sysprep.xml and fixes the permissions on the C:\drivers folder. It's a quite useful tool to use. I recommend at least having:
net STOP "Fog Service"
start "Reset C:\Drivers Perms" /wait "icacls" C:\drivers /reset /T >>"C:\FOGDrivers.log" 2>&1

===Adding Windows Device Drivers===
*The script currently detects three categories of Drivers: PCI, USB & ACPI.
*The first step is to identify the device that you want to install. On an imaged Windows 7 machine, go to device Manager.
**Right click the device, and go to Properties.
**Click the details tab, and go to the Hardware IDs dropdown.
**You'll see something like PCI\VEN_XXXX&Dev_YYYY&SUBSYS_ZZZZ.... or USB\VID_XXXX&PID_YYYY or ACPI\XXXXXXXXX
***You take the driver for that device, and place it in a folder of /images/drivers/XXXX/YYYY.
For Example, a driver for Intel Video with a device ID of PCI\VEN_8086&DEV_5A3C would be in the folder /images/drivers/8086/5a3c **Note that it's lower case.
***In the case of a drivers that contains drivers for multiple devices (Ie: Chipset) you don't need to break out each individual device. You can simply make the folder match one of the devices.
***ACPI devices don't have a vendor/ID value, but only contain a single value. ACPI/PNP devices should be placed in /images/pnp/XXXXXX.
For Example, a driver for the Dell Freefall sensor is ACPI\SMO8810 in Device Manager. Place the driver in /images/pnp/SMO8810.

===Adding Silent Install drivers===
*Drivers that require an executable to be run can also be included in this method provided the driver has a silent install option with no user interaction.
*If there is a drvinstall.bat file inside the driver folder, the script will take the contents of the bat file and add it to the end of the SetupComplete.cmd file to be executed at the end of the sysprep process. See the example contents of:
echo Driver for SMO8810
start/wait C:\drivers\pnp\SMO8810\setup.exe /s
*This is handy for devices that aren't detected by Device Manager's Update Driver. Devices that operate this way for us have been some sound cards, freefall sensors, touchscreen calibration tools, etc.
==Install Script==
*There are two files you'll need to add to /images/postdownloadscripts/
*machinedrivers.sh
#!/bin/bash
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#Andrew Single - Frontier School Division (Frontier loves FOG!)

oIFS=$IFS;
getDeviceName()
{
# echo "lspci -mm -d $1";
local devnamefull=`lspci -mm -d $1`;
devnamefull=${devnamefull//\" \"/¤};
IFS=¤;
pciDescr=($devnamefull);
IFS=$oIFS;
}
#Read PCI Device strings
pci=`lspci -n |cut -c 15-23`;
usb=`lsusb |cut -c 23-32`;
last="";
for device in $pci
do
#filter for unique devices
if [ "$device" != "$last" ]; then
last=$device;
#Split up vendor & Device IDs
dMfg=${device:0:4};
dDev=${device:5:4};
# echo "Device: $device";
# echo "Mfg: $dMfg - Dev: $dDev";
# sleep 1;
drvLoc="/images/drivers/$dMfg/$dDev";
#Does the driver folder exist?
if [ -d $drvLoc ];then
#Copy files
# echo $device;
getDeviceName $device;
echo -n " * Copying ${pciDescr[4]} ";
#Does the vendor folder exist?
if [ -d /ntfs/Drivers/$dMfg ]; then
cp -r $drvLoc /ntfs/Drivers/$dMfg
else
mkdir /ntfs/Drivers/$dMfg
cp -r $drvLoc /ntfs/Drivers/$dMfg
fi
if [ -f $drvLoc/drvinstall.bat ]; then
cat $drvLoc/drvinstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
fi
echo "Done.";
fi
fi
done
IFS='

==Building the Universal Image==
*Include driver search path to C:\Drivers (Detect it in the script maybe and add the reg entry if it's missing?)

Auto driver Install

2014-11-02T23:35:30Z

Andrew.single: /* Install Script */

In Progress: Documentation for adding the Auto Driver install script from Frontier School Division.
Script To Do:
*Make device ID's all lower case so PNP devices don't require upper case folder names & are consistent with all lower case.

Overview: The Auto Driver install script is an addon for FOG that allows you to build a hardware independent Windows 7 image. Devices on the system will be detected by FOG, and drivers inserted into C:\Drivers. Windows will then use that as an additional driver search path when doing Sysprep first run.

==Setup Repository==
*Create a folder inside of /images named drivers
mkdir /images/drivers
*Create a Common folder for drivers/scripts you want on all systems.
mkdir /images/drivers/Common
*Create a SetupComplete.cmd file. This is a script, that when copied to C:\Windows\Setup\Scripts is executed at the end of the SysPrep process. The Frontier script stops the FOG service, runs a netsh command to push out a wlan profile, deletes the profile xml file, the sysprep.xml and fixes the permissions on the C:\drivers folder. It's a quite useful tool to use. I recommend at least having:
net STOP "Fog Service"
start "Reset C:\Drivers Perms" /wait "icacls" C:\drivers /reset /T >>"C:\FOGDrivers.log" 2>&1

===Adding Windows Device Drivers===
*The script currently detects three categories of Drivers: PCI, USB & ACPI.
*The first step is to identify the device that you want to install. On an imaged Windows 7 machine, go to device Manager.
**Right click the device, and go to Properties.
**Click the details tab, and go to the Hardware IDs dropdown.
**You'll see something like PCI\VEN_XXXX&Dev_YYYY&SUBSYS_ZZZZ.... or USB\VID_XXXX&PID_YYYY or ACPI\XXXXXXXXX
***You take the driver for that device, and place it in a folder of /images/drivers/XXXX/YYYY.
For Example, a driver for Intel Video with a device ID of PCI\VEN_8086&DEV_5A3C would be in the folder /images/drivers/8086/5a3c **Note that it's lower case.
***In the case of a drivers that contains drivers for multiple devices (Ie: Chipset) you don't need to break out each individual device. You can simply make the folder match one of the devices.
***ACPI devices don't have a vendor/ID value, but only contain a single value. ACPI/PNP devices should be placed in /images/pnp/XXXXXX.
For Example, a driver for the Dell Freefall sensor is ACPI\SMO8810 in Device Manager. Place the driver in /images/pnp/SMO8810.

===Adding Silent Install drivers===
*Drivers that require an executable to be run can also be included in this method provided the driver has a silent install option with no user interaction.
*If there is a drvinstall.bat file inside the driver folder, the script will take the contents of the bat file and add it to the end of the SetupComplete.cmd file to be executed at the end of the sysprep process. See the example contents of:
echo Driver for SMO8810
start/wait C:\drivers\pnp\SMO8810\setup.exe /s
*This is handy for devices that aren't detected by Device Manager's Update Driver. Devices that operate this way for us have been some sound cards, freefall sensors, touchscreen calibration tools, etc.
==Install Script==
*There are two files you'll need to add to /images/postdownloadscripts/
*machinedrivers.sh
#!/bin/bash
#Script version .1alpha
#FOG version 1.2.0
#Copies drivers to a C:\drivers on a universal image based on the hardware
#detected on PCI, USB & PNP. Full documentation & How-To's on the FOG Wiki.
#Andrew Single - Frontier School Division (Frontier loves FOG!)

oIFS=$IFS;
getDeviceName()
{
# echo "lspci -mm -d $1";
local devnamefull=`lspci -mm -d $1`;
devnamefull=${devnamefull//\" \"/¤};
IFS=¤;
pciDescr=($devnamefull);
IFS=$oIFS;
}

#Read PCI Device strings
pci=`lspci -n |cut -c 15-23`;
usb=`lsusb |cut -c 23-32`;
last="";
for device in $pci
do
#filter for unique devices
if [ "$device" != "$last" ]; then
last=$device;
#Split up vendor & Device IDs
dMfg=${device:0:4};
dDev=${device:5:4};
# echo "Device: $device";
# echo "Mfg: $dMfg - Dev: $dDev";
# sleep 1;
drvLoc="/images/drivers/$dMfg/$dDev";
#Does the driver folder exist?
if [ -d $drvLoc ];then
#Copy files
# echo $device;
getDeviceName $device;
echo -n " * Copying ${pciDescr[4]} ";
#Does the vendor folder exist?
if [ -d /ntfs/Drivers/$dMfg ]; then
cp -r $drvLoc /ntfs/Drivers/$dMfg
else
mkdir /ntfs/Drivers/$dMfg
cp -r $drvLoc /ntfs/Drivers/$dMfg
fi
if [ -f $drvLoc/drvinstall.bat ]; then
cat $drvLoc/drvinstall.bat >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd
unix2dos /ntfs/Windows/Setup/Scripts/SetupComplete.cmd
fi
echo "Done.";
fi
fi
done
IFS='

==Building the Universal Image==
*Include driver search path to C:\Drivers (Detect it in the script maybe and add the reg entry if it's missing?)

Auto driver Install

2014-11-02T23:32:35Z

Andrew.single:

Auto driver Install

2014-11-02T23:08:57Z

Andrew.single: Created page with "In Progress: Documentation for adding the Auto Driver install script from Frontier School Division. Overview: The Auto Driver install script is an addon for FOG that allows..."

In Progress: Documentation for adding the Auto Driver install script from Frontier School Division.

Overview: The Auto Driver install script is an addon for FOG that allows you to build a hardware independent Windows 7 image. Devices on the system will be detected by FOG, and drivers inserted

==Setup Repository==
*Create a folder inside of /images named drivers
mkdir /images/drivers
*Create a Common folder for drivers/scripts you want on all systems.
mkdir /images/drivers/Common
*Create a SetupComplete.cmd file. This is a script, that when copied to C:\Windows\Setup\Scripts is executed at the end of the SysPrep process. The Frontier script stops the FOG service, runs a netsh command to push out a wlan profile, deletes the profile xml file, the sysprep.xml and fixes the permissions on the C:\drivers folder. It's a quite useful tool to use. I recommend at least having:
net STOP "Fog Service"
start "Reset C:\Drivers Permissions" /wait "icacls" C:\drivers /reset /t >>"C:\FOGDriverInstall.log 2>&1

===Adding Drivers===
*The script currently detects three categories of Drivers: PCI, USB & PNP.
*The first step is to identify the device that you want to install. On an imaged Windows 7 machine, go to device Manager.
**Right click the device, and go to Properties.
**Click the details tab, and go to the Hardware IDs dropdown.

==Install Script==

==Building the Universal Image==
*Include driver search path to C:\Drivers (Detect it in the script maybe and add the reg entry if it's missing?)

FOGUserGuide

2014-11-02T22:45:28Z

Andrew.single: /* Other Advanced Topics */

A guide to deployment, management,
And concept overview
For FOG.

Based on a document by:
Thomas J. Munn
CISSP

== Introduction ==

=== Preface ===

This document is intended to be modified by FOG users, in fact it is based on a document created by a FOG user. If you feel something could be said better or put more clearly, it is encouraged that you make changes to this document. We just ask that you keep it constructive and in good taste. In order to edit the wiki you are now required to create an account, as spamming of the forum has gotten pretty bad recently.

<UL><LI>'''What is FOG?''' 

FOG is a Linux-based, free and open source computer imaging solution for Windows XP, Windows Vista, Windows 7, Windows 8, and Linux (limited) that ties together a few open-source tools with a php-based web interface. FOG doesn't use any boot disks, or CDs; everything is done via TFTP and PXE. Your PC boots via PXE and automatically downloads a small Linux client. From there you can select many activities on the PC, including imaging the hard drive.

Also with FOG many network drivers are built into the Linux client's kernel, so you don't really need to worry about nic drivers (unless there isn't kernel support for it yet). FOG also supports putting an image that came from a computer with a 80GB partition onto a machine with a 40GB hard drive as long as the data is less than 40GB. FOG supports multi-casting, meaning that you can image many PCs from the same stream. So it should be as fast whether you are imaging 1 PC or 20 PCs.</li> 

<LI>'''How should FOG be implemented?''' 

FOG is best implemented on a dedicated server, any spare machine you have. We recommend that you have '''sufficient''' hard drive space as each image you make is usually between 5 and 10 GB. Using a RAID array allows imaging multiple computers simultaneously without much performance degradation. A '''gigabit NIC''' is recommended. For faster image compression and decompression, provide as much processor and RAM as you can make available. </li> 

<LI>'''What features are included with FOG?''' 

FOG is more than just an imaging solution, FOG has grown into an imaging/cloning and network management solution. FOG now performs tasks like installing and managing printers, tracking user access to computers, installing applications remotely via snap-ins, automatic user log offs and computer shutdown on idle timeouts. If a computer is badly infected with a virus or malware, you can boot FOG in AV mode and have it remove the viruses. You can wipe your disks, destroying all information that was on them, restore deleted files, or scan the disk for bad blocks.</li> 

<LI>'''How much does FOG cost?''' 

FOG is an Open Source project and licensed under the GPL which means that you are free to use FOG on as many computers as you like for free. This also means that if you want to make any changes to the source code you are free to do so.

The creators of FOG make no profits from this project with the exception of donations. FOG comes with absolutely '''NO WARRANTY''' and the creators of FOG are in '''NO WAY RESPONSIBLE FOR ANY DAMAGE OR LOSS CAUSED BY FOG!''' Please see the license file included with the FOG release for more information. With that being said we attempt to do a very good job of supporting our users, in fact it is one of the goals of FOG to have better support than most commercial products. All support requests should be placed through the FOG's forum which is located at:

http://fogproject.org/forum/

Thanks for supporting open source software and enjoy!</li></UL>

=== Background on FOG ===

<UL><LI>'''Why FOG?''' 

Working in an educational environment our organization's techs very often re-imaged computers in their day to day activities. For a long time we used a commercial product that in many ways didn't meet our needs. It wasn't web based, and you needed to create driver disks, floppys or USB drives. Other things were very difficult, such as searching for a host by MAC address and the product was expensive, even with an educational discount. So we started to investigate ways in which we could do things better, and as our organization struggled to make a commercial product work better by trying to pxe boot dos, and testing it in Windows PE, we, the FOG Team started to build linux based solution on our own time. We finally got a working version and decided to release it as open source since we use many other open source products, and figured we should give back to the community.</li></UL>

=== Fundamental Concepts ===
This section provides some basic concepts that the FOG Project uses.
<UL><LI>'''Unicasting''' 
Unicasting in FOG means sending a single image to a single host. This can mean an upload or a deploy, and is independent of the image type. 
See this section for more on [[Unicasting]]</li>
<LI>'''Multicasting''' 
Multicasting in FOG uses UDPcast to send a single image to multiple computers using only slightly more bandwidth than sending the image to a single computer with unicast. 
See this section for more on [[Multicasting]]</li>
<LI>'''PXE Network Bootstrap loading''' 
What is iPXE and the difference between the files? Check out the [[iPXE]] page.</li></UL>

== Installing FOG ==
FOG is a typical ''[http://en.wikipedia.org/wiki/LAMP_%28software_bundle%29 LAMP]'' software bundle, so the main server is a '''L'''inux box. The rest of the components: '''A'''pache, '''M'''ySQL, '''P'''HP, and several other services, are automatically downloaded and installed by the FOG installation script.

=== Requirements ===
This listing is for informational purposes only, as the required components will be automatically downloaded and installed by the FOG installation script.

*PHP 5.3.0+
*MySql 5+
*Apache 2+

=== Installation on different distributions of Linux ===
Click below for step-by-step guides written for your favorite flavor of Linux:
{{Installation}}

== Network Integration ==
=== Basic Network Setup ===
The FOG setup script asks several questions which might not be obvious. These sections describe only the most generic settings.
<ul><li>'''Isolated Network''' 
The easiest method to image machines and get started using FOG is on a small, isolated network. The FOG setup program will configure all the necessary services for you completely automatically. This section covers only those basic steps.
 '''See [[FOG on an Isolated Network]]'''</li> 
<li>'''Integrating FOG Server with Existing Network Systems''' 
Slightly more complicated is the task of integrating FOG into your existing network infrastructure. This section attempts to describe the steps to link FOG with a fairly generic enterprise system. 
'''See [[Integrating FOG into an Existing Network]]'''</li></ul>

===Advanced Network Setup===
==== Integrating FOG Server with Existing Network Systems in non intrusive mode using MAC filtration ====
This methods allows to use Fog in existing network without the need of controlling existing DHCP server. Requires you to input the MAC address of FOG clients.
See [[Integrating FOG into an Existing Network in non intrusive mode]]
==== Integrating FOG server into an existing network in non intrusive mode using ProxyDHCP ====
This methods allows to use Fog in existing network without the need of controlling existing DHCP server. Does NOT required you to input the MAC addresses of FOG clients.
See [[Setting up ProxyDHCP]].

==== Wake On Lan (WOL) ====
<ul><li> [[Cisco_Wake_on_lan|Cisco WOL - Layer 3]] </li>
<li> [[ProCurve_Wake_on_lan|ProCurve WOL]] </li></ul>
==== Multicast/UDPCast ====
<ul><li> [[Cisco_Multi_Cast|Cisco Multicast - Layer 3]] </li></ul>
<ul><li> [[HPMulticast|HP Multicast - Layer 2&3]] </li></ul>
==== Full Listing of Ports used by FOG server and client ====
FTP – tcp 20,21 
SSH – tcp 22 
TFTP – udp 69 
HTTP(s) – tcp 80,443 
Portmap – tcp/udp 111 
NFS – tcp/udp 2049 
Transfer ports – tcp/udp 1024 – 65535 
As found at: http://fogproject.org/forum/threads/firewall-config.27/

== Getting Started ==

=== Quick Start - Basic Tasks ===

So you have a FOG server installed and setup, now what do you do? Below are a few common "Getting Started" items.

#[[Booting into FOG and Uploading your first Image]]
#[[Deploying your Image a single client]]
#[[Deploying your Image a group of clients]]

=== Tips ===

#FOG requires that all hosts be entered in the FOG Database for imaging. The most important part is getting the MAC address of the host right. FOG uses the MAC for targeting image installs and acquires. Using the wrong MAC could result in unpredictable results, including the complete erasure of the wrong pc! The IP address isn’t that important, and the ‘name’ field is more for the user. Mac address format is 00:12:3F:C4:57:0C . Using dashes, spaces, or no items at all will result in the GUI not accepting the host.
#After hosts are entered, it is wise to group them together by function, hardware, or common image. The image will be shared among all members of a particular group. This occurs within the ‘hosts’ screen, and NOT on the groups screen. This is a little confusing, so it helps to think of the ‘groups’ screen as a task generator, rather than controlling group memberships.
#For importing hosts in a .csv file follow the format below: 1 line per host:<pre>"00:c0:4f:18:62:63","Hostname","1.1.1.1","Your description","XP/Vista","Image filename to use"</pre>
#Hosts are then configured to boot via PXE boot by going into the BIOS. Make sure PXE boot is the FIRST option, NOT the hard disk, or things won’t work.
#Configure your ‘master’ pc for the first image. Probably a good idea to run ‘[http://support.microsoft.com/kb/302577 sysprep]’ prior to imaging, but not necessary. Sysprep will make your imaging life easier, if hardware is different, etc. See Microsoft.com for more details on using sysprep.

== Preparing a Client for Cloning ==
FOG's strength can be better harnessed if some time and work is put into preparing a master image that fits the needs of your environment. 
This section covers client preparation steps that will save you time and headaches like:
::Setting a [[Client_Setup#Set_up_Default_Profile|Default User Profile]] Installing Windows Updates Pre-Installing the [[Client_Setup#Final_Steps_Before_Imaging_.2F_Before_Sysprep|FOG service]], etc. 
It also covers more advanced ideas that are guaranteed to ''cause'' headaches, like:
::Sysprep, [[Client_Setup#Hardware-Independent_Images_-_Understand_HAL|Hardware-Independent Images (HAL)]], and Driver integration. 
Read more about ''[[Client Setup]]''

== FOG Benchmarks ==

=== [[Internal Benchmarks]] ===
== Managing FOG ==
The FOG web interface is your primary management console. It is very well-documented in the pages linked below: 
===The Main [[Managing FOG]] Document===
The link above opens the Main Managing FOG document and has a Table of Contents of its own. 
Subcategories within the Managing Fog section include the following sections:
<UL><LI>'''Understanding the FOG [[Managing_FOG#Dashboard|Dashboard]]''' 
Provides an overview of the GUI and explains the symbols used on the [[Managing_FOG#Menu Bar|Menu Bar]].</LI>
<LI>'''Managing [[Managing_FOG#Hosts|Hosts]]''' 
This section covers management tasks such as: [[Managing_FOG#Adding a new host|Adding a new host]], [[Managing_FOG#Managing Hosts|Managing Hosts]], [[Managing_FOG#Host Status|Host Status]], and [[Managing_FOG#Creating Host Groups|Creating Host Groups]].</LI>
<LI>'''Managing [[Managing_FOG#Groups|Groups of Hosts]]''' 
This section provides an [[Managing_FOG#Overview_4|Overview]] of sorting hosts into useful Groups, and provides instruction on [[Managing_FOG#Managing Groups|Managing Groups]].</LI>
<LI>'''Defining and Managing [[Managing_FOG#Images|Images]]''' 
Defines types of images: Single Partition | Multiple Partition - Single Disk | Multiple Partition - All Disks | Raw Image 
Also describes [[Managing_FOG#Creating_Images_Objects|Creating]], [[Managing_FOG#Modifying_Image_Objects|Modifying Image Objects]], and [[Managing_FOG#Adding_Existing_Image_Objects|Adding Images to Existing Objects]].</LI>
<LI>'''[[Managing_FOG#Storage_Management|Storage Management]] - adding additional Storage Nodes''' 
This section introduces the [[Managing_FOG#Overview_6|concept of Storage Nodes]], which provide scalability to FOG with the ability to "share the load of computers being imaged." 
Also covered are [[Managing_FOG#Adding_a_Storage_Node|Adding Storage Nodes]], Monitoring [[Managing_FOG#Monitoring_The_Master_Node|Image Replication]] between nodes, and Understanding the [[Managing_FOG#Master_Node_Status|role of the "Master Node"]] in a group. 
In addition, this section details the necessary steps to [[Managing_FOG#Including_multiple_PXE_.2F_TFTP_servers|include PXE and TFTP Services]] for a node located on a remote network segment.</LI>
<LI>'''Defining types of [[Managing_FOG#Users|Administrative FOG Users]]''' 
The difference between a regular FOG user and a [[Managing_FOG#Overview_7|Mobile user]] 
Also covered are [[Managing_FOG#Creating_Accounts|Creating]] and [[Managing_FOG#Modifying_Users|Modifying]] FOG user accounts</LI></UL>

==FOG [[Managing_FOG#Tasks|Tasks]]==
This is a major section of FOG Management because all day-to-day client management is initiated within the FOG Tasks section. 
The [[Managing_FOG#Overview_8|Overview Section]] provides a quick list of tasks available within FOG. 
[[Managing_FOG#General_Tasks|General Tasks]] - Basic Imaging Tasks:
::Uploading an image (includes video tutorial) Deploying an image Multicasting 
[[Managing_FOG#Advanced_Tasks|Advanced Tasks]] - Describes tasks other than imaging:
::Debug Upload - Unicast (Debug) Send - Unicast (Debug) Send - Unicast (Without Snapins) Deploy All Snapins Deploy Single Snapin Memory Test Wake Up Fast Wipe Normal Wipe Full Wipe Disk Surface Test File Recovery Virus Scan Hardware Inventory
===Delayed Tasks, or [[Managing_FOG#Scheduling|Scheduling Tasks]] in the future===
Describes advanced settings available for scheduling tasks including Shutdown after Execution, [[Managing_FOG#Single_Execution_Scheduling|Single Task]] scheduling, and [[Managing_FOG#Cron_Style_Task_Scheduling|setting a CRON-Style Task]].
===[[Managing_FOG#Printers|Adding Printers]] to FOG===
How to add printers to FOG. This allows the [[Managing_FOG#Printer_Manager|FOG Service to manage printers]] on FOG Clients
==The [[Managing_FOG#The_FOG_Client_Service|FOG Client Service]]==
A service that runs on client computers allowing FOG to better manage them. Provides AD Integration, the ability to change a Hostname, Green Power management, Snap-in installation, User tracking, Printer Management, and more. See the [[Managing_FOG#Overview_10|Overview]] for a more complete list. 
The FOG client can be partially or fully-enabled by [[Managing_FOG#Module_specific_configuration_settings|modifying the ini file.]] 
===[[Managing_FOG#Installation|Installing]] the FOG Client===
A typical client installation, Silent installation, and a video tutorial.
===Advanced Description of [[Managing_FOG#Functions_and_Operation|FOG Services]]===
More detail on: 
::Auto Log Out Hostname Changer Host Register Task Reboot Directory Cleaner Display Manager Green FOG Snapin Client User Tracker User Cleanup Printer Manager Client Updater
===[[Managing_FOG#Keeping_Clients_up_to_date|Updating]] the FOG Client===
How to update the FOG client.
===The [[Managing_FOG#FOG_Tray|FOG Tray]]===
Describes the Windows application that runs in the taskbar

===[[Managing_FOG#Troubleshooting|Troubleshooting]] the FOG Client===
Log file location
==Snap-ins==
A FOG [[Managing_FOG#Snap-ins|Snap-in]] is anything that can be run on a Windows client. This can be ''just about anything'', including: installing applications like Firefox or Microsoft Office, adding an icon or shortcut to the desktop, or tweaking a registry key. This section covers [[Managing_FOG#Creating_a_Snapin_.2F_Overview|Creating a Snap-in]], adjusting the FOG server to handle snap-ins [[Managing_FOG#Preparing_the_FOG_Server|larger than 2MB]], [[Managing_FOG#Uploading_the_Snapin|Uploading the Snap-in]] into the FOG system, and [[Managing_FOG#Linking_the_Snapin_to_Hosts|Linking]] the Snap-in to hosts.

== FOG Plugins ==
Plugins enhance FOG's functionality.
<UL><LI>The Capone plugin allows FOG to recognize similar hardware platforms and push your specified image to them with minimal (or no) interaction.</LI>
</UL>
See [[Plugins]] to activate and manage plugins.

== FOG Server Maintenance ==
<ul><LI>[[Backing up FOG]]</LI>
<LI>[[Restoring FOG from Backup]]</LI>
<LI>[[Upgrading the FOG Server]]</LI></ul>

== Advanced Installations ==

=== Separate TFTP and DHCP Server ===

In this setup, the TFTP server and the DHCP server are hosted on a separate server. The TFTP server holds the PXE boot files including the Linux Kernel, boot file system image, and pxe config files. The DHCP server is the server that assigns the clients with IP addresses and network connection information.

Click here for detailed steps: 
[[Separate TFTP and DHCP Server]]

=== Additional TFTP / DHCP Server on separate subnet ===
This setup allows FOG to manage systems at a remote network location by installing the necessary services to allow clients to PXE boot to a Storage Node: 
[[Multiple_TFTP_servers|Including multiple PXE / TFTP servers]]

This extends the work done in the above article, [[Multiple_TFTP_servers|Including multiple PXE / TFTP servers]], and extends it a bit to allow for FOG nodes to be used in various locations that pull from a central server. 
[[Fog_deployment_nodes| Using remote FOG nodes for distributed deployment]]

=== Separate NFS Server ===

Edit the storage node definition with the IP address of your NFS server and set the image location to the path on the nfs server.
Make sure it has a file called .mntcheck in the root of the share, a directory called dev and a .mntcheck file in the dev folder.

if you want to mount it on the fog server too, follow these steps:-
* mv /images /imagesold
* mkdir /images
* edit /etc/fstab

For example if your server name is mynfsserver and the share on it is called fogimages
<pre>mynfsserver:/fogimages /images nfs defaults 0 0 </pre>

then type
<pre>mount -a</pre>

'''KNOWN ISSUE'''
You will get an error "Ftp connection to storage server has failed" at the end of uploading images though.
You will have to manually rename and move the file from the dev directory to the directory below.

If your NFS server supports ftp as well, enable ftp on it too with the username and password specified in the storage server settings and this message will go away.

Hopefully someone will re-write POST_Stage2.php to change this at some point as if you already have the NFS share mounted why do we do this bit with ftp?

You may also get an infinite loop of the following message:-
<pre>"Unable to find a valid task ID based on the clients mac address of: <mac address>".</pre>
if you add an @ sign before the ftp commands it appears to have fixed the issue.

so line 133 of /var/www/fog/service/Post_Stage2.php would look like this

<pre> if (@ftp_rename ( $ftp, $src, $dest ) || @ftp_rename ( $ftp, $srcdd, $dest ))</pre>

=== Change NFS location ===

This is '''not about a seperate NFS server''' in general, but about how to '''change the local storage directory''' and export it correctly.

See [[Change NFS location]] for more.

== Other Advanced Topics ==

*[[Building a Custom Kernel]]
*[[Creating Custom FOG Service Modules]]
*[[Modifying the Init Image]]
*[[Translating FOG]]
*[[Bypass Host Registration]]
*[[Building undionly.kpxe]]
*[[Chainloading PXE to iPXE using pxelinux.0]]
*[[Auto driver Install]]

== Troubleshooting ==
This section is intended to bring together the most common issues from the [http://www.fogproject.org/forum forums].

==== Troubleshooting Installation and Configuration Issues ====
<ul><li>[[Knowledge Base]]</li>
<li>[[Password Central]]</li>
<li>[[Troubleshooting an image push to a client]]</li>
<li>[[Troubleshooting an image upload]]</li>
<li>[[Troubleshooting a multicast]]</LI>
<li>[[Troubleshooting Driver Issues]]</li>
<li>[[Speeding up the Graphical User Interface]]</li>
<li>[[Bottleneck]] / Imaging Speed Issues</li>
<li>[[Advanced_Boot_Menu_Configuration_options]]</li>
<li>[[Troubleshooting Host Management Showing Hosts as Down]]</li></ul>

== Appendix C: Alternative Resources ==
For Microsoft sysprep information, see this page:
http://vernalex.com/guides/sysprep/video.shtml

FOG install HOWTO:
http://www.howtoforge.com/installing-fog-computer-imaging-solution-on-fedora8

FOG sourceforge page:
http://freeghost.sf.net/

Deployment Forum at Edugeek contains many Fog related threads
http://www.edugeek.net/forums/o-s-deployment/

= About the Developers =

=== Chuck Syperski ===

Chuck Syperski is the lead developer for FOG computer imaging solution. He is a software developer and network integration specialist for a public school district outside of Chicago, IL. Chuck Syperski has a Bachelor of Science in Computer Science from the University of Illinois and is half way done with his master's degree :). He specializes in Java, jsp, jsf, objective C, C, C++, C#, perl and php. You can contact Chuck Syperski directly via sourceforge as the following link:

http://sourceforge.net/users/microleaks/

Chuck Syperski releases other software titles through his company [http://cwssoft.com CWS Software LLC]

=== Jian Zhang ===

No content

=== Tom Elliott ===

Tom Elliott is a contributing developer for FOG computer imaging solution. He is a technical support specialist for Burlington School District in Burlington, VT. Tom Elliott has a Bachelor of Science in Information Technology (BSIT) Information Systems Security from the University of Phoenix. Currently looking at Master's programs. He also served 8 years active duty service with the United States Army as a Signal Support Systems Specialist. You can contact him directly via email at tommygunsster@gmail.com, thomas@mastacontrola.com, or on the FOG Forums. Username on the forums is Tom Elliott.