Secure Boot causing failures in SD5

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 5
Comments: 3

I can reliably image systems using Windows 10 on SD5 using a WinPE USB Bootable disk. PXE is not an option in my environment. The only issue is that I have to keep Secure Boot disabled. Obviously this is going to cause a headache from a cyber perspective as we move to full disk encryption. Whenever I enable secure boot, I get a boot error "unable to find boot drive" or similar.

Can anyone shed any light on this?

Wed, 11/15/2017 - 15:57
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 5
Comments: 47

What build are you using?

We're using a different environment (PXE and Linux Media) but Build 1749 has allowed us to keep Secure Boot enabled.  Keep in mind you'll need to update your media as well.

Thu, 11/16/2017 - 16:16
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 5
Comments: 47

I had mentioned PXE and the standard Acronis Linux Boot Media

Actually, we're starting to see inconsistency and I do not have the time to troubleshoot or wait for support to respond to tickets.  It seems that M.2 based disks are failing on 1749 and 1755.  I'm going to need to go back to using WinPE 10 and Ghost64.exe until a new version of SD is released.

Tue, 11/21/2017 - 18:44
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 5
Comments: 30

Cbc-kc is this by chance using Samsung nvme PM961 ssds as target? I am suddenly encountering issues with my HP workstations using 1749. I will create a post to elaborate on my issue.

Tue, 01/09/2018 - 01:33
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 5
Comments: 47

Jason, I do not have any hardware available to check right now, but there were several SSD's that showed the issue.  At this point, we have moved back to our OLD solution (for deploying on troublesome units) until an undated version of SD is released.  Go figure that Ghost64 12 works, huh?

I may or may not open another ticket when time permits, but I don't see the point at the moment.  Sitting on the phone or waiting for replies are not an option at the when I need a working enterprise solution in the long run.

Wed, 01/10/2018 - 12:48
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 5
Comments: 30

Good to know. I am beginning to think most of these issues with m.2 are storage driver related. I just created a master image from a Dell Optiplex 7050 with an m.2 ssd. Not a PM961 but m.2 all the same. My practice is to push newly created master images back onto the pc through Snap Deploy to test the image. I kept having my deployment fail with error "cannot access the selected disk". This was using the Linux boot agent which is what I was using when I had issues earlier this week. So today I created a winPE boot disk and injected the latest storage driver from Dell. I was able to image the pc without any further error. I am on Snap Deploy vers 1749.

Thu, 01/11/2018 - 19:59