none
Office 365 App deployment using Inune within Windows Autopilot hit and miss RRS feed

  • Question

  • Hi folks

    We've over the past few weeks (previous to this, the Office 365 app deployment has been pretty reliable and we've not changed anything - the assignment for the app is set to All Users/All Devices)) we've started to experience the same sort issue detailed in the below post:

    https://social.technet.microsoft.com/Forums/en-US/e0afcb50-d272-4abf-90d0-d8f9d4eb5381/office-365-installation-during-autopilot?forum=microsoftintuneprod

    On some devices and even the same device from time to time (with the same AAD group membership), Office 365 Pro Plus fails to deploy and sits in a status within Intune of "Install Pending".  Even after a sync it can sit there for a day without change.  We can then wipe the device within Intune and go through the whole Autopilot process again and it will install quickly.  It's so unreliable recently in respect of deploying the app.  I've looked in the registry as per the above post and I too have a status of 0x000003e5 (997) which is "Installation in progress".

    Has anyone else had this issue recently?  I see from the above post that as a workaround, some folks have resorted to deploying the app via an MSI app as it is more stable and from the responses by others in the above post, it is working better.

    It's so frustrating at the moment!

    Thanks all for any advice or pointers on this.




    • Edited by RDW72 Tuesday, June 4, 2019 2:49 PM
    Tuesday, June 4, 2019 2:46 PM

