FruitGuy Posted September 10, 2015 Report post Posted September 10, 2015 I can manage the new boot images.....however the older ones, I can no longer add drivers to. But I've just gone back and replaced my OSD task sequences with the new boot images so it's not really an issue. Quote Share this post Link to post Share on other sites More sharing options...
FruitGuy Posted September 10, 2015 Report post Posted September 10, 2015 Also I saw where you're wanting to do this for the Surface Pro's. I had an issue with the Surface Pro's when imaging. It occurred during the formatting of the SSD portion right at the very beginning. It was very frustrating because my test Surface Pro 3 it always worked on, but I bricked my boss's Surface Pro 3 twice, which is what made me look into it further. Apparently the Surface Pro 3 has two hard drive manufacturers, Hynix and Samsung. The Hynix drive has the issue. I had to create a whole separate boot image just for the Surface Pro 3 that only contains drivers for it and none of my Dell models. Once I did this, formatting succeeded properly. http://happysccm.com/2014/12/16/format-failed-0x80070057-during-task-sequence/ Quote Share this post Link to post Share on other sites More sharing options...
pembertj Posted September 10, 2015 Report post Posted September 10, 2015 I can manage the new boot images.....however the older ones, I can no longer add drivers to. But I've just gone back and replaced my OSD task sequences with the new boot images so it's not really an issue. I can't find the Technet article, but this is by design - once you upgrade to ADK 10 you can no longer customize the old boot images. ~Tom Quote Share this post Link to post Share on other sites More sharing options...
tps10 Posted September 10, 2015 Report post Posted September 10, 2015 I can't find the Technet article, but this is by design - once you upgrade to ADK 10 you can no longer customize the old boot images. ~Tom Yeah, and that's ok with me. I just can't get sccm to create new boot images when using ADK 10. If I could somehow just add the new DISM into the 8.1 adk I would be good to go. I would use that as my base wim for creating new boot images. But I can't seem to do that either. And frankly, I don't want to. I want it to work like it should. Quote Share this post Link to post Share on other sites More sharing options...
FruitGuy Posted September 11, 2015 Report post Posted September 11, 2015 Have you tried using that guide yet? Also I know you're doing this in a test environment. Is the test environment just a single PS? I dont have a test environment so I know when I did this. I started at the CAS and then worked down to the PS, the only two locations that had ADK installed. Also I did the import of the new boot image from the CAS itself and not from my own PC. Quote Share this post Link to post Share on other sites More sharing options...
tps10 Posted September 11, 2015 Report post Posted September 11, 2015 Have you tried using that guide yet? Also I know you're doing this in a test environment. Is the test environment just a single PS? I dont have a test environment so I know when I did this. I started at the CAS and then worked down to the PS, the only two locations that had ADK installed. Also I did the import of the new boot image from the CAS itself and not from my own PC. All I have is a primary site, no CAS. We have two workstations running the admin console in addition to on the server. I am trying to add the boot image on console on the server. Quote Share this post Link to post Share on other sites More sharing options...
tps10 Posted September 11, 2015 Report post Posted September 11, 2015 Also I saw where you're wanting to do this for the Surface Pro's. I had an issue with the Surface Pro's when imaging. It occurred during the formatting of the SSD portion right at the very beginning. It was very frustrating because my test Surface Pro 3 it always worked on, but I bricked my boss's Surface Pro 3 twice, which is what made me look into it further. Apparently the Surface Pro 3 has two hard drive manufacturers, Hynix and Samsung. The Hynix drive has the issue. I had to create a whole separate boot image just for the Surface Pro 3 that only contains drivers for it and none of my Dell models. Once I did this, formatting succeeded properly. http://happysccm.com/2014/12/16/format-failed-0x80070057-durin Wow, interesting. I bricked a surface because it failed during some part of the imaging and I reset it and now it won't boot into the OS or boot media at all. I wonder if it had a Hynix drive? Quote Share this post Link to post Share on other sites More sharing options...
tps10 Posted September 11, 2015 Report post Posted September 11, 2015 Tried the guide that FruitGuy suggested. Still doesn't work. I'm surprised that nobody else is having this issue. I found the error in the log file but it means nothing to me. Quote Share this post Link to post Share on other sites More sharing options...
FruitGuy Posted September 11, 2015 Report post Posted September 11, 2015 http://blog.coretech.dk/rja/post-sccm-2012-sp1-failure-to-update-boot-images/ Quote Share this post Link to post Share on other sites More sharing options...
tps10 Posted September 11, 2015 Report post Posted September 11, 2015 http://blog.coretech.dk/rja/post-sccm-2012-sp1-failure-to-update-boot-images/ I'll look into this, but as of now, we only have two devices running Windows 10: Surface Pro 3 and HP 840 G2 laptops. So I decided to inject the network drivers for those two models into the wim from the ADK 10 (with updated DISM) and then downgrade back to ADK 8.1 on the server, since they can still image 7 and 8.1 computers. If I have to add another device to the mix before MS fixes this crock of s**t then I will just manually add the drivers. At any rate this test server is just going to image 64-bit Windows 10 computers anyway. I appreciate everyone's help on this. Quote Share this post Link to post Share on other sites More sharing options...
