Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, September 11, 2018 12:43 PM
I'm struggling getting my Office 2016 install to update without user intervention, or at least it seems to take forever (ok, ~1 week estimate) before they are installed.
I'm using a local share as my update repository and if I manually run the update using the GUI it is 100% fine (confirmed with packet captures it is using my repository), but my users are not being prompted for updates. The scheduled task, which is supposed to initiate at 3am several days per week, doesn't seem to always update even when the user is logged out, or at least I can't find any indication that it has attempted to run. If I remotely initiate the command to run the update on the PC ("C:\Program Files\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe" /Update User displaylevel=False), I see logs in the local app data (see log at bottom).
A few things:
- I must be missing something, can anyone see anything obvious in my policy settings or registry?
- Does the product have to be "licensed" for it to update? I'm primarily curious about this as it affects mass deployments.
- When the update deadline is set, does the program have to be in use periodically for it to work? I ask because I had computers turn on (some without office running, some with) and set the GPO deadline (confirm application via registry check) with a past date for days before some computers actually updated.....but others that had just turned on forced the update immediately.
CrT log in the local appdata folder after sending the command:
Timestamp Process TID Area Category EventID Level Message Correlation
09/11/2018 08:11:19.908 OFFICEC2 (0x1a68) 0x193c Click-To-Run General Telemetry aqkhc Medium InitLogging {"MachineId": "bfb4733c0c55df4fbd4551668864e9ca", "SessionID": "6305cea6-1fa9-44bf-a9ac-58d81d2280a9", "GeoID": 244, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "{\AppVVersion\:\5.0.10348\,\Bitness\:\64\,\CommandLine\:\/Update User displaylevel=False\,\ExeVer\:\16.0.8431.2250\,\IntegrityLevel\:\0x3000\,\Locale\:\1033\,\ModulePath\:\C:\\Program Files\\Common Files\\Microsoft Shared\\ClickToRun\\OfficeC2RClient.exe\,\OSVersion\:\6.1\,\ProcessType\:\OfficeC2RClient\,\ProcessorArch\:\9\,\ProductType\:\1\,\SecuritySessionId\:\0\}"}
09/11/2018 08:11:20.002 OFFICEC2 (0x1a68) 0x193c Click-To-Run General Telemetry bhltg Medium Core::GetFlightData {"MachineId": "bfb4733c0c55df4fbd4551668864e9ca", "SessionID": "6305cea6-1fa9-44bf-a9ac-58d81d2280a9", "GeoID": 244, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "{'flightIdentifier':'Microsoft.Office.Click2Run.DownloadAppVCab','overrideValue':'','flightData':'','returnValue':'unknown'}"}
09/11/2018 08:11:20.002 OFFICEC2 (0x1a68) 0x193c Click-To-Run General Telemetry bhltg Medium Core::GetFlightData {"MachineId": "bfb4733c0c55df4fbd4551668864e9ca", "SessionID": "6305cea6-1fa9-44bf-a9ac-58d81d2280a9", "GeoID": 244, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "{'flightIdentifier':'Microsoft.Office.Click2Run.UseClientCabManager','overrideValue':'','flightData':'','returnValue':'unknown'}"}
09/11/2018 08:11:20.003 OFFICEC2 (0x1a68) 0x193c Click-To-Run General Telemetry bhltg Medium Core::GetFlightData {"MachineId": "bfb4733c0c55df4fbd4551668864e9ca", "SessionID": "6305cea6-1fa9-44bf-a9ac-58d81d2280a9", "GeoID": 244, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "{'flightIdentifier':'Microsoft.Office.Click2Run.UseExperimentalTransportForCabs','overrideValue':'','flightData':'','returnValue':'unknown'}"}
09/11/2018 08:11:20.003 OFFICEC2 (0x1a68) 0x193c Click-To-Run General Telemetry bhltg Medium Core::GetFlightData {"MachineId": "bfb4733c0c55df4fbd4551668864e9ca", "SessionID": "6305cea6-1fa9-44bf-a9ac-58d81d2280a9", "GeoID": 244, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "{'flightIdentifier':'Microsoft.Office.Click2Run.UseExperimentalTransportForPipe','overrideValue':'','flightData':'','returnValue':'unknown'}"}
09/11/2018 08:11:20.003 OFFICEC2 (0x1a68) 0x193c Click-To-Run General Telemetry bhltg Medium Core::GetFlightData {"MachineId": "bfb4733c0c55df4fbd4551668864e9ca", "SessionID": "6305cea6-1fa9-44bf-a9ac-58d81d2280a9", "GeoID": 244, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "{'flightIdentifier':'Microsoft.Office.Click2Run.UseExperimentalTransportForClientCabs','overrideValue':'','flightData':'','returnValue':'unknown'}"}
09/11/2018 08:11:20.006 OFFICEC2 (0x1a68) 0x193c Click-To-Run General Telemetry a4htr Medium ::DoUpdates {"MachineId": "bfb4733c0c55df4fbd4551668864e9ca", "SessionID": "6305cea6-1fa9-44bf-a9ac-58d81d2280a9", "GeoID": 244, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "Triggering an update: {'Parameters':'displaylevel=False flt.downloadappvcab=unknown flt.useclientcabmanager=unknown flt.useexptnsptcb=unknown flt.useexptnsptpl=unknown flt.useexptransportforclientcab=unknown flt.usedms=true flt.dmsapiversion=2 flt.dmsapiuri=https://mrodevicemgr.officeapps.live.com/mrodevicemgrsvc/api flt.dmsshouldsendtenantid=true flt.dmsrequestattemptlimit=3 flt.usevcab=false triggersource=User'}"}
09/11/2018 08:11:27.605 OFFICEC2 (0x1a68) 0x193c Click-To-Run General Telemetry bon04 Medium ReportMachineKey {"MachineId": "bfb4733c0c55df4fbd4551668864e9ca", "SessionID": "6305cea6-1fa9-44bf-a9ac-58d81d2280a9", "GeoID": 244, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "{\MachineKey\:\NotFound\,\Platform\:\x86\,\AppVVersion\:\5.0.10348\}"}
09/11/2018 08:11:28.992 OFFICEC2 (0x1a68) 0x193c Click-To-Run azfea Medium ::wWinMain {"MachineId": "bfb4733c0c55df4fbd4551668864e9ca", "SessionID": "6305cea6-1fa9-44bf-a9ac-58d81d2280a9", "GeoID": 244, "Ver": "0.0.0.0", "C2RClientVer": "0.0", "ContextData": "ClientExe complete. {'Action':'1','Result':'0'}"}
All replies (4)
Thursday, September 13, 2018 7:23 AM ✅Answered
Hi,
From your screenshot, I find that you have set up automatic updates and enable the update prompts. You also create the deadline and the location to get the update.
>>I'm using a local share as my update repository and if I manually run the update using the GUI it is 100% fine (confirmed with packet captures it is using my repository), but my users are not being prompted for updates.
We need to check if there is a problem during the Office update process. We need to check the directory where the update file is stored, whether there is an update for the client version, the log shows the client version information: 16.0.8431.2250 is (May 8, 2018) version of Semi-Annual Channel. For more information about Office update version, read Update history for Office 365 (listed by date) or (listed by version).
Check if the client has detected and downloaded the update when it is confirmed that the update resource is correct, C:\Program Files\Microsoft Office\Updates\ (32-bit system) or C:\Program Files (x86)\Microsoft Office\Updates \ (64-bit system) , check if there are corresponding update files in the Download and Apply directory. Please check download folder(C:\Program Files\Common Files\microsoft shared\ClickToRun\Updates) of Office update on the local computer, to find the update source of the new version Office.
>>Does the product have to be "licensed" for it to update? I'm primarily curious about this as it affects mass deployments.
Yes, it does. Office 365 requires each user to have license assigned for Office installation, Activation and updates.
>>When the update deadline is set, does the program have to be in use periodically for it to work? I ask because I had computers turn on (some without office running, some with) and set the GPO deadline (confirm application via registry check) with a past date for days before some computers actually updated.....but others that had just turned on forced the update immediately.
After the compressed files are downloaded, the scheduled task then attempts to install the updates in the background, without requiring any user intervention.
If the Office program that has to be updated is being used by the user, updates can't be applied. If this is the case, the task tries to apply the updates the next time that the scheduled task runs. If updates can't be applied for several days, users see a message “ that updates are ready to applied”. If the user restarts the computer and updates haven't been applied, the updates are applied as Windows starts. This won't prevent the user from logging in.
The deadline specifies a date and time by when the updates must be applied. If the updates aren't applied by the deadline, Office automatically closes any open Office programs and applies the updates.
If the deadline arrives and the updates still aren't applied, users see a dialog box that warns them that they have 15 minutes before the updates are applied.
This gives users fifteen minutes to save and close any work. When the countdown reaches 00:00, any open Office programs are closed, and the updates are applied.
Please refer to this article to learn more about the update process for Office 365. To know more about end-user update notifications, see here.
If you have any question or update, please feel free to let me know.
Best Regards,
Herb Gu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams
Wednesday, September 12, 2018 10:23 AM
Hi,
I have noticed your question. I am actively doing analysis. I will reply you after completing the analysis. Have a nice day!
Best Regards,
Herb Gu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams
Monday, September 17, 2018 10:23 AM
Hello,
Any update here? Have you solved the problem? Is my answer helpful to you?
I'm looking forward to your response. If you have any additions, or update, please feel free to let me know.
Best Regards,
Herb Gu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams
Wednesday, September 19, 2018 8:55 PM
Hi Herb
The explanations in the links were useful, as well as the paths as they helped me to understand the process and provide level 1 helpdesk with troubleshooting steps.
I have been doing some double checking and it seems that yes, things are sort of working as designed.... I have done new installs, have had the due date set for a date in the past and it can still be days before the application updates. No message bars appear and nothing in the notification tray. It is also unfortunate that it takes up to 4 days for the updates to be applied and there is no nagging previously. With MSI installs I can use WSUS and ensure critical updates are applied within 24 hours. That isn't the case with C2R installs so it seems like a bit of a step backwards unfortunately in their secure computing initative MS has.
I also discovered that no, you do not need to have Office activated for it to update from a local repository, which is good news when you haven't had the opportunity to build a new install and are relying on the update after initial install.
Would love to see some sort of information on dissecting the C2R logs :)