All replies

  • Hello,

    Firstly, you can view the log files at location: %temp% and %windir%\temp. The file name is COMPUTERNAME-yyyymmdd-tttt.log.

    In addition, even the status is install pending, can you view the applications installed on the client device? what's the OS version, 1803 or 1809?

    Best regards,
    Andy Liu


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

    Wednesday, June 5, 2019 5:50 AM
  • Hi Andy

    Apologies for the late response on this.

    I've checked the locations you've specified and I cannot see any logs with computername etc.log at either directory.

    The status is showing pending and nothing has deployed to the device.  The OS version is 1903 (Win 10) but it has done the same on 1809 as well.

    Regards

    Rob

    Monday, July 1, 2019 12:11 AM
  • Hi Andy

    Apologies but I've since gone back to the device and found the logs.  Looking through the logs, it has the following entry:

    07/01/2019 15:09:01.888 OFFICECL (0x1614) 0x167c Click-To-Run bxa8r Monitorable IdentityContext::TryGetImpersonationToken - Failed to impersonate as logged on user.

    Then further down, this:

    07/01/2019 15:09:02.264 OFFICECL (0x1614) 0x167c Activity bjtcw Medium ActivityEnded {"Name": "Office.ClickToRun.CreateRangeTransport", "CV": "F/o1d77um0y+o5cw2GoUeg.5.2.1", "ProcessIdentifier": "OfficeClickToRun.exe_16.0.10730.20348_X86_{7735FA17-EEBE-4C9B-BEA3-9730D86A147A}"} D1BF706B-F3A0-4C1E-B063-9C2A9F7C00B2
    07/01/2019 15:09:02.264 OFFICECL (0x1614) 0x167c Activity bjtcw Medium ActivityEnded {"Name": "Office.ClickToRun.Transport.ExperimentalTransport.PipelineCreateTransport", "CV": "F/o1d77um0y+o5cw2GoUeg.5.2", "ProcessIdentifier": "OfficeClickToRun.exe_16.0.10730.20348_X86_{7735FA17-EEBE-4C9B-BEA3-974HJFA147A}"}
    07/01/2019 15:09:02.264 OFFICECL (0x1614) 0x167c Click-To-Run as6oe Medium Pipeline::SendTrace: PipelineOpenStreamSession: StreamSession (42657587-4EEB-481C-9276-90FC60945A88) successfully opens.
    07/01/2019 15:09:02.264 OFFICECL (0x1614) 0x167c Click-To-Run apz3n Medium TaskStream::DoExecute - Waiting for LoadAll thread to finish
    07/01/2019 15:09:02.264 OFFICECL (0x1614) 0x167c Click-To-Run apkpk Monitorable ScenarioController::CheckProcessPool - Failed to get/create ui process pool, and we are not the ui handler. Cannot process event
    07/01/2019 15:09:04.277 OFFICECL (0x1614) 0x167c Click-To-Run apkpk Monitorable ScenarioController::CheckProcessPool - Failed to get/create ui process pool, and we are not the ui handler. Cannot process event
    07/01/2019 15:09:06.293 OFFICECL (0x1614) 0x167c Click-To-Run apkpk Monitorable ScenarioController::CheckProcessPool - Failed to get/create ui process pool, and we are not the ui handler. Cannot process event
    07/01/2019 15:09:08.305 OFFICECL (0x1614) 0x167c Click-To-Run apkpk Monitorable ScenarioController::CheckProcessPool - Failed to get/create ui process pool, and we are not the ui handler. Cannot process event

    Then further down towards the end of the logs:

    07/01/2019 15:14:34.116 OFFICECL (0x1614) 0x167c Click-To-Run apkpk Monitorable ScenarioController::CheckProcessPool - Failed to get/create ui process pool, and we are not the ui handler. Cannot process event
    07/01/2019 15:14:34.116 OFFICECL (0x1614) 0x167c Click-To-Run apm4d Medium Task::HandleTaskStateCompleted - Handling TaskState (TASKSTATE_COMPLETED) for task (4CCD26FB-A773-42FB-8E44-CD53798BC0E7)
    07/01/2019 15:14:34.116 OFFICECL (0x1614) 0x167c Click-To-Run annu6 Medium TaskGroup::DoHandleWorkerCompleteEvent - Task {4CCD26FB-A773-42FB-8E44-CD53798BC0E7} complete event is handled by task {8D3B8D3F-A1B6-4149-8187-5530518A3849}
    07/01/2019 15:14:34.116 OFFICECL (0x1614) 0x167c Click-To-Run annu9 Medium TaskGroup::HandleTaskStateCompleted - Found task {{732E717C-22C1-4023-816C-7BB33BB24EAD}}, queue for execution.
    07/01/2019 15:14:34.116 OFFICECL (0x1614) 0x167c Click-To-Run annua Medium ProcessPool::QueueTaskItem - Task GROUP:{8D3B8D3F-A1B6-4149-8187-5530518A3849} is being scheduled to run in this process
    07/01/2019 15:14:34.116 OFFICECL (0x1614) 0x167c Activity bjtcw Medium ActivityEnded {"Name": "Office.ClickToRun.Scenario.InstallTaskStream", "CV": "F/o1d77um0y+o5cw2GoUeg.5", "ProcessIdentifier": "OfficeClickToRun.exe_16.0.10730.20348_X86_{7735FA17-EEBE-4C9B-BEA3-9730D86A147A}"}
    07/01/2019 15:14:34.116 OFFICECL (0x1614) 0x14bc Click-To-Run an82i Medium ProcessPool::SpawnProcess - Attempting to shellexec a Click-to-Run process. Path: C:\Program Files\Common Files\Microsoft Shared\ClickToRun\OfficeClickToRun.exe
    07/01/2019 15:14:34.116 OFFICECL (0x1614) 0x14bc Click-To-Run an82r Medium ::SpawnProcessCore - Attempting to spawn a process. Command: "C:\Program Files\Common Files\Microsoft Shared\ClickToRun\OfficeClickToRun.exe", Args: , Verb: runas
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run Non Task Error an82k Unexpected ProcessPool::SpawnProcess {"MachineId": "removedIDforsecurity", "SessionID": "6fb1896a-85ff-4278-b3bf-4946bd0d40d8", "GeoID": 242, "Ver": "16.0.10730.20348", "C2RClientVer": "16.0.10730.20348", "ErrorCode": 0, "ErrorType": "", "AppVErrorSource": "", "ErrorMessage": "", "ErrorDetails": "", "ContextData": "Process started, but RPC endpoint failed to respond."}
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run Non Task Error ap3jc Unexpected ProcessPool::QueueTaskItem {"MachineId": "removedIDforsecurity", "SessionID": "6fb1896a-85ff-4278-b3bf-4946bd0d40d8", "GeoID": 242, "Ver": "16.0.10730.20348", "C2RClientVer": "16.0.10730.20348", "ErrorCode": 1715, "ErrorType": "", "AppVErrorSource": "", "ErrorMessage": "", "ErrorDetails": "", "ContextData": "Unable to ensure process pool for task {'Task':'UNINSTALLCENTENNIAL:{732E717C-22C1-4023-816C-7BB33BB24EAD}'}"}
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run as78i Medium ProcessPool::QueueTaskItem - Task UNINSTALLCENTENNIAL:{732E717C-22C1-4023-816C-7BB33BB24EAD} can't be queued. Attempt to skip the task.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run as78j Medium Task::DoSkip - Hibernating task (732E717C-22C1-4023-816C-7BB33BB24EAD). It is currently in TASKSTATE_NOTSTARTED state
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run as78k Medium Task::DoSkip - Skipping task (732E717C-22C1-4023-816C-7BB33BB24EAD). It is currently in TASKSTATE_HIBERNATED state
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apkpk Monitorable ScenarioController::CheckProcessPool - Failed to get/create ui process pool, and we are not the ui handler. Cannot process event
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run annvj Medium Worker::TaskExecutionThreadProc - Task GROUP:{8D3B8D3F-A1B6-4149-8187-5530518A3849} completed with TaskState TASKSTATE_FAILED.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run annu6 Medium TaskGroup::DoHandleWorkerCompleteEvent - Task {8D3B8D3F-A1B6-4149-8187-5530518A3849} complete event is handled by task {8D3B8D3F-A1B6-4149-8187-5530518A3849}
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {8D3B8D3F-A1B6-4149-8187-5530518A3849}
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm4a Monitorable Task::DoCancel - Can't cancel task (363FEBED-07D2-4993-B860-5925C6FAF115) because it is in TASKSTATE_COMPLETED state
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm4a Monitorable Task::DoCancel - Can't cancel task (4CCD26FB-A773-42FB-8E44-CD53798BC0E7) because it is in TASKSTATE_COMPLETED state
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm4a Monitorable Task::DoCancel - Can't cancel task (732E717C-22C1-4023-816C-7BB33BB24EAD) because it is in TASKSTATE_COMPLETED state
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm39 Medium Task::DoCancel - Task (A42AC5D1-70F7-48E9-8A2D-0A9635A57862) in TASKSTATE_NOTSTARTED, set to Cancelled.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {A94EA03C-786F-49B8-AED1-5F9D84881BF8}
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {2BE168FD-0ECB-46A9-8998-03B2B55B4DF8}
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {31DBF8A1-18DC-4A41-B76B-5BA9D3BFF2D8}
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm39 Medium Task::DoCancel - Task (17492C85-D313-44A7-B3EB-CCFB4029E0CB) in TASKSTATE_NOTSTARTED, set to Cancelled.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm39 Medium Task::DoCancel - Task (D22F3964-0490-4BCB-AEA4-A9C353669022) in TASKSTATE_NOTSTARTED, set to Cancelled.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm39 Medium Task::DoCancel - Task (74E7FD58-81CE-46EA-9BDC-A8125C77CC1A) in TASKSTATE_NOTSTARTED, set to Cancelled.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm39 Medium Task::DoCancel - Task (CB3F6915-84A5-4A18-889C-FA9A42D0BCBD) in TASKSTATE_NOTSTARTED, set to Cancelled.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm39 Medium Task::DoCancel - Task (FD07C30B-1348-43B9-B3F5-8476537C77CB) in TASKSTATE_NOTSTARTED, set to Cancelled.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 31DBF8A1-18DC-4A41-B76B-5BA9D3BFF2D8.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm39 Medium Task::DoCancel - Task (61C08BFC-BFF7-49B5-897B-568FFE11F170) in TASKSTATE_NOTSTARTED, set to Cancelled.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {6E052C8E-62F7-45D3-B864-40191450EFD6}
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm39 Medium Task::DoCancel - Task (50463D7B-18BA-4CCF-A839-9D2C8639F50D) in TASKSTATE_NOTSTARTED, set to Cancelled.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 6E052C8E-62F7-45D3-B864-40191450EFD6.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 2BE168FD-0ECB-46A9-8998-03B2B55B4DF8.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task A94EA03C-786F-49B8-AED1-5F9D84881BF8.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm4p Medium TaskGroup::DoCancel - Attempting to cancel task {C4E145E2-BFAD-4497-AB47-C92314E7E0A3}
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm39 Medium Task::DoCancel - Task (F2A2F522-FCCE-4913-9C0D-C6FEB25CC298) in TASKSTATE_NOTSTARTED, set to Cancelled.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm39 Medium Task::DoCancel - Task (D7E11AA1-F6BD-4101-B7F4-AECA50B0030F) in TASKSTATE_NOTSTARTED, set to Cancelled.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task C4E145E2-BFAD-4497-AB47-C92314E7E0A3.
    07/01/2019 15:14:53.590 OFFICECL (0x1614) 0x14bc Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 8D3B8D3F-A1B6-4149-8187-5530518A3849.
    07/01/2019 15:14:53.605 OFFICECL (0x1614) 0x14bc Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task 8D3B8D3F-A1B6-4149-8187-5530518A3849.
    07/01/2019 15:14:53.605 OFFICECL (0x1614) 0x14bc Click-To-Run aozsm Medium TaskBranch::DoHandleWorkerCompleteEvent - Task {8D3B8D3F-A1B6-4149-8187-5530518A3849} success event is handled by task {DF3BBBD9-F521-43BA-BE89-8749E5F80983}
    07/01/2019 15:14:53.605 OFFICECL (0x1614) 0x14bc Click-To-Run annu6 Medium TaskGroup::DoHandleWorkerCompleteEvent - Task {DF3BBBD9-F521-43BA-BE89-8749E5F80983} complete event is handled by task {FB9843BB-0D8A-4347-A227-C759C3FC9103}
    07/01/2019 15:14:53.605 OFFICECL (0x1614) 0x14bc Click-To-Run apm4o Medium TaskGroup::Finalize - Finalizing task FB9843BB-0D8A-4347-A227-C759C3FC9103.
    07/01/2019 15:14:53.605 OFFICECL (0x1614) 0x14bc Click-To-Run annt0 Medium ExecutionContext::ResetExecutingScenario - Reset executing scenario
    07/01/2019 15:14:53.605 OFFICECL (0x1614) 0x1668 Click-To-Run ati21 Medium SystemProcessPool::WaitOnScenarioReset - Scenario is reset.

    Any ideas from anyone appreciated, as Office 365 Pro Plus from Intune at the moment is hit and miss.

    Thanks

    Rob

    Thursday, July 4, 2019 10:58 PM
  • Hi there,

    We are seeing the same problem. Testing mostly on 1809 (June ISO).
    Previously this was almost never an issue, but as of late O365 fails to install with the Intune C2R method.

    This is unacceptable and needs addressing from Microsoft asap.

    Regards,
    Jan


    Thursday, August 8, 2019 11:22 AM
  • getting this as well, 1903.
    Thursday, September 12, 2019 8:35 AM
  • Also seeing this on my 1903's. Intunes is just so passive, its hard to determine what the problem is stemming from.
    Tuesday, September 17, 2019 4:05 PM