This is just an additional option to consider. Note 1: I know there are numerous rebuttals in support of scripting.
Flexibility - the apps can be added back or additional apps can be removed easily. Just add the app to the store and deploy the uninstall to all users. Manageability - no scripting is required. Visibility - apps can be seen in ConfigMgr or Intune allowing any admin to see what’s being removed. Using PowerShell could still work from ConfigMgr or Intune as well, but I think there are several benefits to this process over using a script. This will allow us to provide a consistent experience to our users whether their devices are built using traditional OSD or if we go more modern with AutoPilot/Intune. We have decided to use the Windows Store to manage the removal of these apps instead of relying on a separate script. However, we are continuing our process of streamlining our processes and reducing customizations for our Windows devices. We used to run this script as part of the Task Sequence but found that it started hanging so we moved it to the offline servicing process instead. I have integrated it into my Windows 10 offline servicing script that I use to apply updates to my image each month. It uses PowerShell and an XML file with a list of apps to be removed. We have been using a customized version of a script that Michael Niehaus published in 2015. If you’ve been managing Windows 10 for very long, you’ve likely implemented a script or other method to remove some of the In-Box apps that come with Windows 10. Using SCCM Task Sequence Variables as Scripts. Triggering ConfigMgr Client Actions from a Task Sequence. Dynamically Updating Unattend.XML during an OSD Task Sequence using MDT Variables and ZTI Scripts. 
Debugging SCCM/ConfigMgr Task Sequences on the Fly. Clearing Local Group Policies during an Windows 7 to 10 In-Place Upgrade Task Sequence. 
Part 5 – Dynamic Whitelisting using the Cisco ISE External RESTful Service.Part 4 – Integrating 802.1x Authentication into an In-Place Upgrade Task Sequence.Part 3 – Integrating 802.1x Authentication into a Bare Metal Task Sequence.Part 2 – Building an 802.1x Enabled WinPE Boot Image.Part 1 – Building an 802.1x Computer Authentication Script.Windows 10 Feature Updates – Using Setupconfig.ini to Manage Feature Updates in the Enterprise.Windows 10 Feature Updates – Using Custom Action Scripts.Windows 10 Feature Updates – The Challenge of Servicing in the Enterprise.Windows 10 Feature Updates – Leveraging SetupDiag for Better Reporting.Demystifying Windows 10 Feature Update Blocks.
0 kommentar(er)
