Alright, now I have my own switch A Netgear prosafe GS108E. I’m hooked up to it, but when I try now to start the isc-dhcp-server, it gives me the error:
[CODE]Starting ISC DHCP server: dhcpdcheck syslog for diagnostics. … failed!
failed![/CODE]
And in /var/log/syslog I have
[CODE]No subnet declaration for wlan0 (10.247.57.50).
** Ignoring requests on wlan0. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface wlan0 is attached. **[/CODE]
I don’t want wlan0 at all. I want it to use eth0.
In my dhcpd.conf file, I have:
[CODE]GNU nano 2.2.6 File: dhcpd.conf

DHCP Server Configuration file. see /usr/share/doc/dhcp*/dhcpd.conf.sample This file was created by FOG

use-host-decl-names on;
ddns-update-style interim;
ignore client-updates;
next-server 10.126.6.26;
subnet 10.126.6.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
range dynamic-bootp 10.126.6.10 10.126.6.254;
default-lease-time 21600;
max-lease-time 43200;
option domain-name-servers 10.98.1.1;
option routers 10.126.0.1;
filename “pxelinux.0”;
}[/CODE]
I’m not quite sure what to do from here.

THANK YOU VERY MUCH.
I was able to register the laptop. Now I have to test uploading the image.

Thanks again,

Tom

It is working now, and I have been told it is a cabling issue. I can’t see why, as the cable works fine, but I have been told to stop questioning it and just accept it will work where it is now and not where it used to be.

Thanks again for the help.

I look forward to using the new version in the future. It sounds like it will be vastly superior to .32.

The problems with my drive are largely due to the fact that it’s an advanced format drive. Even the Windows 8 recovery partition won’t work because it was created on a non-AFD disk. Also my laptop is 64-bit but my desktop is 32-bit so I can’t simply create an install disk from the windows 8 installer. Ugh!

FOG, however, has performed very well. This little adventure has helped me test out version .33b so when we do upgrade I the server at work I know what to expect. At present my plan is to wait until it’s finalized. Since we have about four spare computers (and only need about that many images) at work recreating reference images is not much of an issue. My main concern is for the FOG database since rebuilding it would require going around to the public computers. Is it possible to copy the database, store it somewhere, and then put it back on the server when version .33 is installed? Or is the best way to upgrade simply to have two servers? Note that we do not have any FOG server as of yet, although I do not want our big Windows 7 roll out to be dependent on software which is still in Beta.

Thank for letting us know, I lost internet while trying to get caught up on these posts O.o

The proxyDHCP service added from the dnsmasq, only doles out ip addresses when booting the pxe information. Any ip address given to the machine is temporary and will be removed when it moves from the pxe boot screen, i hope this will help to appease the higher ups.

Tom is correct, there currently aren’t any downloads for a USB version of FOG, however Tom and I recently helped someone to do something similar… [url]http://fogproject.org/forum/threads/fog-image-choice-with-usb.10015/[/url]

He wanted do do EVERYTHING from the usb drive almost like the usb drive was a mobile fog server. I feel it’s better to have a server as you can store a number of images and revisions of those images and you can deploy/revert to them at any time, I only feel a USB option would be acceptable if you had only one make an model of a machine, or a golden image for ALL machines in your area.

I personally, don’t feel that the USB option is that good of an option… if I want to carry a device with me I would go back to using clonezilla.

Sorry I wasn’t able to help much further.

Thank you for your help!

The netbook is still running the [B]dd[/B] command and I’ve purged the MAC address from the pxelinux.cfg directory. Once this finishes, I’ll try to image again.

I’ll let you know how this turns out.

2013.11

that sounds good 😛

I don’t know if I exactly follow… the menu item sounds good… it’s kinda like what I am doing with unicasting, having a menu item for a particular image? What do you mean about a false task?

Quick question, what OS are you running?

I found that the latest Ubuntu 13.10, I had to manually restart the services after installation of FOG, I restarted the mysql and apache2 services and I was able to communicate with my web gui. (no errors were ever reported.) but I was unable to access the web page.

May be something to think about.

No problem, and glad I could be of assistance.

[quote=“Tom Elliott, post: 23193, member: 7271”]You’re welcome.

All is working then I presume?[/quote]

I have succesfull created an image of a Windows 7 machine. I have not tried to deploy the image back to the Windows 7 machine, but I assume that this is going to work, otherwise I let it know. 🙂

I have completed all of those steps, then tried to upload the image once again. I do get something a little different now. When it boots to pxe, it flashes some numbers, to quick for me to read, then boots back to windows. Once I go back into the fog console, the task is gone. If I create the task again, it gives me the same move error as before.

I do notice that before it gets to the failed to move error, a lot of bios and driver checks fail. Not sure if this has any effect on the above.

Thank for letting us know where the issue was! I haven’t worked with Azure, so I am sorry I couldn’t be of assistance.

My guess as to the issue you’re seeing could be a couple things.

NFS isn’t loading so the starting point would be to make sure the nfs server is running.

Most systems now use nfs in conjunction with rpcbind. Some Debian based systems use portmap so replace rpcbind with portmap if necessary.

Try to verify nfs server is running. On Redhat based systems the code to make sure should be:
[code]sudo service rpcbind restart
sudo service nfs restart[/code]

On Debian based systems it should be:
[code]sudo service rpcbind restart
sudo service nfs-kernel-server restart[/code]

The next step is to verify your permissions are correct on the /images folder (or what ever directory structure you’re using for your images).

[code]chmod -R 777 /images[/code]

The last thing to verify is to ensure .mntcheck files are in the right places. The commands below should verify.
[code]rm -rf /images/{.mntcheck,/dev/.mntcheck}
touch /images/.mntcheck /images/dev/.mntcheck
chmod -R 777 /images[/code]

Hopefully this helps you out.

Have you uploaded an image first?

The reason output is useful is it can tell what’s going wrong. It may say, not correct format which would tell us to use a newer or different file. Maybe it’s just not reaching the tftpserver for some reason, in which case it may be saying timeout or cannot load file.

Either way, outout is always useful, even if it isn’t helpful.

That being said, one resource to look at for efi pxe booting could be:
[url]https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-netboot-pxe-config-efi.html[/url]

While I don’t know all the possible methods that will get your system actually working, it’s one place to start.

the code tom’s posted is what i actively use to handle Win7/8/8.1 (mutli-partition) and i build my image in vm and have the disk only a few GB’s bigger than the image (20-25GB) and expand if the image gets bigger that way you never have to worry about putting it onto a “smaller hard drive” and extend partition in the unattend handles the rest 🙂