Windows 10: Custom install or change Microsoft Office with Office Deployment Tool

How to: Custom install or change Microsoft Office with Office Deployment Tool


Information In earlier versions of Microsoft Office, users could select Install options and customize the installation by installing only selected Office applications, or select an application to be installed on first use, or completely disable an application. Later on, this could be changed, other Office applications installed or disabled.

In Office 2016 and later, including Office 365, this is no longer possible. Full Office suite of applications will be installed, be it an MSI installation from ISO or Click-to-Run installation, and it is no longer possible to remove or add individual Office applications.

The Office Deployment Tool (ODT) is a command-line tool that you can use to deploy (install) Office to your computers. Using ODT, you can select which Office suite applications will be installed or removed. You can also add or remove additional languages and edit various options.

ODT needs a configuration script (XML file), which can be created with Office Customization Tool or manually.

This tutorial will show how to create or modify a configuration script and use it with ODT to custom install Office or modify an existing installation.




Contents [/i] Click links to jump to any part [table][tr][td]Part One:[/td] [td]Microsoft Office Editions[/td] [/tr] [tr][td]Part Two:[/td] [td]Configure install options with Office Customization Tool[/td] [/tr] [tr][td]Part Three:[/td] [td]Configure and edit install options manually[/td] [/tr] [tr][td]Part Four:[/td] [td]Run Setup to install Office[/td] [/tr] [tr][td]Part Five:[/td] [td]Change existing Office installation[/td] [/tr] [/table]

Please notice: screenshots can be expanded by clicking them.


Part One [/i] Microsoft Office Editions
1.1) To use ODT, configuration script requires information about which edition (Product ID) to install. Installing wrong edition might make activating Office impossible.

Always use the correct Product ID corresponding with your O365 subscription plan, product key or volume license.

1.2) Table of editions. In Activation column available activation methods for each edition:

• P = Retail product key
• S = O365 Personal, Home, Business or Enterprise subscription / license
• V = Volume licensing (KMS or MAK)

[table][tr][td]Edition[/td] [td]Product ID[/td] [td]Activation[/td] [/tr] [tr][td]O365 Home and Student[/td] [td]HomeStudentRetail[/td] [td]P[/td] [/tr] [tr][td]O365 Home and Business[/td] [td]HomeBusinessRetail[/td] [td]P[/td] [/tr] [tr][td]Office 2016 Personal[/td] [td]PersonalRetail[/td] [td]P[/td] [/tr] [tr][td]O365 Personal[/td] [td]O365PersonalRetail[/td] [td]S[/td] [/tr] [tr][td]O365 Home[/td] [td]O365HomePremRetail[/td] [td]S[/td] [/tr] [tr][td]O365 ProPlus[/td] [td]O365ProPlusRetail[/td] [td]V[/td] [/tr] [tr][td]O365 Enterprise E3, E4, E5[/td] [td]O365ProPlusRetail[/td] [td]S V[/td] [/tr] [tr][td]O365 Business[/td] [td]O365BusinessRetail[/td] [td]S[/td] [/tr] [tr][td]O365 Business Premium[/td] [td]O365BusinessRetail[/td] [td]S[/td] [/tr] [tr][td]O365 Small Business Premium[/td] [td]O365SmallBusinessRetail[/td] [td]S[/td] [/tr] [tr][td]O365 ProPlus 2019 VL[/td] [td]ProPlus2019Volume[/td] [td]V[/td] [/tr] [tr][td]O365 Standard 2019 VL[/td] [td]Standard2019Volume[/td] [td]V[/td] [/tr] [tr][td]Office 2019 Home & Student[/td] [td]HomeStudent2019Retail[/td] [td]P[/td] [/tr] [tr][td]Office 2019 Home & Business[/td] [td]HomeBusiness2019Retail[/td] [td]P[/td] [/tr] [tr][td]Office 2019 Personal[/td] [td]Personal2019Retail[/td] [td]P[/td] [/tr] [tr][td]Office 2019 Professional[/td] [td]Professional2019Retail[/td] [td]P[/td] [/tr] [tr][td]Office 2019 ProPlus[/td] [td]ProPlus2019Retail[/td] [td]P[/td] [/tr] [/table]




Part Two [/i] Configure install options with Office Customization Tool
2.1) Using ODT requires a configuration file in XML format. When setup is run, it reads installation options from this file. Office Customization Tool is a web based application to create ODT configuration files with a few mouse clicks.

2.2) Go to Office Configuration Tool


Note EDIT MAY 2019:

Microsoft has changed the Office Configuration Tool sign-in requirements, using a Microsoft account is no longer possible. Sign-in now requires an Azure AD account (so called work or school account).




