Just came out last week. https://blogs.technet.microsoft.com/enterprisemobility/2016/09/09/configuration-manager-and-the-windows-adk-for-windows-10-version-1607/
Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Monday, September 12, 2016 11:31 AM To: [email protected] Subject: RE: [mssms] RE: Just upgraded 2012 R2 to 1606 As far as I know there has still been no support statement from ConfigMgr for any Win 10 ADK beyond 1511. I’ve been keeping my eye on it, but so far I don’t think the light has turned green on 1607. I’ve been reading mixed results on the web, it is not clear that the problems users are having are related to ADK1607 or not. For me, I am sticking with ADK1511 and CM1602 in Production until win10(1607) goes CBB. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Adam Juelich Sent: Monday, September 12, 2016 9:52 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] RE: Just upgraded 2012 R2 to 1606 With each new version of ConfigMgr, they generally recommend utilizing the latest ADK, although it usually takes a few weeks or months for them to confirm that. Uninstall the existing ADK, install the new one, reboot, and then re-create your boot images. On Mon, Sep 12, 2016 at 9:37 AM, Miller, Todd <[email protected]<mailto:[email protected]>> wrote: There shouldn’t be any SCCM specialization in the WinPE.wim – only extra WinPE components like MDAC, Powershell etc . The ConfigMgr specialization happens in the WinPE wim that has the package ID appended to the name of the WIM. So make sure you use the WimPE.wim and not WinPE.XXX2nnnn.wim. There is also some site specialization done at the time the boot device is created (USB Stick, CD ROM etc) I am using WinPE for ADK 1511 and I didn’t want to have to redo the hotfix patch so I just imported the already patched one from my test environment. It works fine to import WinPE.WIM from test to prod. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Long, Karen Sent: Monday, September 12, 2016 9:05 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] Just upgraded 2012 R2 to 1606 I just upgraded SCCM 2012 R2 to 1606; all looks to have went well except my boot images did not upgrade. I have a dev environment that they upgraded correctly. Is it okay to just import the images from that location to production? Thanks. Karen Long Senior System Engineer YRC Freight Field Resource Center Office: 913.344.3682<tel:913.344.3682> YRC Freight Customer Service Center 1.800.610.6500<tel:1.800.610.6500> Standard<http://yrc.com/services/standard/> / Accelerated<http://yrc.com/services/accelerated/> / Time-Critical<http://yrc.com/services/time-critical/> / Logistics Solutions<http://www.yrc.com/services/logistics-solutions-overview/> [yrcf_sigLogo] ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy all copies of the original message and attachments thereto. Email sent to or from UI Health Care may be retained as required by law or regulation. Thank you. ________________________________ ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy all copies of the original message and attachments thereto. Email sent to or from UI Health Care may be retained as required by law or regulation. Thank you. ________________________________ The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
