olley Posted April 7, 2016 Report post Posted April 7, 2016 Dear all. I received some Surface Pro 4 devices from MS and stucking to deploy Windows 10 to them. My setup is: Config Mgr 2012 R2 SP1 CU3 Surface Pro 4 i7, 16 GB, 128 SSD Windows 10 Enterprise x64 ENG Build 1511 Deployment through PXE x64 Boot image updated to ADK 10 At the end of step "Apply Operating System" -> "Applying image..." it stops with error 80004005. The same Task sequence is running well on Dell XPS 13 machines and Hyper-V Gen1. So when I received that error on my Windows 7 machines it was always related to a wrong time configuration. So I already added anyweb's tweek to fetch the current NTP settings in prestage mode as described here: https://www.windows-noob.com/forums/topic/11016-how-can-i-sync-the-bios-date-in-winpe-to-avoid-pxe-boot-failure-with-system-center-2012-r2-configuration-manager/#entry41925 I'm out of ideas here and any help would be appreciated. Things I checked: SMSTS.log -> Please see attached Task sequence screenshots -> Please see screenshots attached Time while error appears -> I'm from Germany, the Win 10 image is ENG. Date is correct, time is one hour past. I think this is because of the English Windows? Unattended.xml -> Please see attached Option 66/67 -> Not configured, doing all with IP helper Diskpart -> Disk 0 is online with full 128GB So I think this is somehow related to the Surface. It must be related to them because my other devices are working :-) But I've no idea why... Thanks for any ideas and best regards, Oliver smsts.log Win10-Duisburg2016.xml Quote Share this post Link to post Share on other sites More sharing options...
olley Posted April 7, 2016 Report post Posted April 7, 2016 Oh no thats embarassing. Please ignore my post, found the issue myself. If anyone else has the same issue and also already tried things like me please have a look into your Partition step for the device. Because all our current devices ran in legacy mode I forgot to put in the UEFI partition part. You can, if you don't need any specials, simply use the default setup of the basic SCCM task sequence regarding UEFI. Best, Oliver 2 Quote Share this post Link to post Share on other sites More sharing options...
Apexes Posted April 7, 2016 Report post Posted April 7, 2016 haha, i've done exactly the same myself before now Glad you spotted it Quote Share this post Link to post Share on other sites More sharing options...
