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.

I was able to boot using this configuration:

kernel [url]http://${fog-ip}/fog/debian/7.6.0/live/vmlinuz1[/url]
initrd [url]http://${fog-ip}/fog/debian/7.6.0/live/initrd1.img[/url]
imgargs vmlinuz1 boot=live config console=ttyS0 username=live fetch=[url]http://${fog-ip}/fog/debian/7.6.0/live/filesystem.squashfs[/url]
boot

After re-storing my server back to a working state I tried changing all the files mentioned. I still get the same error. Does it make a difference if I am on SQL 5.1 vs 5.5?

I think i found the solution, I downgraded Bios to A8 from A10 and computer is imaging now. Thanks everybody for their help!!!

Slight thread hijack but I have just installed fog 1.2 as I needed more image space (sysprep worked but things like graphics drivers proved an issue)

The problem I have is with Dell OptiPlex 390s they boot from pxe show the menu but then they just go black with a flashing underscore in the top left corner. EDIT: better description blinking white cursor.

They used to work with the previous release of fog. All the bios settings are correct etc. If I escape out of the PXE it boots from the hard disk OK. problem is I have all our machines set to boot from nic then boot from HDD. I have updated the bios and removed all other boot options except from NIC and HDD.

[quote=“Junkhacker, post: 37442, member: 21583”]it sounds to me like you hit upload instead of download once[/quote]

Nope.

Hi thanks for your help Purpleturtle99! after switch fog to do DHCP i can now boot from LAN thank you!

OK. TANKS !!

@zingaro,

The menu options you’re attempting to create do not go in the default file.

They go under the advanced options under the pxe settings under FOG Configuration->PXE Settings->Advanced Options from the fog GUI.

me too.
see my post here (so im not retyping stuff)
[url]http://fogproject.org/forum/threads/need-tutorial-for-making-this-work-with-uefi.10676/page-2#post-36073[/url]

I have a few questions about your network.

1.)What network switches do you have?
2.)Is STP enabled?
3.)Are the host and server on different VLANS?

single disk resizable works this way: check the drive, resize partitions to the minimum size to hold their data, upload image. on download, up all of the data back, and resize the partitions to the capacity of the volume

the others use the method: record what is there, and put it back eactly the way it is on download, partition sizes and all.