May 24 2017 05:05 AM
May 24 2017 05:05 AM
We are testing out using Servicing Plans within ConfigMgr, and upon rolling our first 1703 Feauture Update, we have discovered that all the AppX packages we removed from our 1607 builds seemed to have returned. I thought I had read somewhere that starting with 1703, it would not reinstall what was removed. Is this not the case? This is truly frustrating from an Enterprise customer perspective. We have no plans to roll out Xbox, or need the Get Office app as we already have office. We can remove them again using required standing deployments with ConfigMgr, but we should not have to.
May 30 2017 11:15 AM
May 31 2017 01:54 PMSolution
After upgrading to Windows 10, v1703 in-box apps that were uninstalled by the user won't automatically reinstall as part of the Feature Update installation process. (Apps de-provisioned by IT administrators will still be reinstalled, this is expected to be addressed in the next Feature Update)
Jun 01 2017 04:42 AM
Thanks for the response. Glad it is being addressed. Have to say I'm surprised it wasn't addressed for enterprise customers first, or at least at the same time. I'm really glad we haven't rolled out to more users yet as this is a pain to clean up.
Jun 02 2017 11:05 AM
Jun 16 2017 07:36 AM
I'm already removing them as part of the task sequence for new builds. The issue is with Feature Updates. These are just installed as an update. I have written two scripts to clean this up. One machine script that will run after the FU to remove them from the system, and another user based in case someone logs on before the system script runs. Pretty ugly. Looking forward to not having to do this for 1709.
Jun 21 2017 07:53 AM
you can also remove the unwanted apps in the install.wim directly, so just mount the wim and run the PowerShell against the mounted wim. The newly created wim can be used in new installations and upgrade sequences, so you have a consisten configuration.
Jun 21 2017 08:20 AM
Thanks, I am aware and do that today. My post is around the Feature Update (patch) that is pushed, not new installs. It sounds like the fix is coming in 1709.
Jun 21 2017 08:25 AM
Hey Eddie, we apply the feature update via ConfigManager update task sequence and are using the same customized wim for the update as for new installation (we still face to many issues after just applying the feature update: missing .net 3.5; language packs, Office needs to be repaired,...)
Jun 21 2017 11:22 AM
Are you referring to an "upgrade task sequence"? If so this is different than what I am referring to. I am talking about when you are on a version of Win10, say 1607, and you are going to 1703 using servicing plans.