Imaging SSD first timer
-
@theopenem_admin Good news. It worked. I selected EFI partition. That is great.
-
It isn't a model issue. It's an efi / legacy issue. Your original image was legacy so when it's deployed, Theopenem configures the machine for legacy to match the original. But since it's an efi machine that's not going to work. Setting the partition method to standard tells Theopenem to ignore the original image and match the destination machine type. That's how a single image can be used for both efi / legacy, using the standard partition type.
-
@theopenem_admin Have you had any luck creating a new kernel? Thanks
-
@theopenem_admin I also have a few different Dell machines that have this new realtek family of NICs. Will a new kernel be possible?
-
I ended up building a WinPE bootable usb drive and using it for imaging. It is not ideal but it works.
-
I was thinking about trying that, but we use the universal image aspect. I think that is only available with the Linux imaging environment.
-
@surfboy we use the universal image as well. Use the WinPE boot should not effect the image itself. I use a universal image on my Dell Optiplex 3050, 3060, 3070 and 3080. The WinPE is just for booting purposes. One you get booted into the imaging server the rest works the same as it does in Linux.
-
I will look into then. Thanks.
-
I've released kernel 5.14.12, although I doubt it will make a difference. You can download it from admin-settings-> kernels. Remember to recreate your pxe files or usb with the new kernel.
-
Yeah, it didn't help. Still getting about ~140MB/min.
I did configure the image for WIE. That is working a lot better.
