@Quazz said in Extremely Slow Deploy to NVME drives:
@DeRo93 If available, install firmware updates, BIOS updates and such.
Already done. Nothing helped :/. I hope there will be a Solution in future. We only work with HP. And i think the new one will all get NVME SSD´s… Anyway thank your for your Help.
@Tom-Elliott HP UEFI does not have AHCI - IDE Options in their UEFI Setup 
HP says AHCI is activated by default on newer Models.
Hi,
i tried the Init.xz and the kernel argument. I updated FOG and BIOS from the Notebook. Even tried older BIOS Versions.
With “slow” its like the rate is going to 20 kb / min … it starts with 70 MB / min and then goes lower and lower… Its a Deploy…
SSD in this Notebook is a “sk hynix bc501 hfm256gdjtng-8310a” with the newest firmware.
@Quazz said in Very slow cloning speed on specific model:
@DeRo93 Unfortunately there are some issues on that model with certain SSDs (though not all) that are currently resolved.
I’m unsure where to even point the finger at this point, but extensive attempts from our side have been done with no success.
Another user was using older models to deploy their images to the drive and then put those drives into the G6 model.
Does this mean there is NO other method to get my FOG Image on this Notebook model ?
@Quazz Yes I tried your .xz File. Does not solve the problem for me
I´ts a HP EliteBook 840 G6
@Quazz Is there a way to create a .xz file for PartClone 0.3.13 ?
@Middle I have the same Problem. Updated FOG and PartClone but it does not help 
. Did you find another solution?
ah okay. Unfortunately this does not helped and im not able to deploy images on the HP Elitebook 840 G6.
Do you have any other suggestions :/?
Same here with the “nvme_core.default_ps_max_latency_us=5500 not a valid identifier” problem…
Okay i GOT IT!
I noticed that my HP is getting Information from the replicated DHCP Server. Replication was not completed and there was undionly.kpxe instead of ipxe.efi. Changed the String and now its working!!! Thank you for your help!
I now checked the same process with a Lenovo Notebook. PCAP shows that he is downloading the correct file: ipxe.efi
@george1421 Here is the PCAP File.
I also inspected the File with WireShark. I clearly see that the Notebook tries to download Undionly.kpxe. Why is he doing that? 067 Bootfile Name is set on ipxe.efi
@Quazz said in HP Elitebook 840 G6 - UEFI PXE Boot not working.:
You’ll have to disable secure boot in BIOS.
Did you read my first post? I already mentioned that I disabled Secure Boot in BIOS.
@george1421 said in HP Elitebook 840 G6 - UEFI PXE Boot not working.:
@DeRo93 So if you ignore the filters for a moment and go back to the main scope the default value for dhcp option 67 is undionly right? What happens if you just change that to ipxe.efi. Understand this is only a test and changing this WILL break bios boots. But we need to understand if its the boot file that is having a problem or your filters. Forcing the boot file to ipxe.efi will give you a direction to look.
beeping and back to Startmenu
Also can you explain this? What startmenu? Is it the firmware boot options menu or is it the FOG iPXE menu?
I dont even work with Filters. I have a Scope for FOG in DHCP on Windows Server 2019. Scope Options > 067 Bootfile Name is ipxe.efi atm. If i know i need to install a legacy image i just switch it to undionly.kpxe . Worked for years…
When i boot the HP i press F12 to boot from Network. After F12 i can select IPv4 or IPv6. I choose IPv4. Then Blackscreen with “Start PXE over IPv4”, after that the HP beeps and I see UEFI Startmenu where i can select if i want to boot to UEFI Setup or again Network Boot or Firmware update etc. …
@David-Osinski said in HP Elitebook 840 G6 - UEFI PXE Boot not working.:
@DeRo93 Maybe different UEFI architectures than what your other machines are using
(Example)NOTE: There are many other UEFI architectures besides just “PXEClient:Arch:00007”.“PXEClient:Arch:00002” and “PXEClient:Arch:00006” both should get “i386-efi/ipxe.efi” as their option 067 boot file.
“PXEClient:Arch:00008”, “PXEClient:Arch:00009”, and “PXEClient:Arch:00007” should get “ipxe.efi” as their option 067 boot file.
“PXEClient:Arch:00007:UNDI:003016” should get “ipxe7156.efi” this file is specific to the Surface Pro 4.
I tried every filename as 067 Bootfile Name. But still only beeping and back to Startmenu.
@David-Osinski said in HP Elitebook 840 G6 - UEFI PXE Boot not working.:
@DeRo93 Please try following this article to setup your DHCP for UEFI/Legacy
https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence
But it worked for over 100 Notebooks for years now…Where is the difference with this Notebook…
No I manually switch the boot file in “068 Bootfile Name” on DHCP Server.
Hello Guys,
i have a huge problem and i hope you can help me out with this.
I spent a couple of hours on research but i didnt find any solution.
I have a new HP Elitebook 840 G6 with the newest Bios Version and try to boot into Fog via PXE.
Legacy Boot and Secure Boot is disabled.
After I boot into PXE I see “Start PXE over IPv4.” and then it beeps and goes back to the Startmenu (Bios).
Then i picked my Elitebook 840 G3 and tried the same. Everything fine. Its booting into FOG and i can start deploying.
So i thought maybe i missed some other Bios Options. I Replicated the Setup on both Notebooks. Nothing worked.
DHCP on our Server is on “ipxe.efi”. Legacy with “undionly.kpxe” works fine. But we need UEFI on this Notebook.
I even picked an Lenovo Notebook and it doesnt work. So i have 2 Notebooks where IPXE doesnt work and one G3 where it´s working.
I hope you have any suggestions for me.
Thank you in advance.
@george1421 yes after i tried so much things i remembered that fog runs the batch as SYSTEM. So i think that will be the problem because the Installer copies Files into the Users Folder. I will try your another suggestion with the mapped drive.
@Sebastian-Roth I tried to get a silent command for the installer and tried the standard lines like /verysilent , /silent , /s, /quiet , /q. And yeah it actually worked only with /s 