If you do not have a valid Azure AD account, please post in this tutorial thread telling the exact Office version and edition you have (see Microsoft Docs) or want to install, and which Office applications you want to include in installation, which to exclude.

I will then make the configuration script for you.
2.3) Expand Products and releases:




2.4) Select bit architecture (#1), Office edition from Office Suites (#2), which Office applications you want to install and which to exclude (#3), your preferred update channel (#4), and which version you want to install (#5):






Note Edition selection (#2 in screenshot):

• Office Customization tool lets you choose O365 ProPlus, O365 Business, Office 2019 Standard VL or Office 2019 ProPlus VL edition.
• If you are installing any other edition, select O365 ProPlus and edit configuration script in Notepad when configuration file is ready and downloaded to change edition product ID to correct one. See step 3.3 about how to edit configuration script.

Excluded applications (#3 in screenshot):

• Business and ProPlus editions, exclude OneDrive Desktop. OneDrive is built-in and preinstalled in Windows 10 and does not need to be installed with Office.
• OneDrive (Groove) is SharePoint. Exclude if not required.
• If your organization has already switched to Microsoft Teams, exclude Skype for Business.

Channel selection (#4 in screenshot):

• Monthly Targeted = Office Insider, weekly updates, shown as Channel="Insiders" in script
• Monthly = Monthly updates, shown as Channel="Monthly" in script
• Semi-Annual = Updated twice a year, in January and July, shown as Channel="Broad" in script
• Semi-Annual Targeted = Preview of Targeted, twice a year March and September, shown as Channel="Targeted" in script

2.5) Click Next or expand Language . Select the primary installation language, and additional languages you want to install. In additional languages you can select Full to install a complete language pack. If a full language pack is not available in your language, select Partial to see list of partially translated languages. Proofing shows you languages which do not have a full or partial language pack but with Office proofing tools available.

In this example, I selected English as primary language, and Finnish, Swedish and German language packs.




2.6) Click Next or expand Installation. Select from where Office will be installed. Office Content Delivery Network (CDN) always downloads Office installation files from cloud (recommended, no source path required), Local source downloads Office setup files to a network share or local folder, and installation is run from this folder. The share or folder must exist when setup is run.

In case you select Local source, setup checks what content is already available on given share or folder, and only downloads what is missing. When setup is run first time, content not excluded in configuration script will be downloaded and saved on given Source path. This saves time and bandwidth in case you have multiple computers; use a network share as Source path, download is only done once and Office can be deployed from that share to all computers.

The same if you want to modify existing Office installation. Let's say I originally installed Finnish Office, excluding Access and Publisher. Now I want to add Swedish language pack, Access and Publisher to my existing installation. As setup already finds downloaded Office core and most of the applications from my source, a network share, it only needs to download those components I added.




Turn Show installation to user off if you want no information or progress bars about running installation shown to user. I recommend always turning it ON.

2.7) Click Next or expand Update and upgrade. Select if you want future updates and upgrades being installed from CDN or local source (see 2.6 for difference). Turn automatic updates on or off, select if you want any possible remnants from earlier MSI installation removed before installing Click-to-Run version of Office:




2.8) Click Next or expand Licensing and activation. In case you selected a volume licensed edition of Office in step 2.4, select your volume licencing method. For all editions, select Automatically accept the EULA. Do not turn Autoactivate on:




2.9) Click Next or expand General. This step is optional, but if you want to you can add your name or name of an organization and remarks to be saved in configuration file:




2.10 Click Next or expand Application preferences. This step is optional, you can pre-set a lot of general Office preferences here if you so prefer.

Click a preference to change it, and set the value as you want to:




A pop-up opens to let you change preferences:




2.11) All done. You can now export (download) the configuration file:




2.12) In this example, I created a configuration script to install O365 ProPlus, excluding OneDrive, Publisher and Skype for Business (shown as "Lync" in script). Primary language is US English, additional languages Finnish, Swedish and German, Monthly update channel. No set up progress shown to user:
PHP Code: <Configuration>
<Info Description="This configuration file will install 32-bit O365 ProPlus. Excluded applications: OneDrive, SharePoint (Groove), Publisher and Skype for Business (Lync). " />
<Add OfficeClientEdition="32" Channel="Monthly" AllowCdnFallback="TRUE" ForceUpgrade="TRUE">
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
<Language ID="fi-fi" />
<Language ID="de-de" />
<Language ID="sv-se" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="OneDrive" />
<ExcludeApp ID="Lync" />
<ExcludeApp ID="Publisher" />
</Product>
</Add>
<Property Name="SharedComputerLicensing" Value="0" />
<Property Name="PinIconsToTaskbar" Value="TRUE" />
<Property Name="SCLCacheOverride" Value="0" />
<Updates Enabled="TRUE" />
<RemoveMSI All="TRUE" />
<AppSettings>
<Setup Name="Company" Value="Ten Forums" />
<User Key="software\microsoft\office\16.0\common\toolbars" Name="screentipscheme" Value="0" Type="REG_DWORD" App="office16" Id="L_ShowScreenTips" />
</AppSettings>
</Configuration>

