My office installation was deployed via the ODT and the below configuration file.  I see version 15.0.4719.1002 was released on 5/12 and my users are still running 15.0.4711.1003.     If I update manually from within office it works just fine, but I need these clients to update on their own.  The PC's are rebooted daily.

I am also noticing that the Office Automatic Updates task in Task scheduler shows Queued.

Any ideas why my PC's are not updating?

XML File:

<Configuration>
 <Add SourcePath="(INTERNAL SERVER PATH)" OfficeClientEdition="32" >
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us"/>
<ExcludeApp ID="Access" />
<ExcludeApp ID="InfoPath" />
<ExcludeApp ID="Groove" />
    </Product>
  </Add>

  <Updates Enabled="TRUE" />
  <Display Level="Full" AcceptEULA="TRUE" />
  <Logging Path="%temp%" />
  <!--  <Property Name="AUTOACTIVATE" Value="1" />  -->
</Configuration>

Hi,

Based on the introduction in Choose how to apply updates to Office 365 ProPlus, there are three ways that admins typically apply updates for Office 365 ProPlus:

• Automatically from the Internet

• Automatically from an on-premises location

• By installing an updated version of Office 365 ProPlus

You seem to have chosen the second method. Then we can refer to this blog below:

Managing Updates for Office 365 ProPlus Part 2

There is a sample of Contents of Production.xml

<Configuration>

  <Add OfficeClientEdition="32" >

      <Product ID="O365ProPlusRetail">

        <Language ID="en-us" />

      </Product>

  </Add>
<Updates Enabled="TRUE" UpdatePath="\\MyServer\Updates\Production" />

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

<Logging Name="OfficeSetup.txt" Path="%temp%" />

</Configuration>

There is an "UpdatePath" in the sample while in your post it's missing.

Please also refer to the Step 4: Update the testing source every patch Tuesday, using a scheduled task on a single workstation, create a recurring task that runs the Office Deployment Tool using the /download switch.

Regards,

Melon Chen
TechNet Community Su

According to this technet article if you do not have the Updates element enabled then the click to run installation performs zero updates, regardless if it is pulling from the Microsoft cloud or an internal update path.    Additionally if you do not have the UPDATE PATH value set then  " If UpdatePath is not set, Click-to-Run installations obtain updates from the Microsoft Click-to-Run source (Content Delivery Network or CDN). This is by default."  I take this to be it will pull from the Microsoft cloud if the update path URL is not set.  I spoke to MS support and was told that you leave out the update path URL in your XML file then the updates are pulled from the Microsoft cloud.    Maybe this was bad information.

I have performed a manually update on my internal source and will check to see if my client start to update. I will follow up in a couple of days.

Joshua

Hi,

You are right, if you don't specify the updates will be pulled from the Microsoft directly.

How is everything going now?

Regards,

Melon Chen
TechNet Community Su

Since updating the source all clients are now updating on their own.  

All clients eventually auto-updated over the course of 3-4 days.  

Thank you for your assistance.

• Marked as answer by Melon Chen CHNMicrosoft contingent staff, Moderator 6 hours 59 minutes ago