We are using a task sequence to feature upgrade clients from 1607 to 1703 and would like to make sure extra consumer apps are not (re)installed during the feature update.
There is this article from Michael that suggests it is fine to just DISM those components out of the install.wim that is used by the task sequence when performing the feature update. It says that the is it he best and most straight forward way to feature upgrade Windows 10 while avoiding those extra components. Is the guidance here no longer valid? In our testing this method works great. Removing the components after the upgrade leaves bits of cruft. https://blogs.technet.microsoft.com/mniehaus/2016/08/23/windows-10-1607-keeping-apps-from-coming-back-when-deploying-the-feature-update/ I brought this up recently at MMS, and was told by people who's opinions I respect that this was a really horrible idea because DISM would not remove the components cleanly. Discuss?? ________________________________ 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. ________________________________
