Microsoft Office 365 For Mac Installer Removal Tool
- Microsoft Office 365 For Mac Installer Removal Tool Download
- Installing Microsoft 365 On Mac
- Microsoft Office 365 Installer Download
- Microsoft Office 365 For Mac Installer Removal Tool Windows 10
These instructions may help with troubleshooting activation by removing all Office license files from your Mac. For example, if you previously installed a one-time purchase of Office for Mac and have switched to Office 365, you may not be seeing subscription features because your copy of Office is still using your old license. Aug 22, 2019 We recommend that you uninstall any previous versions of Office before installing Office 365 ProPlus. 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. Mar 10, 2020 No matter what kind of situation you are facing, there's an answer to every problem. We will show you how to properly uninstall all apps and features of Office 365 on Mac manually. An official Office removal tool is offered by Microsoft to the users of the Windows Operating System.
Important
Office 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise. To learn more about this name change, read this blog post.
For details of when this change takes effect, and what actions admins might need to take, read this article.
The Office Customization Tool creates the configuration files that are used to deploy Office in large organizations. These configuration files give you more control over an Office installation: you can define which applications and languages are installed, how those applications should be updated, and application preferences. After creating the configuration files, you can use them with the Office Deployment Tool to deploy a customized version of Office.
Note
The Office Customization Tool is part of the deployment process for installing Office on hundreds or thousands of computers. To follow this process end-to-end, we recommend completing the assessment and planning phases for your Office deployment. If you're not an enterprise administrator and are looking to install Office 365 in your home or business, see Install Office with Office 365.
Get started
To work with the service, go to Office Customization Tool and choose the products, languages, and application preferences you want to configure. For example, you can create a configuration file that downloads the 64-bit English version of Office 365 ProPlus, or you can create a file that installs the 64-bit English and German version of Office without Access and Publisher and with the EULA automatically accepted. When you're done, you export the configuration file, which you can then use with the Office Deployment Tool or another software distribution solution to deploy Office in your organization.
Note
If you use Microsoft Endpoint Configuration Manager (current branch) to deploy Office, we recommend using the Office 365 Installer wizard in the Configuration Manager console. That wizard includes a customized version of the Office Customization Tool. For more details, see Deploy Office 365 ProPlus with Microsoft Endpoint Configuration Manager (current branch).
Create a configuration file
Follow these steps to create a configuration file that can be used by the Office Deployment Tool or another software distribution solution to install Office.
Note
We recommend saving and managing your configuration files in the cloud. To do so, sign in to the Office 365 Client Configuration Service before you create your configuration file. For more details, see Save and manage configuration files in the cloud.
- Go to Office Customization Tool.
- In the Product and releases section, choose the architecture you want to deploy. Each configuration file can only deploy one architecture. For details on which architecture to choose, see Choose the 32-bit or 64-bit version of Office.
- Choose the products and applications you want to deploy.
- Choose the update channel you want to deploy. The update channel determines how frequently your client devices are updated with new features. For best practice recommendations, see Step 3 - Choose your update channels.
- Choose which version you want to deploy. Unless you require a particular version, we recommend choosing the latest. For details on previous versions, see Update history for Office 365 ProPlus.
- In the Language section, choose which languages to include. You can include multiple languages and you can select Match operating system to automatically install the same languages that are in use on the client device. For more details, see Overview of deploying languages in Office 365 ProPlus.
- In the Installation section, choose whether to install the Office files directly from the cloud or from a local source on your network. For more details, see Choose how to deploy.
- Choose whether to display the installation to your end users and whether to pin the Office icons to the taskbar. For more details on these options, see Display element and PinIconsToTaskBar property.
- In the Update and upgrade section, choose whether to install updates directly from the cloud, from a local source on your network, or with Configuration Manager. If you want to update your client devices automatically, choose CDN and Automatically check for updates. For best practice recommendations, see Choose your update channels.
- Choose whether to automatically remove all MSI-versions of Office, and whether to automatically install the same language as the removed MSI-version of Office. For more details, see Install the same languages as a previous MSI installation.
- If you are deploying a volume-licensed version of Office, Visio, or Project, specify the appropriate license key in Licensing and activation settings. Note that Office 365 ProPlus is not volume licensed and does not require a KMS or MAK activation. For more details, see Overview of volume activation of Office.
- In the General section, type your organization name and a description for this particular configuration. For example, you might want to use this file to install the 64-bit version of Office for your finance department.
- Choose whether to automatically accept the EULA.
- Choose whether to enabled shared computer activation. For more details, see Overview of shared computer activation for Office 365 ProPlus.
- In the Application preferences section, choose what preferences to apply when deploying Office. You can search for a setting, filter the preferences by Office app, and learn more about each setting by clicking it and reviewing the detailed description.
- Click Finish, review the configured settings in the right-hand pane, and then click Export.
- Accept the terms in the license agreement, name the configuration file, and then click Export or, if you're saving the configuration file to the cloud, click Done.
- You can now use the configuration file in your deployment workflow with the Office Deployment Tool or another software distribution solution.
Edit an existing configuration file
Follow these steps to import and edit an existing configuration file.
- Go to Office Customization Tool.
- Click Import, and then select the configuration file you want to edit.
- Change the settings you want, and then export the updated file.
Save and manage configuration files in the cloud
You can now use the Office Customization Tool to create, save, and manage your deployment configuration files in the cloud. You can also refer to these cloud-based files directly when running the Office Deployment Tool.
To work with configuration files in the cloud, sign in to the Office 365 Client Configuration Service and go to the Device Configuration page. From that page, you can do the following:
- To create a new file, click Create, create a configuration file, and then click Done. The configuration file is automatically saved to the cloud as part of your tenant.
- To edit an existing file, click the name of the file, make your changes, and then click Done.
- To get a link to a configuration file, select the file, click Get Link, and then click Copy. You can use the link to refer to the configuration file when you use the Office Deployment Tool.
When running the Office Deployment Tool, you refer to the cloud-based configuration file by including the link in quotes. To deploy with the ODT, for example, use setup.exe /configure 'link'.
You can also copy, upload, or download configuration files from the Device Configuration page. For example, you can create a baseline configuration file and then create copies of that baseline for custom configurations.
Define application preferences
As part of the Office Customization Tool, you can define application preferences for supported products, including VBA macro notifications, default file locations, and default file formats. When you define these preferences, you can apply them as part of deploying Office or you can apply them to an existing installation of Office without changing any other deployment settings. For more details, see Apply application preferences and Apply application preferences to an existing installation of Office.
Notes
When creating a configuration file, the Office Customization Tool includes two attributes for the Configuration element: The ID attribute, which identifies the deployment method, and the Host attribute, which identifies the deployment options that have been selected. These attributes don't contain any personally identifiable information (PII), but Click-to-Run sends the attribute values to Microsoft so that we can better understand what configurations customers use and make customization even easier. Because of these insights, we recommend keeping the attributes. They are optional, however, and can be removed without affecting your deployment.
-->We recommend that you uninstall any previous versions of Office before installing Office 365 ProPlus. 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 Office 365 ProPlus.
- 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 2010, 2013, or 2016 versions of Office, Visio, or Project that were installed using Windows Installer (MSI).
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.10306.33602 of the Office Deployment Tool, which you can download from Microsoft Download Center. 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 Office 365 ProPlus. Version 1803 or later is available in Monthly Channel, Semi-Annual Channel (Targeted), and Semi-Annual Channel.
- You must be installing Office 365 ProPlus on a computer running at least Windows 7 Service Pack 1 (SP1) or above.
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.
You can also open, edit and save Microsoft Word, Excel and PowerPoint files with these apps, so you can easily work with others, regardless of whether they’re on a Mac or PC. Are microsoft office documents compatible between windows and mac. A Mac can even run Windows.Got a Windows application you need to use once in a while?
Here’s an example of a configuration.xml file that installs the 64-bit Monthly Channel version of Office 365 ProPlus 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 Office 365 ProPlus. To do this, add <Language /> to your configuration.xml file.
Here’s an example of a configuration.xml file that installs the 64-bit Semi-Annual Channel (Targeted) version of Office 365 ProPlus 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 Office 365 ProPlus.
Important
If you’re installing Office 365 ProPlus 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 fail and the previous version of Office will have been removed. 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
Microsoft Office 365 For Mac Installer Removal Tool Download
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 Semi-Annual Channel (Targeted) version of Office 365 ProPlus 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.
Installing Microsoft 365 On Mac
Additional information about using RemoveMSI
Microsoft Office 365 Installer Download
The following are some additional details about using the RemoveMSI element in your configuration.xml file.
- You can also use these settings if you’re installing any of the following:
- Project Online Desktop Client
- Visio Online Plan 2, which is the subscription version of Visio that was previously named Visio Pro for Office 365.
- Office 365 Business, which is the version of Office that comes with some Office 365 plans, such as Business Premium.
- A volume licensed version of Office 2019, such as Office Professional Plus 2019.
- Installations of the following products will also be removed 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. 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 can’t be removed by using the RemoveMSI element. This is because 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.
- User settings, preferences, and documents are retained, even if you’re uninstalling all Office products.
- Some previous versions of Office, Visio, and Project must be uninstalled before installing Office 365 ProPlus. For example, Office Professional Plus 2016. If they aren’t uninstalled beforehand, the installation of Office 365 ProPlus will fail. For more information, see Supported scenarios for installing different versions of Office, Visio, and Project on the same computer.
- A reboot is required to finish uninstalling the Windows Installer (MSI) versions of Office, but the reboot isn’t enforced. You can reboot after the Office 365 ProPlus installation is finished.
- 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.
- If you're using RemoveMSI on a Windows 7 SP1 computer, pinned shortcuts that the user created might sometimes remain even though the previous version of Office and all of its other shortcuts have been removed. To remove the pinned shortcut, simply click on it and you'll be prompted to remove it. Or, log in as the user who created the pinned shortcut, and then run the Office Deployment Tool to upgrade to Office 365 ProPlus.