James, how have you created the deployment? Are you copying all the files over as additional files?
I created the deployment using the AutoCAD disk using the deployment option, I have tried run from source and download from source even through the admin setup.exe extracts the files required anyway.
Had a few similar problems to this when deployiong sofware with large file structures to Win7 machines.
Where is the deployment location?
How I do it is create the deployment from the DVD in C:\temp\productname of the PC I'm running it on. It will then create he entire deployment in there, then I create a batch file in C:\temp\productname\adminimage\ that runs the setup.exe/
Using Winrar I create a self extracting archive (SFX) of the whole folder so that when it unpacks it goes to the exact same directory I created in step 1, In the sfx option I set it to run the batch file created in step 1 after extraction.
Takes a bit of patience but you only have to hash 1 file on SWD rather than 18,000.
I use the software share on the core to deploy, I even created the package on the core server to see if that worked but no joy, thanks for the advice I will give that a go.
After much testing experimenting and fist slamming on desks, I have managed to get AutoCAD packaged and deployed (via LANDesk Management Suite v9).
So here is how I did it.
You will need:
7-Zip SFX & 7-Zip (and obviously the AutoCAD DVD)
1) Create the deployment package using the AutoCAD stand alone deployment wizard. When asked for the network location, use the "C:\" drive. I chose "C:\Temp\AutodsekAutoCAD2012. (Forgive the typo, but I left the spelling like that so as not to have to recreate the file)
2) Once completed, use 7-Zip to compress the folder to .7z format using "Ultra" compression.
3) Now create a self extracting file using 7-Zip SFX and then test to ensure that the extraction places the files in the exact same location as in step 1). If it doesn't, then recreate the self extractor until it does.
4) Place the self extracting file in the directory you want to use for LANDesk deployment on your core server.
5) Create two batch files, I created them as follows and named the first "Run.cmd" and the second "Install.cmd" (these will be placed in the same directory as step 4):
XCOPY "\\core1\softdist\Packages\OptionApps\Autodesk\Autodesk_AutoCAD_2012_R2\AutodsekAutoCAD2012.sfx.exe" "C:\Temp\" /y
XCOPY "\\core1\softdist\Packages\OptionApps\Autodesk\Autodesk_AutoCAD_2012_R2\Install.cmd" "C:\Temp\AutodsekAutoCAD2012\" /y
* It is vital that the "install.cmd" file is copied to the same directory where the .lnk file is, i.e. one up from "AdminImage", or the install will fail.
C:\Temp\AutodsekAutoCAD2012\AdminImage\setup.exe /qb /I C:\Temp\AutodsekAutoCAD2012\AdminImage\AutoCAD 2012.ini /language en-us
TIMEOUT /T 600
C:\Windows\System32\icacls.exe "C:\Program Files\Autodesk" /T /C /grant \Everyone:(OI)(CI)F
* I added the timeout because otherwise LANDesk reports the completion before the installation has actually finished. The line following that changes the folder permissions as our users have locked down machines. Without the permissions change, AutoCAD cannot write to the log files, nor create the config file and will error. It will then fail to launch.
6) Create a batch distribution package on the LDMS console using Run.cmd as the Primary file. No need to add additional files as the batch will copy the other files to the local device.
That's it .... Done! Now just test your deployment package.
*** This applies to AutoCAD 2012, but I am sure the same is true for 2011***