I think I see what you were referring to and have made the change, the next update will reflect this. Currently testing/fixing snapin deploys though so may be a minute.

And I thought this worked in 0.32.

What sort of code change are we talking about? The feature would be nice, but is not critical.

In windows, you need to configure the card. You can either go through device manager or network and sharing center, change adapter settings, properties of the NIC, click the “configure” button just below the “connect using” box. It may be on the advanced or power management tab.

“Wake on LAN” “Wake system from S5” “Allow this device to wake the computer” or similar. There may be other choices about only allow magic packet, just depending on the card and the driver.

If you’re using the default driver installed by Windows, your choices may be more limited. Try to get the board/chipset specific driver for the LAN card from the manufacturer.

I set up DNSMasq when I work at home with home networking equipment. a lot of the home issued stuff won’t have settings to be able to designated the tftp/boot server or the next-server. Using a DHCP proxy service like dnsmasq has prooved beneficial.

Something else I have done is turn the DNS portion of FOG on and use a hub and keep it separate from the network unless an internet connection is required, which I have not needed DURING imaging, only after.

Glad to be of help.

s
[quote=“Tom Elliott, post: 21615, member: 7271”]That may still be a need, but if you can document the process slightly, I might be able to automate this within the FOG Scripts so we don’t have to do as much.[/quote]
see some message up…

One, add more CPU’s to it. On an upload process, it has to compress the image as it’s being uploaded.

Two, check the compression setting, it’s on the FOG Configuration->FOG Settings menu called: FOG_PIGZ_COMP and should appear as a slider bar. 9 is best/most compression (most cpu intensive and takes time) and 0 is the worst/fastest compression (less compression means more space is used)

no will try that monday thanks for the reply

Yes, thanks. I will use parted now. Apparently using cfdisk to create partitions is not good for me. 😉 😄

This is much easier and from a command line.

[quote=“Tom Elliott, post: 21463, member: 7271”]

[code]
wget https://svn.code.sf.net/p/freeghost/code/trunk/packages/udpcast-20120424.tar.gz
rm -f udpcast-20071228.tar.gz
sed -i ‘s/udpcastout=“udpcast-20071228”/udpcastout=“udpcast-20120424”/’ …/lib/common/config.sh
sed -i ‘s/udpcastsrc=“…/packages/udpcast-20071228.tar.gz”/udpcastsrc=“…/packages/udpcast-20120424.tar.gz”/’ …/lib/common/config.sh
cd …/bin
./installfog.sh
[/code]

[/quote]

[quote=“Tom Elliott, post: 21377, member: 7271”]I don’t know for sure how to get them started, but I know that the Regular Active Tasks should NOT be displaying the multicast tasks.[/quote]

to start unicast:

group management -> list all group -> click on group name -> image association -> x
group management -> list all group -> click on group name -> os association -> x
group management -> list all group -> click on group name -> basic task -> deploy

to start multicast:

task management -> list all group -> deploy multicast, but don’t work giving the error in first message of this thread

[quote=“Tom Elliott, post: 21449, member: 7271”]Are you looking at multicast tasks or active tasks[/quote]

clicking on
group management -> list all group -> click on group name -> image association -> x
group management -> list all group -> click on group name -> os association -> x
group management -> list all group -> click on group name -> basic task -> deploy

starts unicast imaging.

task management -> list all group -> deploy multicast, but don’t work giving the error in first message of this thread

Apparently, had not re run installfog.sh after starting nfs. Tried that first and the error. So, I ran the commands above and still get the error. Just in case, I did re set the password for the Fog user to match the Fog settings in the gui. Also checked permissions of /tftpboot and it is 0755 and the owner is Fog.

I am running fog 0.32. I uploaded an image and then I booted the drive, added a folder to desktop, and then deployed the image and when it booted the folder was gone so I believe that there is an image uploaded. Then when I put in the blank drive it does the restarting business.

V/R
Adam

Your default file (that’s the name sorry) is located at:
/tftpboot/pxelinux.cfg/default

On the bottom line you should see:
[code]TIMEOUT 30[/code]
This means 3 seconds. Thirty seconds would be:
[code]TIMEOUT 300[/code]
I

0.33 doesn’t have the same issues.

no problem.