@jdnoble18 I had it happen with my new HP desktop too… maybe something more likely that it has something to to do with nvme… but I’m sure if you change the nvme0n1§ to just sda it will complete the image process. The other issue besides it not clearing the task is that it doesn’t change the hostname of the device either.

So on the d1.orginal.uuids if I change nvme0n1§ to sda it competes the task. I didn’t check if it still set the guids set in the file but the task completes and the PC boots just fine.
My licensing issue was because the time in the BIOS/UEFI wasn’t correct. I’m guessing that windows was using that as the trusted time and it was 12 hours out so the cert. was failing.

I did try the init files that tom said to try in that post and upgraded fog to the most current version. neither of those made a change. aside from the init files i downloaded didn’t list the args. I posted this in there and Sebastian asked me to open a new thread.

Server

• FOG Version: 1.4.4 Rev 6077
• OS: Ubuntu 16.04.3 LTS

Client

• Service Version: 1703
• OS: Windows 10

Description

When I push down my image made on my new Lenovo’s, ThinkPad T570 and Yogo 370. I get the error "Failed to set disk guid (sgdisk-) (restoreUUIDInformation). I don’t get the error when I push down my generic image, though that image is sda instead of nvme0n1.
I’m not sure if this is causing my issue of then not being able to license windows. the imaged machines say they cannot contact the KMS server but the machine that built the image works fine.

here is the d1.original.uuids for a lenovo image

/dev/nvme0n1 674471e0-83d1-4e08-8244-836a1ca3c0bf
/dev/nvme0n1p1 1:F0006F29006EF64E 1:e7603dce-a954-4023-b00a-c58dd298979e
/dev/nvme0n1p2 2:FC6F-347F 2:f269d22a-3486-41b8-90e0-7b8300e988be
3:5a103e14-fa6b-4517-810d-192e9b075d7a
/dev/nvme0n1p4 4:906E70206E700170 4:54a07814-8489-4b72-ab78-3ab94763142b

and here is a picture of the error screen

Has there been any progress on this? I have 2 new lenovo images, Thinkpad T750 and Yoga 370, I’m trying to make and errors out on nvme0n1 and doesn’t complete the job. I tried the init files posted above but that didn’t help. When I down the generic image it doesn’t have any problems downloading. It’s only with the images that I upload from them.
It boots afterwards just fine but I the imaged machines fail it license windows, the source machine works fine.

@Sebastian-Roth I haven’t had any issue with legacy booting. Just UEFI.
I’ll see if I can do some testing on this tomorrow.

@Iceman344 While I would like to get FOG to boot in EFI. I did get it to boot in legacy mode and image without an issue and then push down an EFI image. I was using the USB 3.0 adapter for this. I also just got the ethernet extension adapter but I haven’t had time to test it yet. I would think this should work better as it will use the on board Intel LM-219 network adapter.

@Tom-Elliott Is there any more info I can get on why just memtest would fail? I browsed ever the logs but I didn’t see anything.

@Tom-Elliott but I did test disk and it did work

@Tom-Elliott Sorry, I go to Group management. click basic tasks next to the group. Then click on advanced select Memtest86+. Click create task. it says
“Memtest86+: Successfully created tasks for
All hosts successfully tasked”

Then when I go to active tasks nothing shows up.