It’s not the XP but the mini-Linux which is not working in 15.2.
I get this error:
[IMG]http://i61.tinypic.com/smru9t.png[/IMG]

If I summarizes, the NFS server export “/images” on FOG server and FOG Server export “/images” on Client, it’s correct?

It would seem I have nfs-common installed:

root@fogserver:~# locate nfs-common
/etc/default/nfs-common
/usr/share/nfs-common
/usr/share/bug/nfs-common
/usr/share/bug/nfs-common/control
/usr/share/bug/nfs-common/script
/usr/share/doc/nfs-common
/usr/share/doc/nfs-common/README.Debian.nfsv4
/usr/share/doc/nfs-common/changelog.Debian.gz
/usr/share/doc/nfs-common/copyright
/usr/share/lintian/overrides/nfs-common
/usr/share/nfs-common/conffiles
/usr/share/nfs-common/conffiles/idmapd.conf
/usr/share/nfs-common/conffiles/nfs-common.default
/var/cache/apt/archives/nfs-common_1%3a1.2.5-3ubuntu3.1_amd64.deb
/var/lib/dpkg/info/nfs-common.conffiles
/var/lib/dpkg/info/nfs-common.list
/var/lib/dpkg/info/nfs-common.md5sums
/var/lib/dpkg/info/nfs-common.postinst
/var/lib/dpkg/info/nfs-common.postrm
/var/lib/dpkg/info/nfs-common.preinst
/var/lib/dpkg/info/nfs-common.prerm
/var/lib/ucf/cache/:etc:default:nfs-common
root@fogserver:~#

But none in /etc/init.d. There is one in /etc/default, is this the one i’m looking for?

Did you ever figure this out?

If you have many of the same model of client, have you considered using the capone plug in for this.
You can associate a particular model with one (or more) image.
On the client you select capone from the menu choices, if there is only one image associated, it deploys with no registration required.
If there is more than one image associated, you select which one you want, and again it deploys, again no registration required.

This is my last day at this location. Giving up on this and moving on. Thanks to everyone who offered assistance along the way.

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. 😉 😄