@george1421 I pulled the latest build of Ipxe and the build number did update and had a different build number but it still did the same thing.

I’ve reimaged using deploy image about 5 times now and it consistently works now go figure!

Luckily in my environment we don’t have any old computers, this moving forward will be the lowest spec machine we will have.

One other thing that was strange was when doing a full registration of the host and I was asked would I like to deploy an image if I said yes it accepted my username and password using Ipxe.

Thanks for explaining why Ipxe was picked as a default efi image too. I just wonder how many others will be affected by this change in firmware by HP and what it is changing in the NIC!

David

@george1421 I pulled the latest build of Ipxe and the build number did update and had a different build number but it still did the same thing.

I’ve reimaged using deploy image about 5 times now and it consistently works now go figure!

Luckily in my environment we don’t have any old computers, this moving forward will be the lowest spec machine we will have.

One other thing that was strange was when doing a full registration of the host and I was asked would I like to deploy an image if I said yes it accepted my username and password using Ipxe.

Thanks for explaining why Ipxe was picked as a default efi image too. I just wonder how many others will be affected by this change in firmware by HP and what it is changing in the NIC!

David

Ok I’ve fixed this now.

I swapped to using snponly.efi instead of ipxe.efi

I couldn’t find any instructions on how to do this as a noob. Is it in the wiki as I couldn’t find it?

I did the following on Ubuntu :-

Open terminal

sudo -i
nano -w /etc/dhcp/dhcpd.conf

edit the entries for UEFI-64-1, UEFI-64-2 and UEFI-64-3

Change the filename from “ipxe.efi” to “snponly.efi”

  }
    class "UEFI-64-1" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:>
        filename "snponly.efi";
    }
    class "UEFI-64-2" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:>
        filename "snponly.efi";
    }
    class "UEFI-64-3" {
        match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:>
        filename "snponly.efi";

Ctrl + o then enter to save

Ctrl + x to exit

Restart DHCP

sudo service isc-dhcp-server restart

You then get the below when booting

Thanks @george1421 for all the help in this thread.

David

Ok I’ve been doing some more investigation.

I have an older batch of HP Probook 430 G8’s here and that can log on to deploy image fine. When it PXE boots I get the following :-

With the newer batch of HP Probook 430 G8 I get the following :-

If I run a firmware update on the old batch of probooks I can no longer log in to deploy image it will not accept the credentials.

The only difference I can see is the warning about using legacy NIC wrapper and all zeros for the mac address.

Does Ipxe need to updated to support this new firmware?

Thanks

David

Also to add I started from scratch and rebuilt the server this morning so it’s just Ubuntu and the fog installation pulled from the git.

@george1421 hi George the laptop is an hp probook 430 g8

Both the hp and dell are using ufei

Correct when hitting deploy image on the hp I still get a logon screen with the password hard coded. On the dell I get no logon screen and just a choice of image.

@george1421 thanks for helping George.

The plot thickens. I think it’s an issue with the latest batch of laptops we have.

With login removed from the parameters and the username and password hard coded it still asks for a login and won’t accept anything.

I tried a very old dell laptop and it went straight through and asked which image to deploy.

Any other suggestions

@george1421 No everything is stock

@george1421 The same user ID works from the web interface yeah.

The only thing I have changed is I updated the kernel as we had some new computers that the Nic was detected on.

If this isn’t something common or there is no solution I will rebuild the server but I was hoping to avoid it.

@george1421 Hi George, Thanks for replying

1. It won’t accept the Fog Admin account.
2. We are using UK english keyboard
3. There is no special characters in the passwords they are pretty basic. I even tried test and test to see if it would work.

David

I’m having an issue with my Fog server, when we try to select the deploy image option from pxe on machines we are imaging it prompts for the username and password but it refuses to accept it.

I have tried creating new users from the web interface, I tried a different Kernel nothing works.

I can of course fore a deployment from the web interface as a task on the host but I would rather the technicians would be able to self serve without using the web interface.

Thanks for any help

David