Another sample script to install 32-bit O365 Home in English, no additional languages. Update channel Semi-Annual, automatic updates turned off, setup progress shown to user and EULA automatically accepted. Office setup files will be downloaded to network share \\W10PC\OfficeSetup and Office installed from there:

PHP Code: <Configuration>
<Add OfficeClientEdition="32" Channel="Broad" SourcePath="\\W10PC\OfficeSetup" AllowCdnFallback="TRUE" ForceUpgrade="TRUE">
<Product ID="O365HomePremRetail">
<Language ID="en-us" />
</Product>
</Add>
<Property Name="SharedComputerLicensing" Value="0" />
<Property Name="PinIconsToTaskbar" Value="TRUE" />
<Property Name="SCLCacheOverride" Value="0" />
<Updates Enabled="FALSE" />
<AppSettings>
<Setup Name="Company" Value="Ten Forums" />
</AppSettings>
<Display Level="Full" AcceptEULA="TRUE" />
</Configuration>

Notice that Semi-Annual channel is shown as "Broad" in script above. Monthly Targeted will show as "Insiders", Monthly as "Monthly", and Semi-Annual Targeted as "Targeted".



Part Three [/i] Configure and edit install options manually
3.1) The configuration XML files can be created and edited manually. Sample files in step 2.12 are a good base, showing some most common options. See full list of options and commands: Configuration options for the Office Deployment Tool | Microsoft Docs

3.2) Configuration file can be created in any text editor and named as you prefer. It must be saved as an XML file with extension .xml

3.3) See the second of sample script in step 2.12. As Office Customization Tool did not allow me to select O365 Home edition, I used O365 ProPlus instead when creating the script, therefore the Product ID when I exported the script to my PC was <Product ID="O365ProPlusRetail">. I changed this manually in Notepad to <Product ID="O365HomePremRetail">.

I also edited the script to exclude Publisher, change install source from network share to cloud (CDN), to change update channel to Monthly, and to add Finnish language pack.

This is the original configuration script I exported (downloaded) from Office Customization Tool:

PHP Code: <Configuration>
<Add OfficeClientEdition="32" Channel="Broad" SourcePath="\\W10PC\OfficeSetup" AllowCdnFallback="TRUE" ForceUpgrade="TRUE">
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
<Property Name="SharedComputerLicensing" Value="0" />
<Property Name="PinIconsToTaskbar" Value="TRUE" />
<Property Name="SCLCacheOverride" Value="0" />
<Updates Enabled="FALSE" />
<AppSettings>
<Setup Name="Company" Value="Ten Forums" />
</AppSettings>
<Display Level="Full" AcceptEULA="TRUE" />
</Configuration>

And here the same after my manual edits:

PHP Code: <Configuration>
<Add OfficeClientEdition="32" Channel="Monthly" AllowCdnFallback="TRUE" ForceUpgrade="TRUE">
<Product ID="O365HomePremRetail">
<Language ID="en-us" />
<Language ID="fi-fi" />
<ExcludeApp ID="Publisher" />
</Product>
</Add>
<Property Name="SharedComputerLicensing" Value="0" />
<Property Name="PinIconsToTaskbar" Value="TRUE" />
<Property Name="SCLCacheOverride" Value="0" />
<Updates Enabled="FALSE" />
<AppSettings>
<Setup Name="Company" Value="Ten Forums" />
</AppSettings>
<Display Level="Full" AcceptEULA="TRUE" />
</Configuration>




Part Four [/i] Run Setup to install Office
4.1) Download ODT:

Download

4.2) Create a folder on root of C: drive, name it as O365 (suggestion, you can name the folder as you prefer).

4.3) Unblock (tutorial) the downloaded EXE file, then run it. The file name is officedeploymenttool_12345-67890.exe, where 12345-67890 is current version number. At the moment of writing this, the ODT version is 11107-33602.

4.4) Accept the license, click Continue:




4.5) To extract ODT, select the folder you created in step 4.2 and click OK:




4.6) Copy your XML configuration file to same folder.

4.7) Open an elevated Command Prompt, move to O365 folder with following command:

cd \O365

4.8) If you selected cloud (CDN) as source in step 2.6, enter following command:

setup.exe /configure YourConfigurationFile.xml




