I have a support case open with Autodesk, but I suspect the problem is really in the SCCM end (Server 2008). I'm hoping one of you has more experience with this than I do.
I'm working with a school to deploy thier Autocad, Acad-A, Revit A and Revit S 2012 via SCCM. The Revits and ACAD-A install fine but vanilla Autocad fails. I've rebuilt the deployment several times - and the deplyment runs fine when SCCM is out of the picture.
We are following the directions from here: http://docs.autodesk.com/ACD/2011/ENU/filesInstall
Some other bits of information - they are using Deep Freeze on the student workstations but thier SCCM thaws the workstations and installs with admin rights. (Like I mentioned before, other ADSK products install ok...wierd, right?)
All of the workstations are brand new Win7 64 bit machines.
I've attached the verbose install log in case one of you can make heads or tails of it. The regular, non-verbose install log fails at the direct X stage with error 1602. Direct X is already installed from the other products and I removed that bit from the adminimage.ini. 1602 is usally permissions - but we are full admin.
Uh oh - this is getting too wordy. If you can help I would be super-duper grateful. Thanks. -Lou
If you assume it is directx which is failing.
You could try to edit the setup.ini/deploymentname.ini file to disable directx installation
this would be in the line "PREREQUISITE=" within the ACAD section.
Please let me know if you need detailed explanation on how to disable directx installation using the ini file
If my post answers your question, please mark it as an Accepted Solution, so that others can find answers quickly!
For more tips & tricks: http://upandready.typepad.com
Autodesk Product Support
Did you get to the bottom of this at all? I am having the exact same problem.
Running the installation manually works fine, but running from SCCM the setup.exe process appears in the task manager for about 2 seconds and then fails!
Angus, I realize this over a year old but I'm seeing the exact same thing as you are. Did you ever get to the bottom of it? Setup.exe doesn't even run long enough for any logs to be generated.