BOOTFILE?

[george1421]

For dhcp option 66 should be the IP address of your fog server.
dhcp option 67 should be undionly.kpxe for bios (legacy) clients and ipxe.efi for uefi clients. For now pick one firmware format and load the right driver. Once you get comfortable with fog we can talk about other solutions to dynamically load the right iPXE kernel.

And just for reference you SHALL NOT use pxelinux.0. We will know if you do.

[cjesso]

@george1421 Ok? i am not sure what UEFI is or legacy. I am doing this with Lenovo E440 with windows 10 installed. They don’t seem to recognize the fog server if i use ipxe.efi

[cjesso]

@george1421 When i boot up the PC, it says Intel UNDI. PXE-2.1 (build 0.83)

[george1421]

@cjesso OK, I’m not so good with mind reading.

But since you have win10 installed, its probably a uefi system.

But based on what you just posted, it could be in bios mode. UEFI pxe bot should say something about a NBF file. Look in the “bios” and see if there is a software switch to change between bios (legacy) and uefi mode. Don’t change it only inspect the setting. Also if it IS in uefi mode, disable secure boot. FOG will not boot if secure boot is enabled.

As I posted before a screen shot of the error would really help.

[cjesso]

@george1421 I was trying to get you to read my mind. This is super new to me and I am not sure what I had to look for. The wiki walkthroughs are def not fool proof and super vague in places. I did look in the BIOS and i can set it to UEFI only, legacy only, both, legacy first, UEFI first etc. I will try whatever you suggest.

[cjesso]

@george1421 sounds good. I have a bunch of screen shots. I will send them shortly.

[Tom Elliott]

As @george1421 is suggesting, the bootfile is up to you and your needs.

Most people start using undionly.kpxe (this is the most generic and tends to work for most systems which is why it’s suggested even in the installer).

That said, this is not a “hard” thing, just a basis to start with.

With more and more systems coming defaulted with UEFI enabled, you may need to use ipxe.efi to boot things.

[cjesso]

@Tom-Elliott ! Ok, so the laptop boots, and gets to the white FOG project screen. I had tried doing full inventory and I get a bunch of errors/info, resulting in a failed task.

I tried uploading images, but it keeps saying something went wrong while parsing server response.

So the first set of errors says: ERROR parsing subspaces from PCCT
Then UDHCPC: sending discover, no lease failing, Failed to get an IP via DHCP, check setup and try again.

Then it goes to generating new host keys, running post init scripts.

Then Attempting to register host…Failed.
An error has occurred. Cannot register host. (/bin.fog.auto.reg)
Args passed:

I realize that is a ton of info but I do not know which part of it is relevant.

I can email screenshots if its easier?

[george1421]

@cjesso OK you have 2 issues here. One is a bug in 1.4.1 and the second we will focus on in a minute.

[Tom Elliott]

Please look at:

FOG Configuration Page->FOG Settings->General Settings->FOG_WEB_ROOT

I’m going to surmize that it’s basically set as WEB_ROOT. Edit it to read /fog/

[cjesso]

@george1421 ok, I am on 1.4.2 now (just updated it)

[george1421]

@cjesso said in BOOTFILE?:

So the first set of errors says: ERROR parsing subspaces from PCCT
Then UDHCPC: sending discover, no lease failing, Failed to get an IP via DHCP, check setup and try again.

Does the network switch where this target computer is connected, have spanning tree turned on and its not using one of the fast spanning tree protocols?

[george1421]

@cjesso said in BOOTFILE?:

@george1421 ok, I am on 1.4.2 now (just updated it)

Still a bug, you need to fix what Tom posted. There was an issue setting up the database that will cause the checkin issue.

As for posting images. I use firefox and just drag and drop the images from my desktop to the FOG editor.

[cjesso]

@george1421 I do not see that option there?

FOG_USE_SLOPPY_NAME_LOOKUPS
FOG_MEMTEST_KERNEL
FOG_CAPTURERESIZEPCT
FOG_CHECKIN_TIMEOUT
FOG_FTP_IMAGE_SIZE
FOG_CAPTUREIGNOREPAGEHIBER
FOG_USE_ANIMATION_EFFECTS
FOG_KEYMAP
FOG_KERNEL_ARGS
FOG_USE_LEGACY_TASKLIST
FOG_DEFAULT_LOCALE

FOG_HOST_LOOKUP
FOG_UUID
FOG_ADVANCED_STATISTICS
FOG_DISABLE_CHKDSK
FOG_CHANGE_HOSTNAME_EARLY
FOG_FORMAT_FLAG_IN_GUI
FOG_MEMORY_LIMIT
FOG_USED_TASKS
FOG_SNAPIN_LIMIT
FOG_TZ_INFO

FOG_FTP_PORT
FOG_FTP_TIMEOUT
FOG_BANDWIDTH_TIME
FOG_URL_AVAILABLE_TIMEOUT
FOG_URL_BASE_CONNECT_TIMEOUT
FOG_URL_BASE_TIMEOUT
FOG_LOGIN_INFO_DISPLAY
FOG_IMAGE_COMPRESSION_FORMAT_DEFAULT

FOG_TASKING_ADV_SHUTDOWN_ENABLED
FOG_TASKING_ADV_WOL_ENABLED
FOG_TASKING_ADV_DEBUG_ENABLED
FOG_REAUTH_ON_DELETE
FOG_REAUTH_ON_EXPORT

[george1421]

@cjesso Its under here. FOG Configuration Page->FOG Settings->General Settings

Goto FOG settings page, and select Expand all
Then search for FOG_WEB_ROOT on the web page.

[cjesso]

@Tom-Elliott Its under webserver and its already set to that

Web Server
FOG_WEB_HOST
FOG_WEB_ROOT
FOG_REPORT_DIR
FOG_THEME

[george1421]

@cjesso So right now FOG_WEB_ROOT == /fog/ Did you do a fresh install of fog 1.4.1 or was it upgraded to 1.4.1?

[cjesso]

@george1421 its under web server and its already set to /fog/

[george1421]

@cjesso Very interesting, what we posted was the exact cause of that check in message on the client.

Have you attempted again to pxe boot since you updated to 1.4.2?

[cjesso]

@george1421 yes and actually i did a fresh install of 1.4.2. I decided to wipe everything and start from scratch.