microsoft Office Customization Tool .xml worked on one machine and no more, why?

TIPSWORD Brian * OMD 1 Reputation point

Hi All,

I'm very new to this and am wondering what I might have done incorrectly. I went through the steps in the microsoft Office Customization Tool to create an .XML to install the 2019 standard we paid for.

It appears to have worked fine on my first machine, but the other two I tried this on failed.

Here is the config (key redacted):

<Configuration ID="f157b97d-7690-4de1-8eb9-eae05b14b8ea">
<Info Description="Oregon Office of Emergency Management - O2019 Standard install" />
<Add OfficeClientEdition="64" Channel="PerpetualVL2019">
<Language ID="en-us" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="OneDrive" />
<Property Name="SharedComputerLicensing" Value="0" />
<Property Name="SCLCacheOverride" Value="0" />
<Property Name="AUTOACTIVATE" Value="0" />
<Property Name="FORCEAPPSHUTDOWN" Value="FALSE" />
<Property Name="DeviceBasedLicensing" Value="0" />
<Updates Enabled="TRUE" />
<IgnoreProduct ID="VisPro" />
<IgnoreProduct ID="VisStd" />
<Setup Name="Company" Value="OEM" />
<User Key="software\microsoft\office\16.0\excel\options" Name="defaultformat" Value="51" Type="REG_DWORD" App="excel16" Id="L_SaveExcelfilesas" />
<User Key="software\microsoft\office\16.0\powerpoint\options" Name="defaultformat" Value="27" Type="REG_DWORD" App="ppt16" Id="L_SavePowerPointfilesas" />
<User Key="software\microsoft\office\16.0\word\options" Name="defaultformat" Value="" Type="REG_SZ" App="word16" Id="L_SaveWordfilesas" />

Office Management
Office Management
Office: A suite of Microsoft productivity software that supports common business tasks, including word processing, email, presentations, and data management and analysis.Management: The act or process of organizing, handling, directing or controlling something.
1,993 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Emily Hua-MSFT 27,521 Reputation points

    @TIPSWORD Brian * OMD

    It appears to have worked fine on my first machine, but the other two I tried this on failed.

    Is there any error message/code if the Office Standard 2019 installation failed?
    On my clean test environment, I could install Office Standard 2019 successfully with your configuration file.

    Please ensure you have used administrator permission to install Office on these 2 machines.

    Besides, were there the Visio, especially volume licensed versions of Visio 2016 installed on these two machines before?

    If yes, please note, Office 2019 use the Click-To-Run installation technology, according to the article "Supported scenarios for installing different versions of Office, Project, and Visio on the same computer", if you want to install Office 2019 with volume licensed versions of Visio 2016, you need to use the Office Deployment Tool to install it.

    So, it's recommended to use <RemoveMSI /> replace the part of <RemoveMSI> <IgnoreProduct ID="VisPro" /> <IgnoreProduct ID="VisStd" /> </RemoveMSI> to uninstall volume licensed versions of Visio 2016 first.

    Any questions you may let me know.

    If an Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. TIPSWORD Brian * OMD 1 Reputation point

    Visio is not supposed to be included in this install. This is purely Office 2019 standard.

    See attached .jpg for a screenshot of the error message

    Thank you for taking the time to respond to my question,

  3. DingoDigits-2736 1 Reputation point

    In case this helps someone in the future.

    I had the same issue and error message. In my experience, this error is most always a sign of a syntax error.

    After a long rage against Microsoft for creating an Office Configuration Tool that doesn't provide logging to troubleshoot their half-baked Tool - I found the issue was a missing slash - as in:

    <RemoveMSI >

    . Once I correct this to

    <RemoveMSI />

    Everything worked, no error message.

    Double check every line for syntax.

    Seems Microsoft gave the creation of the Office Configuration Tool to some summer intern and forgot to make it truly helpful.

    0 comments No comments