It’s possible it’s a network issue. Meaning it could be the kernel doesn’t have the driver for your nic. (Can you provide NIC informatoin of the trouble system?)

The error as I zoom in, says the network is unreachable, which would explain not mounting the file as well.

Okay,

So there is no issue with Capone, or the menu generation.

Rather, it’s the method at which you’re creating the DMI/Shutdown fields with the image association fields.

These are two separate forms.

What this means:

When you are setting up capone, it gives one page full of all the information you need.

The DMI and shutdown fields are their own form because these are global values.

The Image association field is it’s own form to separate between the two.

Please, set your DMI/Shutdown fields and use it’s corresponding button to update.

Then set your image associations (or leave them if you set them already.)

Then boot a host, if the menu isn’t set, it will create the menu item.

After the item is created, you can specify it as default.

That will be this then! :

[COLOR=#007700][FONT=monospace]if ([/FONT][/COLOR][COLOR=#0000bb][FONT=monospace]substr[/FONT][/COLOR][COLOR=#007700]FONT=monospace==[/FONT][/COLOR][COLOR=#dd0000][FONT=monospace]“00:15:5d”[/FONT][/COLOR][COLOR=#007700][FONT=monospace]){
print [/FONT][/COLOR][COLOR=#dd0000][FONT=monospace]“# Hyper-V MAC address detected - no console background\n”[/FONT][/COLOR][COLOR=#007700][FONT=monospace];
} else {
print [/FONT][/COLOR][COLOR=#dd0000][FONT=monospace]“console --picture [/FONT][/COLOR][COLOR=#0000bb][FONT=monospace]$this[/FONT][/COLOR][COLOR=#007700][FONT=monospace]->[/FONT][/COLOR][COLOR=#0000bb][FONT=monospace]booturl[/FONT][/COLOR][COLOR=#dd0000][FONT=monospace]/ipxe/bg.png --left 100 --right 80\n”[/FONT][/COLOR][COLOR=#007700][FONT=monospace];
}[/FONT][/COLOR]

[COLOR=#007700][FONT=monospace]Will give that shot! :)[/FONT][/COLOR]

sanboot isn’t used for loading iso’s typically. i’ve always had the best luck with [CODE]chain memdisk iso raw[/CODE]
sorry if this isn’t addressing your question, i’m having a hard time understanding what you meant

Can you post the install log?

/var/log/foginstall.log

it never stops blinking, I have to power it down.

what are the details of the computer you’re having problems with? brand/model
the first step i would take would be to update the undionly.kpxe file to the latest version from here
[url]http://sourceforge.net/p/freeghost/code/HEAD/tree/trunk/packages/tftp/[/url]
if that doesn’t work, try using undionly.kkpxe instead
there are plenty of threads about troubleshooting ipxe error 0x040ee119

you could edit the “imageID” field of the “images” table in the “fog” database, but if it’s purely for aesthetics i recommend against it.
that ID is used for internal record keeping and task management in fog

I recommend you try Ahsay Software ([url]http://www.ahsay.com[/url]). Ahsay?? Backup Software is an advanced disk-to-disk-to-disk (D2D2D) backup solution for Businesses and MSPs / VARs. It comes with the most comprehensive features that can fulfill all the on-premises backup, online backup, offsite backup, and cloud backup needs of nowadays businesses. At the same time, it is the most affordable backup solution available in the market.

Just make sure you have routing enabled between the two subnets (as in, the routers know that each other are responsible for their own network), and point to FOG as the next server. TFTP & HTTP work over layer 3 as long as you can route to it.

If your images are starting at sector 63, you may look into updating to SVN as I’ve made fixes that should allow your systems to not only image, but also boot after they’re completed.

Does /images exist on the server at 10.89.63.5

before the feature snapins should work, though editing the snapins may not.

I’m taking a look to see if there’s a better way for me to get a list of hdd’s and partition data.

Works perfectly Thanks Tom.

I made the configuration change (took me a bit to find where to make that change) and started another upload task.

Results: Seems to be working! I’ll hold off on being certain its fixed until it’s completely uploaded, but I have no reason to believe it won’t right now.

Thanks for the quick replies. Would have taken me a lot longer to have spotted that configuration error. If anything pops up, I’ll reply here, but this upload won’t be for a while as the hard drive is quite large and I’m only able to upload over a 100MB LAN connection.

That is spanning tree making sure there are no loops before allowing data to pass on the port. All managed switches have it turned on by default (which is a good thing). All our switches on campus have it, so if you have 3-4 swithces in a row that have to learn its new path, it does take longer then usual to come up then on unmanaged switches, hense our issue we were having.

Now I am on svn2547.
After upgrading from 1.2 no clients is renamed and can join.
Client log is attached.

Please help!

Michael

[url=“/_imported_xf_attachments/1/1485_foglog-client.zip?:”]foglog-client.zip[/url]

Sorry to reply so late now … the problem with the later version of FOG - as I painfully discovered - is that they have difficult time to migrate the schema. The schema said it “migrated successfully” but not in actuality.

I ended up using PHPmyadmin to manually export the hosts, change a few table names, export the mac addresses, match them up with host IDs, etc. etc. etc. … painful process, but once the correct fields were entered, the whole thing was smooth !

Easiest method, turn off autofill in chrome/ie/firefox.

I’ve fixed this in SVN by placing a false field that get’s autofilled, hence leaving the real fields as they should be.

This really is a browser thing though as my autocomplete=“off” statements are completely ignored by chrome/safari.