none
SCCM 2002 and Office 2019 Deployment issue RRS feed

  • Question

  • Hi,

    If I deploy Office 2019 using my SCCM 2002, sometimes works and sometimes not. If I check the log file AppEnforce.lg, I see there the following entry

        Unmatched exit code (2147972488) is considered an execution failure.

    On the same machine I get the above error message I can run manually the command for Office 2019 and it works fine.

    My command is called:

    setup.exe /configure config.xml

    my config.xml:

    <Configuration>
    <Add SourcePath="\\sccm\Applications\Office2019\" OfficeClientEdition="32" >
    <Product ID="ProPlus2019Retail" PIDKEY="my key" >
    <Language ID="en-us" />
                <ExcludeApp ID="Groove"/>
                <ExcludeApp ID="Lync"/>
                <ExcludeApp ID="OneDrive"/>
                <ExcludeApp ID="OneNote"/>
                <ExcludeApp ID="Outlook"/>
                <ExcludeApp ID="PowerPoint"/>
                <ExcludeApp ID="Publisher"/>

    </Product>
    </Add>
    <RemoveMSI All="True" />
    <Display Level="None" AcceptEULA="TRUE" />
    <Property Name="AUTOACTIVATE" Value="1" />
    </Configuration>

    Can anybody tell what is here wrong?

    Regards

    Nick

    Thursday, June 25, 2020 1:46 PM

All replies

  • Hi Nick,

    Thanks for posting in TechNet.

    May we know which Install Behavior you are using, Install for user or Install for system? If you are using Install for system, can it successfully access the path \\sccm\Applications\Office2019\? If possible, change it to Install for user to have a try. 

    Thanks for your time.

    Best regards,
    Simon

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, June 26, 2020 9:44 AM
  • Hi Simon,

    I am using install for system

    As I mention, sometimes works fine and sometimes I am getting the above error message

    Regards

    Nick

    Friday, June 26, 2020 10:28 AM
  • Hi,

    Thanks for your information. Maybe the system context of problematic devices has no access to the source path. Please use the Install for user option and redeploy it to have a try.

    Best regards,
    Simon

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, June 29, 2020 2:58 AM