Deployment of Office 365 Click to Run

Having an issue getting the O365 to install and wondering if I could get some help.    I am new to SCCM and have managed to get a few other apps/packages pushed out without issue.  I have followed a couple of online resources to get this one going but am at the end of my rope.

Created an Application that pushes out to a user Group.

Client Computer (default device) is seeing the package and downloading for the appropriate users and I can see the complete package in the \windows\CCMCACHE

The issue appears that it is timing out waiting for user input when doing the install.

the app is calling setup.exe /configure configuration.xml

Contents of configuration.xml below 

<Configuration>
 
<Product ID="O365ProPlusRetail">
 
<Language ID="en-us" />
 
</Product>
 
</Add>
 
<Display Level="None" AcceptEULA="TRUE" />
 
<Property Name="AUTOACTIVATE" Value="1" />
 
</Configuration>

Here is the App enforcment log that tells me it is exceeding 120 minutes

<![LOG[+++ Starting Install enforcement for App DT "Deploy Office 365 Pro Plus X32" ApplicationDeliveryType - ScopeId_F0A72C6A-71AD-48AB-9637-3C4F9DC381D0/DeploymentType_ee4472b1-c0c3-4ed5-aeda-b6d844c62944, Revision - 6, ContentPath - C:\windows\ccmcache\1i, Execution Context - System]LOG]!><time="14:16:04.873+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appprovider.cpp:1702">
<![LOG[    A user is logged on to the system.]LOG]!><time="14:16:04.885+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appprovider.cpp:2083">
<![LOG[    Performing detection of app deployment type Deploy Office 365 Pro Plus X32(ScopeId_F0A72C6A-71AD-48AB-9637-3C4F9DC381D0/DeploymentType_ee4472b1-c0c3-4ed5-aeda-b6d844c62944, revision 6) for system.]LOG]!><time="14:16:04.889+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appprovider.cpp:2148">
<![LOG[+++ Application not discovered. [AppDT Id: ScopeId_F0A72C6A-71AD-48AB-9637-3C4F9DC381D0/DeploymentType_ee4472b1-c0c3-4ed5-aeda-b6d844c62944, Revision: 6]]LOG]!><time="14:16:04.910+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="localapphandler.cpp:291">
<![LOG[    App enforcement environment:
                Context: Machine
                Command line: setup.exe /configure configuration.xml
                Allow user interaction: No
                UI mode: 0
                User token: null
                Session Id: 4294967295
                Content path: C:\windows\ccmcache\1i
                Working directory: ]LOG]!><time="14:16:04.911+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appcontext.cpp:85">
<![LOG[    Prepared working directory: C:\windows\ccmcache\1i]LOG]!><time="14:16:04.912+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appcontext.cpp:189">
<![LOG[    Prepared command line: "C:\windows\ccmcache\1i\setup.exe" /configure configuration.xml]LOG]!><time="14:16:05.012+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appcontext.cpp:338">
<![LOG[    Post install behavior is BasedOnExitCode]LOG]!><time="14:16:05.411+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appcommon.cpp:1094">
<![LOG[    Waiting for process 1612 to finish.  Timeout = 120 minutes.]LOG]!><time="14:16:05.414+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appexcnlib.cpp:1958">
<![LOG[Exceeded timeout of 120 minutes while waiting for process 1612 to finish.]LOG]!><time="16:16:05.723+300" date="02-12-2015" component="AppEnforce" context="" type="2" thread="11560" file="appexcnlib.cpp:1972">
<![LOG[WaitForRunningProcess failed.  Error 0x87d00213.]LOG]!><time="16:16:05.723+300" date="02-12-2015" component="AppEnforce" context="" type="3" thread="11560" file="appexcnlib.cpp:1988">
<![LOG[CMsiHandler::CompleteEnforcement failed with 0x87d00213]LOG]!><time="16:16:05.724+300" date="02-12-2015" component="AppEnforce" context="" type="3" thread="11560" file="msihandler.cpp:320">
<![LOG[CAppProvider::CompleteEnforcement failed with error 0x87d00213]LOG]!><time="16:16:05.729+300" date="02-12-2015" component="AppEnforce" context="" type="3" thread="11560" file="appprovider.cpp:2544">
<![LOG[++++++ Failed to enforce app. Error 0x87d00213. ++++++]LOG]!><time="16:16:05.736+300" date="02-12-2015" component="AppEnforce" context="" type="3" thread="11560" file="appprovider.cpp:2467">

As this is the first package that really has failed miserably I would love any help trying to troubleshoot what is wrong.

February 13th, 2015 4:57pm

I haven't pushed this application out but I have looked at OneDrive which was very similar.

https://social.technet.microsoft.com/Forums/en-US/fdc35051-796f-4c94-98b4-19df0bc316e3/one-drive-for-business-deployment-with-sccm?forum=configmanagergeneral

Forget about Configuration manager, it's just running the installation via a command line under the system account.

Copy your application to a local machine and run it from from a command line,

It might be worth changing the display level property so you can see if the installation is prompting for anything.

You could also add

<!--  <Logging Level="Standard" Path="%temp%" />  -->

and check the temp directory for the log file.

Start run %temp%

or if running under the system account this will be located C:\windows\temp.

Once you have your installation going through silently then run it under the system account. again do this from the local machine without configmgr using PSEXEC -i -s cmd.exe

http://richardbalsley.com/a-simple-tip-to-test-software-installation-using-the-local-system-account

One that works it will fly out using ConfigMgr.
  • Edited by -Richk- 12 hours 24 minutes ago
Free Windows Admin Tool Kit Click here and download it now
February 13th, 2015 6:55pm

I haven't pushed this application out but I have looked at OneDrive which was very similar.

https://social.technet.microsoft.com/Forums/en-US/fdc35051-796f-4c94-98b4-19df0bc316e3/one-drive-for-business-deployment-with-sccm?forum=configmanagergeneral

Forget about Configuration manager, it's just running the installation via a command line under the system account.

Copy your application to a local machine and run it from from a command line,

It might be worth changing the display level property so you can see if the installation is prompting for anything.

You could also add

<!--  <Logging Level="Standard" Path="%temp%" />  -->

and check the temp directory for the log file.

Start run %temp%

or if running under the system account this will be located C:\windows\temp.

Once you have your installation going through silently then run it under the system account. again do this from the local machine without configmgr using PSEXEC -i -s cmd.exe

http://richardbalsley.com/a-simple-tip-to-test-software-installation-using-the-local-system-account

One that works it will fly out using ConfigMgr.
  • Edited by -Richk- Friday, February 13, 2015 11:50 PM
February 14th, 2015 2:49am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics