Just an FYI from my experience today with multicast speeds. I was using a dumb Netgear GS516T and getting multicast speeds ranging from 900 mb to 1.5 gig at best. After switching (pun intended) to a better Netgear (GS716T) our speeds jumped to pushing 5 gigs consistently. I was always under the impression that a dumb switch was dumb and gigabit meant gigabit speeds. Turns out I was dumb and gigabit doesn’t guarantee gigabit. There are many more elements in play in switching speeds like its processor and backplane. So if everything else seems to work with fog but you’re still not achieving the speeds you thought or hoped for - always remember the IT troubleshooting mantra. Eliminate the hardware issues first.

@Sebastian-Roth

https://drive.google.com/file/d/1613JgCnNn_mqkwHHFt7T-7kA7e298BF-/view?usp=sharing

d1.partitions:

label: gpt
label-id: 56CE61A2-3D37-4F14-8AE0-A0084F00A7A5
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 976773134

/dev/sda1 : start=        2048, size=      921600, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=F2461728-72A6-4200-93E7-B1159265B72C, name="Basic data partition"
/dev/sda2 : start=      923648, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=2104822C-DD09-4840-B543-67340B8E099B, name="EFI system partition"
/dev/sda3 : start=     1128448, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=5AEC1D8F-C565-4809-8EAC-A996FCA88367, name="Microsoft reserved partition"
/dev/sda4 : start=     1161216, size=   973700027, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=9A8688F9-4EF1-4550-B220-00E1FE21B447, name="Basic data partition"
/dev/sda5 : start=   974862336, size=     1908736, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=CAEE35CD-7BE7-4432-9B68-DE060AF1A69E, attrs="RequiredPartition GUID:63"

d1.minimum partitions

label: gpt
label-id: 56CE61A2-3D37-4F14-8AE0-A0084F00A7A5
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 976773134

/dev/sda1 : start=        2048, size=      921600, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=F2461728-72A6-4200-93E7-B1159265B72C, name="Basic data partition"
/dev/sda2 : start=      923648, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=2104822C-DD09-4840-B543-67340B8E099B, name="EFI system partition"
/dev/sda3 : start=     1128448, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=5AEC1D8F-C565-4809-8EAC-A996FCA88367, name="Microsoft reserved partition"
/dev/sda4 : start=     1161216, size=   330329656, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=9A8688F9-4EF1-4550-B220-00E1FE21B447, name="Basic data partition"
/dev/sda5 : start=   974862336, size=     1908736, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=CAEE35CD-7BE7-4432-9B68-DE060AF1A69E, name="attrs="RequiredPartition GUID:63"

d1.fixed size partitions

:2:3:1

Additional update. I installed Windows 10 off a USB. Captured image successfully. Tried to deploy back to itself and Windows will not start. It comes up with the Automatic Repair screen.
For image settings I used: Multiple Partition, Single Disk not resizable, Partclone Compressed

@Joe-Gill

The OS is Windows 10 x64.
My FOG version is 1.5.4
I did not use sysprep. This image was created with on the mechanical drive.
The image is set to: Windows 10. Single Disk - Resizeable. Partition - Everything.

I tried installing Windows 10 on the blank SSD just to format and add some partitions but the deploy still failed with the same error.

The laptop does not give me any ACHI options in BIOS on the drive. When I try to boot with UEFI devices only FOG will not load so I have to set it to Legacy boot.

I have an image that was built and captured on a mechanical drive. I swapped out the drive for an SSD and tried to redeploy the image. The deploy failed while restoring partition tables GPT. The Exit Return Code was 4.

I tested the image on a different laptop with a mechanical drive and it deployed without issue.

The computer is an HP Zbook 15U G3. The drive is recognized in bios as I’m able to perform a hard drive error check on it.

@Wayne-Workman

Tried a totally different, but exactly the same, box and the master image worked for capturing and deploying. Very strange but whatever. I’ll take it.

Thanks!

@wayne-workman

Recent development. I pulled a master image from a different computer and tried that. I’ve had one successful deployment. Going to test another on Monday. Will update then. Thanks!

@sebastian-roth

Here’s what I’ve found. I recaptured the image from the master. I was able to re-image the master machine with the capture and it worked. Then I tried a totally different computer and it didn’t work. These are all factory new HP’s out of the box.

Now, something I noticed different in the BIOS. On the machine that is working I have a boot option under UEFI that says M.2 Windows Boot Manager which does not exist on the machines that I’m attempting to image. I’m still getting the operating system not found on those.

@SEBASTIAN ROTH thank you kindly for your reply. Please find the requested information below.

I am on version 1.5.4

I currently have the partition set to Singe Disk - Resizeable but I’ve also tried Multiple Part Single Not Resizeable without any success.

The OS is correctly set to Windows 10

No errors are received on deploying the image. It simply reboots and comes back to the boot device not found screen.

Please note that this workstation uses an NVMe SSD. The only change I’ve made in BIOS is to allow LEGACY PXE booting.

CONTENTS

d1.fixed_size_partitions
:1:3

d1.minimum.partitions
label: gpt
label-id: 4251A099-FB23-4AA7-8DE7-0FB9F64FBBD8
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 1000215182

/dev/nvme0n1p1 : start= 2048, size= 2072576, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=9C48635D-51CD-4F39-94B1-92BE6906A844
/dev/nvme0n1p2 : start= 2074624, size= 377257624, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=54FE51CA-67BE-4800-8050-F48BE37C6938
/dev/nvme0n1p3 : start= 999951024, size= 262144, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=434727C3-71FF-4950-898F-F6AAC7DDEA69

d1.partitions
label: gpt
label-id: 4251A099-FB23-4AA7-8DE7-0FB9F64FBBD8
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 1000215182

/dev/nvme0n1p1 : start= 2048, size= 2072576, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=9C48635D-51CD-4F39-94B1-92BE6906A844
/dev/nvme0n1p2 : start= 2074624, size= 997876400, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=54FE51CA-67BE-4800-8050-F48BE37C6938
/dev/nvme0n1p3 : start= 999951024, size= 262144, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=434727C3-71FF-4950-898F-F6AAC7DDEA69

I am able to capture the image for the HP EliteDesk 800 G3 but when I try to restore it fails to boot. The message I receive is BootDevice Not Found. Please install an operating system on your hard disk. Hard Disk - (3F0)

I’ve downloaded the latest version of FOG but it hasn’t resolved the issue. Any help would be appreciated.

Just an FYI from my experience today with multicast speeds. I was using a dumb Netgear GS516T and getting multicast speeds ranging from 900 mb to 1.5 gig at best. After switching (pun intended) to a better Netgear (GS716T) our speeds jumped to pushing 5 gigs consistently. I was always under the impression that a dumb switch was dumb and gigabit meant gigabit speeds. Turns out I was dumb and gigabit doesn’t guarantee gigabit. There are many more elements in play in switching speeds like its processor and backplane. So if everything else seems to work with fog but you’re still not achieving the speeds you thought or hoped for - always remember the IT troubleshooting mantra. Eliminate the hardware issues first.