First Impressions / Introduction
-
@mtmulch I would recommend just putting it on the network, setting it up, and then just remove it from the network. This way is much more simple.
Just tell FOG you don’t want to use DHCP.
Then, later on, just manually setup the DHCP. it’s easy, we have lots of examples here.
-
So I’ve got the lab setup, more issues I’ve ran into. I can successfully PXE boot into the FOG menu but, once I get there if I select anything the machine does a complete reboot.
I tried changing my dhcp settings to load unidonly.kkpxe no, same results. So I am currently unable to register a host. I have no problem accessing the web GUI but I cannot register the host there either.I am currently running the latest trunk release as of 9 am this morning.
-
@mtmulch Please let us know the exact model of computer you’re trying to network boot. Also try another model too. You might also take a look at our working hardware list: https://wiki.fogproject.org/wiki/index.php/WorkingDevices
Let us know, we are here to help.
-
Sorry for the vague responses. The first model I had issues with was an Dell Optiplex 780, second model I tested was HP Compaq 4000. Looking at that list the HP model is not supported, while the Optiplex is. I see a recommended kernel for the Dell, could this potentially be the culprit? Not sure if this helps at all but I was able to successfully get these to register through the FOG boot menu and web GUI using FOG 1.2.0 on Ubuntu 14.04 ( my current trunk install is running on this).
Is it possible that this is a result of my DHCP configuration? I’m currently using isc-dhcp-server is dnsmanq a preferred option?
-
@mtmulch said:
Sorry for the vague responses. The first model I had issues with was an Dell Optiplex 780, second model I tested was HP Compaq 4000. Looking at that list the HP model is not supported, while the Optiplex is. I see a recommended kernel for the Dell, could this potentially be the culprit? Not sure if this helps at all but I was able to successfully get these to register through the FOG boot menu and web GUI using FOG 1.2.0 on Ubuntu 14.04 ( my current trunk install is running on this).
Is it possible that this is a result of my DHCP configuration? I’m currently using isc-dhcp-server is dnsmanq a preferred option?
There is no preferred way to deliver the boot file option, what matters is that the option gets delivered. Some methods are more feasible and possible than others for different people and different situations.
Just because a model isn’t listed in the working hardware list doesn’t mean it isn’t supported. That list is only what people have graciously taken the time to tell us about - FOG is a 100% community driven project. We rely on people like you to tell us things.
Set your boot file to undionly.kkpxe in your isc-dhcp conf file, then restart DHCP, and then see if you have better luck.
-
@mtmulch said:
I can successfully PXE boot into the FOG menu but, once I get there if I select anything the machine does a complete reboot.
Really any entry you select will cause the machines to reboot? memtest, boot from disk, …? All?
I have no problem accessing the web GUI but I cannot register the host there either.
Any error here? Why wouldn’t you be able to add hosts by hand in the web interface?
I am currently running the latest trunk release as of 9 am this morning.
I just saw Tom talking about a buildroot issue he fixed today. Maybe you get the newest latest trunk again and see if that helps?
-
Updating to the latest of trunk this morning resolved the issues I was having. I was able to upload an image of an Optiplex 780 running Windows Vista x64. The deployment of said image seemed to go off without a hitch. After the imaging process was complete, I was unable to boot to my HD. No error message regarding corrupted MBR was displayed, it would just follow to PXE, manually selecting HD would cause the boot order menu to freeze. Boot order was set to HD first and PXE second. Once PXE load screen was brought up it would list the PXE version then a blinking cursor in the top left, no indication of it attempting to reach out to the network. I put a Windows Vista cd to run start up repair, it is able to detect my image installation but startup repair didn’t help either. It could very likely be a bad disk, guy here before me seemed to have a problem separating bad parts.
I’m close gentlemen I can feel it. Thank for continuing to point me in the right direction.
-
@mtmulch Play around with your Exit Style. It should now be a global setting in FOG Configuration and a host setting too. The host portion of it is very new, so it may or may not be a bug.
-
Well gentlemen it works! I cranked out 15 images in about 5 hours this afternoon with my lab. To say the least my team was impressed with FOG, considering I had nothing but problems up until today. I would like to thank everyone for their help with the initial setup. Now its time to convince the suits to let us put it on the production network
-
@mtmulch I help run FOG Trunk at 6 (soon to be 21) public schools. Respect the Trunk - it is a great thing to have it virtualized with snapshots before each major change or upgrade. Backup your DB often, keep your old DB backups. And don’t upgrade on a whim. Upgrade when you have a need to do so.
And of course, if you have any issues; the fog community is always willing to lend assistance.
