Try to use a different kernel, such as a KitchenSink one, or compile your own following the Wiki using different interface/video options.

[url]http://www.fogproject.org/wiki/index.php/Building_a_Custom_Kernel[/url]

I’ve imaged both i5’s and Core 2’s from FOG with the stock kernel.
What parts arn’t working?
Have you tried a kitchensink kernel?
Are your i7’s setup to boot legacy roms, or Secure boot/EFI only?

Kitchensink is the configuration used to create the kernel.
The kitchensink config has more options included (such as drivers) which will support more devices than the core kernel. (I use a kitchensink based kernel it to get Dell Optiplex 755’s working with FOG)
Downside is the kernel is larger and may be slower.

FOG has an option to download a Kitchensink kernel in it’s UI. Or you could use the kitchensink.config to compile a new kernel.
[URL=‘http://www.fogproject.org/wiki/index.php/Building_a_Custom_Kernel’] http://www.fogproject.org/wiki/index.php/Building_a_Custom_Kernel[/URL]

The RAMDISK is created on the client machines, not on the server. So the clients will need over 3 GB of RAM in order to load the disk. Then after the disk is loaded, that amount of RAM is unusable by the OS. Also i’m not sure what BIOS limitations there are on how much RAM the computer can use and if it is stuck in a 32 bit address space with PAE disabled until an OS boots, so only iso’s under 3 GB would load(Just my guess). Do ISO’s under 3 GB (stock Windows 7 SP1 should be 2.4 GB) work?

Perhaps you could modify the iso so it gets it’s Windows sources from a network share, so it only needs to memdisk a smaller installer ISO.

A quick Google came up with this thread. Perhaps it pertains to you?

[url]https://supportforums.cisco.com/thread/2137283[/url]

Assuming your server is on the same subnet as the client PC’s.

Change this line in the ltsp.conf file:
[CODE]dhcp-range=192.168.1.10,proxy[/CODE]
to
[CODE]dhcp-range=192.168.101.240,proxy[/CODE]

then restart dnsmasq
[CODE]sudo /etc/init.d/dnsmasq restart[/CODE]

There is not an easy way that i’m aware of. But in the web settings(FOG_WOL_INTERFACE, FOG_UDPCAST_INTERFACE, FOG_NFS_ETH_MONITOR) and in the two config files switch all the eth0’s with eth1’s. And restart the FOGMulticastManager and FOGScheduler.

There may be more you need ot edit for each of the services if they are configured to listen on only one interface.

I havn’t tried this but perhaps editing “/etc/udev/rules.d/70-persistent-net.rules” and swapping the eth0 and eth1 for the devices, then rebooting would swap which one is which. This may break other things that are depending on specific interfaces though(other services/uses for the server).

Is it working successfully now?

You typed in upcast, it is supposed to be udpcast.
[CODE]tail -f /opt/fog/log/multicast.log.udpcast*[/CODE]

Post #13 suggests there is an issue starting UDPcast, Is eth0 the correct interface and is not disabled? Do you have SE Linux or a firewall running?

Run this (taken from the multicast log in post #13)and see what error it gives you
[CODE] gunzip -c “/images/win7dual2/d1p1.img” | /usr/local/sbin/udp-sender --min-receivers 2 --portbase 63106 --interface eth0 --half-duplex --ttl 32 --nokbd;gunzip -c “/images/win7dual2/d1p2.img” | /usr/local/sbin/udp-sender --min-receivers 2 --portbase 63106 --interface eth0 --half-duplex --ttl 32 --nokbd;gunzip -c “/images/win7dual2/d1p3.img” | /usr/local/sbin/udp-sender --min-receivers 2 --portbase 63106 --interface eth0 --half-duplex --ttl 32 --nokbd;[/CODE]

if it isn’t working , could you also check the udpcast log , to see if clients are connecting successfully or not.

[CODE]tail -f /opt/fog/log/multicast.log.udpcast*[/CODE]