Chapter 13: Identifying and Resolving Application Conflicts Using ConflictSolverIdentifying and Resolving Conflicts1114 ADS-0950-UG00 AdminStudio 9.5 User GuideNote • If performing conflict analysis with multiple source packages, and if this option is selected, both ACE21 andACE22 are automatically evaluated when either one is selected. If only one of them is evaluated, then there is thepossibility that conflicts will not be detected.Checking for ConflictsThe following topics are included in this section:• Checking for Conflicts Using the Conflict Wizard• Checking for Conflicts During Import• Viewing Identified Conflicts in the Conflicts View• Running Conflict Identification Again• Deleting Persisted Conflict Data• Conflict PersistenceChecking for Conflicts Using the Conflict WizardThe Conflict Wizard can be used to identify conflicts between an external Windows Installer package and onesalready in the Application Catalog, or between one or more packages in the Application Catalog.Identifying Conflicts with an External PackageThe ConflictSolver Wizard allows you to run conflict checks against external MSI packages and packages importedinto the ConflictSolver Application Catalog Database. ConflictSolver supports external package conflict checkingfor User Defined Custom/Source Only Packages ACEs. The Source package can be selected from theConflictSolver Application Catalog Database or from an external MSI package. See Creating a Custom/SourceOnly Packages ACE for more information.However, ConflictSolver does not support external package conflict checking for Custom/Source and TargetPackages ACEs. Both the Source and Target Packages must be selected from the ConflictSolver ApplicationCatalog Database.Task: To identify conflicts between an external Windows Installer package and packages already in theApplication Catalog:1. Select Conflict Wizard from the Conflicts menu. The Welcome Panel opens.2. Click Next. The Source Type Panel opens.3. Select Windows Installer package. Click Next. The MSI Source Information Panel opens.4. Click Browse to locate the MSI file you want to check against packages in the Application Catalog.
