When an MSI contains a feature-based or post-install prerequisite, and that MSI is run under the SYSTEM account (such as when using Group Policy Software Installation), bad things happen. The Download/extraction folder set on the Prerequisites page is not honored. Instead, the prerequisites are extracted to C:\<Company_Name>\<MSI_Name>\prerequisites\.... Also, there are two cmd.exe processes left after the install that are pegging the CPU (100% usage).
There are multiple ways to get into this state. The easiest is probably to create an MSI project with any feature-based prerequisite and run the MSI using the SYSTEM account (you can use a scheduled task to do this). Another way is to have two MSI projects: A and B. A contains a feature-based prerequisite, and B contains A as a feature-based prerequisite. Run B in silent mode, which causes the "aipackagechainer" to be launched using the SYSTEM account, and thus A will be in the bad state. This also happens if a deferred custom action is used to launch the second MSI asynchronously and the Run under the LocalSystem account... option is checked.
Because of this issue, we cannot deploy using Group Policy.
FOLLOW US
Get the latest news in Application Packaging