User manual SYMANTEC CONFLICTMANAGER 8.0 REFERENCE V1.0

[. . . ] ConflictManager Reference ConflictManager The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement. Documentation version 8. 0 Legal Notice Copyright © 2009 Symantec Corporation. Symantec, the Symantec Logo, and Altiris are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U. S. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. [. . . ] 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: Define conflict settings, which determine the type of conflicts that are detected and the files and registry keys that are excluded from conflict detection. 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. ConflictManager Reference 28 Conflict Detection and Resolution See Conflict Resolution Rules on page 24. Import packages into the Software Manager database, using Software Manager. Note Conflict detection requires package resources to be in the Software Manager database. If a package's meta data is in the database but not its resources, you must perform an import in Software Manager. Process for Resolving Conflicts Typically, you will follow the steps below in the order listed. Example: During the analysis phase of a repackaging project, you might want to check for conflicts but not resolve them. When it finds resources that conflict, it populates the Software Manager database with conflict information. View conflicts in the Applications/Packages pane and the Conflict List, or use the ConflictManager reports to display and print conflict information. Resolving a conflict involves looking at each file that is installed by multiple packages and selecting the version to install on the destination computer. You also can change the location of conflicting files so that each package can use its version of the file. You can use conflict resolution rules to resolve conflicts automatically, or run the Resolve wizard, which lets you review and resolve file conflicts one at a time. After you resolve conflicts, export the changes to the original Windows Installer or WiseScript installation to produce an installation that does not conflict with other packages. After you save and recompile a resolved package, install it on a clean machine and test it. A machine that is not clean might contain newer versions of some of the files you resolved. Because these newer files are not overwritten during the installation, you do not get a true representation of the resolved installation. Redo conflict resolution if necessary. ConflictManager Reference 29 Conflict Detection and Resolution If the package does not work, return to ConflictManager and redo the conflict resolution in any of the following ways. To revert changes for just one or a few files Select Conflicts menu > Resolve. In the Resolve wizard, select one or more files and click Revert to undo your previous conflict resolutions for those files. Try other ways to resolve the conflicts. To redo the conflict resolutions with rules Select Conflicts menu > Resolve with Rules. This reverts all the previous conflict resolutions for that package and then resolves them using the different rule set. This reverts all previous conflict resolutions but does not resolve the conflicts. [. . . ] Conflict Types to Display Errors are conflicts that deserve attention. Application and Package Name (Conflicts by Package only. ) Specify the applications and packages on which to run reports. If you select an application from Application Name, only its packages appear in Package Name. Group Name (Conflicts by Group only. ) File Name (File Conflicts by File only. ) SQL wildcards are accepted. [. . . ]