FOG Project - User contributions [en]

BIOS and UEFI Co-Existence

2020-02-08T10:25:15Z

Necros: /* Using Linux DHCP */ left brace missing

= General =

To make network booting for several different client platforms possible you'd have to offer adequate boot images for those clients. To be able to distinguish between varying platforms the DHCP server needs to utilize the information sent by the clients. According to [http://tools.ietf.org/html/rfc4578 RFC 4578] "the following pre-boot architecture types have been requested" (by the RFC):
Type Architecture Name
---- -----------------
0 Intel x86PC
1 NEC/PC98
2 EFI Itanium
3 DEC Alpha
4 Arc x86
5 Intel Lean Client
6 EFI IA32
7 EFI BC (EFI Byte Code)
8 EFI Xscale
9 EFI x86-64

There are different files that come with FOG that are pre-configured to work with these various architecture types. They are located in the /tftpboot directory usually. Here is more information on them: [[Filename Information]]

= Using Linux DHCP =

According to this post there are (at least) three different ways to configure ISC DHCP server that way: http://www.syslinux.org/archives/2014-October/022683.html

Edit /etc/dhcp/dhcpd.conf and add the 'authoritative' option to your subnet definition and the following classes anywhere in the config:

subnet ... {
authoritative;
...
}
...

class "pxeclient" {
match if substring (option vendor-class-identifier, 0, 9) = "PXEClient";

if substring (option vendor-class-identifier, 15, 5) = "00000" {
# BIOS client
filename "undionly.kpxe";
}
elsif substring (option vendor-class-identifier, 15, 5) = "00006" {
# EFI client 32 bit
filename "ipxe32.efi";
}
else {
# default to EFI 64 bit
filename "ipxe.efi";
}
}

== Example 1 ==
Here's a complete configuration example where TFTP and DNS is on the same Server. No router is defined in this configuration but can easily be added by changing X.X.X.X and un-commenting the line.

<pre>
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
option arch code 93 = unsigned integer 16; # RFC4578

use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server 192.168.1.1;
authoritative;

subnet 192.168.1.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
range dynamic-bootp 192.168.1.10 192.168.1.254;
default-lease-time 21600;
max-lease-time 43200;
option domain-name-servers 192.168.1.1;
#option routers x.x.x.x;

class "UEFI-32-1" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006";
filename "i386-efi/ipxe.efi";
}

class "UEFI-32-2" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002";
filename "i386-efi/ipxe.efi";
}

class "UEFI-64-1" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
filename "ipxe.efi";
}

class "UEFI-64-2" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008";
filename "ipxe.efi";
}

class "UEFI-64-3" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009";
filename "ipxe.efi";
}

class "Legacy" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000";
filename "undionly.kkpxe";
}

}
</pre>

== Example 2 ==
Here is another complete example setup for a 10.0.0.0/24 network where 10.0.0.3 is the TFTP server, 10.0.0.1 is the router, and 10.0.0.1 is the DNS Server. The range for this configuration is set to 10.0.0.20 through 10.0.0.254.

<pre>
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-cport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
option arch code 93 = unsigned integer 16; # RFC4578

use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server 10.0.0.3;
authoritative;

subnet 10.0.0.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
range dynamic-bootp 10.0.0.20 10.0.0.254;
default-lease-time 21600;
max-lease-time 43200;
option domain-name-servers 10.0.0.1;
option routers 10.0.0.1;

class "UEFI-32-1" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006";
filename "i386-efi/ipxe.efi";
}

class "UEFI-32-2" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002";
filename "i386-efi/ipxe.efi";
}

class "UEFI-64-1" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
filename "ipxe.efi";
}

class "UEFI-64-2" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008";
filename "ipxe.efi";
}

class "UEFI-64-3" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009";
filename "ipxe.efi";
}

class "Legacy" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000";
filename "undionly.kkpxe";
}

}
</pre>

