Posts made by Andy Abplanalp

@RobTitian16 That’s what I’ve done, yes. I discovered, by luck, that not appending anything to memdisk works for certain ISOs. I use Parted Magic frequently, so I was happy to get it working. I’ve never seen this documented anywhere…glad you’re working!

@RobTitian16 that sounds correct

@RobTitian16 mine is under my Advanced Menu but works great like this:
:parted
initrd ${boot-url}/iso/pmagic.iso
chain memdisk ||
echo failed to boot
prompt
goto MENU

@Bigredcherokee said in boot pxe issue:

FOG_PXE_BOOT_IMAGE

my FOG_PXE_BOOT_IMAGE is set for init.xz

@Wayne-Workman yes, but also his settings in FOG (that he has pictured) should be pointing to a kernel and the init file. Basically…it appears to have both incorrect configuration settings AND the typo in the dhcpd.conf

@Andy-Abplanalp not only that - your dhcpd.conf file has “undionly.kxpe” listed instead of “undionly.kpxe”

@Bigredcherokee your boot file is “ipe.pxe”?

@Junkhacker correct me if I’m wrong but wouldn’t 7671 be after @Tom-Elliott fixed the sanitization fields? I had this issue as well and just went to my Advanced menu and clicked “save” to update it. Cleared out the ampersand issue for me and started working right away.

@sgennadi is your path correct? You’re defining {boot-url} but you’re using {fog-ip} in the path to your image files

@loosus456 does this server have Broadcom NICs in it by chance? If so, you can look into disabling Virtual Machine Queues.

@mlnancejr8808 that still doesn’t answer my question. If you are creating a local admin account with your answer file, then make sure it doesn’t exist already in the image before you sysprep it again. Delete it from Local Users and remove any corresponding entries in the registry under the ProfileList key. That should solve this problem.

@mlnancejr8808 when you say “adding the local admin account”, do you mean other than ‘Administrator’? If so, then yes, I’m guessing my last reply is on the right track.

@mlnancejr8808 is sysprep adding any local accounts with your answer file? The reason I ask is…I’ve seen the exact symptoms you’ve described where a local account gets added during sysprep from the answer file but stops with that exact error because that account already exists from being added during previous syspreps. Make sure the ProfileList registry keys are cleaned up before subsequent/repeated sysprepping.

@mlnancejr8808 How many times has this image been sysprepped?

@pmonstad Do you see the progress indicator if you click the “Active Tasks” link in the left pane?

I can tell you from personal experience that FOG and Kace can coexist. Look into the ITNinja forums for setting the 244 option for DHCP for the K2000 and leave DHCP option 66 for FOG. Then look into PXE chaining to the IP address of the K2000 if you still want to use it for imaging. The K1000 and K2000 are completely separate so you shouldn’t have to worry about the ticketing/inventory system at all.

Our FOG installation works similarly to the K2000 Dell drivers feed where it uses DPInst to install hardware-specific drivers after sysprep based on Dell model number. (You may also need to rebuild your KBE ISO to tell it to use option 244.)

Carsten,

I can tell you from personal experience that this development team has gone far above and beyond even what could be reasonably expected from PAID support. When you say that this “feature” is “simple to make for that matter”, it’s OPEN SOURCE - do it yourself.

Andy

If that works, chances are you’ll have to run “service FOGMulticastManager restart && service FOGImageReplicator restart && service FOGScheduler restart” to get everything running properly.

run “service mysql restart” after the reboot and see if you can get in

Does “service mysql restart” bring the login page up?