We ran into the same issues many have reported trying to install AutoCAD 2009 and other AutoDesk products with SCCM 2007 SP1. Following their own instructions to use SCCM doesn't result in a usable package.

I opened an incident with Microsoft Premier Support (CASE_ID_NUM: SRZ081104000346), and, got an answer on the issue, which I forwarded to AutoDesk, and, posted on their Forums (http://discussion.autodesk.com/forums/thread.jspa?messageID=5993608&#5993608). While AutoDesk eventually acknowledged their problem, they are only going to fix it in the next release, AutoCAD 2010, rather than issue a fix or patch.

Basically, when you run their setup.exe, it spawns a bunch of processes to start the prerequites, then base program installs, then exits. Unfortunately...it exits with a non-standard error code of 259, which neither SCCM nor CA DSM recognize as anything, so, they both report failure (within about 20 seconds after starting). At least with SCCM, the install continues, but, SCCM has basically quit monitoring anything, and, my programmed reboot after the install (required) never happened.

It seems that AutoDesk is a proud member of the other A-List vendors (Apple, Adobe) that produce problematic products for enterprise deployment.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
It would be useful to post this as a 'Note' in the 'Package KB' for the application.
Answered 12/22/2008 by: VBScab
Red Belt

Please log in to comment
0
I'll do that. Thanks.
Answered 12/22/2008 by: gmouse
Orange Senior Belt

Please log in to comment
0
guys,

i am experiencing another similar issue. I am deploying the msi with an mst built from Orca.
Unsure of the reason, the deployment via SCCM to user has cause admin elevation, and shortcut is not install to user profile. anyone hit this before?
Answered 12/22/2008 by: dinozilla
Orange Senior Belt

Please log in to comment
0
anyone hit this before? As ever, enable Windows Installer logging (set it to use a verbose log) to begin the process of finding out.REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer]
"Debug"=dword:00000007
"Logging"="voicewarmup"
Answered 12/23/2008 by: VBScab
Red Belt

Please log in to comment
0
It appears that this problem has not been resolved for AutoCAD 2010 64-bit. I am seeing the exact same behavior of the setup.exe sending a return code of 259 but it is still running and spawing off the other components.

The 32-bit version works just fine.
Answered 12/02/2009 by: luvwarmth
Senior Yellow Belt

Please log in to comment
0
I dont know anything about SCCM but could you not wrap the Autodesk installation in a VB Script that process the Autodesk exit code and then presents an exit code to SCCM in the format that it expects?
Answered 12/08/2009 by: t_claydon
Senior Yellow Belt

Please log in to comment
0
Here at the Uni we use Altiris to push out the Vendor generated Shortcut to the local workstation and saw that once Altiris passed the shortcut to Autocad 2009/2010 it lost track of the install and errored with the same error code of 259 (no further data) - however the install still continued. So we added a small VB script to watch for the process setup.exe

This worked a treat, we have found other apps that behave like this - as if the initial installer then passes the buck off to another app that does the work yet we are left with no way to monitor it hence the need to use the VB script to watch for the 2nd process
Answered 12/16/2009 by: Rodus
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity