anyweb

hi Peter, please post the smsts.log file so we can determine why it failed, first thoughts would be to verify the cdkey and/or unattend.xml references

have you tried integrating MDT into ConfigMgr and using what it provides ?

you can use maik kosters web services to achieve that, have you looked at them at all ?

what does distmgr.log tell you ?

from log1 that means it cannot communicate with the mp due to network issues (no ip, or dns problems), so you need to pause the task sequence mid action, and verify if it indeed is able to communicate with the dp/mp otherwise of course it will fail most likely cause, lack of network drivers in the boot image for the hardware involved cheers niall

what doesn't work exactly, can you attach your smsts.log file so i can take a look ?

you must always use the correct language pack cab file for the respective version of Windows, so Windows 10 1607 needs the 1607 cab files, and same for Windows 10 1511, it needs the 1511 language cab files and so on...

is sql running on a separate server ? what do the event viewer logs tell you ?

that's the way it works with Windows 10, see > http://rzander.azurewebsites.net/how-to-change-the-welcome-screen-language-in-win10/

are the client settings to enable SCEP management correctly deployed to the target collection ?

i'll happily help you with getting your frontend working, feel free to add me to skype or whatever

hi Art and welcome, glad you are here :-) cheers niall

can you attach your smsts.log please

hi and welcome take a look at these posts they should get you started, you'll need to incorporate web services to get that functionality it's all covered in the windows-noob OSD book in great details by the way https://www.windows-noob.com/forums/topic/1064-step-by-step-guides-system-center-configuration-manager-2007/#entry11753

can you attach your dmpdownloader.log and cmupdate.log please

have you tried restarting the SMS_Executive component ?

it will hide if you use the correct version (architecture) of windowhide.exe for those boot images.

are you sure it's using the specified customsettings.ini ?

what version of SCCM are you running exactly ?

a standard user is fine, the permissions are not for changing the time, but to contact Active Directory via Net Time .

have you seen this post from Paul ? it's for 1602 but it should be the same scenario

so to summarize, you have captured the Windows 7 wim using SCCM correct ? and when you deploy it using a task sequence Windows ends up on D: ? when using the osdpreservedriveletter=false, what drive letter does Windows end up on ? cheers niall

hi, look at your logs again, it's ok if you missed it, so did I Feature update to Windows 10 <SKU>, version 1607, <language> are the actual updates for Windows 10 1607, so it's working fine ! i.e. the Windows 10 upgrades are now known as Feature Updates... cheers niall

i havn't tried it yet but hope to do so this weekend, i'll ask Microsoft to comment in the meantime

is the computer in the collection that you've deployed the task sequence to ? did you update machine policy on that computer ?