anyweb

can you reboot the machine and using a winpe USB key or pxe boot manually open up the unattend.xml file stored on the hard drive and see what's in it ?

after making the change and 'saving' it you still need to update the boot wim to the dp's otherwise you'll be using the boot image that doesn't have f8 support added.

welcome ! 1. yes, but it should be an mdt integrated task sequence. The only time you'd want to recreate the mdt boot images is when changing MDT version (mdt 2013 update 1 to update 2 for example) or changing ADK version or when wanting to revert the mdt boot images to how they were before they got bloated with drivers or scripts. 2. when you create new task sequences you absolutely can re-use the MDT Toolkit and MDT Settings packages, as regards the naming convention something like this is what I use \\sources\os\mdt\mdt 2013 update 2\ _____________________________\MDT Toolkit _____________________________\MDT Settings as described here but it's entirely up to you how they should be created. 3. use the default one if you are not using any of the facilities it provides, otherwise download many sample customsettings.ini from the MDT pro's like Mikael Nystrom and Johan Arwidmark, they have plenty of example blog posts to help you with that

you can deploy the driver pack (msi) as an application via the Application Catalog, have you tried that ?\ here's some info https://msdn.microsoft.com/en-us/library/mt210838.aspx

here's one guide but it is for MDT 2013 Update 1 https://www.windows-noob.com/forums/topic/13190-how-can-i-deploy-windows-10-x64-to-the-microsoft-surface-pro-4-using-mdt-2013-update-1/ basically this guide is all you need for deploying Windows 10 in SCCM 2012 R2, the only difference for Surface Pro 4 is that you'll need the nic drivers injected into the boot wim, the exact same drivers and method as in this guide, the only thing you'd have to change is the WMI query to point it to Surface Pro 4 instead of Surface Pro 3

yup it works the same, it just looks different in windows 10 (more polished)

have either of you asked Dell which NIC is supported for UEFI network boot ?

well for UEFI network boot to work you need to have dhcp scope options 66/67 removed if they are set and configure iphelpers to point to the ip address of the distribution point hosting the WDS server. Can you video the PXE boot attempt ? what does the smspxe.log (on the dp) reveal ? do any UEFI only devices PXE boot and if they do are they booting from the x64 boot wim or an x86 one....

According to statcounter.com Windows 10 has overtaken Windows 8.1 usage cross the world. from the graph above it looks like this occurred last December. Interesting to note is that Windows 7 tops the usage at approx 46%. Based on this graph it looks like Windows 10 still has an uphill battle before it becomes the dominant Operating System more info > http://gs.statcounter.com/#desktop-os-ww-monthly-201506-201601

did you click next ?

probably because the drivers are already imported and therefore duplicates, you can use jason sandys duplicate script to create a txt file in each folder of the driver pack before importing

7b is usually storage driver related, are you adding any storage drivers for that model ?

what do you get ?

works fine for me, can you please describe exactly what issues you are having and attach logs where appropriate

thanks ! show me a screenshot of yours with the ribbon, you are probably just looking in a different place to me

are you asking how to do client push ?

well that's how it's done, so are you saying your boot image doesn't respond to F8 ?

interesting, have you raised a bug on connect about it so Microsoft can fix it ?

yup, you can do it using wbemtest as described here (step 9) https://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/

what version of configmgr are you using ? what version of the adk ? what version of windows 10 and lastly, can you attach some logs ?

well it sounds like it can't write to the hard disc, can you attach the entire SMSTS.log file please ?

R2 simply enables features that are already in the product, however there are licensing implications to using R2, check if you are licensed to use it or not first

so for those of you who are not on R2 it would be something like this 2012 SP1 CU5 > 2012 SP2 > 2012 SP2 CU2 confusing, perhaps, here's some explanation hopefully https://www.niallbrady.com/2015/05/16/confused-about-the-system-center-2012-r2-configuration-manager-sp1-and-system-center-2012-configuration-manager-sp2/

not quite, I said this

if the os completes successfully or not there will be an smsts.log look in C:\Windows\CCM\Logs do you see it there ? we need the smsts*.log in order to see why it's failing on the enable bitlocker step.