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, December 29, 2015 8:30 AM
Hello,
I try to deploy Office 2016 Click-To-Run by SCCM 2012 R2. I use the following article: http://prajwaldesai.com/deploy-office-2016-using-click-to-run-deployment-tool/ but I am still getting the error code 0x87d00324. I have tried to find the solution on the Internet and I have found that it may be caused by incorrect detection method. Here is my detection method:
and my logs:
AppEnforce.log:
<![LOG[+++ Starting Install enforcement for App DT "Office 2016 x86 Cloud PL" ApplicationDeliveryType - ScopeId_F4B5B717-C2B0-4924-97CD-9B84AE77CE73/DeploymentType_b94825ae-e59f-44cf-bf50-744f7654b028, Revision - 4, ContentPath - C:\Windows\ccmcache\1g, Execution Context - System]LOG]!><time="09:17:57.999-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="appprovider.cpp:1702">
<![LOG[ A user is logged on to the system.]LOG]!><time="09:17:58.009-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="appprovider.cpp:2083">
<![LOG[ Performing detection of app deployment type Office 2016 x86 Cloud PL(ScopeId_F4B5B717-C2B0-4924-97CD-9B84AE77CE73/DeploymentType_b94825ae-e59f-44cf-bf50-744f7654b028, revision 4) for system.]LOG]!><time="09:17:58.015-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="appprovider.cpp:2148">
<![LOG[+++ Application not discovered. [AppDT Id: ScopeId_F4B5B717-C2B0-4924-97CD-9B84AE77CE73/DeploymentType_b94825ae-e59f-44cf-bf50-744f7654b028, Revision: 4]]LOG]!><time="09:17:58.041-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="localapphandler.cpp:291">
<![LOG[ App enforcement environment:
Context: Machine
Command line: setup.exe /configuration Configure.xml
Allow user interaction: No
UI mode: 1
User token: null
Session Id: 1
Content path: C:\Windows\ccmcache\1g
Working directory: ]LOG]!><time="09:17:58.043-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="appcontext.cpp:85">
<![LOG[ Prepared working directory: C:\Windows\ccmcache\1g]LOG]!><time="09:17:58.045-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="appcontext.cpp:189">
<![LOG[ Prepared command line: "C:\Windows\ccmcache\1g\setup.exe" /configuration Configure.xml]LOG]!><time="09:17:58.536-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="appcontext.cpp:338">
<![LOG[ Executing Command line: "C:\Windows\ccmcache\1g\setup.exe" /configuration Configure.xml with user context]LOG]!><time="09:17:58.543-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="appexcnlib.cpp:205">
<![LOG[ Working directory C:\Windows\ccmcache\1g]LOG]!><time="09:17:58.543-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="appexcnlib.cpp:219">
<![LOG[ Post install behavior is BasedOnExitCode]LOG]!><time="09:17:58.763-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="appcommon.cpp:1094">
<![LOG[ Waiting for process 3356 to finish. Timeout = 120 minutes.]LOG]!><time="09:17:58.769-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="appexcnlib.cpp:2015">
<![LOG[ Process 3356 terminated with exitcode: 0]LOG]!><time="09:18:01.896-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="appexcnlib.cpp:2024">
<![LOG[ Looking for exit code 0 in exit codes table...]LOG]!><time="09:18:01.897-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="appexcnlib.cpp:508">
<![LOG[ Matched exit code 0 to a Success entry in exit codes table.]LOG]!><time="09:18:01.898-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="appexcnlib.cpp:587">
<![LOG[ Performing detection of app deployment type Office 2016 x86 Cloud PL(ScopeId_F4B5B717-C2B0-4924-97CD-9B84AE77CE73/DeploymentType_b94825ae-e59f-44cf-bf50-744f7654b028, revision 4) for system.]LOG]!><time="09:18:01.911-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="appprovider.cpp:2148">
<![LOG[+++ Application not discovered. [AppDT Id: ScopeId_F4B5B717-C2B0-4924-97CD-9B84AE77CE73/DeploymentType_b94825ae-e59f-44cf-bf50-744f7654b028, Revision: 4]]LOG]!><time="09:18:01.935-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="localapphandler.cpp:291">
<![LOG[++++++ App enforcement completed (3 seconds) for App DT "Office 2016 x86 Cloud PL" [ScopeId_F4B5B717-C2B0-4924-97CD-9B84AE77CE73/DeploymentType_b94825ae-e59f-44cf-bf50-744f7654b028], Revision: 4, User SID: ] ++++++]LOG]!><time="09:18:01.937-60" date="12-29-2015" component="AppEnforce" context="" type="1" thread="2468" file="appprovider.cpp:2450">
AppDiscovery.log:
<![LOG[Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_F4B5B717-C2B0-4924-97CD-9B84AE77CE73/DeploymentType_b94825ae-e59f-44cf-bf50-744f7654b028" AND Revision = 4)"]LOG]!><time="09:17:55.230-60" date="12-29-2015" component="AppDiscovery" context="" type="1" thread="2468" file="appprovider.cpp:406">
<![LOG[ Performing detection of app deployment type Office 2016 x86 Cloud PL(ScopeId_F4B5B717-C2B0-4924-97CD-9B84AE77CE73/DeploymentType_b94825ae-e59f-44cf-bf50-744f7654b028, revision 4) for system.]LOG]!><time="09:17:55.275-60" date="12-29-2015" component="AppDiscovery" context="" type="1" thread="2468" file="appprovider.cpp:2148">
<![LOG[+++ Application not discovered. [AppDT Id: ScopeId_F4B5B717-C2B0-4924-97CD-9B84AE77CE73/DeploymentType_b94825ae-e59f-44cf-bf50-744f7654b028, Revision: 4]]LOG]!><time="09:17:55.364-60" date="12-29-2015" component="AppDiscovery" context="" type="1" thread="2468" file="localapphandler.cpp:291">
<![LOG[+++ Did not detect app deployment type Office 2016 x86 Cloud PL(ScopeId_F4B5B717-C2B0-4924-97CD-9B84AE77CE73/DeploymentType_b94825ae-e59f-44cf-bf50-744f7654b028, revision 4) for system.]LOG]!><time="09:17:55.364-60" date="12-29-2015" component="AppDiscovery" context="" type="1" thread="2468" file="appprovider.cpp:540">
<![LOG[ ActionType - Install will use Content Id: Content_4b2f3598-8251-466d-bab8-7f19f6868572 + Content Version: 1 for AppDT "Office 2016 x86 Cloud PL" [ScopeId_F4B5B717-C2B0-4924-97CD-9B84AE77CE73/DeploymentType_b94825ae-e59f-44cf-bf50-744f7654b028], Revision - 4]LOG]!><time="09:17:56.384-60" date="12-29-2015" component="AppDiscovery" context="" type="1" thread="2468" file="appprovider.cpp:1543">
<![LOG[ ActionType - Install will use Content Id: Content_4b2f3598-8251-466d-bab8-7f19f6868572 + Content Version: 1 for AppDT "Office 2016 x86 Cloud PL" [ScopeId_F4B5B717-C2B0-4924-97CD-9B84AE77CE73/DeploymentType_b94825ae-e59f-44cf-bf50-744f7654b028], Revision - 4]LOG]!><time="09:17:56.411-60" date="12-29-2015" component="AppDiscovery" context="" type="1" thread="2468" file="appprovider.cpp:1543">
I have also tried to use registry value in the detection method but with no luck, too. The application installs correctly when run manually in command line: "setup.exe /configure configuration.xml. Here is my configuration.xml file:
<Configuration>
<Add OfficeClientEdition="32">
<Product ID="O365ProPlusRetail" >
<Language ID="pl-pl" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
</Configuration>
Could you help me with this issue?
All replies (12)
Tuesday, December 29, 2015 6:20 PM ✅Answered | 1 vote
Your Command Line is incorrect.
Command line: setup.exe /configuration Configure.xml
This should be: setup.exe /configure Configuration.xml (depending on what your XML file is called)
Tuesday, December 29, 2015 6:33 PM ✅Answered
Worked ok for me as a package and an application.
Detection rule was a windows installer :
{90160000-008F-0000-1000-0000000FF1CE}
Grabbed the code from one of the MSI's in the windows\installer directory on one of the clients.
My xml was called configure.xml
Tuesday, December 29, 2015 8:55 AM
Hi,
I agree, 0x87D00324 indicates that the installation was successful, but the detection method did not detect the software as "installed"
The logs show the same thing.
Have you checked the machine to see if the software is actually installed? I noticed the install time reported to be incredibly short so I would double check it.
Once you change the detection rule to something else make sure you do a machine policy update on the device and then an application deployment evaluation cycle and check appdiscovery.log
Tuesday, December 29, 2015 9:39 AM
Thank you for the reply. Yes, I have checked it before and Office 2016 is not installing at all (there are no changes on the disk, registry etc.). It looks like the setup finishes just in several seconds. I have also tried to change detection methods (registry value, filesystem) but they also don't work for me.
Is it possible that 0x87D00324 code indicates the error other than DM issue?
Tuesday, December 29, 2015 10:38 AM | 1 vote
Hi,
Ok so the application is not installing at all, it's a little strange the installer is reporting a 0 exit code.
Detection methods are not going to make any difference as the application is not on the device, so it will never be detected.
I would use psexec.
http://richardbalsley.com/a-simple-tip-to-test-software-installation-using-the-local-system-account
On a client device copy the application content to the desktop.
Download psexec from sysinternals.
Use psexec -i -s cmd.exe to open a command prompt as the system account.
Run the installation using this account and monitor the installation.
Configuration Manager uses the local system account to do the installation.
Your command line is just 'setup.exe /configuration Configure.xml'?
Tuesday, December 29, 2015 10:50 AM | 1 vote
Once you get the installation working locally via psexec it will work fine in Configuration Manager.
Don't get to hung up about the detection method initially. Once you get the software installing via Configuration Manager you can then tweak the detection method to detect the installed software by running the two actions I mentioned earlier.
Also worth looking at this excellent guide by one of the dons :)
https://gallery.technet.microsoft.com/How-to-Deploying-Office-e9f296fb
In the guide he mentions a bug in the installer so check out step 9.
Tuesday, December 29, 2015 12:16 PM
We have some progress:
1. The test installation using psexec works. Office 2016 has been installed without any problems.
2. The "package" method of installation described in the document works fine.
3. "The "application" (scripted installer) method doesn't work. The error is still the same: 0x87D00324. For me this is the preferred method so I'd like to resolve this issue.
Do you have any ideas how to resolve it?
Tuesday, December 29, 2015 5:12 PM
I am just prepping it now, will fire it out in the lab once it's downloaded and let you know.
Tuesday, December 29, 2015 6:25 PM
Yeah well spotted :)
Tuesday, December 29, 2015 6:27 PM
Sometimes it's the little things. :)
Wednesday, December 30, 2015 7:44 AM
Yes, I have made a stupid mistake with the name. But after correcting it, the error still appeared.
W have done the following:
1. Changed file name in application properties (from "/configure configure.xml" to "/configure configuration.xml").
2. Updated the content of the deployment.
3. Refreshed computer's policy.
4. Tried to install the application again.
So, I have deleted the application (everything including deployment, deployment type and application) and then recreated it again. And it worked as expected :)
Thank you for the help. Sometimes, the little mistakes can be the most difficult to find and resolve.
Wednesday, December 30, 2015 8:42 AM
Glad you got it sorted :)