What are the details of this method of deployment regarding the INI files?
This question is based on the fact that there are 2 .INI files created during the creation of the network based deployment image of ACAD 2012. Both of these .INI files have references to the creation UNC, which becomes a problem when deploying to multiple Distribution Points. I have read forums recommending that versions of these .INI files be created for each DP to resolve this issue.
To complicate matters, I must also deploy to Windows XP X64 & X32 systems. I have experimented with both Program based deployments as well as Task Sequences based on command line executions. AutoDesk documentation states that SCCM cannot deploy the DirectX specific to ACAD 2012, requiring it to be a separate install.
I have tried the Program method with the AdminImage\Setup.exe command line which has resulted in an exit code 1603...which research has suggested is the result of missing prereqs like .NET and DirectX.
Please share any real life successful experiences.
Community Chosen Answer
I have packaged ACAD2012 and works fine. It comes with a deployment agent tool from which you can create an image which you require. In your case, you will have to create two different packages for 32 bit and 64 bit and then install them respectively.