tps10

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.

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.

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?

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.

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.

I can try that. I did see that guide. My question is can you still manage these images in the console? Meaning adding drivers and such? I really don't want to have to use DISM for everything when it should work like it is supposed to.

I don't have any antivirus software on this server. This is simply a test server to see how this all works.

I did. I had hoped it would be that easy. I uninstalled 8.1 > reboot > Install 10 > reboot > Nothing....

Ok so apparently the permissions on that folder don't matter. I uninstalled ADK 10 and put 8.1 back on and it works fine, even though that folder still says I don't have rights.

Im wondering if I were to uninstall SCCM 2012 entirely and reinstall if that would fix it but this is a test environment. No way I am going to do that on our production environment. Did I need to install ADK10 before installing R2 SP1? That doesn't seem like it makes any sense as it needs 8.1 to install and then after that you uninstall 8.1 and install 10.

So I have been beating my head against the wall here trying to figure out how to get this to work so we can image Surface Pros with Windows 10. I am able to image them using SCCM 2012 R2 SP1 but they don't get any of the drivers. Well doing some research it appears they need the updated version of DISM (which you get with the newer Windows 10ADK) Test environment Windows Server 2012 R2 Standard ConfigMgr 2012 R2 SP1 CU1 Windows ADK 10 (initially it was ADK 8.1) Surface Pro 3 Once I realized I can't install drivers using the version of WinPE with ADK 8.1, I followed the below instructions to upgrade to ADK 10. Upgrade to ADK10 Ok, so the upgrade went fine but then whenever I try and add new boot images I get the following error: "The specified file cannot be imported. Make sure the file is not read only and you have read and write access to it." I looked at the SMSPROV log file and get the following error every time I try and create a boot image. I think I have narrowed it down to permissions in C:\Windows\Temp on the server (which seems to be where it stages all it's boot image files). When you add a boot image, it creates a folder (in my case BootImages) in the Temp folder. Well shortly after it errors out and when I go look in the temp folder sure enough it created the BootImages folder, but when I try and open it I get an error saying I don't currently have permission to access this folder. Click here to permanently get access. Well I can do that, and even give it all the permissions I want and then go in and out of that folder all day long. The secound I go back and try and add a boot image however, the permissions reset and I am denied access to that folder. Really want to get this working the way it should and not deal with putting band-aids on existing boot images because you lose the ability to update it through the console.