If you have rebooted the server since installing FOG (and hence TFTPD-HPA package) then you need to restart TFTP daemon. 12.04 tries to start tftpd-hpa before the interfaces have an IP bound to it. common issue and widely discussed on the forums. If a simple restart solves your problem, search the forums and there are modifications you can make to handle this for you.

Make sure you are setting your IP related settings correct. [url]https://help.ubuntu.com/lts/serverguide/network-configuration.html#name-resolution[/url]

[CODE]iface eth0 inet static
address 192.168.3.3
netmask 255.255.255.0
gateway 192.168.3.1
dns-search example.com
dns-nameservers 192.168.3.45 192.168.8.10[/CODE]

You’re going to need to review the threads here on using gPXE and interpret them to apply to proxy-dhcp/ltsp/dnsmasq. It should not be that difficult, you’re just going to hand off from pxe to gPXE, then grab the correct menu and go from there. The only difference may be the location of your pxelinux.0 file and the pxelinux.cfg directory location.

[CODE]6/27/2013 11:17 AM FOG::HostnameChanger Domain Error! (‘Unknown Error’ Code: 87)[/CODE]

Always use the code tags when posting logs or code to keep the board from eating it and pooping out smilies.

Double check the information used for AD joining that is stored in the global FOG settings against the information that is stored in the Active Directory page for the particular host. Make sure they match, with the global FOG settings winning out over the host Active Directory settings if there is a difference.

I have not experienced this issue. If you are using FOG 0.32 and Windows 7, you should not need to use FogPrep anymore.

Are you /generalize when you sysprep and do you keep or purge the hardware configuration information as part of you unattend?

This is already considered for FOG 0.33. I think the database is already updated for the new version, but there is some legacy code that needs to be fixed. So consider this done for FOG 0.33. Keep the suggestions coming.

Do you also need to
[code]sudo touch /images/dev/.mntcheck[/code]

Is your ERP server the only thing FOG is going to back up?

the unsupported bios, abort error is a false alarm. It’s a low level driver error for acer laptops with a faulty fan controller. Ingore.

The kernel panic is important. Grab a screenshot/pic of the error and post it. Also, do you best to copy and paste or link to the spec sheet for this model to see if a driver change in the kernel might help.

that error is unrelated.

To correct your issue with domain join, try using domain\username instead.

If you want to correct the error about connecting to the database server, start a new thread and I’ll be glad to address it there.

Some MACs are formatted with dashes, other with colons, others without anything. FOG needs colons. 11:22:33:aa:bb:cc is valid. 11-22-33-aa-bb-cc is invalid, 112233aabbcc is invalid.

1. No, Sysprep is required for Windows, but FOG can clone Windows 7 without sysprep, but you may run into weird things with Windows and related service such as KMS activation, WSUS.
2. In FOG 0.32 and Windows 7, you do not need FogPrep
3. You’ll have to find a kernel that works best for you.
4. If you make it a hardware generalized image, and you include the necessary drivers somehow. Scripted, SAD2, inserted via some other method.

check permissions on your tftpboot/pxelinux.cfg folder and the the 01-mac-address file. Also, try restarting tftpd-hpa service. There is a known issue with 12.04 and tftp where tftpd-hpa doesn’t start correctly at system boot.

There is a lot of interesting discussion in the Ubuntu bug reporting utility about TFTP not starting. The solution to change the start up to “start on (local-filesystems and net-device-up IFACE!=lo)” [I]I think[/I] works if you have only one interface other than “lo”. I may have misread the comments on the bug report. So as long as you don’t have multiple nics, that should be the solution.

It depends on your goals for sysprep and FOG.

My goal is to make an image for a particular brand and model of laptop that is as complete as possible (drivers and software) so I can blast it out to student laptops as quickly as possible and have as little to do after imaging as possible.

Others’ goals are to have a hardware generic base image, and then use utilities after imaging to install drivers and software and run complex scripts to finalize the machine before sending it to the end user.

I have plenty of storage space but little time over the summer to image 5 different models of laptops. I have even less patience to wait on updates and scripts that may fail for any variety of reasons.

If it wasn’t for KMS activation for Windows 7, I would probably skip sysprep altogether. We are upgrading our domain this summer to support Active Directory Based Activation for all our Windows 8 tablets and Office 2013, but our Windows 7 laptops are stuck with KMS for now.

Sysprep is not required for FOG. FOG will image computers just fine without sysprep. Windows is what needs sysprep, more specifically Windows on different hardware, Windows Activation, WSUS services, KMS activation, and other stuff.

If you use the new Volume Licensed media to install windows, it has a 1000 rearm limit, as opposed to the old 3 rearm limit. If you have volume licensing agreement, I strongly urge you to update your install media and download the new installs from microsoft. They also come with SP1 included to save you some time.

When I first started with FOG 0.32 and Windows 7, I was not able to preserve the OEM key because FOG would not image the laptops due to the OEM and windows recovery partitions. So I installed Windows from scratch and cloned without sysprep and used our MAK key to activate all 700 of our computers. Each summer, we reimage all of our laptops, and so we ran out of activations. I call/email to MS licensing, and they increased our activation count to allow more MAK activations. But really, these are re-activations of the Windows on the same machines. The problem here is that every year, when we re-image our laptops, we have to up our activation counts and deal with MS licensing.

When we installed the KMS server to avoid having to up our MAK count each year, we ran into problems that all the machine had the same CMID and we never got to the 25 activations minimum for KMS to actually activate the machines. I had 700 machines all using one CMID.

I am redoing our images this year to be able to use Sysprep to create unique CMID’s so KMS will work for our Windows 7 machines. You really only need the small part of sysprep which is to generalize and OOBE. You don’t need to learn about all the other steps unless you just really want to.

I googled “dnsmasq junk command line” and found some interesting results. Have you had a look yet to see if anything applies to you?

I just saw in your post that you are mounting the apple storage to /images, and then trying to export /images. I think you are getting the error where you can’t export an nfs mount pount.

See if this post helps: [url]http://www.fogproject.org/forum/threads/how-to-setup-a-fog-storage-node-without-installing-fog.4294/#post-12035[/url]

In an earlier post in another thread, I had suggested mounting the nfs shares to /images and /images/dev, respectively, but we tried that and found you cannot export them from the fog server.

Have you seen: [url]http://www.fogproject.org/forum/threads/how-to-setup-a-fog-storage-node-without-installing-fog.4294/#post-12035[/url]

Figgy_steve, please start a new thread with your issue. It might be related to this thread, so feel free to link back to it, but it’s not in support of or in addition to this thread, so you need your own.