When you have Mac OS clients as well you might want to check out this: [[FOG_on_a_MAC#architecture]]

Restart the DHCP service and you are good to go!

== ISC-DCHP static IP address and other things ==

Here are a few examples of exclusively defined options based on MAC addresses. These would be placed at the '''very end''' of your dhcpd.conf file. You may use MAC matching to hand out static IP address or specific boot options.

<pre>

#Just set a static IP based on MAC address. The "Optiplex380" is what is suggested as a hostname
# To my knowledge, only Linux respects this and offers it to the user for confirmation.

host Optiplex380 {
hardware ethernet F0:4D:A2:22:6E:2C;
fixed-address 10.0.0.6;
}

#Define a static IP and a specific boot file for this computer.

host FOG {
hardware ethernet 00:13:72:AB:FD:7C;
fixed-address 10.0.0.3;
filename "My_Custom_Boot_File.kkpxe";
}

#Make this access point use Google's DNS.

host TP-Link-Access-point {
hardware ethernet C4:E9:84:7D:F0:2E;
option domain-name-servers 8.8.8.8;
}

</pre>

= Using ProxyDHCP (dnsmasq) =

Related article: [[ProxyDHCP with dnsmasq]]

There are powerful matching rules in dnsmasq's configuration syntax. Here is an example of how this could be used to distingush between BIOS and UEFI. '''Note: This will NOT work in proxy mode!!'''

dhcp-match=set:bios,60,PXEClient:Arch:00000
dhcp-boot=tag:bios,undionly.kpxe,x.x.x.x,x.x.x.x # x.x.x.x = TFTP/FOG server IP

dhcp-match=set:efi32,60,PXEClient:Arch:00006
dhcp-boot=tag:efi32,i386-efi/ipxe.efi,x.x.x.x,x.x.x.x # x.x.x.x = TFTP/FOG server IP

dhcp-match=set:efibc,60,PXEClient:Arch:00007
dhcp-boot=tag:efibc,ipxe.efi,x.x.x.x,x.x.x.x # x.x.x.x = TFTP/FOG server IP

dhcp-match=set:efi64,60,PXEClient:Arch:00009
dhcp-boot=tag:efi64,ipxe.efi,x.x.x.x,x.x.x.x # x.x.x.x = TFTP/FOG server IP

= Using Windows Server 2012 (R1 and later) DHCP Policy =

The below method assumes that your normal Scope options 066 and 067 are already setup for BIOS based network booting (without these already set, the below steps will not result in success). The below DHCP policy will only apply to UEFI based network booting. Regular BIOS based network booting will still use the default scope options set in the scope.

You may substitute whatever Vendor Class Identifier you need in the ASCII field on step 3.

== Step 1 ==

Right click IPv4, and pick "Define vendor class".

[[File:Step 1.png]]

== Step 2 ==

[[File:Step 2.png]]

== Step 3 ==

Here, The display name and description aren't really important but should describe what this does.

What's important is the "ASCII" field. In this field, you would type this, exactly, because it's case sensitive:
<pre>PXEClient:Arch:00007</pre>

As you type this in, the ID and Binary fields will auto-update. When done, click Ok, ok, ok to finish this part of the procedure.

'''NOTE:'''
There are many other UEFI architectures besides just "PXEClient:Arch:00007".

"PXEClient:Arch:00002" and "PXEClient:Arch:00006" both should get "i386-efi/ipxe.efi" as their option 067 boot file.

"PXEClient:Arch:00008", "PXEClient:Arch:00009", and "PXEClient:Arch:00007" should get "ipxe.efi" as their option 067 boot file.

"PXEClient:Arch:00007:UNDI:003016" should get "ipxe7156.efi" this file is specific to the Surface Pro 4.

In order to support these other architectures, just re-run through the Server 2012 steps for each one, Set the matching (step 3) and the boot file for each accordingly, and change the names to reflect what they are.

[[File:Step 3.png]]

== Step 4 ==

Underneath IPv4 -> Scope -> Policies, right click on "Policies" and choose "New Policy..."

[[File:Step 4.png]]

== Step 5 ==

[[File:Step 5.png]]

== Step 6 ==

[[File:Step 6.png]]

== Step 7 ==

[[File:Step 7.png]]

== Step 8 ==

[[File:Step 8.png]]

== Step 9 ==

[[File:Step 9.png]]

== Step 10 ==

[[File:Step 10.png]]

= Using Windows Server 2008 (and earlier) using DHCP Vendor Predefined options =

This has been attempted '''unsuccessfully'''. The setup for Server 2008 is very similar to Windows Server 2012. You would create a Vendor Class and use the same vendor identifiers as used in Server 2012 and ISC-DHCP above, then you would set vendor predefined options for that class. The ''understanding'' is that you hard-code options 066 and 067 into your custom Vendor Class, and then can configure them after they are created for the class, and then later enable them on your server options or scope options.

However - '''Nobody in the FOG Community has succeeded with this as of yet.''' If you have it working, '''please let us know''' in the forums.

Here are some pictures of the unsuccessful steps taken, perhaps they can help out.

Right click to create the vendor class. Setup the class with the targeted vendor class identifier. Setup pre-defined options for the new class. Select the correct class in the drop down list and click add. Setup an option 66 and 67. After the options are created for the class, you can set their values in the Predefined options and values window. Enable these two options under the advanced tab of either scope options or server options.

[[File:A. Create DHCP Vendor Class.png]]

[[File:B. Edit Class.png]]

[[File:C. Select predefined options.png]]

[[File:D. Predefined options and values.png]]

[[File:E. Option 66.png]]

[[File:F. Option 67.png]]

[[File:G. Apply Scope Options.png]]

= Using OS X DHCP =

== Steps Here ==

Please list OS X steps here.'

= Building custom DHCP Classes for co-existence with FOG =

It's possible and easy to configure ISC-DHCP and Windows Server 2012 to support network booting with FOG and other devices (like IP Phones or Apple products) configurations at the same time on the same network. You would simply use Wireshark to examine the DHCP Request broadcast from the device and examine it's option 060. This will be a string. You'd then create a Vendor Class for that device and supply it with the correct option, in windows 066 and 067, in ISC-DHCP next-server and filename.

In the ISC-DHCP examples for IPXEClient architures, you see '''0, 20''', this means to start the string comparison at character zero and end 20 characters after the starting place. You may begin at 15 or even 20, but the next digit defines how much further to compare.

For example, Legacy clients send this in their DHCP Request option 060:

<pre>PXEClient:Arch:00000</pre>

To match this string with a class, any of these will work:

<pre>
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000";

match if substring(option vendor-class-identifier, 15, 5) = "00000";

match if substring(option vendor-class-identifier, 19, 1) = "0";
</pre>

Obviously the less you use to compare, the more chances you'll have of DHCP handing out incorrect options to the various devices on your network due to mismatches.

For example, This line would (incorrectly) match the below IP Phone's option 060:

match if substring(option vendor-class-identifier, 19, 1) = "'''0'''";

"Cisco VOIP phone 00'''0'''562"

It would also match this string:

"PXEClient:Arch:0000'''0'''"

Because the 20th character is a zero, this IP phone using the above configuration would be matched and given the defined options instead of the correct options.
I made up this example just to show the possibility of a class mismatch if the matching is limited too much.

In Windows Server DHCP, you cannot match like you can in ISC-DHCP, however you can define a string value of your liking when you setup a Vendor Class.

= Relevant Resources =
{{:Related to ISC-DHCP}}

Ubuntu 14.04 and LXC containers

2015-03-01T08:02:25Z

Necros:

Ubuntu releases after 10.04 LTS do no longer provide unfs3. Unfs3 is useful when one want to setup a fog server in a container with OpenVZ or LXC. Nfs kernel server cannot run in these containers.

Here's how to setup a FOG server in a LXC container.

= Prerequisites =

* A computer (physical or virtual) running Ubuntu 14.04 Server, may or may not using LVM, with available space in at least one volume group

= Network setup on the LXC host =

Setup a bridge on the computer, with at least one ethernet interface attached to it.

apt-get install bridge-utils

edit the file '''/etc/network/interfaces''' and add the following lines. '''Please ensure you're not using a SSH session''', because you may lose your connection !

Add the following lines :
auto br0
iface br0 inet static
address 192.168.1.2
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports eth0
bridge_fd 0
bridge_maxwait 0

Reboot the computer and check network connectivity

= LXC container creation =

First, create a LXC container running Ubuntu. The version is the latest LTS version available at the moment of creating the container

lxc-create -n server-fog -t ubuntu -B lvm --vgname vg --lvname lv-server-fog --fssize=10G --fstype=ext4

This will create a logical volume '''lv-server-fog''' in the volume group '''vg0''', with a 10GB ext4 filesystem. The container wil be named '''server-fog'''. At the end of the process, the system will give you a login and a password.

Edit the file '''/var/lib/lxc/server-fog/config''' and setup networking for the container :

lxc.network.link = br0
lxc.network.ipv4 = 192.168.1.3
lxc.network.gateway = 192.168.1.1

start your container

lxc-start -n server-fog -F

login with the credentials given earlier, and '''change the password''' ! If needed, you have to shutdown the container to go back to the host's console

sudo init 0

To run the container non interactively, use the following command

lxc-start -d -n server-fog

To use a terminal in the container :

lxc-console -n server-fog

You may exit the container at any time using the following keys (do not forget to logout first, because this will NOT logout any user in the container) :

CTRL+A, Q

In the container you have to download, compile and install unfs3 from sources.

* [http://sourceforge.net/projects/unfs3/files/ Download unfs3]
* decompress the archive : tar zxf unfs3-0.9.22.tar.gz
* apt-get install build-essential make flex bison
* cd unfs3-0.9.22
* ./configure
* make
* make install
* make install-init
* edit /etc/init.d/unfsd and replace the occurence of /usr/sbin/unfsd with /usr/local/sbin/unfsd
* /etc/init.d/unfsd start
* check unfsd is running : ps -ef | grep unfsd
* if it runs, then run update-rc.d unfsd defaults

Install and configure fog as usual.

If you want to setup a separate volume for your images :

* assuming you want to use a logical volume (LVM) /dev/vg0/lv with a ext3 filesystem :
* run your container and move all files located in /images into an other location (/root/images-bak), including the hidden file /images/.mntcheck
* from the lxc host, open /var/lib/your-container/fstab and add the following line : /dev/vg0/lv images ext3 defaults 0 0
* restart the container, and check the nex volume is available : run mount without any argument.
* If the LVM volume has been successfully mounted, move back the files backed up in /root/images-bak. Note there is no slash before '''images'''.
* chmod 777 /images

Once your setup is up and running, do not forget to enable autostart of your container :

edit /var/lib/lxc/server-fog/config :

lxc.start.auto = 1

Ubuntu 14.04 and LXC containers

2015-03-01T08:00:37Z

Necros:

Ubuntu releases after 10.04 LTS do no longer provide unfs3. Unfs3 is useful when one want to setup a fog server in a container with OpenVZ or LXC. Nfs kernel server cannot run in these containers.

= Prerequisites =

* A computer (physical or virtual) running Ubuntu 14.04 Server, may or may not using LVM, with available space in at least one volume group

= Network setup on the LXC host =

Setup a bridge on the computer, with at least one ethernet interface attached to it.

apt-get install bridge-utils

edit the file '''/etc/network/interfaces''' and add the following lines. '''Please ensure you're not using a SSH session''', because you may lose your connection !

Add the following lines :
auto br0
iface br0 inet static
address 192.168.1.2
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports eth0
bridge_fd 0
bridge_maxwait 0

Reboot the computer and check network connectivity

= LXC container creation =

First, create a LXC container running Ubuntu. The version is the latest LTS version available at the moment of creating the container

lxc-create -n server-fog -t ubuntu -B lvm --vgname vg --lvname lv-server-fog --fssize=10G --fstype=ext4

This will create a logical volume '''lv-server-fog''' in the volume group '''vg0''', with a 10GB ext4 filesystem. The container wil be named '''server-fog'''. At the end of the process, the system will give you a login and a password.

Edit the file '''/var/lib/lxc/server-fog/config''' and setup networking for the container :

lxc.network.link = br0
lxc.network.ipv4 = 192.168.1.3
lxc.network.gateway = 192.168.1.1

start your container

lxc-start -n server-fog -F

login with the credentials given earlier, and '''change the password''' ! If needed, you have to shutdown the container to go back to the host's console

sudo init 0

To run the container non interactively, use the following command

lxc-start -d -n server-fog

To use a terminal in the container :

lxc-console -n server-fog

You may exit the container at any time using the following keys (do not forget to logout first, because this will NOT logout any user in the container) :

CTRL+A, Q

In the container you have to download, compile and install unfs3 from sources.

* [http://sourceforge.net/projects/unfs3/files/ Download unfs3]
* decompress the archive : tar zxf unfs3-0.9.22.tar.gz
* apt-get install build-essential make flex bison
* cd unfs3-0.9.22
* ./configure
* make
* make install
* make install-init
* edit /etc/init.d/unfsd and replace the occurence of /usr/sbin/unfsd with /usr/local/sbin/unfsd
* /etc/init.d/unfsd start
* check unfsd is running : ps -ef | grep unfsd
* if it runs, then run update-rc.d unfsd defaults

Install and configure fog as usual.

If you want to setup a separate volume for your images :

* assuming you want to use a logical volume (LVM) /dev/vg0/lv with a ext3 filesystem :
* run your container and move all files located in /images into an other location (/root/images-bak), including the hidden file /images/.mntcheck
* from the lxc host, open /var/lib/your-container/fstab and add the following line : /dev/vg0/lv images ext3 defaults 0 0
* restart the container, and check the nex volume is available : run mount without any argument.
* If the LVM volume has been successfully mounted, move back the files backed up in /root/images-bak. Note there is no slash before '''images'''.
* chmod 777 /images

Once your setup is up and running, do not forget to enable autostart of your container :

edit /var/lib/lxc/server-fog/config :

lxc.start.auto = 1

Ubuntu 14.04 and LXC containers

2015-02-28T19:04:20Z

Necros: /* LXC container creation */

Ubuntu releases after 10.04 LTS do no longer provide unfs3. Unfs3 is useful when one want to setup a fog server in a container with OpenVZ or LXC. Nfs kernel server cannot run in these containers.

= Prerequisites =

* A computer (physical or virtual) running Ubuntu 14.04 Server, may or may not using LVM, with available space in at least one volume group

= Network setup on the LXC host =

Setup a bridge on the computer, with at least one ethernet interface attached to it.

apt-get install bridgeutils

edit the file '''/etc/network/interfaces''' and add the following lines. '''Please ensure you're not using a SSH session''', because you may lose your connection !

Add the following lines :
auto br0
iface br0 inet static
address 192.168.1.2
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports eth0
bridge_fd 0
bridge_maxwait 0

Reboot the computer and check network connectivity

= LXC container creation =

First, create a LXC container running Ubuntu. The version is the latest LTS version available at the moment of creating the container

lxc-create -n server-fog -t ubuntu -B lvm --vgname vg --lvname lv-server-fog --fssize=10G --fstype=ext4

This will create a logical volume '''lv-server-fog''' in the volume group '''vg0''', with a 10GB ext4 filesystem. The container wil be named '''server-fog'''. At the end of the process, the system will give you a login and a password.

Edit the file '''/var/lib/lxc/server-fog/config''' and setup networking for the container :

lxc.network.link = br0
lxc.network.ipv4 = 192.168.1.3
lxc.network.gateway = 192.168.1.1

start your container

lxc-start -n server-fog -F

login with the credentials given earlier, and '''change the password''' ! If needed, you have to shutdown the container to go back to the host's console

sudo init 0

To run the container non interactively, use the following command

lxc-start -d -n server-fog

To use a terminal in the container :

lxc-console -n server-fog

You may exit the container at any time using the following keys (do not forget to logout first, because this will NOT logout any user in the container) :

CTRL+A, Q

In the container you have to download, compile and install unfs3 from sources.

* [http://sourceforge.net/projects/unfs3/files/ Download unfs3]
* decompress the archive : tar zxf unfs3-0.9.22.tar.gz
* apt-get install build-essential make flex bison
* cd unfs3-0.9.22
* ./configure
* make
* make install
* make install-init
* edit /etc/init.d/unfsd and replace the occurence of /usr/sbin/unfsd with /usr/local/sbin/unfsd
* /etc/init.d/unfsd start
* check unfsd is running : ps -ef | grep unfsd
* if it runs, then run update-rc.d unfsd defaults

Install and configure fog as usual.

If you want to setup a separate volume for your images :

* assuming you want to use a logical volume (LVM) /dev/vg0/lv with a ext3 filesystem :
* run your container and move all files located in /images into an other location (/root/images-bak), including the hidden file /images/.mntcheck
* from the lxc host, open /var/lib/your-container/fstab and add the following line : /dev/vg0/lv images ext3 defaults 0 0
* restart the container, and check the nex volume is available : run mount without any argument.
* If the LVM volume has been successfully mounted, move back the files backed up in /root/images-bak. Note there is no slash before '''images'''.
* chmod 777 /images

Once your setup is up and running, do not forget to enable autostart of your container :

edit /var/lib/lxc/server-fog/config :

lxc.start.auto = 1

Ubuntu 14.04 and LXC containers

2015-02-28T18:58:51Z

Necros: /* LXC container creation */

Ubuntu releases after 10.04 LTS do no longer provide unfs3. Unfs3 is useful when one want to setup a fog server in a container with OpenVZ or LXC. Nfs kernel server cannot run in these containers.

= Prerequisites =

* A computer (physical or virtual) running Ubuntu 14.04 Server, may or may not using LVM, with available space in at least one volume group

= Network setup on the LXC host =

Setup a bridge on the computer, with at least one ethernet interface attached to it.

apt-get install bridgeutils

edit the file '''/etc/network/interfaces''' and add the following lines. '''Please ensure you're not using a SSH session''', because you may lose your connection !

Add the following lines :
auto br0
iface br0 inet static
address 192.168.1.2
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports eth0
bridge_fd 0
bridge_maxwait 0

Reboot the computer and check network connectivity

= LXC container creation =

First, create a LXC container running Ubuntu. The version is the latest LTS version available at the moment of creating the container

lxc-create -n server-fog -t ubuntu -B lvm --vgname vg --lvname lv-server-fog --fssize=10G --fstype=ext4

This will create a logical volume '''lv-server-fog''' in the volume group '''vg0''', with a 10GB ext4 filesystem. The container wil be named '''server-fog'''. At the end of the process, the system will give you a login and a password.

Edit the file '''/var/lib/lxc/server-fog/config''' and setup networking for the container :

lxc.network.link = br0
lxc.network.ipv4 = 192.168.1.3
lxc.network.gateway = 192.168.1.1

start your container

lxc-start -n server-fog -F

login with the login and password given earlier, and '''change the password''' ! If needed, you have to shutdown the container to go back to the host's console

sudo init 0

To run the container non interactively, use the following command

lxc-start -d -n server-fog

To use a terminal in the container :

lxc-console -n server-fog

You may exit the container at any time using the following keys (do not forget to logout first, because this will NOT logout any user in the container) :

CTRL+A, Q

In the container you have to download, compile and install unfs3 from sources.

* [http://sourceforge.net/projects/unfs3/files/ Download unfs3]
* decompress the archive : tar zxf unfs3-0.9.22.tar.gz
* apt-get install build-essential make flex bison
* cd unfs3-0.9.22
* ./configure
* make
* make install
* make install-init
* edit /etc/init.d/unfsd and replace the occurence of /usr/sbin/unfsd with /usr/local/sbin/unfsd
* /etc/init.d/unfsd start
* check unfsd is running : ps -ef | grep unfsd
* if it runs, then run update-rc.d unfsd defaults

Install and configure fog as usual.

If you want to setup a separate volume for your images :

* assuming you want to use a logical volume (LVM) /dev/vg0/lv with a ext3 filesystem :
* run your container and move all files located in /images into an other location (/root/images-bak), including the hidden file /images/.mntcheck
* from the lxc host, open /var/lib/your-container/fstab and add the following line : /dev/vg0/lv images ext3 defaults 0 0
* restart the container, and check the nex volume is available : run mount without any argument.
* If the LVM volume has been successfully mounted, move back the files backed up in /root/images-bak. Note there is no slash before '''images'''.
* chmod 777 /images

Once your setup is up and running, do not forget to enable autostart of your container :

edit /var/lib/lxc/server-fog/config :

lxc.start.auto = 1

Ubuntu 14.04 and LXC containers

2015-02-28T18:57:40Z

Necros: /* LXC container creation */

Ubuntu releases after 10.04 LTS do no longer provide unfs3. Unfs3 is useful when one want to setup a fog server in a container with OpenVZ or LXC. Nfs kernel server cannot run in these containers.

= Prerequisites =

* A computer (physical or virtual) running Ubuntu 14.04 Server, may or may not using LVM, with available space in at least one volume group

= Network setup on the LXC host =

Setup a bridge on the computer, with at least one ethernet interface attached to it.

apt-get install bridgeutils

edit the file '''/etc/network/interfaces''' and add the following lines. '''Please ensure you're not using a SSH session''', because you may lose your connection !

Add the following lines :
auto br0
iface br0 inet static
address 192.168.1.2
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports eth0
bridge_fd 0
bridge_maxwait 0

Reboot the computer and check network connectivity

= LXC container creation =

First, create a LXC container running Ubuntu. The version is the latest LTS version available at the moment of creating the container

lxc-create -n server-fog -t ubuntu -B lvm --vgname vg --lvname lv-server-fog --fssize=10G --fstype=ext4

This will create a logical volume '''lv-server-fog''' in the volume group '''vg0''', with a 10GB ext4 filesystem. The container wil be named '''server-fog'''. At the end of the process, the system will give you a login and a password.

Edit the file '''/var/lib/lxc/server-fog/config''' and setup networking for the container :

lxc.network.link = br0
lxc.network.ipv4 = 192.168.1.3
lxc.network.gateway = 192.168.1.1

start your container

lxc-start -n server-fog -F

login with the login and password given earlier, and '''change the password''' ! If needed, you have to shutdown the container to go back to the host's console

sudo init 0

To run the container non interactively, use the following command

lxc-start -d -n server-fog

To use a terminal in the container :

lxc-console -n server-fog

You may exit the container at any time using the following keys (do not forget to logout first, because this will NOT logout any user in the container) :

CTRL+A, Q

In the container you have to download, compile and install unfs3 from sources.

* [http://sourceforge.net/projects/unfs3/files/ Download unfs3]
* decompress the archive : tar zxf unfs3-0.9.22.tar.gz
* apt-get install build-essential make flex bison
* cd unfs3-0.9.22
* ./configure
* make
* make install
* make install-init
* edit /etc/init.d/unfsd and replace the occurence of /usr/sbin/unfsd with /usr/local/sbin/unfsd
* /etc/init.d/unfsd start
* check unfsd is running : ps -ef | grep unfsd
* if it runs, then run update-rc.d unfsd defaults

Install and configure fog as usual.

If you want to setup a separate volume for your images :

* assuming you want to use a logical volume (LVM) /dev/vg0/lv with a ext3 filesystem :
* run your container and move all files located in /images into an other location (/root/images-bak), including the hidden file /images/.mntcheck
* from the lxc host, open /var/lib/your-container/fstab and add the following line : /dev/vg0/lv images ext3 defaults 0 0
* restart the container, and check the nex volume is available : run mount without any argument.
* If the LVM volume has been successfully mounted, move back the files backed up in /root/images-bak. Note there is no slash before '''images'''.
* chmod 777 /images

Ubuntu 14.04 and LXC containers

2015-02-28T18:52:11Z

Necros: /* LXC container creation */

Ubuntu releases after 10.04 LTS do no longer provide unfs3. Unfs3 is useful when one want to setup a fog server in a container with OpenVZ or LXC. Nfs kernel server cannot run in these containers.

= Prerequisites =

* A computer (physical or virtual) running Ubuntu 14.04 Server, may or may not using LVM, with available space in at least one volume group

= Network setup on the LXC host =

Setup a bridge on the computer, with at least one ethernet interface attached to it.

apt-get install bridgeutils

edit the file '''/etc/network/interfaces''' and add the following lines. '''Please ensure you're not using a SSH session''', because you may lose your connection !

Add the following lines :
auto br0
iface br0 inet static
address 192.168.1.2
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports eth0
bridge_fd 0
bridge_maxwait 0

Reboot the computer and check network connectivity

= LXC container creation =

First, create a LXC container running Ubuntu. The version is the latest LTS version available at the moment of creating the container

lxc-create -n server-fog -t ubuntu -B lvm --vgname vg --lvname lv-server-fog --fssize=10G --fstype=ext4

This will create a logical volume '''lv-server-fog''' in the volume group '''vg0''', with a 10GB ext4 filesystem. The container wil be named '''server-fog'''. At the end of the process, the system will give you a login and a password.

Edit the file '''/var/lib/lxc/server-fog/config''' and setup networking for the container :

lxc.network.link = br0
lxc.network.ipv4 = 192.168.1.3
lxc.network.gateway = 192.168.1.1

start your container

lxc-start -n server-fog -F

login with the login and password given earlier, and '''change the password''' ! you have to shutdown the container to go back to the host's console

sudo init 0

check the connectivity

You have to download, compile and install unfs3 from sources.

* [http://sourceforge.net/projects/unfs3/files/ Download unfs3]
* decompress the archive : tar zxf unfs3-0.9.22.tar.gz
* apt-get install build-essential make flex bison
* cd unfs3-0.9.22
* ./configure
* make
* make install
* make install-init
* edit /etc/init.d/unfsd and replace the occurence of /usr/sbin/unfsd with /usr/local/sbin/unfsd
* /etc/init.d/unfsd start
* check unfsd is running : ps -ef | grep unfsd
* if it runs, then run update-rc.d unfsd defaults

Install and configure fog as usual.

If you want to setup a separate volume for your images :

* assuming you want to use a logical volume (LVM) /dev/vg0/lv with a ext3 filesystem :
* run your container and move all files located in /images into an other location (/root/images-bak), including the hidden file /images/.mntcheck
* from the lxc host, open /var/lib/your-container/fstab and add the following line : /dev/vg0/lv images ext3 defaults 0 0
* restart the container, and check the nex volume is available : run mount without any argument.
* If the LVM volume has been successfully mounted, move back the files backed up in /root/images-bak. Note there is no slash before '''images'''.
* chmod 777 /images

Ubuntu 14.04 and LXC containers

2015-02-28T18:47:08Z

Necros:

Ubuntu releases after 10.04 LTS do no longer provide unfs3. Unfs3 is useful when one want to setup a fog server in a container with OpenVZ or LXC. Nfs kernel server cannot run in these containers.

= Prerequisites =

* A computer (physical or virtual) running Ubuntu 14.04 Server, may or may not using LVM, with available space in at least one volume group

= Network setup on the LXC host =

Setup a bridge on the computer, with at least one ethernet interface attached to it.

apt-get install bridgeutils

edit the file '''/etc/network/interfaces''' and add the following lines. '''Please ensure you're not using a SSH session''', because you may lose your connection !

Add the following lines :
auto br0
iface br0 inet static
address 192.168.1.2
netmask 255.255.255.0
gateway 192.168.1.1
bridge_ports eth0
bridge_fd 0
bridge_maxwait 0

Reboot the computer and check network connectivity

= LXC container creation =

First, create a LXC container running Ubuntu. The version is the latest LTS version available at the moment of creating the container

lxc-create -n server-fog -t ubuntu -B lvm --vgname vg --lvname lv-server-fog --fssize=10G --fstype=ext4

This will create a logical volume '''lv-server-fog''' in the volume group '''vg0''', with a 10GB ext4 filesystem. The container wil be named '''server-fog'''.

Edit the file '''/var/lib/lxc/server-fog/config''' to assign a static IP address to

You have to download, compile and install unfs3 from sources.

* [http://sourceforge.net/projects/unfs3/files/ Download unfs3]
* decompress the archive : tar zxf unfs3-0.9.22.tar.gz
* apt-get install build-essential make flex bison
* cd unfs3-0.9.22
* ./configure
* make
* make install
* make install-init
* edit /etc/init.d/unfsd and replace the occurence of /usr/sbin/unfsd with /usr/local/sbin/unfsd
* /etc/init.d/unfsd start
* check unfsd is running : ps -ef | grep unfsd
* if it runs, then run update-rc.d unfsd defaults

Install and configure fog as usual.

If you want to setup a separate volume for your images :

* assuming you want to use a logical volume (LVM) /dev/vg0/lv with a ext3 filesystem :
* run your container and move all files located in /images into an other location (/root/images-bak), including the hidden file /images/.mntcheck
* from the lxc host, open /var/lib/your-container/fstab and add the following line : /dev/vg0/lv images ext3 defaults 0 0
* restart the container, and check the nex volume is available : run mount without any argument.
* If the LVM volume has been successfully mounted, move back the files backed up in /root/images-bak. Note there is no slash before '''images'''.
* chmod 777 /images

Ubuntu 14.04 and LXC containers

2015-02-28T15:18:55Z

Necros:

Ubuntu releases after 10.04 LTS do no longer provide unfs3. Unfs3 is useful when one want to setup a fog server in a container with OpenVZ or LXC. Nfs kernel server cannot run under these containers.

You have to download, compile and install unfs3 from sources.

* [http://sourceforge.net/projects/unfs3/files/ Download unfs3]
* decompress the archive : tar zxf unfs3-0.9.22.tar.gz
* apt-get install build-essential make flex bison
* cd unfs3-0.9.22
* ./configure
* make
* make install
* make install-init
* edit /etc/init.d/unfsd and replace the occurence of /usr/sbin/unfsd with /usr/local/sbin/unfsd
* /etc/init.d/unfsd start
* check unfsd is running : ps -ef | grep unfsd
* if it runs, then run update-rc.d unfsd defaults

Install and configure fog as usual.

If you want to setup a separate volume for your images :

* assuming you want to use a logical volume (LVM) /dev/vg0/lv with a ext3 filesystem :
* run your container and move all files located in /images into an other location (/root/images-bak), including the hidden file /images/.mntcheck
* from the lxc host, open /var/lib/your-container/fstab and add the following line : /dev/vg0/lv images ext3 defaults 0 0
* restart the container, and check the nex volume is available : run mount without any argument.
* If the LVM volume has been successfully mounted, move back the files backed up in /root/images-bak. Note there is no slash before '''images'''.
* chmod 777 /images

Ubuntu 14.04 and LXC containers

2015-02-27T22:20:09Z

Necros:

Ubuntu releases after 10.04 LTS do no longer provide unfs3 to workaround OpenVZ and LXC containers limitations

You have to download, compile and install unfs3 from sources.

* [http://sourceforge.net/projects/unfs3/files/ Download unfs3]
* decompress the archive : tar zxf unfs3-0.9.22.tar.gz
* apt-get install build-essential make flex bison
* cd unfs3-0.9.22
* ./configure
* make
* make install
* make install-init
* edit /etc/init.d/unfsd and replace the occurence of /usr/sbin/unfsd with /usr/local/sbin/unfsd
* /etc/init.d/unfsd start
* check unfsd is running : ps -ef | grep unfsd
* if it runs, then run update-rc.d unfsd defaults

Install and configure fog as usual.

If you want to setup a separate volume for your images :

* assuming you want to use a logical volume (LVM) /dev/vg0/lv with a ext3 filesystem :
* run your container and move all files located in /images into an other location (/root/images-bak), including the hidden file /images/.mntcheck
* from the lxc host, open /var/lib/your-container/fstab and add the following line : /dev/vg0/lv images ext3 defaults 0 0
* restart the container, and check the nex volume is available : run mount without any argument.
* If the LVM volume has been successfully mounted, move back the files backed up in /root/images-bak. Note there is no slash before '''images'''.
* chmod 777 /images

Ubuntu 14.04 and LXC containers

2015-02-27T21:16:51Z

Necros:

Ubuntu 14.04 and LXC containers

2015-02-27T21:12:28Z

Necros:

Ubuntu releases after 10.04 LTS do no longer provide unfs3 to workaround OpenVZ and LXC containers limitations

You have to download, compile and install unfs3 from sources.

* [http://sourceforge.net/projects/unfs3/files/ Download unfs3]
* decompress the archive : tar zxf unfs3-0.9.22.tar.gz
* apt-get install build-essential make flex bison
* cd unfs3-0.9.22
* ./configure
* make
* make install
* make install-init
* edit /etc/init.d/unfsd and replace the occurence of /usr/sbin/unfsd with /usr/local/sbin/unfsd
* /etc/init.d/unfsd start
* check unfsd is running : ps -ef | grep unfsd
* if it runs, then run update-rc.d unfsd defaults

Install and configure fog as usual.

If you want to setup a separate volume for your images :

assuming you want to use a logical volume (LVM) /dev/vg0/lv with a ext3 filesystem :

run your container and move all files located in /images into an other location (/root/images-bak), including the hidden file /images/.mntcheck

from the lxc host, open /var/lib/your-container/fstab and add the following line

/dev/vg0/lv images ext3 defaults 0 0

restart the container, and check the nex volume is available : run mount without any argument.
If the LVM volume has been successfully mounted, move back the files backed up in /root/images-bak.
Note there is no slash before '''images'''.

Ubuntu 14.04 and LXC containers

2015-02-27T19:43:32Z

Necros: Created page with "Ubuntu releases after 10.04 LTS do no longer provide unfs3 to workaround OpenVZ and LXC containers limitations You have to download, compile and install unfs3 from sources. ..."

WorkingDevices

2014-01-04T20:49:05Z

Necros: /* Hardware */ Suggestion for virtual machines hosts !

== Devices that are known/tested to work with FOG Imaging solution. ==

If you have a device that is known to work with FOG, please post it on this page.

We would like to thank for following manufacturers for sending devices to us to verify their devices will function with FOG:

* ByteSpeed Computers (http://www.bytespeed.com),

=== Computers ===

{| class="wikitable sortable" border="1" cellspacing="0" cellpadding="3"
|-
! Manufacturer !! Model !! Type !! Kernel Version !! Date !! Notes
|-
| Acer || Aspire One D150-1920 || Laptop || n/a || n/a ||
|-
| Acer || AspireOne AOA150 || Netbook || n/a || n/a ||
|-
| Acer || Aspire One D250 || Netbook || n/a || n/a || Must use Multiple Partition Image - Single Disk (Not resizable)
|-
| Acer || Aspire 1520 || Laptop || Kernel 2.6.24-ks || Requires kernel argument vga=6 to have a working display ||
|-
| Acer || Aspire 5310 || Laptop || n/a || n/a ||
|-
| Acer || Aspire 5315 || Laptop || n/a || n/a ||
|-
| Acer || Aspire 5670 Series || Laptop || n/a || n/a ||
|-
| Acer || Aspire 5735 || Laptop || n/a || n/a ||
|-
| Acer || Aspire 5920 || Laptop || n/a || n/a ||
|-
| Acer || Aspire 5920G || Laptop || n/a || n/a ||
|-
| Acer || Aspire 6930G || Laptop || n/a || n/a ||
|-
| Acer || L460 Series || Desktop || n/a || n/a ||
|-
| Acer || TravelMate 270 Series || Laptop || n/a || n/a ||
|-
| Acer || TravelMate 290 Series || Laptop || n/a || n/a ||
|-
| Acer || TravelMate 530 Series || Laptop || n/a || n/a ||
|-
| Acer || TravelMate 6592 || Laptop || n/a || n/a ||
|-
| Acer || TravelMate 6410 || Laptop || n/a || n/a ||
|-
| Acer || TravelMate 7530 || Laptop || 0.28 || 2009-11-17 || South bridge ATI/AMD SB700. Cannot access SATA hard drive with kernel 0.27 and probably older ones. Use kernel 0.28
|-
| Acer || Veriton L410 || Desktop || n/a || n/a ||
|-
| Acer || Veriton L6610G || Desktop || n/a || 2011-08-03 || Enable LAN Boot in BIOS: Advanced > Integrated Peripherals > Onboard LAN Option Rom
|-
| Acer || Veriton M410 || Desktop || n/a || n/a || Requires kernel args: acpi=force or acpi=off See the following forum post [https://sourceforge.net/projects/freeghost/forums/forum/716419/topic/3441761]
|-Kernel-2.6.35.7
| Acer || Veriton M480G|| Desktop || Kernel 2.6.35.3-PS || 2011-03-23 ||
|-
| Acer || Veriton X680B || Desktop || n/a || n/a || Works with: Kernel-2.6.35.7 Download [http://sourceforge.net/projects/freeghost/files/Kernels/Kernel-2.6.35.7/]
|-
| Aopen || MP57-D || Desktop || FOG 0.32 || 2012-02-29 || Enable PXE in BIOS
|-
| Aopen || DE57-HA || Desktop || FOG 0.32 || 2012-02-29 || Enable PXE in BIOS
|-
| Asus || L3800 || Laptop || n/a || n/a ||
|-
| Asus || L4R (Ergo Ensis L4500R) || Laptop || n/a || n/a || Buggy PXE - will boot roughly 1 out of 5 tries. gPXE works fine. tested with FOG 0.28
|-
| Asus || EEE Top ET1601 || Touchscreen nettop || n/a || n/a || Requires PS Kernel
|-
| Asus || EEE Box B202 || Nettop || n/a || n/a ||
|-
| Asus || EEE Box EB1007 || Nettop || FOG 0.29 || 2012-05-01 || Change BIOS, AHCI -> IDE
|-
| Asus || EEE Box EB1012P || Nettop || FOG 0.29 || 2012-05-22 || Change BIOS, AHCI -> IDE, Crucial SSD
|-
| Asus || EEE Box EB1033 || Nettop || FOG 0.29 || 2013-03-11 || Change BIOS, AHCI -> IDE, Crucial SSD
|-
| Asus || EeePC 1000HE || NetBook || FOG 0.29 || n/a ||
|-
| Asus || EeePC 1005PE || NetBook || FOG 0.29 || n/a ||
|-
| Asus || EeePC 1016PT || NetBook || FOG 0.29 || n/a ||
|-
| Asus || G1S || Laptop || FOG 0.29 || n/a ||
|-
| Asus || Z91E (Ergo Ensis S Z9100E) || Laptop || n/a || n/a || Works fine with FOG 0.28
|-
| Boxx || 7500 series || Desktop || FOG 0.29 || 2011-03-03 || works with FOG 0.29, both Tyan and SuperMicro mobo versions
|-
| ByteSpeed || 10" N450 Netbook || Laptop/Netbook || Core (2.6.36.1) || n/a || Works with 'Core' Kernel
|-
| Compaq || Armada 1700 || Laptop || FOG 0.29 || 2010-11-08 || Using PCMCIA Cardbus NICs under Ubuntu 10.x. See "Known issues" under Ubuntu.
|-
| Compaq || Armada 1750 || Laptop || FOG 0.29 || 2010-11-08 || Using PCMCIA Cardbus NICs under Ubuntu 10.x. See "Known issues" under Ubuntu.
|-
| Compaq || iPAQ 777 || Desktop || n/a || n/a || BIOS sees max 10GB disk.
|-
| Compaq || Presario SR1607FR || Desktop || FOG 0.32 || 2012-06-06 || kernel 2-6-35-7-ks
|-
| Data Limited || DLI 8300 || Tablet || n/a || 2009-11-1 || Rugged tablet
|-
| Dell || Dimension E510 || Desktop || n/a || n/a ||
|-
| Dell || Dimension 2400 || Desktop || n/a || n/a ||
|-
| Dell || Dimension 3000 || Desktop || n/a || n/a ||
|-
| Dell || Dimension 4100 || Desktop || n/a || n/a ||
|-
| Dell || Dimension 4600 || Desktop || n/a || n/a ||
|-
| Dell || Inspiron 1464 || Laptop || n/a || n/a ||
|-
| Dell || Inspiron 1525 || Laptop || n/a || n/a ||
|-
| Dell || Inspiron 1545 || Laptop || FOG 0.29 || 2011-03-14 ||
|-
| Dell || Inspiron 1546 || Laptop || n/a || n/a ||
|-
| Dell || Inspiron 3800 || Laptop || FOG 0.29 || 2010-11-08 || Using PCMCIA Cardbus NICs under Ubuntu 10.x. See "Known issues" under Ubuntu.
|-
| Dell || Inspiron 4100 || Laptop || n/a || n/a ||
|-
| Dell || Inspiron 8600 || Laptop || n/a || n/a ||
|-
| Dell || Latitude D520 || Laptop || n/a || 2011-06-22 ||
|-
| Dell || Latitude D630 || Laptop || 2.6.35.7 KS || 2011-02-24 ||
|-
| Dell || Latitude D830 || Laptop || 2.6.35.7 KS || 2011-02-24 ||
|-
| Dell || Latitude 131L || Laptop || n/a || n/a ||
|-
| Dell || Latitude 2100 || NETBOOK|| 0.28 || 3-26-10 || must reformat and repartition disk to single partition, reload WinXP SP3 using provided disks. Upload image fine after rebuilding Windows. Defrag several times before doing upload.||
|-
| Dell || Latitude D410 || Laptop || n/a || n/a ||
|-
| Dell || Latitude D430 || Laptop || n/a || n/a ||
|-
| Dell || Latitude D510 || Laptop || n/a || n/a ||
|-
| Dell || Latitude D520 || Laptop || n/a || n/a ||
|-
| Dell || Latitude D530 || Laptop || n/a || n/a ||
|-
| Dell || Latitude D531 || Laptop || n/a || n/a || the fix seems to be disable PC-Card/FireWire in the BIOS if you have [[Dell_D531_laptop | reported errors]]
|-
| Dell || Latitude D600 || Laptop || n/a || n/a ||
|-
| Dell || Latitude D610 || Laptop || 2.6.35.7 KS || 2011-02-24 ||
|-
| Dell || Latitude D620 || Laptop || 2.6.35.7 KS || 2011-02-24 ||
|-
| Dell || Latitude D630 || Laptop || 2.6.35.7 KS || 2011-02-24 ||
|-
| Dell || Latitude D810 || Laptop || n/a || n/a ||
|-
| Dell || Latitude D820 || Laptop || 2.6.35.7 KS || 2011-02-24 ||
|-
| Dell || Latitude D830 || Laptop || 2.6.35.7 KS || 2011-02-24 ||
|-
| Dell || Latitude E5400 || Laptop || 2.6.33.0-KS || n/a ||
|-
| Dell || Latitude E5500 || Laptop || n/a || n/a ||
|-
| Dell || Latitude E6320 || Laptop || n/a || 2011-05-31 || No issues, used .39 kernel and a few below it ||
|-
| Dell || Latitude E6400 || Laptop || 2.6.35.7 KS || 2011-02-24 ||
|-
| Dell || Latitude E6410 || Laptop || 2.6.35.7 KS || 2011-02-24 ||
|-
| Dell || Latitude E6420 || Laptop || >= FOG 0.30 || 2011-05-11 || Fog with throw a few errors about an unsupported BIOs but imaging will continue and work fine. ||
|-
| Dell || Latitude E6430 || Laptop || 3.6.9 FOG.32 || 1/29/2013 || Works with factory SSD (Samsung).
|-
| Dell || Latitude E6500 || Laptop || 2.6.35.7 KS || 2011-02-24 ||
|-
| Dell || Latitude E6510 || Laptop || 2.6.35.7 KS || 2011-02-24 ||
|-
| Dell || Latitude XT || Laptop || n/a || n/a || Tablet PC
|-
| Dell || Latitude XT 2 || Laptop || n/a || n/a || Tablet PC
|-
| Dell || Optiplex 160 || Desktop || 3.2.4.core|| 2012-02-15 || 0.32 works well
|-
| Dell || Optiplex 170L || Desktop || n/a || n/a ||
|-
| Dell || Optiplex 210L || Desktop || n/a || n/a ||
|-
| Dell || Optiplex GX150 || Desktop || n/a || n/a ||
|-
| Dell || Optiplex GX200 || Desktop || n/a || n/a ||
|-
| Dell || Optiplex GX240 || Desktop || n/a || n/a ||
|-
| Dell || Optiplex GX260 || Desktop || n/a || n/a ||
|-
| Dell || Optiplex GX270 || Desktop || Kitchen Sink (ALL) || 2012-09-20 || DOES NOT work with Kernel 3.3.3.core or Kernel 3.2.4.core. DOES work with FOG 0.32 default Kernel.
|-
| Dell || Optiplex GX280 || Desktop || Kitchen Sink (ALL) || 2009-01-23 ||
|-
| Dell || Optiplex GX520 || Desktop || n/a || n/a ||
|-
| Dell || Optiplex GX620 || Desktop || 2.6.39.1 Core || 2011-09-06 ||
|-
| Dell || Optiplex SX280 || Desktop || n/a || n/a ||
|-
| Dell || Optiplex 320 || Desktop || n/a || n/a || kernel args: acpi=force irqpoll - Use Dell Bios 1.1.12
|-
| Dell || Optiplex 330 || Desktop || n/a || n/a ||
|-
| Dell || Optiplex 360 || Desktop || n/a || 2012-04-03 || Ubuntu 10.x w/ FOG .32
|-
| Dell || Optiplex 380 || Desktop || n/a || n/a || Requires Kernel: 2.6.32.1.PS
|-
|-
| Dell || Optiplex 390 || Desktop || n/a || 2011-11-25 || With FOG 0.32, use [http://www.fogproject.org/wiki/index.php?title=FIX:_Chainloading_alternate_SYSLINUX_to_force_boot_from_first_hard_drive Syslinux FIX] and disable Deep Sleep in BIOS
|-
| Dell || [[Optiplex 740]] || Desktop || PS (2.6.28.7) || n/a || Problematic http://sourceforge.net/forum/forum.php?thread_id=2335674&forum_id=716419
Works with 740 Enhanced with bios version 2.1.8 and 2.2.2
|-
| Dell || Optiplex 745 || Desktop || n/a || n/a || Working with the latest bios 2.6.2
|-
| Dell || Optiplex 755 || Desktop || 2.6.35.7 KS || 2011-02-24 ||
|-
| Dell || Optiplex 760 || Desktop || n/a || n/a || With Kernel: 2.6.28 or FOG 0.25+. Problematic with newer kernel (at least 2.6.36.1 Core +): http://fogproject.org/forum/threads/snow-screen-with-hp-elitebook-8460p.164/
|-
| Dell || Optiplex 780 || Desktop || 2.6.35.7 KS || 2011-09-06 || Not working with kernel 2.6.39.1 Core
|-
| Dell || Optiplex 790 || Desktop || n/a || 2011-11-25 || Same as Optiplex 390
|-
| Dell || Optiplex 7010 || Desktop || 3.6.9 FOG.32 || 1/29/2013 || Similar to Optiplex 790
|-
| Dell || Optiplex 960 || Desktop || KS FOG 0.27 || 7/20/2009 ||
|-
| Dell || Optiplex 980 || Desktop || FOG 0.28 || 05/26/2011 ||Does not work with .30 We are using .30 and changed these hosts to use the .28 kernel
|-
| Dell || Optiplex 990 || Desktop || >= FOG 0.30 || 2011-05-05 || Intel NIC. Would not work with 0.29, Works with 0.30 but freezes after booting into FOG. However, hitting ESC allows you to continue. You will receive an error about incompatible BIOs, then it will start imaging. Confirmed working with .31
|-
| Dell || Precision 340 || Desktop || n/a || n/a ||
|-
| Dell || Precision 350 || Workstaion || FOG 0.29 || 2011-03-14 ||
|-
| Dell || Precision 370 || Desktop || FOG 0.30 || 2011-03-24 || Fog message says doesn't recognize system. Did quick inventory to get system registered. Had to reboot twice when initial upload image task didn't work. Second try went through ok. Haven't tested restore.
|-
| Dell || Precision 390 || Desktop || n/a || 2009-05-21 ||
|-
| Dell || Precision 490 || Desktop || n/a || n/a ||
|-
| Dell || Precision T3400 || Desktop || n/a || n/a ||
|-
| Dell || Precision T3500 || Desktop || n/a || n/a ||
|-
| Dell || Precision T5400 || Desktop || n/a || n/a ||
|-
| Dell || Precision M60 || Laptop || FOG 0.32 || 2012-05-07 ||
|-
| Dell || Precision M4400 || Laptop || n/a || n/a ||
|-
| Dell || PowerEdge SC1425 || Server || 2.6.29 || 2009-07-07 || none - works great
|-
| Dell || PowerEdge SC1435 || Server || 2.6.29 || 2009-07-07 || none - works great
|-
| Dell || [[PowerEdge R200]] || Server || 2.6.28 || 2009-07-07 || ** Had to roll back to FOG Kernel-2.6.28.7.PS - Kernel-2.6.29 would not load tg3 module (see possible Linux bug discussion [http://lkml.indiana.edu/hypermail/linux/kernel/0903.3/00186.html here]). Also had to add "-m" option to Partimage... see [[Dell PowerEdge R200|here]] for details
|-
| Dell || Studio 1557/1558 (PP39L) || Laptop || FOG 0.32 || n/a || default kernel
|-
| Dell || Vostro 200 || Desktop || n/a || n/a || I needed change the SATA mode to ATA in the BIOS
|-
| Dell || Vostro 220 || Desktop || n/a || n/a || Works with latest FOG "PS" kernel, with either BIOS setting ATA or AHCI setting
|-
| Dell || Vostro 220 || Desktop || 2.6.39.1.core || 2012-02-15 || 0.32 works well
|-
| Dell || Vostro 230 || Desktop || 2.6.39.1.core || 2012-02-15 || 0.32 works well
|-
| Dell || Vostro 260 || Desktop || 2.6.39.1.core || 2012-02-15 || 0.32 works well
|-
| Dell || Vostro 320 || All-In-One Desktop || n/a || 2010-01-31 || Sata set to Compatible in BIOS.
|-
| Dell || Vostro 410 || Desktop || 2.6.35.7 KS || 2012-12-18 || "irqpoll" in kernel arguemnts
|-
| Dell || Vostro 460 || Desktop || 2.6.35.7-KS || 2011-05-27 ||
|-
| Dell || Vostro 1220 || Laptop || 2.6.31.1 || 2009-12-06
|-
| Dell || Vostro 1520 || Desktop || n/a || n/a || Gives error "'''ide1: Unexpected interrupt, status=0xff, count=n'''" during imaging, but works anyway.
|-
| Dell || Vostro Vostro 3500 || Desktop || n/a || n/a || Works with this kernel Kernel - 2.6.39 Core FOG ID: 1045 Date: May 27, 2011 Version: 2.6.39 FOG Type: Core
|-
| Dell || Vostro 1700 || Desktop || n/a || n/a ||
|-
| Dell || Vostro 1700 || Desktop || Kernel FOG 0.30 || 2011-05-06 || Must specify /dev/sdb un web interface cause /dev/sda seems to be something else|| --
|-
| eMachines || E520 || Laptop || n/a || n/a ||
|-
| Fujitsu || t4010 Tablet PC || Laptop || n/a || n/a ||
|-
| Fujitsu-Siemens || Esprimo Mobile U9200 || Laptop || n/a || n/a || sata set to compatible in the bios
|-
| Fujitsu-Siemens || Esprimo Mobile V5505 || Laptop || n/a || 2009-03-13 ||
|-
| Fujitsu-Siemens || Esprimo Mobile V5515 || Laptop || n/a || 2010-12-14 || Needs [http://www.fogproject.org/wiki/index.php?title=SiS-191_based_NIC SiS-191 NIC workaround to image]
|-
| Fujitsu-Siemens || Esprimo E5600 || Desktop || n/a || 2009-10-01 ||
|-
| Fujitsu-Siemens || Esprimo P5700 || Desktop || n/a || n/a ||
|-
| Fujitsu-Siemens || Esprimo P2530 || Desktop || n/a || 2009-03-18 || sata set to enhanced in the bios
|-
| Fujitsu-Siemens || Esprimo P2560 || Desktop || FOG 0.32 || 2012-02-29 ||
|-
| Fujitsu-Siemens || Esprimo P3510 || Desktop || FOG 0.32 || 2012-02-29 ||
|-
| Fujitsu-Siemens || Scenic Edition X 102 || n/a || n/a || n/a ||
|-
| Fujitsu-Siemens || Scenic P300 sis661|| Desktop || FOG 0.32 || 2012-06-12 || Default kernel, model with sis based mainboard
|-
| Fujitsu-Siemens || Scenic P320 || Desktop || FOG 0.32 || 2012-02-29 ||
|-
| Fujitsu-Siemens || Scenic C610 || n/a || n/a || n/a ||
|-
| Gateway || E-4100 || Desktop || ALT || n/a || Requires ALT kernel with Gateway BIOS
|-
| Gateway || E-4300 || Desktop || ALT || n/a || Using ALT for E4100 but should work without.
|-
| Gateway || E-4500S || Desktop || Default || 2011-07-05 || Had to enable Legacy mode for the Sata/IDE controller in Bios
|-
| Gateway || E-4610S || Desktop || n/a || n/a ||
|-
| Gateway || E295C || Laptop || n/a || n/a ||
|-
| Gateway || E155C || Laptop || n/a || n/a ||
|-
| Gateway || E265M || Laptop || n/a || n/a ||
|-
| Gateway || E275M || Laptop || ALT || n/a || Using ALT for E4100 but should work without.
|-
| Gateway || E460M || Laptop || ALT || n/a || Using ALT for E4100 but should work without. Requires kernel argument acpi=off
|-
| Gateway || E475M || Laptop || n/a || n/a ||
|-
| Gateway || MX3417 || Laptop || n/a || n/a ||
|-
| Gateway || MX6931 || Laptop || n/a || n/a ||
|-
| Gateway || MX6448 || Laptop || n/a || n/a ||
|-
| Gateway || Profile 3 || Desktop || n/a || n/a ||
|-
| Gateway || Profile 4 || Desktop || n/a || n/a || Using ALT, otherwise display was scrambled for this model's GEForce MX400. Screen will take time to wake, it can make you think PXE not loading.
|-
| Gateway || Profile 6 || Desktop || n/a || n/a ||
|-
| HiGrade || ?L100 || Laptop || n/a || n/a ||
|-
| HP || Mini 2140 || Netbook || n/a || n/a ||
|-
| HP || 2710p || Laptop || Kitchen Sink (ALL) || 2009-01-23 ||
|-
| HP || 2730P || Laptop || Peter Sykes (ALL) || 2009-01-23 ||
|-
| HP || 3125 || Laptop || n/a || 2013-06-25 || Not compatible with Kernel 3.8.8.core
|-
| HP || 8510p || Laptop || n/a || n/a || not tested yet with sata native enabled in bios
|-
| HP || Compaq 6000 Pro || All-in-one || 0.31 || 2011-06-22 ||
|-
| HP || Compaq 6000 Pro || Desktop || n/a || 2011-08-04 ||
|-
| HP || Compaq 6005 Small || Desktop || 0.31 || 2011-06-22 ||
|-
| HP || Compaq 6200 Pro || Desktop || 0.32 || 2011-08-04 ||
|-
| HP || Compaq 6710b || Laptop || n/a || n/a ||
|-
| HP || Compaq 6715s || Laptop || n/a || n/a ||
|-
| HP || Compaq 6715b || Laptop || n/a || n/a ||
|-
| HP || Compaq 6720s || Laptop || n/a || n/a ||
|-
| HP || Compaq 6730b || Laptop || n/a || 2009-06-10 ||
|-
| HP || Compaq 6735b || Laptop || n/a || n/a || Working also with AHCI SATA settings in BIOS (0.26)
|-
| HP || [[HP Compaq 6910p|Compaq 6910p]] || Laptop || n/a || n/a ||
|-
| HP || Compaq n610c || Laptop || n/a || n/a || Working with Alt or KS kernel
|-
| HP || nc6320 || Laptop || n/a || n/a ||
|-
| HP || nc6400 || Laptop || FOG 0.32 || 2012-05-07 ||
|-
| HP || nx6100 || Laptop || FOG 0.32 || 2012-05-07 ||
|-
| HP || Compaq NX6325 || Laptop || n/a || n/a ||
|-
| HP || 550 || Laptop || n/a || n/a ||
|-
| HP || D530 || Desktop || n/a || n/a || Requires Translation Mode to be set to LBA Assisted for HDD in BIOS
|-
| HP || DC5100 || Desktop || n/a || n/a ||
|-
| HP || DV9620US || Laptop || n/a || 2010-05-04 ||
|-
| HP || [[HP DC5700|DC5700]] || Desktop || n/a || n/a ||
|-
| HP || DC5750 || Desktop || n/a || n/a ||
|-
| HP || DC5800 || Desktop || n/a || n/a ||
|-
| HP || DC5850 || Desktop || n/a || n/a ||
|-
| HP || DC7100 || Desktop || n/a || n/a ||
|-
| HP || DC7600 || Desktop || Kitchen Sink (ALL) || 2009-01-23 ||
|-
| HP || DC7700 || Desktop || 3.2.4.core || 2012-02-15 || 0.32 works well. ||
|-
| HP || DC7800 || Desktop || 0.31 || 2011-06-22 || After the image process we had to enable Legacy mode on the Sata controller.
|-
| HP || DC7900 || Desktop || Kitchen Sink (ALL) || 2009-10-06 || Tested with Kernel-2.6.31.1.kitchensink. Blue screens in AHCI mode unless drivers are loaded, deactivate it in BIOS or install AHCI driver before upload.
|-
| HP || DC8200 || Desktop || 0.33 Beta with core 3.8.8 and 3.2.4 || 2013-08-20 || Got an ioctl error but working without problems.
|-
| HP Compaq || D610 || Laptop || 3.2.4.core || 2012-02-15 || 0.32 works well
|-
| HP || 620 || Laptop || 3.2.4.core || 2012-02-15 || 0.32 works well
|-
| HP Compaq || 8200 Elite || Desktop || 3.2.4.core || 2012-02-15 || 0.32 works well
|-
| HP || DX2200MT || Desktop || n/a || 2011-07-13 ||
|-
| HP || DX2000MT || Desktop || n/a || n/a || Requires kernel args: acpi=force irqpoll, acpi=off also works.
|-
| HP || DX6100MT || Desktop || n/a || n/a || Requires Translation Mode to be set to LBA Assisted for HDD in BIOS
|-
| HP || [[HP DX2250|DX2250]] || Desktop || n/a || n/a ||
|-
| HP || [[HP DX2300|DX2300]] || Desktop || n/a || n/a ||
|-
| HP || DX2400 || Desktop || n/a || n/a ||
|-
| HP || Business Desktop 6000 Pro || Desktop || n/a || 2009-12-15 ||
|-
| HP || Business Desktop 6005 Pro || Desktop || 0.28 || 15-02-2010 || Only seems to with "Multiple Partition Image - Single Disk"
|-
| HP || Business Desktop DX7500 || Desktop || n/a || 2010-01-04 ||
|-
| HP || Business Desktop 8000 Elite || Desktop || n/a || 2010-05-17 || 0.29 Kernel - 2.6.35.7 PS, with "acpi=off irqpoll hpet=disable" kernel arguments (may work without them). Kernel 2.6.37-core panics.
|-
| HP || Business Desktop 8100 Elite || Desktop || n/a || 2010-01-18 || 0.29 Kernel - 2.6.35.7 PS otherwise poor performance.
|-
| HP || HP Touch Smart 9100 Business PC || Desktop || n/a || 2010-07-16 || 0.29
|-
| HP || XW4400 || Desktop || n/a || n/a ||
|-
| HP || XW4600 || Desktop || n/a || 2011-08-03 ||
|-
| HP || xw9400 || Desktop || n/a || 2011-03-03 || Works fine with FOG 0.29, Windows 7
|-
| HP || Z400 || Desktop || n/a || 2011-03-03 || Works fine with FOG 0.29, Windows 7
|-
| HP || Z600 || Desktop || n/a || 2011-03-03 || Works fine with FOG 0.29, Windows 7
|-
| HP || Z800 || Desktop || n/a || 2011-03-03 || Works fine with FOG 0.29, Windows 7
|-
| HP || Pavilion dv4000 || Laptop || n/a || 2010-08-18 || 0.29
|-
| HP || Pavilion dv7-3125ef || Laptop || default Kernel 0.30 || 2011-05-27 ||
|-
| HP || [[HP Pavilion 734n|Pavilion 734n]] || Desktop || n/a || n/a ||
|-
| HP || NX7400 || Laptop || n/a || n/a ||
|-
| HP || Pavilion dm1-3010nr || Laptop || Kernel-2.6.35.7.kitchensink || 9/14/2011 || Works with Kernel-2.6.35.7.kitchensink and kernel arugements acpi=off noirq pci=use_crs
|-
| HP || NX7300 || Laptop || n/a || n/a ||
|-
| HP || Pavilion ze2000 || Laptop || n/a || n/a ||
|-
| HP || Mini 1101 || Laptop || n/a || n/a ||
|-
| HP || Mini Note || Laptop || n/a || n/a ||
|-
| HP || Mini 5102 || Laptop || 0.29 || 2010-07-09 || Very poor performance on imaging until acpi=force irqpoll was used as a Host Kernel Argument
|-
| HP || Mini 5103 || Netbook || n/a || 2012-01-19 || Disabling audio in BIOS will circumvent extremely slow imaging issue
|-
| HP || Mini Note 110 || Laptop || n/a || n/a ||
|-
| HP || Mini 311-1037NR || Netbook || PS 2.6.28 || 2010-12-06 || FOG .29 with kernel arg acpi=off noirq pci=use_crs Win 7
|-
| HP || EliteBook 6930p || Laptop || n/a || n/a ||
|-
| HP || EliteBook 8440p || Laptop || FOG 0.32 || n/a ||
|-
| HP || EliteBook 8540p || Laptop || KS from Aug 10 2010 || 2010-03-30 || Did not recognize NIC until Kernel was updated to Kitchen Sink build from Aug 10 2010
|-
| HP || Pro 3000 MT || Desktop || 2.6.35.3 PS || 2011-02-02 ||
|-
| HP || Pro 3400 MT || Desktop || 2.6.28.7 PS || 2012-02-21 || Works well
|-
| HP || Pro 3015 MT || Desktop || 2.6.35.3 PS || 2010-08-25 || Requires kernel argument hpet=disable (if not disabled you will get ehci/ohci interrupt errors, very slow boot, and the ethernet device will no longer work while kernel initializes himself).
|-
| HP || ProBook 4510s || Laptop || 0.29 || 2010-07-09 || Requires gPXE boot disk
|-
| HP || ProBook 4515s || Laptop || FOG 0.28 || 2010-06-28 || May have a Blinking cursor after graphical FOG PXE menu and hard disk set to AHCI mode and using Windows XP.
|-
| HP || ProBook 4520s || Laptop || FOG 0.32 || 2012-05-07 ||
|-
| HP || ProBook 4525s || Laptop || FOG 0.29 || 2011-05-03 || May have a Blinking cursor after graphical FOG PXE menu (Bios F.08). Upon changing to bios F.09, no changes in behavior.
|-
| HP || ProBook 6440b || Laptop || n/a || n/a ||
|-
| HP || ProBook 6540b || Laptop || n/a || n/a ||
|-
| HP || t5730 || Thinclient || n/a || 2010-05-03 || 0.29
|-
| HP || t5730w 2GF/1GR || Thinclient || n/a || 2010-06-16 || 0.29
|-
| HP || dx7300 || Desktop || 0.26 || 2011-06-16 ||
|-
| HP || dx7400 || Desktop || 0.26 || 2011-06-16 ||
|-
| HP || ML110g5 || Server || 0.26 || 2011-06-16 ||
|-
| HP || ML150g6 || Server || 0.26 || 2011-06-16 ||
|-
| IBM || ThinkCentre S50 || Desktop || FOG 0.32 || 2012-05-07 ||
|-
| MSI || Hetis 900 || Desktop || 2.6.39.1.core || 2012-02-15 || 0.32 works well
|-
| MPC || TXTBook || Laptop || n/a || n/a || ATOM Based netbook
|-
| MPC || ClientPro 365 || n/a || n/a || n/a ||
|-
| MSI || Wind U100 || Netbook || n/a || 2009-05-15 ||
|-
| MSI || MegaBook S270 (Model MS-6855B) || Notebook || Fog 0.29 || 2011-01-06 ||
|-
| NEC || Powermate ML-7 || Desktop || Fog 0.28 || 2010-02-01 ||
|-
| NEC || Powermate ML-250 || Desktop || FOG 0.28 || 2010-02-01 || Mainboard Asus P5S800, BIOS Ver 160 updated to 216: cannot connect to TFTP Server if IP differs from DHCP server. Use GPXE as a workaround.
|-
| NEC || Powermate VL-350 || Desktop || n/a || 2009-06-25 || Requires kernel argument acpi=off irqpoll
|-
| NEC || Powermate VL-370 || Desktop || 2.6.30.1 KS || 2009-11-11 || Requires kernel argument acpi=off . If you don't set this argument, the BIOS will freeze on next boot. You will need to clear CMOS.
|-
| NEC || Versa One || Laptop || 2.6.35.3 PS || 2010-10-12 || Only worked with kernel 2.6.35.3 PS
|-
| Panasonic || Toughbook CF-W7 || Laptop || n/a || n/a ||
|-
| Omni Tech || OTC-3200D01850 || n/a || n/a || n/a ||
|-
| Omni Tech || OTC-H3111D00 || n/a || n/a || n/a ||
|-
| Omni Tech || OTC-H3243D00 || n/a || n/a || n/a ||
|-
| Lenovo || A55 || n/a || n/a || n/a ||
|-
| Lenovo || M51 || n/a || n/a || n/a ||
|-
| Lenovo || M55 || n/a || n/a || n/a ||
|-
| Lenovo || M55P || Desktop || 0.31/32 || 07-20-2011 ||
|-
| Lenovo || M57 || n/a || n/a || n/a ||
|-
| Lenovo || M58 || n/a || n/a || n/a ||
|-
| Lenovo || R60 || n/a || n/a || n/a ||
|-
| Lenovo || R61 || n/a || n/a || n/a ||
|-
| Lenovo || S9 || Laptop || n/a || n/a || Fails at within 30seconds of image uptake using (took image by placing hard disk in another Lenovo R500), Image loading works okay with v 0.28
|-
| Lenovo || S10e || Laptop || n/a || n/a || Netbook
|-
| Lenovo || S10-2 || Laptop || n/a || n/a || Netbook
|-
| Lenovo || ThinkCenter A70z || Desktop || 0.29 || 08/2010 || needs Kernel-2.6.35.3PS, BIOS 98KT13AUS
|-
| Lenovo || ThinkCenter E31 || Desktop || 0.32 || 09/2012 || needs kernel 3.3.3.core
|-
| Lenovo || ThinkCentre Edge71 || 1577-N8G || 0.32 || 11-06-2012 || Works with default 0.32 kernel
|-
| Lenovo || ThinkCenter M90z || Desktop || 0.29 || 08/2010 || works out of the box, BIOS 9BKT28AUS and 9BKT31AUS
|-
| Lenovo || ThinkCentre M75e || Desktop || 0.32 / 2.6.35.3 PS || 07/2011 ||
|-
| Lenovo || ThinkCenter T400 || Desktop || 0.29 || 08/2010 || works with Kernel-2.6.35.3PS
|-
| Lenovo || ThinkCenter T500 || Desktop || 0.29 || 08/2010 || works with Kernel-2.6.35.3PS
|-
| Lenovo || ThinkCenter T510 || Desktop || 0.29 || 08/2010 || works with Kernel-2.6.35.3PS
|-
| Lenovo || ThinkCenter X61 || Desktop || 0.29 || 08/2010 || works with Kernel-2.6.35.3PS
|-
| Lenovo || ThinkPad E520 || Laptop || 0.32 || 02-10-2012 ||
|-
| Lenovo || ThinkPad R61 || Laptop || 0.31 || 2011-06-22 ||
|-
| Lenovo || Thinkpad R400 || n/a || n/a || n/a ||
|-
| Lenovo || Thinkpad SL500 || n/a || n/a || n/a || Requires kernel argument irqpoll
|-
| Lenovo || Thinkpad SL410 || Laptop || 0.28 || n/a ||
|-
| Lenovo || Thinkpad Edge 13|| Laptop || 0.28 || n/a ||
|-
| Lenovo || Thinkpad Edge 15|| Laptop || 0.32 || n/a || Requires PXE Bzimage upgrade to 3.012
|-
| Lenovo || Thinkpad T60 || 1951-45G || 0.29 || 18-01-2011 ||
|-
| Lenovo || Thinkpad T61 || BK7+13G+CTO || 0.27 || 14-08-09 || right off the bat with 0.27
|-
| Lenovo || Thinkpad T400 || n/a || n/a || n/a ||
|-
| Lenovo || Thinkpad T410s || Laptop || 2.6.35.7 KS || 2011-02-24 || 0.29, Upload and deploy as Linux not Windows.
|-
| Lenovo || Thinkpad T420 || Laptop || n/a || n/a || 0.29, Need to run fdisk /mbr before laptop will boot after imaging.
|-
| Lenovo || Thinkpad T500 || Laptop || 0.28 || 15-02-2010|| Only seems to with "Multiple Partition Image - Single Disk"
|-
| Lenovo || Thinkpad W510 || Laptop || 0.32 || 08-23-2013 || kernel 2.6.35-4
|-
| Lenovo || Thinkpad x100e || Laptop || 0.29 || n/a ||
|-
| Lenovo || Thinkpad x200 || Laptop || n/a || n/a || (works with traditional HD and Solid State Disk)
|-
| Lenovo || Thinkpad x300 || Laptop || n/a || n/a || (regular and Solid State Disk)
|-
| Lenovo || Thinkpad x301 || Laptop || n/a || n/a || (regular and Solid State Disk)
|-
| Lenovo || Thinkpad x61 || Laptop || n/a || n/a ||
|-
| Lenovo || ThinkStation S20 || Desktop || 0.29 || 08/2010 || works with Kernel-2.6.35.3PS
|-
| Lenovo || ThinkStation D20 || Desktop || 0.29 || 08/2010 || works with Kernel-2.6.35.3PS
|-
| Lenovo || Z60 || n/a || n/a || n/a ||
|-
| IBM || 300 PL || n/a || n/a || n/a ||
|-
| IBM || Thinkcenter || n/a || n/a || n/a ||
|-
| IBM || Netvista || n/a || n/a || n/a ||
|-
| RM || WV949(SGR) || n/a || n/a || n/a ||
|-
| Samsung || NC10 || Laptop || n/a || n/a ||
|-
| Samsung || R20 (F00)|| Laptop || n/a || n/a ||
|-
| Samsung || R510|| Laptop || n/a || n/a || Requires kernel argument irqpoll
|-
| Samsung || R60 || Laptop || n/a || n/a ||
|-
| Samsung || R60Plus || Laptop || n/a || n/a ||
|-
| Shuttle || SA76G2 || Desktop || PS (2.6.28.7) || n/a || With Marvel Yukon Gigabit Ethernet Controller
|-
| Sony || VAIO PCG-K23 || Laptop || n/a || n/a ||
|-
| Sony || VAIO VGN-AR71M || Laptop || n/a || n/a ||
|-
| Sony || VAIO VGN-BZ31VT || Laptop || 0.28 (2.6.31) || 2010-04-07 ||
|-
| Sony || VAIO VGN-V2S || Desktop || n/a || n/a ||
|-
| Sun || xVM Virtualbox || Virtual Machine || n/a || 2009-05-12 ||
|-
| Toshiba || Tecra S1 || Laptop || n/a || n/a ||
|-
| Toshiba || Tecra S2 || Laptop || n/a || n/a ||
|-
| Toshiba || Tecra S3 || Laptop || n/a || n/a ||
|-
| Toshiba || Tecra S4 || Laptop || n/a || n/a ||
|-
| Toshiba || Tecra A3X || Laptop || n/a || n/a ||
|-
| Toshiba || Tecra A7-S254 || Laptop || n/a || n/a || Imaged using the latest fog server (0.27)
|-
| Toshiba || Tecra A9 || Laptop || n/a || n/a ||
|-
| Toshiba || Tecra A10 || Laptop || n/a || n/a ||
|-
| Toshiba || Tecra M10 || Laptop || n/a || n/a ||
|-
| Toshiba || Tecra S11 || Laptop || n/a || n/a || use FOG 0.28 is very slow, FOG 0.29 NOT working ! ( BIOS 2.20 )
|-
| Toshiba || Tecra S11-140 PTSE3E || Laptop || 0.29 || 2010-09-17 || Default kernel doesn't support ethernet interface. You must use the kernel 2.6.35.3 PS (KS doesn't work)
|-
| Toshiba || Tecra A10 || Laptop || n/a || n/a ||
|-
| Toshiba || Tecra M10 || Laptop || n/a || n/a ||
|-
| Toshiba || Protege M400 || Laptop || n/a || n/a ||
|-
| Toshiba || Protege M600 || Laptop || n/a || n/a ||
|-
| Toshiba || Protege M650 || Laptop || n/a || n/a ||
|-
| Toshiba || Protege M700 || Laptop || n/a || n/a ||
|-
| Toshiba || Protege M750 || Laptop || n/a || n/a ||
|-
| Toshiba || Protege M780 || Laptop || n/a || n/a ||
|-
| Toshiba || Protege R100 || Laptop || n/a || n/a ||
|-
| Toshiba || Protege R200 || Laptop || n/a || n/a ||
|-
| Toshiba || Protege R500 || Laptop || n/a || n/a ||
|-
| Toshiba || Protege R600 || Laptop || n/a || n/a || BIOS 1.60 or newer
|-
| Toshiba || Satellite A10-S127 || Laptop || default || 2009-04-28 ||
|-
| Toshiba || Satellite L300 || Laptop || n/a || n/a ||
|-
| Toshiba || Satellite L350 || Laptop || n/a || n/a ||
|-
| Toshiba || Satellite L670 || Laptop || 2.6.35 KS || 2011-04-06 ||
|-
| Toshiba || Satellite Pro S300-EZ1513 || Laptop || Default || 28JUL09 ||
|}

=== Hardware ===

====Controllers====
*LSI SAS 1068

====Motherboards====

{| class="wikitable sortable" border="1" cellspacing="0" cellpadding="3"
|-
! Manufacturer !! Model !! BIOS Version !! Onboard NIC !! Kernel Version !! Date !! Notes
|-
|Asus || M4N78-AM V2 || 1102 || Nvidia NForce || Fog 0.29 || 2011-02-12 || Upload test !
|-
|Asus || M5A88-M || 0505 || Realtek 8111E || 3.3.3 Core || 2013-01-13 || FOG 0.32, wouldn't boot with default kernel, but later discovered was another issue (not kernel related)
|-
|Asus || M4A89GTD-PRO/USB3 rev 1.x|| 2001 || Realtek 8111E || 3.3.3 Core || 2013-01-11 || FOG 0.32, also worked with default kernel
|-
|Asus || M4A78LT-M-LE || 0407 || Atheros AR8131 || 3.3.3 Core || 2013-01-10 || FOG 0.32, also worked with default kernel
|-
|ASRock || M3A785GXH/128M || 1.1 || Realtek RTL8111DL || .28 || 1.1.2010 || Works Great!
|-
|Gigabyte || GA-MA770-DS3 rev 1.0 || F6 || Realtek 8111B || 2.6.28.7 Peter Sykes || 2009-04-28 || FOG 0.26, required different kernel than default
|-
|Gigabyte || GA-78LMT-S2P rev ? || FB || Atheros AR8151 || 3.3.3 Core || 2013-01-14 || FOG 0.32, also worked with default kernel
|-
|Intel || DG31GL || n/a || n/a || n/a || n/a || n/a
|-
|Intel || D845BG || n/a || Intel Pro100VE || n/a || n/a || Problematic Intel Boot ROM version 4.0.19 (D845BGL)
|-
|Intel || DG35EC || n/a || n/a|| n/a || n/a || n/a
|-
|Intel || D945GCZ || n/a || n/a|| n/a || n/a || n/a
|-
|Intel || DQ965JO || n/a || n/a|| n/a || n/a || n/a
|-
|Intel || DP55WB || n/a || n/a|| n/a || n/a || n/a
|-
|Intel || DQ45CB || n/a || n/a|| n/a || n/a || n/a
|-
|Intel || DG35EC || n/a || n/a|| n/a || n/a || n/a
|-
|Jetway || NF93R-LF || n/a || 2 x Realtek RTL8111C || 2.6.30.1 ks || 2012-08-19 || kernel arguments (maybe not necessary) acpi=off irqpoll vga=6
|-
|Sapphire|| Pure Black X58 || n/a || 1 x Marvell Yukon || FOG 0.32 || 2013-12-14 || kernel arguments (maybe not necessary) acpi=off irqpoll vga=6
|}

=== Virtual Machines ===

{| class="wikitable sortable" border="1" cellspacing="0" cellpadding="3"
|-
! Manufacturer !! Model !! BIOS Version !! Onboard NIC !! Kernel Version !! Date !! Notes
|-
|Proxmox VE 3.1|| KVM virtual machine || Seabios 1.7.4 || 1 x Intel E1000 || FOG 0.32 || 2014-01-04 || VM CPU=Nehalem (not working with CPU=Host), kernel arguments (maybe not necessary) acpi=off irqpoll vga=6
|}

Create a windows 7 image for many different hardware

2013-03-27T18:04:21Z

Necros: /* Files for the reseal process */ added unattend.xml for windows 7 64 bits

[[Category:Windows]]
== Tools required ==

* [http://www.microsoft.com/downloads/fr-fr/details.aspx?FamilyID=696DD665-9F76-4177-A811-39C26D3B3B34 WAIK]
* [http://downloads.vmware.com/fr/d/info/desktop_downloads/vmware_player/3_0 VMWare Player]
* windows PE

= Create Master computers =

== configure the master VM ==
A Virtual Machine gives an easy way to backup your windows 7 installation before you lauch sysprep. This can be done by copying the virtual machine's folder in an other place. (You may also upload an image to your FOG server). This is very useful because you may have errors when trying your unattend.xml file. If an error occurs, I recommend to revert back your VM, correct the errors and try again. If you need to rebuild a new master image, you may alter date of your virtual machine before restoring it and prevent windows from complaints for activation. In an other hand you may have dificulties to instal the latest hotfixes from windows update. I recommend maintaining a private repository of all hotfixes. It is easy to install them with a batch script. This is also faster because you will not have to download them again and again.

Install VMWare player if not already done.

Configure the VM as following
* 2 microprocessors to install windows 7 with ACPI multiprocessor HAL.
* a 160 GB hard drive
* configure the VM BIOS to boot on the ethernet device first

'''Edit .vmx file''' describing your VM and edit the following line:

<pre>
SCSI0.Present="TRUE"
</pre>

Change this line to this:

<pre>
SCSI0.Present="FALSE"
</pre>

This will disable the SCSI controller which is useless when you don't have any SCSI virtual drive. This is known to cause some trouble when dealing with windows XP and sysprep [http://www.fogproject.org/wiki/index.php?title=Create_a_windows_XP_image_for_many_different_hardware#configure_the_master_VM] . To prevent any similar problem, disable it.

Boot your virtual machine and configure it to boot on the ethernet interface first, then DVD, then HDD.

== Install windows 7 ==

Use the needed version of windows 7 32 bits or 64 bits. Update to the latest SP and hotfixes.

== Prepare sysprep ==

=== Files for the reseal process ===

Create a folder in a USB flash disk named '''sysprep-7-32''' (for windows 7 32 bits). You should create an other folder for windows 7 64 bits. All files for each windows version in separate folders will maye your work very straightforward when you will need to recreate your master image.

In this folder create unattend.xml from the following example, or by reproducting it with WAIK [
http://blog.brianleejackson.com/sysprep-a-windows-7-machine-%E2%80%93-start-to-finish-v2]

Please note that this unattend.xml is for Windows 7 32 bits, french localized, and has first logon commands to register the licence KEY and activate it against Microsoft's activation server (Multiple Activation Key MAK). It seems the administrator account must be named in english. Its name appears localized after deploying the image.

The file is very similar for windows 7 64 bits (see below).

You have to
* set the administrator password on account definition section and autologon section
* set the licence key
* set Registered Organisation and Owner

'''unattend.xml 32 bits version'''
<pre>
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="generalize">
<component name="Microsoft-Windows-Security-SPP" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipRearm>1</SkipRearm>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Path>net user administrator /active:yes</Path>
<Order>1</Order>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipAutoActivation>true</SkipAutoActivation>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ShowWindowsLive>false</ShowWindowsLive>
<TimeZone>Romance Standard Time</TimeZone>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>fr-FR</InputLocale>
<SystemLocale>fr-FR</SystemLocale>
<UILanguage>fr-FR</UILanguage>
<UserLocale>fr-FR</UserLocale>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<AutoLogon>
<Password>
<Value>password</Value>
<PlainText>true</PlainText>
</Password>
<LogonCount>5</LogonCount>
<Enabled>true</Enabled>
<Username>administrator</Username>
</AutoLogon>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX </CommandLine>
<RequiresUserInput>true</RequiresUserInput>
<Order>1</Order>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<Order>2</Order>
<RequiresUserInput>false</RequiresUserInput>
<CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ato</CommandLine>
</SynchronousCommand>
</FirstLogonCommands>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<ProtectYourPC>1</ProtectYourPC>
<NetworkLocation>Work</NetworkLocation>
<SkipMachineOOBE>true</SkipMachineOOBE>
<SkipUserOOBE>true</SkipUserOOBE>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
</OOBE>
<UserAccounts>
<AdministratorPassword>
<Value>password</Value>
<PlainText>true</PlainText>
</AdministratorPassword>
</UserAccounts>
<RegisteredOrganization>Your organization</RegisteredOrganization>
<RegisteredOwner>Your organization</RegisteredOwner>
</component>
</settings>
<cpi:offlineImage cpi:source="catalog://master-pc/users/master/desktop/win 7 sources/sources/install_windows 7 professional.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
</pre>

'''unattend.xml 64 bits version'''
<pre>
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="generalize">
<component name="Microsoft-Windows-Security-SPP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipRearm>1</SkipRearm>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Path>net user administrator /active:yes</Path>
<Order>1</Order>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipAutoActivation>true</SkipAutoActivation>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ShowWindowsLive>false</ShowWindowsLive>
<TimeZone>Romance Standard Time</TimeZone>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>fr-FR</InputLocale>
<SystemLocale>fr-FR</SystemLocale>
<UILanguage>fr-FR</UILanguage>
<UserLocale>fr-FR</UserLocale>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<AutoLogon>
<Password>
<Value>password</Value>
<PlainText>true</PlainText>
</Password>
<LogonCount>5</LogonCount>
<Enabled>true</Enabled>
<Username>administrator</Username>
</AutoLogon>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX </CommandLine>
<Order>1</Order>
<RequiresUserInput>true</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<RequiresUserInput>false</RequiresUserInput>
<CommandLine>cscript //b c:\windows\system32\slmgr.vbs /ato</CommandLine>
<Order>2</Order>
</SynchronousCommand>
</FirstLogonCommands>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
<SkipMachineOOBE>true</SkipMachineOOBE>
<SkipUserOOBE>true</SkipUserOOBE>
</OOBE>
<UserAccounts>
<AdministratorPassword>
<Value>password</Value>
<PlainText>true</PlainText>
</AdministratorPassword>
</UserAccounts>
<RegisteredOrganization>Your Organization</RegisteredOrganization>
<RegisteredOwner>Your Organization</RegisteredOwner>
</component>
</settings>
<cpi:offlineImage cpi:source="wim://master-pc/users/master/desktop/win%207%20sources/sources/install.wim#Windows 7 x64 Professionnel" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
</pre>

Create '''reseal.cmd''' and store it in the folder '''sysprep-7-32'''.

<pre>
@echo off
set curdir=%~dp0
%~d0
cd %curdir%
set unattendfile=unattend.xml
if NOT %1!==! set unattendfile=%1

echo sysprep with %unattendfile%
echo pres Ctrl+C to cancel, or any key to continue
pause

:: Step #12
mkdir %windir%\Setup\Scripts
echo del /Q /F %windir%\system32\sysprep\unattend.xml > %windir%\Setup\Scripts\SetupComplete.cmd
echo del /Q /F %windir%\panther\unattend.xml >> %windir%\Setup\Scripts\SetupComplete.cmd

:: Step #13

echo on
copy "%unattendfile%" %windir%\system32\sysprep\unattend.xml
cd %windir%\system32\sysprep
%systemdrive%

sysprep /generalize /oobe /quit /unattend:unattend.xml
</pre>

Create in '''sysprep-7-32''' the file SetupComplete.cmd with the following content:

<pre>
del /Q /F c:\windows\system32\sysprep\unattend.xml
del /Q /F c:\windows\panther\unattend.xml
</pre>

== Rename your master ==

If you wish to, rename your master computer. You may also need to join your domain, install some domain dependant software, and leave the domain, with all reboots required after joining an leaving your domain.

== Delete user account ==

If you wish to activate the administrator account, do it now. Then reboot the master computer, log in with the administrator account, then erase the limited user account, and his personal folder.

== Install FOG service ==

The time has come to install your most useful service ever made. Download it from your FOG server, and install it. Configure it for your server in your organization. the service will start on the next reboot,

== Run Sysprep ==

The file '''reseal.cmd''' accepts one argument: an unattend file. If no file has been provided, reseal.cmd will use unattend.xml in his directory.

Run it by right clicking on it and selecting '''run as administrator'''. You may run it from a command line with administrator privileges to specify a unatteded file.

After sysprep you may turn off the master computer.

== Driver repository ==

Create a subfolder in '''sysprep-7-32''' in your UFD named '''drivers'''

Create again two subfolders in '''drivers''' '''stor''' and '''net'''.

Store your ethernet/wifi drivers in '''net''' and mass storage drivers in '''stor'''. You need the driver in his simplest form: a .inf file, .sys files, .cat file and any file you feel useful. You need to unpack most of drivers to build your repository.

Here is an example of the directory structure to store them.

* drivers
** net
*** atheros
**** L1
**** L2
*** broadcom
**** BCM43xx
**** BCM57xx
** stor

== Add drivers ==

Reboot your master computer on windows PE (CD or UFD)

in the command line use diskpart to mount a UFD with drivers

<pre>
diskpart
</pre>

Identify the UFD with your drivers

<pre>
list disk
</pre>

select the disk number which associated to your UFD

<pre>
select disk 2
</pre>

select the partition 1 (most UFD have only one partition, or use the command '''list partition''' to list them)

<pre>
select partition 1
</pre>

Mount the partition

<pre>
assign letter=z
</pre>

exit diskpart

<pre>
exit
</pre>

Run dism to add all the drivers in your repository.

<pre>
dism /image:c:\ /add-driver /recurse /driver:z:\sysprep-7-32\drivers
</pre>

Check the command runs with no error.

Exit windows PE by typing '''exit''' in the command line. The computer will reboot. Shut it down before windows boots or press "pause" on the keyboard to suspend the BIOS boot process. Press "space" to resume.

Reboot the computer with a third party tool to shrink the NTFS partition to its smallest possible size.

Capture your image with FOG.

= Links =

http://blog.brianleejackson.com/sysprep-a-windows-7-machine-%E2%80%93-start-to-finish-v2

Talk:Supported Snapin's and Command Line Switches

2011-09-09T08:42:19Z

Necros: Created page with "Hi I may add lots of methods for deploying softwares like Solidworks, AutoCAD Revit, Inventor, Ciel (french business software) and many others. However some of them require a lo..."

Hi

I may add lots of methods for deploying softwares like Solidworks, AutoCAD Revit, Inventor, Ciel (french business software) and many others. However some of them require a long work and cannot be explained shorly.

Working device drivers snapins

2011-05-30T13:35:54Z

Necros: /* Display */ added comment to prevent a trap when using intel drivers

= Chipset =

{| class="wikitable sortable" border="1" cellspacing="0" cellpadding="3"
|-
! Manufacturer !! Version !! Operating system !! Method !! Date !! Notes
|-
| ATI || SMBus v10.9 || XP 32 bits || bin\atisetup.exe -Install || 2010-0930 || Launch the original package, cancel the setup after unpacking process. Create a batch with the given commandline, create an autoextractible 7Zip archive.
|-
| Intel || i848 and later v9.1.1.1020 || XP 32 bits || command line switch: '''/S''' || 2010-09-17 || original package
|-
| NVidia || NForce 4,6,7,9, IGP v15.49|| 7 32 bits || command line: '''setup.exe -s -n''' || 2011-04-18 || Lauch the package and copy the extracted drivers from '''c:\NVIDIA\nForcewareWinVista\15.49\English''', edit setup.iss to set '''BootOptions=0'''
|-
| SiS || [http://www.sis.com/download/agreement.php?id=155871 sis AGP v1.21] || XP 32 bits || start setup-s.bat given in the ZIP archive || 2010-09-17 || Unzip, edit setup.iss to set '''BootOptions=0''', create an autoextractible which will start setup-s.bat
|-
|}

= Network =
{| class="wikitable sortable" border="1" cellspacing="0" cellpadding="3"
|-
! Manufacturer !! Version !! Operating system !! Method !! Date !! Notes
|-
| Intel || Centrino 6200N wifi driver v13.2.0.2 || XP 32 bits || command line : '''ICS_Dx32.exe -s''' || 2010-09-21 || original package
|-
|}

= Display =

{| class="wikitable sortable" border="1" cellspacing="0" cellpadding="3"
|-
! Manufacturer !! Version !! Operating system !! Method !! Date !! Notes
|-
| ATI || Radeon 9x00, Xx00, X1x00, X2x00, Xpress v10.2 || 2K, XP 32 bits || start continue.exe & start /wait "" driver\setup.exe -s & start /wait "" ccc\setup.exe -s & taskkill /F /IM continue.exe || 2010-09-30 || Use an Autoit script to accept unsigned driver installation (coming soon). Launch the package, cancel the installation, create a batch which launches the 2 given commandlines using '''start /wait ""''', pack the whole package in an autoextractible 7zip. (continue.exe is the compiled autoit script)
|-
| Intel || [http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=12531&lang=eng i91x v14.25.50.4764] || 2K, XP 32 bits || command line: '''setup.exe /S''' || 2010-09-20 || Unzip, repack into an 7Zip autoextractible
|-
| Intel || i94x v14.32.4 || XP 32 bits || command line switch: '''-s -A -s''' || 2010-09-17 || original package .exe version (NOT zip)
|-
| Intel || i85x v14.19.50 || XP 32 bits || command line switch: '''-s -A -s''' || 2010-09-17 || original package .exe version (NOT zip)
|-
| NVidia || Quadro v182.65 || XP 32 bits || command line switch: '''-s -A -s''' || 2010-09-17 || original package .exe version (NOT zip)
|-
| NVidia || GeForce 7 and later v260.89|| 7 64 bits || command line switch: '''/s /noreboot''' || 2011-02-02 || Unpack the driver with 7-zip. Create a snapin with the extracted content with command line swtches in '''lower case'''.
|-
| NVidia || HDMI Audio v1.0.0.59 || XP 32 bits || command line switch: '''setup.exe -s''' || 2010-09-17 || start the original package, cancel the setup, go to subfolders in c:\NVIDIA, add '''BootOption=0''' in '''setup.iss''' and create an autoextractible with 7Zip
|-
|}

= Audio =

{| class="wikitable sortable" border="1" cellspacing="0" cellpadding="3"
|-
! Manufacturer !! Version !! Operating system !! Method !! Date !! Notes
|-
| Realtek || [http://www.realtek.com.tw/DOWNLOADS/downloadsCheck.aspx?Langid=1&PNid=24&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false#High%20Definition%20Audio%20Codecs HDAudio v2.51] || XP 32 bits || command line switch: '''-s -A -s''' || 2010-09-17 || original package
|-
| Realtek || [http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=23&PFid=23&Level=4&Conn=3&DownTypeID=3&GetDown=false AC97] || XP 32 bits || command line switch: '''-s -A -s''' || 2011-01-19 || original package
|-
| Sigmatel || [http://support.euro.dell.com/support/downloads/driverslist.aspx?os=WW1&catid=3&dateid=-1&impid=-1&osl=FR&typeid=-1&formatid=-1&servicetag=&SystemID=PLX_PNT_P4_CEL_210L&hidos=WW1&hidlang=fr&TabIndex=&scanSupported=False&scanConsent=False Dell Optiplex 210L HDAudio v5.10.0.4664 STAC92xx] || XP 32 bits || command line: '''setup.exe -s''' || 2010-09-20 || Run the Dell autoextractible, cancel the setup, add '''BootOption=0''' in '''setup.iss''', repack into an 7Zip autoextractible
|-
|}

= Bluetooth =

{| class="wikitable sortable" border="1" cellspacing="0" cellpadding="3"
|-
! Manufacturer !! Version !! Operating system !! Method !! Date !! Notes
|-
| Toshiba || [http://aps2.toshiba-tro.de/bluetooth/index.php?page=download-toshiba Bluetooth Stack for Toshiba laptops] || XP 32 bits || command line: '''silent_install_for_W2000_XP.bat''' or '''silent_install_for_Vista_Win7.bat''' || 2010-09-21 || Edit the .bat file depending your target OS to remove the '''pause''' instruction, repack into an 7Zip autoextractible to launch the previously edited batch.
|-
|}

= Modem =

{| class="wikitable sortable" border="1" cellspacing="0" cellpadding="3"
|-
! Manufacturer !! Version !! Operating system !! Method !! Date !! Notes
|-
| Agere for Toshiba Tecra S11 laptop|| [http://support1.toshiba-tro.de/tedd-files2/0/mdm-20100119151941.zip Agere modem driver for Toshiba laptops] || XP 32 bits || command line: '''setup.exe -s''' || 2010-09-21 || Unpack and repack only Disk1 subfolder into an 7Zip autoextractible to launch the setup.exe. May work for other agere drivers from other sources
|-
|}

= Biometrics =

{| class="wikitable sortable" border="1" cellspacing="0" cellpadding="3"
|-
! Manufacturer !! Version !! Operating system !! Method !! Date !! Notes
|-
| Fingerprint Toshiba Tecra S11 laptop|| [http://support1.toshiba-tro.de/tedd-files2/0/fp-sw-20100517133206.zip Fingerprint driver for Toshiba laptop Tecra S11] || XP 32 bits || command line: '''Toshiba32AT9Net35.exe /s /v"/qn REBOOT=R"''' || 2010-09-21 || Unpack and repack only Toshiba32AT9Net35.exe into an 7Zip autoextractible to launch the software with the given command line.
|-
|}

= Trusted Platform Module (TPM) =

{| class="wikitable sortable" border="1" cellspacing="0" cellpadding="3"
|-
! Manufacturer !! Version !! Operating system !! Method !! Date !! Notes
|-
| Infineon TPM || [http://support1.toshiba-tro.de/tedd-files2/0/trustpm-20100119152340.zip TPM driver for Toshiba laptop Tecra S11] || XP 32 bits || command line: '''msiexec.exe /i Infineon TPM Professional Package.msi /quiet /norestart''' || 2010-09-21 || Unpack and repack only the Win32 or win64 subfolder depending your OS is 32 bits or 64 bits into an 7Zip autoextractible which will launch the .msi file. Same method for HP desktops with Infineon TPM
|-
|}