Having no issues so far with MDT 2013 U2, SCCM 2012 R2, SCCM CB 1606 deploying Win10 1607 using ADK 1507 in all scenarios. I intend to upgrade to ADK 1607, just not now, unless something is broken or unsupported. So far, nothing broken.
From: [email protected] [mailto:[email protected]] On Behalf Of Aaron Czechowski Sent: Friday, August 12, 2016 2:39 PM To: [email protected] Subject: RE: [MDT-OSD] New MDT updates for Windows 10 1607? (finally catching up on DL mails after being out for a while…) FYI, I’m working on a blog post to cover as much of this as I can. Hoping to publish next week. A few thoughts in short: · MDT 2013 Update 2 with ADK 1607 appears to be working ok with basic deployment actions with Win10 Anniversary Edition. We WILL have a new release of MDT later this fall to fully support this Win10 release, as well as Server 2016 and such. · SCCM procedure is to uninstall old ADK, install new ADK, and then reboot. The reboot may not be required, but is generally a good idea to make sure the new ADK (especially the wimapi driver) is properly registered. o Then you need to regenerate the default boot images. Just updating the boot image does not grab the latest winpe.wim, just stuffs in the latest SCCM binaries. There’s a WMI method to do this (ExportDefaultBootImage), I’ll include this in the blog. We also have a work item to add this right into the console. ☺ I’ll have more info in the blog to come, including support version matrixes, upgrade paths, etc. Stay tuned! Aaron From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Giroux, Eric J Sent: Wednesday, 10 August, 2016 08:44 To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] New MDT updates for Windows 10 1607? Interesting, I tried just adding the Win10 1607 OS to my existing MDT 2013 Update 2 server without updating the ADK. ADK is still at 1507 level. I did not run into any issues with build & capture of a 1607 using the old ADK. Is there something I’m missing here? I had no trouble editing Unattend.xml with WSIM. Nothing broke but is there something incomplete or incorrect due to not using ADK 1607 on the MDT server (boot images)? Thanks, Eric Giroux Solutions Engineer E-mail: [email protected]<mailto:[email protected]> | Office: (207) 575-2482 Mobile: (207) 239-5190 | Fax: (207) 575-2158 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Steve Whitcher Sent: Tuesday, August 2, 2016 6:40 PM To: [email protected]<mailto:[email protected]> Subject: Re: [MDT-OSD] New MDT updates for Windows 10 1607? This message originated outside of Unum. Use caution when opening attachments, clicking links or responding to requests for information. There is no need for a new MDT, just the new ADK. On Tue, Aug 2, 2016 at 4:56 PM ODONNELL Aaron M <[email protected]<mailto:[email protected]>> wrote: Is there any word of an update to MDT 2013 now that the Win10 1607 update is out? Or will just updating the Win10 ADK to 1607 on an existing MDT 2013 environment be OK? Thanks, Aaron O’Donnell Field Services Technician Oregon Department of Transportation [email protected]<mailto:[email protected]> [email flying-t]