4.9) Office will be installed as configured in configuration script.

4.10) If you selected a local folder or network share as Source path in step 2.6, Office setup files need to be downloaded first once with following command:

setup.exe /download YourConfigurationFile.xml

4.11) When downloaded, you can install Office from your local source with command in step 4.8

Notice that when installing from network share, ODT must be run on the computer on which you want to install Office. However, the configuration file and Source path for downloaded Office setup files can be located on a network share.

To download:

setup.exe /download \\ServerName\O365Share\YourConfigurationFile.xml

To install:

setup.exe /configure \\ServerName\O365Share\YourConfigurationFile.xml



Part Five [/i] Change existing Office installation
5.1) You can change your existing Office installation whenever you want to. You can create a new script, or edit existing as told in step 3.3

5.2) Run the modified script with /configure switch as shown in step 4.8 or step 4.11, depending on if the configuration script is saved locally or on network share.

5.3) Office installation will be modified, features removed or added as told in configuration file.
That's it, geeks!



Note Depending on selected options, using ODT to install or modify Office can be confusing because sometimes no indicator about progress is shown.

Even if you can see no progress, keep Command Prompt running until setup is ready, until you can see that Office Setup has finished running. Cursor shown under your command on column 1, setup is still running, either downloading or installing Office:




Setup ready, a prompt will be shown:




Kari

:)

 

Custom install or change Microsoft Office with Office Deployment Tool  

OK, tested. No issues.

Running the script, exactly the same script I posted for you, the install screen shows that only the selected apps (Word, Excel, PowerPoint, Outlook) will be installed:




Installation done:




I run an Office application, in my example case now Word, and sign in with my O365 Home account when the following screen is shown:




… and check the account status:




One more check, I will use Office License Management Tool (see this post) to check O365 license status. It shows my Office installation is licenced, and that the installed Office edition is Office Home Premium:



(Click to enlarge.)

I repeated the test on one virtual and two physical computers. Script worked, all O365 installations were activated and licenced.

I cannot explain why you have activation issues.

 

Office 2019

Only supported on Win10. Sorry, 8.1 users, only 4 years old, gotta go.

Microsoft Office 2019 will only work on Windows 10

https://blogs.technet.microsoft.com...-to-office-and-windows-servicing-and-support/

Spoiler Office 2019
Last year at Ignite, we announced Office 2019 – the next perpetual version of Office that includes apps (including Word, Excel, PowerPoint, and Outlook, and Skype for Business) and servers (including Exchange, SharePoint, and Skype for Business). Today we’re pleased to share the following updates:

• Office 2019 will ship in H2 of 2018. Previews of the new apps and servers will start shipping in the second quarter of 2018.
• Office 2019 apps will be supported on:
  • Any supported Windows 10 SAC release
  • Windows 10 Enterprise LTSC 2018
  • The next LTSC release of Windows Server
• The Office 2019 client apps will be released with Click-to-Run installation technology only. We will not provide MSI as a deployment methodology for Office 2019 clients. We will continue to provide MSI for Office Server products.

 

Customizing Outlook settings in Office 2019

Our company is looking to replacing the soon to be EOL office 2010 with Office 2019 so I was following the tutorial available here (Custom install or change Microsoft Office with Office Deployment Tool) and using the Office Customization tool website on how to setup MAK, choose office program to install etc.

The question is is it possible to pre-setup the outlook 2019 portion like back in office 2010 so it will auto create the exchange account based on logged in username & OST during first launch?

 

Help With Office 2013 Install

Our IT department sent a note about home use (Office 365, specifically), and this warning:

A suggestion... re-install Office 2010, then try to install 2013?

 

Microsoft Office 2007 Beta 2 arrived

Today Microsoft released the puplic Beta 2 of Office 2007. It's available in English, French, German, Japanese, Spanish. After signing up on windows live, answer some questions, everyone can download the following products:

• Microsoft® Office Professional Plus 2007
• Microsoft® Office Visio® Professional 2007
• Microsoft® Office Outlook® 2007 with Business Contact Manager
• Microsoft® Office Project Server 2007
• Microsoft® Office Project Professional 2007
• Microsoft® Office Groove® 2007
• Microsoft® Office Groove® Server 2007
• Microsoft® Office Multi Language Pack 2007 – French/German/Japanese/Spanish
• Microsoft® Office OneNote® 2007
• Microsoft® Office SharePoint® Designer 2007
• Microsoft® Office SharePoint® Server 2007 - Enterprise
• Microsoft® Office SharePoint® Server 2007 - Enterprise(x64)
• Microsoft® Office Forms Server 2007
• Microsoft® Office Forms Server 2007 (x64)

You can get it here