23-04-2021

Setup Controller File For Office 2010

Learning has never been so easy!

While there are many how-to's that cover silently installing Office using SCCM or script, there are few methods (that worked for me) for uninstalling it.
Using the msiexec command with the correct product code doesn't work from SCCM, since it invokes a user prompt, and SCCM is set to hide prompts.
Below is what worked for me, using PDQ-Inventory to send a remote command. I expect similar results using something like PSexec or similar tools.

Dosto Hamare Saare Video Dekhne Ke Liye Yaha Click Kare:Facebook Page: https://www.facebook.com/. May 10, 2012 Hi Everyone; I finally got a full install of Office 2010 Professional to go through. Luckly, I have a friend who also had a copy of what I got. 'C: Program Files (x86) Common Files Microsoft Shared OFFICE14 Office Setup Controller setup.exe' /uninstall PROPLUS /config UninstallQuietly.xml In a few minutes, your target client(s) should have removed Office 2010 completely, without any notifications or nag screens to the user.

4 Steps total

Microsoft Office 2010 Free Download and Install Microsoft Office 2010 is a version of the Microsoft Office productivity suite for Microsoft Windows.

Step 1: Open Notepad and paste the following

Step 2: Save as an XML file

Click 'File' > 'Save as' and change the 'Save as type' from 'Text Documents (*.txt)' to 'All files (*.*)'
Once you have chosen an appropriate temporary location (Desktop works), choose a name that is meaningful to you; add .xml to the end, and click 'Save'
(I chose UninstallSilently.xml)

Step 3: Copy the file to the PC needing uninstall

On a target machine, navigate to the 'C:Program Files (x86)Common FilesMicrosoft SharedOFFICE14Office Setup Controller' folder.
Place a copy of the .xml file you just created there.

You may need to perform this uninstall on multiple machines, in which case, copying the .XML file would be tedious. In that case, use your mass-deployment tool of choice (I like PDQ-Deploy for this sort of task) and send a command task to your group of machines, {xcopy DeploySilentScript*.xml 'C:Program Files (x86)Common FilesMicrosoft SharedOFFICE14Office Setup Controller' /Y} (Ommitting the curly braces).

Step 4: Execute the uninstall script

Using PDQ-Inventory, PSexec (from PSTools) or however else you prefer to run scripts remotely, execute the following command:
'C:Program Files (x86)Common FilesMicrosoft SharedOFFICE14Office Setup Controllersetup.exe' /uninstall PROPLUS /config UninstallQuietly.xml

In a few minutes, your target client(s) should have removed Office 2010 completely, without any notifications or nag screens to the user.
I have run this in two labs in the past two days, hitting 52 machines so far, and haven't had a single one need to reboot yet.
That said, if there is the possibility of disrupting a user on the machine, you may decide to run this script, as this method does not include suppression of reboots, if they are necessary.

Published: Jan 22, 2016 · Last Updated: Jun 04, 2020

4 Comments

Thai Pepper
StandingForChildren Nov 23, 2017 at 10:06pm
Had to use ProPlusWW in command, line but seemed to work well otherwise, thanks
Datil
Peter (Action1) Feb 25, 2019 at 04:32am
Action1 is a free software which can help to uninstall software on multiple computers at the same time. https://www.action1.com/p/Free-Uninstall-Software-Remotely-73.html
Poblano
Chad8135 Jun 4, 2020 at 05:39pm
Thank you for this, I tried so many different ways to get 2010 to uninstall, because OCT with 2016 doesn't properly remove EVERY 2010 asset and there are leftovers which was annoying to me as I wanted 2010 completely gone in place of 2016. One issue I noticed with your guide was in step 3, after 'program files' and before '(x86) there should be a space, (I copy/pasted your step to avoid any typos) and it created an improper folder structure and thus wasn't working at all.
The way I did it was I used PDQ Deploy with 2 steps, first step was a simply copy file which copied the XML from a network share over to the local computer. The next step was to run the actual uninstall command, again using PDQ Deploy even though you suggested Inventory. It seems more complicated and unintuitive to do that way, at least from what I understand about PDQ. Thank you though, this helped a lot.
Tabasco
Gcracker Jun 8, 2020 at 04:10pm
@Chad8135
Thanks for the kind words! It's been a while since I wrote this one, but it is exactly what I needed back then, and I couldn't find it all in one place at the time.
Thanks for letting me know about the typo! I've corrected the section you mentioned, though I wanted to point out that it was only the description of the command that was missing a space. The command in curly braces {} was correct to being with. I still have the original document that I created for this how-to, and I can see it has the space, so I think something may have been lost in on the SW side when they moved the docs into the newer format.
Cheers!

Download Office 2010 Setup Files

-->

We recommend that you uninstall any previous versions of Office before installing Microsoft 365 Apps. To help you uninstall versions of Office that use Windows Installer (MSI) as the installation technology, you can use the Office Deployment Tool and specify the RemoveMSI element in your configuration.xml file.

There are several ways that you can use the RemoveMSI element when installing Microsoft 365 Apps.

Uninstall all Office products on the computer.
Identify any existing language resources, like language packs, and install the same languages.
Keep some Office products and uninstall all other Office products on the computer.

RemoveMSI can be used to uninstall 2007, 2010, 2013, or 2016 versions of Office, Visio, or Project that were installed using Windows Installer (MSI).

Note

