I've been trying to deploy DWG TrueView 2013, and I think I'm finally in the right direction. A lot of the information out there is outdated at most (since most have to do with SCCM 2007).

Here's what I've found so far, and that has worked with SCCM 2012, sort of:

1. Pre-requisites: .NET 4 (the following article IDs must be installed: 2656405, 2656351(2 updates), 2604121 (3 updates), 2656405, 2487367, 982671 (2 updates .NET 4) and 2487367)
2. DWG TrueView product code: {5783F2D7-B028-0409-0100-0060B0CE6BBA}  (taken from the MSI included)
3. Installation command line: setup.exe /w /t /l /q setup.ini

SCCM 2012 pushes the application to the client; however, it fails upon installation with message: The software change returned error code 0x87D01106 (-2016407290)

Now, here's the interesting part. I open a command prompt and go to the CCMCACHE folder and manually run the setup using - setup.exe /w /t /l /q setup.ini - and the application installs successfully! Looks like SCCM 2012 has a problem somewhere, and I can't figure that out.

Any ideas or pointers will be greatly appreciated.

Thanks!

What does AppEnforce.log tell?

Here's the the information pertaining to that installation:

+++ Starting Install enforcement for App DT "DWG TrueView 2013" ApplicationDeliveryType - ScopeId_F3FDFED5-D21B-42C9-8CC1-4A8D8EECDF67/DeploymentType_c8466e8b-ae30-42ac-9c93-c2308374663c, Revision - 3, ContentPath - C:\Windows\ccmcache\2i, Execution Context - System AppEnforce 6/27/2012 10:40:43 PM 3972 (0x0F84)
    A user is logged on to the system. AppEnforce 6/27/2012 10:40:43 PM 3972 (0x0F84)
    Performing detection of app deployment type DWG TrueView 2013(ScopeId_F3FDFED5-D21B-42C9-8CC1-4A8D8EECDF67/DeploymentType_c8466e8b-ae30-42ac-9c93-c2308374663c, revision 3) for system. AppEnforce 6/27/2012 10:40:43 PM 3972 (0x0F84)
+++ Application not discovered. [AppDT Id: ScopeId_F3FDFED5-D21B-42C9-8CC1-4A8D8EECDF67/DeploymentType_c8466e8b-ae30-42ac-9c93-c2308374663c, Revision: 3] AppEnforce 6/27/2012 10:40:43 PM 3972 (0x0F84)
    App enforcement environment: 
Context: Machine
Command line: "setup.exe /w /t /l /q setup.ini"
Allow user interaction: Yes
UI mode: 1
User token: null
Session Id: 2
Content path: C:\Windows\ccmcache\2i
Working directory: AppEnforce 6/27/2012 10:40:43 PM 3972 (0x0F84)
    Prepared working directory: C:\Windows\ccmcache\2i AppEnforce 6/27/2012 10:40:43 PM 3972 (0x0F84)
Invalid data file "setup.exe /w /t /l /q setup.ini" to execute using file association AppEnforce 6/27/2012 10:40:43 PM 3972 (0x0F84)
PrepareCommandline failed with 0x87d01106 for cmdline "setup.exe /w /t /l /q setup.ini" AppEnforce 6/27/2012 10:40:43 PM 3972 (0x0F84)
ScriptHandler::EnforceApp failed (0x87d01106). AppEnforce 6/27/2012 10:40:43 PM 3972 (0x0F84)
AppProvider::EnforceApp - Failed to invoke EnforceApp on Application handler(0x87d01106). AppEnforce 6/27/2012 10:40:43 PM 3972 (0x0F84)
CommenceEnforcement failed with error 0x87d01106. AppEnforce 6/27/2012 10:40:43 PM 3972 (0x0F84)
Method CommenceEnforcement failed with error code 87D01106 AppEnforce 6/27/2012 10:40:43 PM 3972 (0x0F84)
++++++ Failed to enforce app. Error 0x87d01106. ++++++ AppEnforce 6/27/2012 10:40:43 PM 3972 (0x0F84)

I think I know what caused this error message.

The command "setup.exe /w /t /l /q setup.ini" was enclosed in quotes. I removed the quotes and I think it finally deployed! I'll do a few more installations to make sure that it works properly.

Torsten, thanks for your time and input. I'm still learning about SCCM 2012 (first time using the product), and I didn't know about the log until you pointed it out.

