FruitGuy

Anyone have an update on this? I'm starting to see the same thing.

Alright, I found the issue. The Default Client settings were not something that I got to configure on the front end. I started poking my head around there and saw that the default settings had Remote Tools disabled. Which is why, once it pulled in the actual policy, everything at a later time worked like it should. Sorry for wasting everyone's time, I had assumed something like this would have been setup correctly to begin with.

Alright so I googled that. That isn't the issue. The registry key for provisioning is set to false when I login, and again after I login after reboot.

what registry keys need to be changed? I'm new to the whole OSD thru SCCM, we just implemented it. I'd been using MDT for imaging and LanDesk for Remote Control.

Also, I'm referring to Remote Control, not Remote Assistance or anything like that.

So I've noticed that when I image a machine, it seems to take about 30+ minutes before I can remote to it. As soon as OSD is done and it goes to the Ctrl+Alt+Del screen, I can remote to it. But then I have the user reboot and I can't link to it for about 30+ minutes. I have the user reboot, because I've noticed for some reason, I can't access any network shares until I do. Any idea on what I can do to fix this?

http://blog.coretech.dk/rja/post-sccm-2012-sp1-failure-to-update-boot-images/

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.

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/

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.

http://blogs.technet.com/b/brandonlinton/archive/2015/07/30/windows-10-adk-boot-image-updates-for-configuration-manager.aspx ^^ that's the guide I followed.

I believe I had this exact same issue when I did the upgrade. By chance, did you reboot the server after you installed the ADK? I think that was my issue and after reboot, everything was fine.