A new update has been released that adds the following platforms to the supported platforms list for Microsoft System Center Configuration Manager current branch, version 1606:
This update adds the following platforms to the supported platforms list for Microsoft System Center Configuration Manager current branch, version 1606:
All iOS 10 iPhone or iPod Touch devices
All iOS 10 iPad devices
These iOS 10 devices may be targeted as client platforms for features such as Application Deployment, Compliance Settings, and Company Resource Access.
After you install this update, the Supported Platforms tab of policy settings has an All iOS 10 iPhone or iPod Touch devices option in the iPhone category and an All iOS 10 iPad devices option in the iPad category.
Policies that previously had the root category (iPhone or iPad) selected now have iOS 10 automatically selected together with all earlier iOS versions. Previously, when individual iOS versions, such as All iOS 7 IPad devices, were selected but the corresponding top level category was not selected, the policies did not automatically have iOS 10 selected.
Update information for System Center Configuration Manager, version 1606
This update is available for installation in the Updates and Servicing node of the Configuration Manager console if the following conditions are true:
The Configuration Manager environment uses Microsoft Intune for hybrid mobile device management
This version of the ADK has been primarily tested and is supported starting with the most recent release of the Configuration Manager current branch, version 1606. As noted in the above FAQ (which you already read, right?) we have limited support for Windows 10, version 1607, in Configuration Manager version 1602. Customers that are still on this version of Configuration Manager and will be deploying the newer version of Windows 10 can upgrade the ADK to the latest version if desired, or remain with the prior version, Windows ADK for Windows 10, version 1511. Beyond that, we do not support deployment of Windows 10, version 1607, with older versions of Configuration Manager , so the need for this new version of the Windows ADK does not apply.
If you’ve read that last paragraph a few times and are still scratching your head, let’s try the same in tabular format:
Windows 10 ADK Version
1 The Windows ADK for Windows 10, version 1511, provides basic forward compatibility and can be used for image capture, image apply, driver injection, and offline update servicing of Windows 10, version 1607, if absolutely necessary. We strongly recommend upgrading to the latest ADK version, but basic forward compatibility is supported during the transition period.
2 The newer ADK is only needed if deploying Windows 10, version 1607.
Frequently Asked Questions
Q. Does this include the hotfix 3143760 for the Windows 10 ADK, version 1511?
As noted in support article 3143760, that hotfix only applies to version 1511. The underlying problem requiring the hotfix is not present in the Windows 10 ADK, version 1607.
Q. What’s the process to update? Do I need to restart the server?
Use the following process to update the Windows ADK on your site server(s):
Uninstall the previous Windows ADK from Programs/Features control panel.
Install the Windows ADK for Windows 10, version 1607.
NOTE: We do not recommend using a custom installation path for the Windows ADK when used in conjunction with Configuration Manager.
Restart the server. (You may not be prompted to restart, and some will suggest that this is not required. The best practice to ensure all components are properly registered, especially the WIMGAPI filter driver used by DISM, is to restart.)
Refresh the package for the User State Migration Tool for Windows. Select the package and click Update Distribution Points.
Q. Do I need to update boot images and media?
Yes, any Windows 10-based boot image will need to be regenerated to consume the new version of Windows PE. (Updating the boot image just rebuilds from a cached copy, injecting the latest Configuration Manager binaries, drivers, etc.) There is not (yet) currently a process in the console to regenerate boot image with the latest winpe.wim (as this was traditionally handled by the Configuration Manager setup process), so it does require triggering the ExportDefaultBootImage WMI method against the target boot images. Here is a Windows PowerShell script (RegenerateBootImageWinPE10.ps1), written by Wilhelm Kocher and Herbert Fuchs from Microsoft Premier, to automate and simplify this process. Run the script from an elevated Windows PowerShell prompt.
Q. I’m upgrading from Configuration Manager version 1511/1602 to version 1606. Should I upgrade the Windows ADK first?
The in-console servicing updates do not currently regenerate the default boot images, just update them with the latest Configuration Manager binaries. You can use the ADK install process above to upgrade the Windows ADK before or after updating the site to 1606, but you also must use the process above to regenerate the default boot images so that they are using the latest version of Windows PE.
Q. My site version is currently System Center 2012 R2 Configuration Manager SP1 and I plan on upgrading to current branch version 1511 and then immediately updating the site to version 1606. When should I upgrade the Windows ADK?
The default boot images will be regenerated from the installed Windows ADK during the CD-based setup process when upgrading to the current branch baseline build. While we do not support the use of the Windows ADK for Windows 10, version 1607, with any version of System Center 2012 R2 Configuration Manager, we recommend upgrading the Windows ADK first (immediately before upgrading the site) so that the latest Windows PE is consumed at that time.
Q. What about Configuration Manager Technical Preview sites?
Yes, the Windows ADK for Windows 10 should be upgraded to version 1607 with Configuration Manager Technical Preview version 1606 and later.
Q. What about the Microsoft Deployment Toolkit (MDT)?
We have done limited testing with MDT 2013 Update 2 and the Windows ADK for Windows 10, version 1607, thus support this usage. There will be an update to MDT coming later this fall.