Here's the log information on this last attempt:

+++ Application not discovered. [AppDT Id: ScopeId_F3FDFED5-D21B-42C9-8CC1-4A8D8EECDF67/DeploymentType_c8466e8b-ae30-42ac-9c93-c2308374663c, Revision: 4] AppEnforce 6/28/2012 9:35:59 AM 1560 (0x0618)
    App enforcement environment: 
Context: Machine
Command line: setup.exe /w /t /l /q setup.ini
Allow user interaction: No
UI mode: 1
User token: null
Session Id: 4294967295
Content path: C:\Windows\ccmcache\2i
Working directory: AppEnforce 6/28/2012 9:35:59 AM 1560 (0x0618)
    Prepared working directory: C:\Windows\ccmcache\2i AppEnforce 6/28/2012 9:35:59 AM 1560 (0x0618)
    Prepared command line: "C:\Windows\ccmcache\2i\setup.exe" /w /t /l /q setup.ini AppEnforce 6/28/2012 9:35:59 AM 1560 (0x0618)
    Executing Command line: "C:\Windows\ccmcache\2i\setup.exe" /w /t /l /q setup.ini with system context AppEnforce 6/28/2012 9:35:59 AM 1560 (0x0618)
    Working directory C:\Windows\ccmcache\2i AppEnforce 6/28/2012 9:35:59 AM 1560 (0x0618)
    Post install behavior is BasedOnExitCode AppEnforce 6/28/2012 9:35:59 AM 1560 (0x0618)
    Waiting for process 644 to finish.  Timeout = 120 minutes. AppEnforce 6/28/2012 9:35:59 AM 1560 (0x0618)
    Process 644 terminated with exitcode: 0 AppEnforce 6/28/2012 9:38:07 AM 1560 (0x0618)
    Looking for exit code 0 in exit codes table... AppEnforce 6/28/2012 9:38:07 AM 1560 (0x0618)
    Matched exit code 0 to a Success entry in exit codes table. AppEnforce 6/28/2012 9:38:07 AM 1560 (0x0618)
    Performing detection of app deployment type DWG TrueView 2013(ScopeId_F3FDFED5-D21B-42C9-8CC1-4A8D8EECDF67/DeploymentType_c8466e8b-ae30-42ac-9c93-c2308374663c, revision 4) for system. AppEnforce 6/28/2012 9:38:07 AM 1560 (0x0618)
+++ Discovered application [AppDT Id: ScopeId_F3FDFED5-D21B-42C9-8CC1-4A8D8EECDF67/DeploymentType_c8466e8b-ae30-42ac-9c93-c2308374663c, Revision: 4] AppEnforce 6/28/2012 9:38:07 AM 1560 (0x0618)
++++++ App enforcement completed (128 seconds) for App DT "DWG TrueView 2013" [ScopeId_F3FDFED5-D21B-42C9-8CC1-4A8D8EECDF67/DeploymentType_c8466e8b-ae30-42ac-9c93-c2308374663c], Revision: 4, User SID: ] ++++++ AppEnforce 6/28/2012 9:38:07 AM 1560 (0x0618)

• Edited by GonzEd Thursday, June 28, 2012 1:43 PM
• Marked as answer by Moiz Rassiwala[MSFT]Microsoft employee, Moderator Thursday, June 28, 2012 6:03 PM

Hi,

I know this is an old topic but just wanted to add my experience with the same config.

I also had the same error also trying to deploy DWG TrueView 2013 with sccm 2012.

But if i try install a few times after a couple of times it succeeds. Very strange. This is not because i was to fast after deployment (i deployed it a day ago) or to fast after a boot of the destination computer (it's been running for 7 hours before i tried).

My program line has no quotes so that's not the reason for getting this error (in my case). I'm still testing if i find a reason i will post back, but just wanted to add my findings ;)

Hi  All,

For me, the solution is to correct the "content location" of the package or application.

Go to the "Deployment Types" tab in Application properties, after select the deployment types below and select the properties. (For me, It's script)

Finaly, go to "Content" tab in the properties of Deployment Types and correct the Content Location and set the complete path of the folder where the script is located.

It's my contribution to solve this issue.

Thanks,

Masaoud

• Edited by massaoudb 3 hours 22 minutes ago
• Proposed as answer by Weslee db 1 hour 22 minutes ago