RemoveMSI doesn’t uninstall prior versions of Office, including Visio and Project, that use Click-to-Run as the installation technology. You can uninstall those versions of Office through Control Panel or by running the Office Deployment Tool and using the Remove element in your configuration.xml file.

Requirements for using RemoveMSI

The following are requirements for using the RemoveMSI element in your configuration.xml file:

You must be using at least version 16.0.12827.20268 (setup.exe version 16.0.12827.20258) of the Office Deployment Tool, which you can download from Microsoft Download Center. We recommend that you always download and use the most current version of the Office Deployment Tool. To check the version of the Office Deployment Tool, right-click on setup.exe, choose Properties, and then choose Details.
You must be installing at least Version 1803 of Microsoft 365 Apps. Version 1803 or later is available in Current Channel, Monthly Enterprise Channel, Semi-Annual Enterprise Channel (Preview), and Semi-Annual Enterprise Channel.
You must be installing Microsoft 365 Apps on a computer running at least Windows 7 Service Pack 1 (SP1) or above.

Note

Support for Windows 7 ended on January 14, 2020. For more information, see Windows 7 end of support and Microsoft 365 Apps.

Uninstall all Office products

To uninstall all versions of Office, including Visio and Project, that are already installed on the computer, add <RemoveMSI /> to your configuration.xml file. Language resources – for example, language packs, language interface packs, or proofing tools – will also be removed.

Here’s an example of a configuration.xml file that installs the 64-bit Current Channel version of Microsoft 365 Apps for enterprise in English from the Office Content Delivery Network (CDN) on the internet and uninstalls any Windows Installer (MSI) versions of Office on the computer.

Install the same language resources

If there are language resources – for example, language packs, language interface packs, or proofing tools – already installed on the computer, you can get Click-to-Run versions of the same language resources installed when you install Microsoft 365 Apps. To install the same language resources, add <Language /> to your configuration.xml file.

Here’s an example of a configuration.xml file that installs the 64-bit Monthly Enterprise Channel version of Microsoft 365 Apps for enterprise in English, along with any existing languages on the computer, from the Office Content Delivery Network (CDN) on the internet and uninstalls any Windows Installer (MSI) versions of Office on the computer.

The following are some additional details about using MatchPreviousMSI in your configuration.xml file.

You must include the RemoveMSI element.
You must specify at least one language ID. For example, en-us.
The setting isn’t product specific. For example, if Office Professional Plus 2013 in French and Visio Standard 2013 in German are installed, you will get both French and German, along with any other language IDs you have specified, when you install Microsoft 365 Apps.

Important

If you’re installing Microsoft 365 Apps from a location on your local network, such as a shared folder, make sure you’ve downloaded all the possible language files to that folder. If any of the languages needed to install aren't available in that folder, the installation will continue but without those languages being installed. To avoid this situation, we recommend that you include AllowCdnFallback='True' in your configuration.xml file. This will use the Office Content Delivery Network (CDN) on the internet as a backup source from which to install the language files.

Keep some Office products and uninstall all other Office products

We recommend that you uninstall any previous versions of Office, including Visio and Project, before installing the newer version. But, in a few cases, such as for application compatibility testing, you might need to keep a previous version installed for a limited time while you transition to the new version.

To keep a particular Office product, you add an IgnoreProduct line to your configuration.xml file and you specify its product ID.

The following are examples of supported IDs for Project and Visio:

PrjStd
PrjPro
VisStd
VisPro
PrjStdR
PrjProR
VisStdR
VisProR

Note

The product ID is the Setup ID that is found in the Setup.xml file in the {product}.WW folder of the installation files for your previous version of Office. For example, the Setup.xml file for Office Professional Plus 2010 is found in the ProPlus.WW folder.

The ID isn't version specific. All versions found on the computer will be kept. For example, if you specify VisPro, both Visio Professional 2016 and Visio Professional 2013 will be kept. Language resources for those versions are also kept. For example, language packs, language interface packs, or proofing tools.

Only full product removals are supported. For example, if you have Office Professional Plus 2013 installed, you can't uninstall everything except Excel. You either must keep or uninstall the entire product. You can only keep a previous installation of Excel if it was installed as a standalone product, not installed as part of an Office suite, like Office Professional Plus.

Here’s an example of a configuration.xml file that installs the 64-bit Monthly Enterprise Channel version of Microsoft 365 Apps for enterprise in English from the Office Content Delivery Network (CDN) on the internet and uninstalls any Windows Installer (MSI) versions of Office, except for Visio Professional, on the computer.

Other products that can be removed

Installations of the following products will also be removed by using the RemoveMSI element unless you use IgnoreProduct:

SharePoint Designer. The product ID is SharePointDesigner.
InfoPath. The product ID is either InfoPath (for volume licensed versions) or InfoPathR (for retail versions).
Lync 2013 or later. Note that Lync 2010 can't be removed by using the RemoveMSI element.
Office products that were installed separately and not as part of an Office suite. For example, a standalone installation of Access.
Access 2010 Runtime or later. The product ID is AccessRT.
Access Database Engine 2010 Redistributable or later. The product ID is AceRedist.

Ms Office 2010 Setup File

Note

Access Database Engine is most commonly included as part of other applications which are interacting with Access data sources, and uninstalling Access Database Engine could impact functionality of these applications. Before removing Access Database Engine, ensure that any applications which require this component are removed or no longer needed.