ConflictManager Reference
28
Chapter 3
Conflict Detection and Resolution
This chapter includes the following topics:
z
About Conflict Detection and Resolution
on page 28
z
Prerequisites for Conflict Detection and Resolution
on page 28
z
Process for Resolving Conflicts
z
Detecting Conflicts
on page 30
z
Viewing Conflicts
on page 31
z
Conflict Resolution
on page 35
z
Package Export After Conflict Resolution
on page 45
z
ConflictManager Reports
on page 48
About Conflict Detection and Resolution
After you import packages into the Software Manager database, use ConflictManager to:
z
Detect conflicts.
z
Display conflicts.
z
Resolve conflicts.
z
Export the changes to the original installation file and recompile it.
z
Generate ConflictManager reports.
You also can detect and resolve conflicts in Windows Installer Editor. Do this to compare
a package that is still in the authoring phase with those that have already been
deployed, without importing the package into the Software Manager database. This lets
you:
z
Streamline repackaging by identifying conflicts earlier in the process.
z
Maintain your Software Manager database as a pristine image of packages that have
already been deployed in the production environment.
See Resolving File Conflicts Within Windows Installer Editor in the Windows Installer
Editor Help.
Prerequisites for Conflict Detection and Resolution
Before you use ConflictManager to detect and resolve conflicts:
z
Define conflict settings, which determine the type of conflicts that are detected and
the files and registry keys that are excluded from conflict detection.
See
About Conflict Settings
on page 19.
z
Decide whether to use conflict resolution rules and, if so, decide which predefined
rule sets to use. You can edit the predefined rule sets or create new rule sets.
Summary of Contents for CONFLICTMANAGER
Page 1: ...ConflictManager Reference ...