Edition:Application Manager is included with AdminStudio Professional and Enterprise Editions.
You can identify conflicts between packages in the Application Catalog using the Conflict Wizard. You can also check for conflicts between packages and OS Snapshots that have been imported into the Application Catalog.
Note:Conflict testing can be performed between Windows Installer packages, App-V packages, and OS snapshots in the Application Catalog; other deployment types—such as Citrix XenApp, VMware ThinApp, mobile apps, legacy applications, and web applications—are not supported.
ACE tests are used to detect conflicts between one or more source packages and one or more target packages/OS snapshots in the Application Catalog. Conflict evaluation is done for each source package against each target package.
For information about performing application conflict testing, see the following topics:
|•||Testing for Conflicts Between Packages|
|•||Testing for Conflicts Between Packages and OS Snapshots|
Note:In previous releases, the Conflict Wizard included a Conflict Rules panel where you could override the default conflict test selections for a specific execution of conflict testing. Starting in AdminStudio 11.5, this panel is no longer included in the Conflict Wizard. Each time you use the Conflict Wizard to perform conflict analysis, the default set of conflict tests will be run. For instructions on how to specify which ACE tests are executed during conflict testing, see Configuring Testing Options on the Analyze Tab and Selecting Tests to Execute.
Note:In previous releases, you were able to perform conflict analysis between external packages and packages in the Application Catalog. Starting in AdminStudio 11.5, you can no longer perform conflict testing using external packages; all packages must first be imported into the Application Catalog before conflict testing (or any other type of testing) can be performed.