Chapter 3: Conflict Detection And Resolution; About Conflict Detection And Resolution; Prerequisites For Conflict Detection And Resolution - Symantec CONFLICTMANAGER 8.0 - REFERENCE V1.0 Reference

Chapter 3
Conflict Detection and Resolution

About Conflict Detection and Resolution

Prerequisites for Conflict Detection and Resolution

ConflictManager Reference
This chapter includes the following topics:
About Conflict Detection and Resolution
Prerequisites for Conflict Detection and Resolution
Process for Resolving Conflicts
Detecting Conflicts on page 30
Viewing Conflicts on page 31
Conflict Resolution on page 35
Package Export After Conflict Resolution
ConflictManager Reports
After you import packages into the Software Manager database, use ConflictManager to:
Detect conflicts.
Display conflicts.
Resolve conflicts.
Export the changes to the original installation file and recompile it.
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:
Streamline repackaging by identifying conflicts earlier in the process.
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.
Before you use ConflictManager to detect and resolve conflicts:
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
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.
on page 28
on page 45
on page 48
on page 19.
on page 28
28