[quote=“Junkhacker, post: 28753, member: 21583”]what type of DHCP server are you using?
can you retrieve the file with this command?
[FONT=Consolas]tftp -i <server IP> get default.ipxe[/FONT][/quote]
“Transfer successful: 167 bytes in 1 second(s), 167 bytes/s”
[quote=“Jaymes Driver, post: 28760, member: 3582”]I don’t have that luxury I am stuck on 6.5 
We are looking to move to AD.[/quote]
Long live NetWare, still my fav server OS. You can still keep eDirectory and not deal with AD. Actually I think, even eDirecotry will now run on a Windows host OS.
[quote=“Tom Elliott, post: 28758, member: 7271”]What version of Novell are you running?
Novel 6.5 prior to sp2 apparently has a file character limit to 12, so you may want to try relabeling the file as undionly.0 or something similar.[/quote]
We are past Novell NetWare and now on their Linux flavor of servers, the base is SuSe Linux, and the Novell “stuff” that was NetWare is now called Open Enterprise Server. So…
Novell Open Enterprise Server 11 (x86_64)
VERSION = 11.1
PATCHLEVEL = 1
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 2
[quote=“Junkhacker, post: 28753, member: 21583”]what type of DHCP server are you using?[/quote]
The host OS is SuSe Linux Enterprise Server and the DHCP server itself is part of Novell’s Open Enterprise Server.
[quote=“Tom Elliott, post: 28743, member: 7271”]
How did you try those 5 files?[/quote]
Downloaded each file then used ssh to transfer them to our fog server’s /tftpboot directory.
[quote=“Tom Elliott, post: 28743, member: 7271”]
What FOG Version are you using?[/quote]
v1.0.1
[quote=“Tom Elliott, post: 28743, member: 7271”]
Did you rename the files as your /tftpboot/undionly.kpxe?[/quote]
I didn’t rename the files other then the orginial undionly.kpxe to undionly.kpxe.bak. I then changed the file name for PXE in my DHCP server to match the file I wanted to try. ipxe.kkpxe, ipxe.kpxe, ect…
[quote=“Jaymes Driver, post: 28734, member: 3582”][url]http://fogproject.org/forum/threads/040ee119-error-on-boot.10493/page-2#post-28487[/url][/quote]
I tried the 5 files located in the f473-good directory and each one takes me back to “could not boot: no such file or directory ([URL=‘http://ipxe.org/2d8c203b)%E2%80%9D’]http://ipxe.org/2d8c203b)”[/URL].
[quote=“Scott B, post: 28719, member: 15315”]Updated the BIOS to 786G2 v2.02 on the dc6000 without a change.[/quote]
Error now says “Error 0x040ee119 ([url]http://ipxe.org/040ee119[/url])”
Updated the BIOS to 786G2 v2.02 on the dc6000 without a change.
We have FOG 1.0.1 rolled out, but since have been having issues with imaging some of our older PCs with Intel NICs. The machines will get their IP, start to PXE, start to load, then gives the error “could not boot: no such file or directory ([url]http://ipxe.org/2d8c203b)”[/url]. Newer PCs image fine. HP dc6000 and d530s are two troubled devices.
FOG: 1.0.1 on Fedora 12.
Updated to 1.0.1 and now there is no choice for OS type, and thus, I can’t image a workstation. Was this removed and I missed it or did something go wrong with the install? Everything looked good while doing it.
Great thread, helped me out a lot!
[quote=“Kylejb007, post: 4521, member: 1442”]Chad and Raff,
That Did it!!! The intial results have been really impressive. Today we imaged our high School (Classrooms), which is approx. 80 machines… Normally we use to use Novell Zenworks to image them and it would take practically 1 whole day to image (at least 4-6 hours) and we would come in the next day and join them to the domain. Well im pleased to say that we started this morning at 9am, and completed the last computer (we dont have the fog service setup yet) we joined the last computer to the domain at 3:30PM. All of the machines loaded up fine with no Kernel downloading slow, and the Storage Node happily pumped images out to 10 machines at a time with everyone taking roughly 25-30 minutes to complete each. We even had to re-queue a couple computers due to Sysprep failing to process the unattend file, I assume this happens due to a network glitch pushing it to it or hardware glitch on the end station, usually a second image to it and it works rarely have I had to do it a thrid time, I end up switching patch cords and that fixes it.
Do I dare increase the amount of machines imaging at one time or I do have another decomissioned G5 I could use if I wanted… This is our largest building so the others shouldnt have any issues at all with time, I just figured for planning in the future to do 20 at a time would speed things up tremendously.
Definitly thanks for the advice, best product around![/quote]
Same experience here. We use ZENWorks for other functions, but dropped it for imaging purposes as soon as we found FOG!
It would be great if there was a way to add hardware information for equipment that will not PXE boot. In our case we use FOG for inventory information and on devices such as iPads having the ability to include additional information would be great. Currently we just add the name, mac, and IP.
Would anyone have an interest in the ability of doing an offline image? With the side of flash drives and usb disks being able to copy a FOG image to movable storage and book from a disk, usb drive, flash drive, ect and image would be nice.
We considered this as well for certain tech savvy staff but ended up choosing not to. A phone call or support ticket into IT and we can set a PC to reboot and image from here with the web gui. Still quick and easy.
[FONT=Tahoma]First I want to say thank you to everyone who has helped to create and develop FOG. I consider adding FOG to our network as one of the top, if not the top changes we have ever made. We have used PTMagic, Ghost, and ZENWorks in the past, but none of them have been as fast, user friendly, and stable as FOG.[/FONT]
[FONT=Tahoma] [/FONT]
[FONT=Tahoma]Working for a school district with budget cuts at every turn and a do more with less feeling for support gets difficult at times. FOG has filled several holes for us. While our primary use of FOG is imaging of our desktops and our primary inventory source the “other” tasks such as password recovery, disk scanning, memory testing, hostname change (very much so), and even the AV have been very helpful! While we have never gotten to use the snap-ins and printer management I trust others have found them useful.[/FONT]
[FONT=Tahoma] [/FONT]
[FONT=Tahoma]I hope for the continuing development of FOG as newer operating systems are released and times change. Thank you again to everyone who helps with development![/FONT]