Search the Community
Showing results for tags 'adk win10'.
Found 2 results
Amani posted a topic in System Center Configuration Manager (Current Branch)So l’m kind new to SCCM’s OSD and I’ve been assigned to do an upgrade for Windows 7 workstation to Windows 10 v1703. I read online that the maximum ADK supported by SCCM 1606 is v1607, lucky I also read some posts online saying that it worked fine with Windows 10 v1706 although Microsoft does not support it. Now, my questions is our environment has an older ADK version that I don’t wish to remove if that possible. Can I just install the new ADK + upload new images to console + use new USMT Package for user data migration? Or must I upgrade the whole winPE to the new ADK environment? And if so, is there is any easier way then using scripts to update image and adk level ? ( older SCCM versions don’t have the option of reloading boot images) *current environment has two ADKs !! win 8.1 /older version of win 10 adk . If anyone can guide me please, I’m supposed to start the upgrade as soon as possible as windows 7 is going to be out of support in 2020.
After upgrading to 1511 and ADK win10 and running the patch kb314370, F12 a client and get "No boot file name available". Cannot get F8 to open a cmd prompt for support logs either, yes it is enabled. Both the new (x86 and x64 from ADK) boot images are distributed and have WinPE 10 drivers. PXE is enable and advertised by the DT. SMSPXE.log on the server is not even being populated. Previous to this upgrade, we could PXE boot, now we can't. Thank you for any help! KACouillard