Topics created by netbootdisk

Hi Guys

Two quick updates on this:

This ipxe7156.ipxe also seems to be working for some Dell machines we have.

To make Hyper-V Generation 2 VM’s to PXE boot UEFI correctly; I had to add a new PXEclient mapping of PXEClient:Arch:00007:UNDI:003000 for the ipxe7156.ipxe boot file. (Secure boot should also be disabled!)

(Tested with FOG 1.5.2)

Revised Powershell Code:

import-module dhcpserver $DHCPserv = "DHCP-SERVER-HOSTNAME" Add-DhcpServerv4Class -Name "PXEClient (UEFI x64) 2" -Type Vendor -data 0x505845436c69656e743a417263683a3030303032 -Description "UEFI Architecture Type 2" -ComputerName $DHCPserv Add-DhcpServerv4Class -Name "PXEClient (UEFI x64) 6" -Type Vendor -data 0x505845436c69656e743a417263683a3030303036 -Description "UEFI Architecture Type 6" -ComputerName $DHCPserv Add-DhcpServerv4Class -Name "PXEClient (UEFI x64) 9" -Type Vendor -data 0x505845436c69656e743a417263683a3030303039 -Description "UEFI Architecture Type 9" -ComputerName $DHCPserv Add-DhcpServerv4Class -Name "PXEClient (UEFI x64) 7" -Type Vendor -data 0x505845436c69656e743a417263683a3030303037 -Description "UEFI Architecture Type 7" -ComputerName $DHCPserv Add-DhcpServerv4Class -Name "PXEClient (UEFI x64) 7 UNDI 3016" -Type Vendor -data 0x505845436c69656e743a417263683a30303030373a554e44493a303033303136 -Description "UEFI Architecture Type 7 UNDI 3016 (Surface Pro 4)" -ComputerName $DHCPserv Add-DhcpServerv4Class -Name "PXEClient (UEFI x64) 7 UNDI 3000" -Type Vendor -data 0x505845436c69656e743a417263683a30303030373a554e44493a303033303000 -Description "UEFI Architecture Type 7 UNDI 3000 (Hyper-V)" -ComputerName $DHCPserv Add-DhcpServerv4Policy -Name "UEFI-IPXE" -Description "UEFI IPXE" -ScopeId 0.0.0.0 -Condition OR -VendorClass EQ, "PXEClient (UEFI x64) 7*","PXEClient (UEFI x64) 9*" -ComputerName $DHCPserv Add-DhcpServerv4Policy -Name "UEFI-IPXE32" -Description "UEFI IPXE32" -ScopeId 0.0.0.0 -Condition OR -VendorClass EQ, "PXEClient (UEFI x64) 2*","PXEClient (UEFI x64) 6*" -ComputerName $DHCPserv Add-DhcpServerv4Policy -Name "UEFI-IPXE7156" -Description "UEFI IPXE7156" -ScopeId 0.0.0.0 -Condition OR -VendorClass EQ, "PXEClient (UEFI x64) 7 UNDI 3016*","PXEClient (UEFI x64) 7 UNDI 3000*" -ComputerName $DHCPserv Set-DhcpServerv4OptionValue -PolicyName "UEFI-IPXE" -OptionId 67 -Value "ipxe.efi" -ComputerName $DHCPserv Set-DhcpServerv4OptionValue -PolicyName "UEFI-IPXE32" -OptionId 67 -Value "i386-efi/ipxe.efi" -ComputerName $DHCPserv Set-DhcpServerv4OptionValue -PolicyName "UEFI-IPXE7156" -OptionId 67 -Value "ipxe7156.efi" -ComputerName $DHCPserv Set-DhcpServerv4OptionValue -OptionId 67 -Value "undionly.kpxe" -ComputerName $DHCPserv Set-DhcpServerv4OptionValue -OptionId 66 -Value "10.20.30.40" -ComputerName $DHCPserv

@netbootdisk You can create a universal image within the firmware style. The disk and hardware interface is different between uefi and bios. The disk format is less of an issue. We use MDT and two VMs (one bios and one uefi) to create a consistent golden image for each firmware style. That way each golden image is consistently the same.

In working branch, I’ve now included a History Report. It’s likely not perfect, but at least the information is presented to the GUI now. It allows for CSV and PDF exporting as well.

No SSD drives, they are standard Optiplex 3010’s. Will give the delayed started trick a go.

Odd thing too is the problem lab was still booting Win7 fine despite gparted showing a blank partition table too! Back to reimaging now 🙂

[quote=“netbootdisk, post: 32609, member: 5249”]Hi

Fog 1.1.2 is looking like an awesome improvement over 0.32 so far - which in itself was an awesome upgrade over Ghost Solution Suite :D[/quote]That was my overall goal, so I’m glad to make it a reality.
[quote=“netbootdisk, post: 32609, member: 5249”]
Not sure if this has already been reported, however FYI…

A) Renaming computers in the Host Management page usually doesn’t seem to save. Although other settings on that host/general page do save.[/quote] Not to sound relentless, but what’s the exact usage that’s giving the problem. Are there any messages? I know when you update the host or any field it resets, but if you scroll the page to the top, it should show a “box” that displays “Host updated successful, host failed because of …, etc…” or some message of the sort. I believe there may be a bug here but don’t have a means to reproduce. I have no issues renaming.
[quote=“netbootdisk, post: 32609, member: 5249”]B) I installed the Location plugin on 1.1.2 (previously not installed when I upgraded from 0.32) and whilst the Location page icons appears, none of the “New Search”, “List All Locations”, “Create New Location” pages display anything. (I’ve just edited the database location table manually with the required details and this does appear to actually work, so I can assign hosts to locations and then they TFTP boot the bzImage from the correct server then :))[/quote] I don’t know what the exact issue is but I have a hunch it’s due to the way plugins were loading or trying to load. I know it’s fixed in SVN. Did you have to create the location table, or did the install of the plugin do that for you?
[quote=“netbootdisk, post: 32609, member: 5249”]C) I don’t think Multicast is working at all - partimage just sits waiting. Not too worried as we mostly unicast anyway. (FYI on 0.32 Multicast was super slow/useless on 100Mbit workstations, but perfect on any Gigabit machines. Yet Ghost’s Multicast worked fine on the same machines. HP Procurve switches with IGMP filtering configured, etc.)[/quote]Multicast of partimage isn’t working? I don’t know and is totally possible. I do know it’s working for partclone. Have you checked that FOGMulticastManager service is actually running on the fog server? If you’d like you can PM me and maybe we can chat and I can help you find/fix this issue?

That’s excellent news then!

(Was referring to this in 0.32: [url]http://www.fogproject.org/wiki/index.php/Multiple_TFTP_servers[/url])