Share via

OfficeC2RClient.exe /update SCHEDULEDTASK and the 30016-27 error (where /update USER works)

Anonymous
2018-02-13T01:03:53+00:00

Hello

Apologies for having to repost this, given there are a number of older threads concerning this issue, but I cannot seem to find an answer which provides the reason as to why this occurs:

With Microsoft Office 365 ProPlus delivered through Office 2016 Deployment Tool, we are finding that when it comes to updates:

The Microsoft-created scheduled task that runs as SYSTEM fails:

OfficeC2RClient.exe /update SCHEDULEDTASK displaylevel=False

We change this scheduled task, removing silent operation, we see this error returned:

OfficeC2RClient.exe /update SCHEDULEDTASK displaylevel=Full

We change this scheduled task, changing update parameter (task still runs as SYSTEM) and Office will update without issue (both work):

OfficeC2RClient.exe /update USER displaylevel=False

OfficeC2RClient.exe /update USER displaylevel=Full

Test envrionment:

Clean Windows 7 SP1 Professional x64 with IE11 and .NET Framework 4.7.1, fully patched up to 2018-01 Quality Rollup

Single user: Administrator

Standalone machine (not domain-joined)

Office install:

Latest Office 2016 Deployment Tool with following configuration.xml file

<Configuration>

    <Add OfficeClientEdition="32" Channel="Broad" Version="16.0.8201.2217">

        <Product ID="O365ProPlusRetail">

            <Language ID="en-us"/>

            <ExcludeApp ID="Groove"/>

            <ExcludeApp ID="OneDrive"/>

        </Product>

    </Add>

    <Display Level="None" AcceptEULA="TRUE"/>

</Configuration>

Expected result:

  1. Office 365 ProPlus x86 1705 Build 16.0.8201.2217 will be installed
  2. Require end-user to activate application using valid Microsoft Account with Office 365 subscription
  3. Office applications will keep up-to-date via MS Semi-Annual Channel (will automatically update to 1708 (Build: 16.0.8431.2153) as of 12 Feb 2018 and will check against MS CDN.

Result:

All above true except the automated scheduled task with SCHEDULEDTASK flag does not work. Will only work either with using the update now menu item in Office

Or running OfficeC2RClient.exe /update USER displaylevel=Full (or displaylevel=False), as described above

Given this information, can anyone explain why the MS Default scheduled task with SCHEDULEDTASK flag, not work?

Thank you in advance for your support

Kind regards

Ivan Hollins

Microsoft 365 and Office | Install, redeem, activate | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
  1. Anonymous
    2018-02-16T00:41:30+00:00

    Hi Rosen

    Upon further analysis,  I have come to the conclusion that I mistakenly attributed the issue of background updates of MS Office 365 failing to update to an incorrect XML configuration file. However, it would seem that the scheduled task will not trigger an update until the value UpdateDiscoveryPeriodStartTime is surpassed...

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Updates

    I checked this through installing Office with a system date of a few weeks back, putting the system clock to automatic time sync and the update task runs without incident, with MSO being brought up-to-date as per defined update channel.

    Pleased I've found the answer, but apologies for leading you down the wrong path.

    Kind regards

    Ivan Hollins

    0 comments

5 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-03-19T09:27:43+00:00

    The UpdateDiscoveryPeriodStartTime registry value on my test computer is 13131683831992. Can someone tell me what this value means?

    0 comments
  2. Anonymous
    2018-02-15T11:21:05+00:00

    Hi Rosen

    Unfortunately, this guide doesn't resolve the issue in my initial post. I note very early on in the article you provided, the following statement.

    https://docs.microsoft.com/en-us/DeployOffice/configure-update-settings-for-office-365-proplus?ui=en-US&rs=en-US&ad=US

    By default, updates for Office 365 ProPlus are downloaded automatically from the Internet and applied in the background, without any user or administrator intervention.

    For completeness, I did add the following XML node to the config file, but makes no difference, the issue as per my initial post still occurs.

    <Configuration>

        <Add OfficeClientEdition="32" Channel="Broad" Version="16.0.8201.2217">

            <Product ID="O365ProPlusRetail">

                <Language ID="en-us" />

                <ExcludeApp ID="Groove" />

                <ExcludeApp ID="OneDrive" />

            </Product>

        </Add>

        <Display Level="None" AcceptEULA="TRUE" />

    <Updates Channel="Broad" Enabled="TRUE" />

    </Configuration>

    I have something else that I will test, come back with the result, and will advise accordingly.

    0 comments
  3. Anonymous
    2018-02-15T07:03:25+00:00

    Hi Ivan Hollins,

    Do you need more help?

    Regards,

    Rosen

    0 comments
  4. Anonymous
    2018-02-13T10:06:39+00:00

    Hi Ivan Hollins,

    Please make sure you have followed the correct steps mentioned in the following article:

    Configure update settings for Office 365 ProPlus.

    Regards,

    Rosen

    0 comments