Hi all. I'm in the process of configuring the deployment of Autodesk Product Design Suite Ultimate 2015. It's quite a large package and all up after running it's own deployment, the software is approximately 26.6GB in size with 41 pre-requisite components and 52 Autodesk components. The Autodesk deployment creates a .txt file for the entire deployment. The way we have other applications set up in our SCCM 2012 is very modular. I've created and configured anywhere up to 11 components modular of each other deployed as a task sequence, for example: Avid Media Composer 7, with 6 pre-reqs and 5 Avid components. No problems. But Autodesk Product Design Suite Ultimate 2015 has 93 components in total. Should I separate all pre-reqs including autodesk components in it's container (folder) and have one command to represent the entire pre-requisite and another for Autodesk itself? OR, Do I itemize everything (much much more time consuming)? Any suggestions would be greatly appreciated.  Thank you.
Answer Summary:
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity


It would take ages to itemize everything on that Autodesk products. Just use the sccm output file and convert it to a batch file or call the setup.exe using the parameters on it.

If the prereqs are already available in your production, use them and exclude them in the list. If you are calling the one-liner setup.exe for deployment, it is fine but you have to be careful on modifying the INI file.

I still prefer the sccm txt file which I convert to a batch file. I can see the entire list of applications to be deployed and exclude everything that are for a separate deployment like the prereqs. (MS C++ Redistributables). I then modify the location of log files into one location for easy reference and change the progress bar with a basic (With one-liner setup.exe, there is a cancel button which is not ideal). I also pipe each results into another log file which I check for success or failures.
Answered 06/23/2014 by: dj_xest
Fifth Degree Black Belt

  • Thanks dj_xest. Well that's more than one source recommending to do it this way, including Autodesk's information:

    I will go down this path, it'll just take too long as you said, 93 packages to import. I'll go down the batch file path so I can also pipe results out for logging if anything goes wrong. Thank you again.
  • Quick update: I'm requiring to duplicate the answer files from their original location and placing them from the base/root of the execution locations. Some msi files do not like using relative paths at all and hence I get the 1624 errors. But placing the mst files from the execution location fixes this. The previous person who packaged the previous version had itemized everything, this is probably why he had to do it this way.
    • This could be related to the limitations in the maximum characters that you use. I had the same issue and this little trick from batch commands was able to fix everything by inserting somewhere in the beginning of your batch file.
      cd /d %~dp0
      • Brilliant! Thank you so much!
  • Just as a follow up. The 27GB of the actual Autodesk Suite (I split up prereqs, 5GB, and Autodesk Product Suite, 27GB) went all corrupt. I had to do this to clear the actual SCCM Object: http://markswinkels.nl/2013/06/error-cannot-edit-the-object-which-is-in-use-by-site-p01-in-sccm-2012/

    Posted initially in Technet because I didn't know what to do: http://social.technet.microsoft.com/Forums/en-US/cff47e9a-611c-4411-a9d2-3b7d764e26ff/application-configmgr-error-object?forum=configmanagergeneral

    Now I'm hesitant to make another attempt, but I will, cirect from the server instead of a remote console session from my computer. Fingers crossed, if it doesn't work I'll just have to itemize each and every component, which as you said, will be extremely time consuming.
Please log in to comment