I have not verified that they didn't break TerminateChildProcesses in the release, but suspect a typing issue. I didn't think ACE had TerminateChildProcesses, glad to hear they added it.
You can't do this with TerminateEnv or TerminateProcess scripting, only TerminateChildProcesses. The final option is to add LaunchIt to the package and modify your package shortcut to run LaunchIt with the autocad EXE as the argument, but you shouldn't have to go there.
We actually did this using ACE but it does not seem to be working. We have even tried implementing a simple .bat script to kill the process but for some reason, the script doesn't get called when closing out of the AutoCAD app.
The solution is to use TerminateChildProcesses. This will cause the App-V client to monitor the termination of a specified application and kill off all child processes automatically (and without warning).
In 5.1 Sequencing, you can easily use the new AVME tool to add the entry into the internal AppXManifest.xml file with a quick GUI pulldown.
Sequencing on 5.0 SP3 would require you to manually edit the external DeploymentConfig.xml file to add the entry. You need to location the ApplicationID associated with the app that should be monitored (this is found in the "Applications" part of the file). Then add the TerminateChildProcesses element with that AppId in the file. With SCCM deployment, the file just needs to be in the folder when you import and it is automatically used. WIth App-V Server deployment you import the App-V file, then go to the advanced properties of the app and import the XML file.
Ok so I figured out that because App-V is currently at SP2 HF4, I had to use the root install dir as the PVAD which fixed my issue. The issue I need to resolve now is to have the process terminate upon closing the app. I am working with 2 of my colleagues and we know what needs to be done but implementing it seems to be not such an easy task.
I have been working on sequencing AutoCAD 2015 using the recipe from Tim Mangan located
. I created a deployment to start and installed using the deployment on the sequencer without issue. Once I determined that the install went well, I reverted the system and packaged the deployment. Please keep in mind, I have also run through just using the setup.exe and not the deployment.
What I am seeing at first run initializing is an APPCRASH specifying a StackHash for the Fault Module
Problem Event Name: APPCRASH
Application Name: acad.exe
Application Version: 188.8.131.52
Application Timestamp: 52f4a7e0
Fault Module Name: StackHash_5a49
I have seen something suggesting that the stackhash occurs because DEP is having an issue with the application being launched. But I would think this would happen all the time. If I close out as the popup suggests and re-launch the app, it loads just fine. So, DEP doesn't make sense to me.
I would love to stop banging my head against the wall because it hurts. Does anyone have any ideas on this?