How to Create an SCCM Microsoft Office Uninstallation Package
Question details
The user needs to create a deployment package in Microsoft Configuration Manager (SCCM) to mass uninstall on-premises Microsoft Office Standard or Professional across an organization.
- Product
- Microsoft Configuration Manager / Microsoft Office
- Device & OS
- Windows
- Scenario
- Enterprise deployment and mass uninstallation of software.
- Observed behavior
- IT administrators need to silently remove existing MS Office installations via SCCM deployment to free up licenses or prepare for alternative office suites.
Before deploying an uninstallation package, ensure you have administrative access to the Microsoft Endpoint Configuration Manager console and test the removal script on a small pilot group of machines to verify silent execution without interrupting end users.
Use the Office Deployment Tool (ODT) to Create an Uninstallation Package
The most reliable method for removing modern Click-to-Run Microsoft Office installations is using the ODT with a custom XML file configured for silent uninstallation.
This method applies to Office 365, Office 2019, and Office 2021 installations deployed via Click-to-Run. For older MSI installations, different command parameters or OffScrub scripts are required.
Download the Office Deployment Tool (ODT) from the official Microsoft Download Center and extract the setup.exe file to a shared network source folder accessible by your SCCM environment.
Create a new text file named `uninstall.xml` in the same directory. Add the `<Remove>` configuration tag specifying the product ID you wish to uninstall, and ensure `<Display Level="None" AcceptEULA="TRUE" />` is set to force a silent removal.
Open the Configuration Manager Console, navigate to 'Software Library' > 'Application Management' > 'Applications', and click 'Create Application'. Choose to manually specify the application information.
In the Deployment Types tab, add a new script installer. Set the uninstallation program command line to `setup.exe /configure uninstall.xml` and define your detection method based on the Office registry key or file path.
Distribute the application content to your Distribution Points and deploy the uninstallation task to your chosen device collection, setting the purpose to 'Required' and user experience to 'Hidden'.
Consult the Microsoft Configuration Manager Community
If you encounter errors, have a mix of MSI and Click-to-Run environments, or need highly specific detection methods, the Microsoft Q&A community is the official channel for SCCM guidance.
Deploy WPS Office as Your Lightweight Enterprise Alternative
If your organization is uninstalling Microsoft Office to cut licensing costs, optimize system performance, or deploy a unified solution across different platforms, WPS Office is an exceptional choice. It offers a free, lightweight, and highly compatible alternative that integrates seamlessly into standard IT deployment workflows, including SCCM.
Frequently Asked Questions
Can I uninstall older MSI versions of Office using SCCM?
Yes. For MSI-based Office installations (such as Office 2016 or earlier), you can often use the standard `msiexec /x {ProductCode} /qn` command, or utilize Microsoft's official OffScrub scripts packaged into an SCCM deployment for a cleaner removal.
How do I ensure the SCCM Office uninstallation is completely silent?
In your ODT XML configuration file, set the display property to `<Display Level="None" AcceptEULA="TRUE" />`. Additionally, in the SCCM deployment settings, ensure the user experience is set to 'Hidden' and 'Install for system'.
Will an SCCM uninstallation package remove user data and settings?
Standard Office uninstallation methods remove the application program files but typically leave user-specific settings, Outlook profiles, macros, and saved documents intact in their respective AppData and Documents directories.
Why is my SCCM Office uninstall deployment failing with error 17002?
Error code 17002 usually indicates that a reboot is pending on the client machine or another installation is currently in progress. Ensure your SCCM deployment package handles reboot return codes correctly or enforces a system restart prior to execution.
