@ZINGARO1972 Sure you can move files around in /tftpboot. That’s one way of doing it. Or you can use symbolic links. Or change the filename in your DHCP configuration. Moving files or using symbolic links you might overwrite files if you don’t pay full attention. So I’d prefer to change DHCP config.

I guess you installed FOG with DHCP. Then edit /etc/dhcp/dhcpd.conf and simply change the filename there. After saving the file you only need to restart the DHCP service: service isc-dhcp-server restart

Do I get this right, you are trying to boot your HP server as a client via PXE to be cloned?
Do you see any error messages when trying to boot via PXE? Without that we won’t be able to help.

Seams like others have achieved booting from a Broadcom NetXtreme II NIC https://forums.fogproject.org/topic/3949/ipxe-problems-with-broadcom-netxtreme-ii

Marking this solved as I have done extended testing on virtualbox 5.0.0 and cannot find an issue, see here: https://forums.fogproject.org/topic/5884/client-boot-error-msg-error-0x040ee119

Please let us know if you cannot get it to work this way.

@gooroox said:

@Wayne-Workman
I have the same issue now with only one of 12 Lenovo Laptops. After typing “fog” the database was updated “Updating Computer Database Status!”. This update is not helping. What could I do?

Try deleting that one laptop from your DB via the web interface, and then try to re-register it. Also make sure there are not pending tasks for this laptop - and that it has both the wired NIC present in the DB after registration.
If you’re getting a particular error, please take a photograph of it and post it here so we can see.

What version of FOG are you using?

Another potential fix would be to try svn/trunk/dev as I believe the mbr is downloaded up to the first two megs of hdd. I don’t know if it will work but from what I’ve heard it seems to do the trick.

What is the problem? My best guess for now is the issue is dealing with nic startup?

Think of it this way.

It’s like trying to fit a quarter through a dime sized hole.

There are ways you can force the quarter through, but most times it’s simply just not going to happen.

@RileyG said:

@Wayne-Workman Can you install FOG directly from the TRUNK install? If so, I think I will start from that next time.

Yes, however, if you want to keep your host data and image data and other custom settings, you need to install 1.2.0 and then import your data, then move to trunk.

But, it might be best to start fresh.

Also, if you comment out the port=0 line in the dnsmasq config, it’s highly likely that you can have internet and fog at the same time.

@cml Well Shoot! that did it. I’m sorry I should have tried a different computer first. It’s early on a Monday here in Michigan and my brain is still mush after the weekend. Thanks again…I feel dumb lol

@Wayne-Workman said:

Do you have this area in 1.2.0 ?
FOG Configuration -> iPXE Boot Menu -> Exit to Hard Drive Type

If so, play around with that setting. Not every type is supported by every machine. The default is normally Sanboot style.

Actually, that was a good recommendation, when I changed it in the FOG admin/config http interface. Helped for some for sure! Thx

I would say specify an older kernel for those models. Try kernels earlier than 3.18 and see what you find.

For now, just using the kernel update feature is fine, but once you find some that work, you can make copies and specify the kernel for those particular hosts inside their general menu.

For what it’s worth, if it’s stuck on the black screen + “ipxe initialising devices”, undionly.kkpxe works. Our HP 4520s have the Realtek NICs which have this issue.

x-post here: https://forums.fogproject.org/topic/2807/ipxe-boot-issue-with-realtek-rtl8153/18

@Frode-Woldsund It’s not a big deal. People come here for help / advice / to tell others things…

and the people that hang here are willing to give help and listen lol.

@Tom-Elliott said:

@brizio Can you clear the multicastSessions, multicastSessionsAssoc, and tasks tables?

The tasks I only want you to clear the multicast jobs.

A mysql statement to do these things would be:

TRUNCATE TABLE multicastSessions; TRUNCATE TABLE multicastSessionsAssoc; DELETE FROM tasks WHERE taskTypeID=8;

My guess, from an earlier revision, a multicast session didn’t clear properly. Because of the non-clearing, a few hosts linked to the wrong Job and the others, who had no prior setting stored in the DB, created their own session.

Again, this is just a guess, as I really don’t know what actually caused this to happen.

I’m working on a “Troubleshoot Multicast” article that has commands more friendly to Red-Hat based distros… aparently the truncate commands don’t work in Fedora 22… so… Here you go:

https://wiki.fogproject.org/wiki/index.php/Troubleshoot_Downloading_-_Multicast

@Wayne - I just tested out using snp.efi and that solution seems to have worked! I am uploading an image of our surface pro 3 as I write this.

With an option that we can active or not, like bitcoin mining

@no1bossman

That’s quite the old article, last updated in 2012 (things move fast around here).

Where it talks about IDE, it’s referring to hosts. Hosts being what you would build your image on, and upload from.

Some people really like building their images inside of a virtualized environment… I don’t get it, really. You can’t see how the image is performing on the actual hardware that it’s going on… You can’t ensure the boot time and log-in time are acceptable. You can’t ensure your drivers WILL work when you NEED to image. And de-fragmenting within a virtual host is questionable… And what about the FOG Client Service timing? That’s a big issue with the legacy client…

Maintaining an image per each model of computer you maintain is the absolute best way to ensure a flawless deployment - without bloating your image with a ton of software and drivers that it doesn’t need…

Personally, I’ll never create images on a virtual host if I can help it.

Try to turn off secure boot.

@Bill-Rice Hi, SPP and Smart Boot iso are on torrent or direct download : duckduckgo, or yahoo, or google , or other…

https://wiki.fogproject.org/wiki/index.php/Known_FOG_Bugs#The_Image_Resize_Bug