1. Manuals
  2. Brands
  3. Symantec Manuals
  4. Software
  5. CONFLICTMANAGER 8.0 - REFERENCE V1.0
  6. Reference

Symantec CONFLICTMANAGER 8.0 - REFERENCE V1.0 Reference

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
ConflictManager Reference

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the CONFLICTMANAGER 8.0 - REFERENCE V1.0 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Symantec CONFLICTMANAGER 8.0 - REFERENCE V1.0

Summary of Contents for Symantec CONFLICTMANAGER 8.0 - REFERENCE V1.0

  • Page 1 ConflictManager Reference...
  • Page 2 Copyright © 2009 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, and Altiris are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

  • Page 3: Technical Support

    The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates.
  • Page 4 Licensing and registration If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/techsupp/ Customer service Customer service information is available at the following URL: www.symantec.com/techsupp/ Customer Service is available to assist with the following types of issues:...
  • Page 5 Consulting Symantec Consulting Services provide on-site technical Services expertise from Symantec and its trusted partners. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment, design, implementation, monitoring, and management capabilities. Each is focused on establishing and maintaining the integrity and availability of your IT resources.

  • Page 6: Table Of Contents

    Contents Technical Support ............3 Chapter 1: Introduction to ConflictManager .
  • Page 7 ConflictManager Reports ........... . . 48 Generating a ConflictManager Report .

  • Page 8: Chapter 1: Introduction To Conflictmanager

    Chapter 1 Introduction to ConflictManager This chapter includes the following topics: About ConflictManager on page 8 Starting ConflictManager on page 9 About the ConflictManager Window on page 10 About Conflicts on page 13 Product Documentation on page 17 About ConflictManager ConflictManager is a tool in the Professional Edition of Wise Package Studio.

  • Page 9: Starting Conflictmanager

    Introduction to ConflictManager See Setting Software Manager and ConflictManager Security in the Wise Package Studio Help. Starting ConflictManager To start ConflictManager In Wise Package Studio, do one of the following: On the Projects tab, click the Run link to the right of the task or tool associated with ConflictManager.

  • Page 10: About The Conflictmanager Window

    Introduction to ConflictManager The Select Data Source dialog box appears. This is a standard Windows ODBC connection wizard, which lets you connect to a database through an ODBC data source. Connect to the database. If you need help, ask your database administrator. The database’s contents are listed in the Applications/Packages pane.
  • Page 11 Introduction to ConflictManager Toolbar Contains buttons for quick access to many ConflictManager commands and to Software Manager. While conflict detection is running, its status appears at the right end of the toolbar. Summary Pane Displays different information depending on what is selected in the Applications/ Packages pane: When you select a database, the Summary pane displays the current filter criteria.

  • Page 12: Customizing The Conflictmanager Workspace

    Introduction to ConflictManager Conflict Details Pane Displays resources in other packages that conflict with the item selected in the Conflict List. You can sort the items in this pane by clicking a column header, and you can re- order the columns by dragging the column headers. Double-click an item in this pane to display the Properties dialog box.

  • Page 13: About Conflicts

    Introduction to ConflictManager With Enterprise Management Server, Security Setup determines whether you can edit meta data in Software Manager and ConflictManager. Click the Source tab to view the location of the package installation file and any transforms and patches that were applied to the package. Click OK.

  • Page 14: Hash Value Comparisons In Conflict Detection

    Introduction to ConflictManager View this information: In the Conflict Details pane when you select a conflict in the Conflict List. In the Resolve wizard, which you start by selecting Conflicts menu > Resolve. On the Properties dialog box, which you open by double-clicking a package in the Conflict Details pane.
  • Page 15 Introduction to ConflictManager Filter the conflict display. The conflict display filter determines which packages and conflicts appear in the Applications/Packages, Conflict List, and Conflict Details panes. Filtering the Conflict Display on page 33. Ignore conflicts when components are permanent. When two Windows Installer applications install components with identical resources, but different component GUIDs, ConflictManager detects a conflict.

  • Page 16: Resource Conflicts

    Introduction to ConflictManager WiseScript variable Resolves to %MainDir% Program Files\default maindir or, if default maindir is empty: Program Files %Program_Files% Program Files %Sys% Windows\System %Sys32% Windows\System32 %Win% Windows When the package resource appears in Software Manager and ConflictManager, the resolved value is displayed instead of the formatted text string. Resource Conflicts You use ConflictManager primarily to find file conflicts, but it also can find conflicts between other resources.

  • Page 17: Types Of Conflicts

    Introduction to ConflictManager Icon Resource type Conflict caused by Path Changes to the PATH variable made by multiple packages. These conflicts do not occur in Windows Installer installations. Types of Conflicts Conflicts are classified as either warnings, errors, or information. After conflict detection, conflicts are displayed in the Conflict List and Conflict Details panes.
  • Page 18 The product release notes cover new features, enhancements, bug fixes, and known issues for the current version of this product. To access the release notes, select Release Notes from the Symantec program group on the Windows Start menu. ConflictManager Reference...

  • Page 19: Chapter 2: Setting Up Conflictmanager

    Chapter 2 Setting Up ConflictManager This chapter includes the following topics: About Conflict Settings on page 19 Conflict Resolution Rules on page 24 About Conflict Settings Conflict settings determine the type of conflicts that are detected and the files and registry keys that are excluded from conflict detection.
  • Page 20 Setting Up ConflictManager From File Conflicts, select an option. Normal file conflicts (warnings and errors only) Find files with the same name but different file information that are installed to the same directory or to different directories by multiple packages. Normal conflicts plus informational Find files with identical file information that are installed to the same directory or to different directories by multiple packages.
  • Page 21 Setting Up ConflictManager Component conflicts involving registry keys only Find component conflicts involving registry keys (example: components that update or create the same registry key but have different component GUIDs). Because these conflicts cannot be resolved from within ConflictManager, you might not want to see them.

  • Page 22: Excluding Files And Directories From Conflict Detection

    Setting Up ConflictManager unimportant. To designate a conflict to be ignored, (or to remove the “ignore” designation), right-click the conflict in the Conflict Details pane. 11. To define additional settings, see: Excluding Files and Directories From Conflict Detection on page 22 Excluding Registry Keys From Conflict Detection on page 23 12.

  • Page 23: Excluding Registry Keys From Conflict Detection

    Setting Up ConflictManager To define additional settings, see: Defining Types of Conflicts to Detect on page 19 Excluding Registry Keys From Conflict Detection on page 23 Click OK on the Conflict Settings dialog box. Note If you delete a file from the lower-right list box and it empties the directory, the directory structure is still displayed temporarily but disappears after you close the Conflict Settings dialog box.

  • Page 24: Conflict Resolution Rules

    Setting Up ConflictManager during conflict detection. The left list boxes contain key structure, and the right list boxes contain values. Note The upper-left list box contains information for all packages, even if a package group is selected in the Groups pane. To exclude registry keys from conflict detection Select Setup menu >...

  • Page 25: Predefined Rule Sets

    Setting Up ConflictManager with Rules process performs the action only on conflicts caused by files having different version numbers. A sort option determines how conflicting files are sorted and thus which one is used to resolve the conflict. Example: If you sort by version number, then the file with the highest version number is used.

  • Page 26: Creating A New Rule Set

    Setting Up ConflictManager Aggressive (using These rule sets change as many files as possible in the application paths) active package and can change files in other conflicting packages. They replace all conflicting files with the most Aggressive (using isolated recent version; this means that files in the other components) conflicting packages might be replaced.
  • Page 27 Setting Up ConflictManager If an action contains underlined text, click the underlined text to open a Rule Detail Settings dialog box, where you can specify a value for the underlined text. Example: If you marked the action Isolate the file via AppPaths into the directory Shared, you would click the word AppPaths and select the isolation method, and then click the word Shared and enter a directory name.

  • Page 28: Chapter 3: Conflict Detection And Resolution

    Chapter 3 Conflict Detection and Resolution This chapter includes the following topics: About Conflict Detection and Resolution on page 28 Prerequisites for Conflict Detection and Resolution on page 28 Process for Resolving Conflicts Detecting Conflicts on page 30 Viewing Conflicts on page 31 Conflict Resolution on page 35...

  • Page 29: Process For Resolving Conflicts

    Conflict Detection and Resolution Conflict Resolution Rules on page 24. Import packages into the Software Manager database, using Software Manager. See Package Import in the Software Manager Help. Note Conflict detection requires package resources to be in the Software Manager database.

  • Page 30: Detecting Conflicts

    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 Select Conflicts menu > Resolve. one or a few files In the Resolve wizard, select one or more files and click Revert to undo your previous conflict resolutions for those files.

  • Page 31: Stopping Conflict Detection

    Conflict Detection and Resolution Detect conflicts between all packages Find conflicts between every package and all other packages in the database. Detect conflicts for selected packages Find conflicts between the package you select and all other packages in the database. Marking this option enables the list of packages on the dialog box.

  • Page 32: When Conflict Detection Yields Unexpected Results

    Conflict Detection and Resolution To view conflicts (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane. If you are using package groups, select a group name in the Groups pane. The Applications/Packages pane displays only packages that are assigned to that group.

  • Page 33: Filtering The Conflict Display

    Conflict Detection and Resolution Resource Conflicts on page 16 Check your conflict settings to verify that ConflictManager is detecting the types of conflicts that are important to you. About Conflict Settings on page 19 Verify that ConflictManager is set to display the types of conflicts that you want to see.

  • Page 34: Hiding Conflicts

    Conflict Detection and Resolution To filter the display by a meta data value, mark Filter Based on Meta Data. Then specify the following filter criteria: Name Select a meta data field name to filter packages by. The drop-down list contains meta data fields that are defined in the selected database. Operation Select the operation to use when comparing the meta data value to the value you enter below.

  • Page 35: Conflict Resolution

    Conflict Detection and Resolution Conflict Resolution Resolving a conflict involves looking at each file that is installed by more than one package 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.
  • Page 36 Conflict Detection and Resolution Conflict Problem Recommended resolution Two files with the same name If the installation does not use Copy the file information (source path have different hash values, or a versioning rules (WiseScript included) from one package to another, or different version, date/time, or replacement options or the isolate the file.

  • Page 37: Copying File Information

    Conflict Detection and Resolution Conflict Problem Recommended resolution The shared DLL counter is not In a mixed WiseScript/Windows Set the Shared DLL flag on one or both set for a file shared by a Installer environment, shared files. WiseScript package and a DLL counters must be set so the Resolve wizard: Windows Installer package.

  • Page 38: Isolating Files

    Conflict Detection and Resolution Method How to copy with the How to copy with rules Resolve wizard Aggressive Use the Copy Down button Use a conflict resolution rule containing this action: Replace the conflicting files with the active application’s file Add a condition to compare the package file version to the conflicting files.

  • Page 39: Resolving File Conflicts With Rules

    Conflict Detection and Resolution registry when a file is moved to a private application directory. This can cause other packages to follow the moved file and result in a further conflict. Experiment to determine which packages find the file in the registry and which look in the path. Then move the file for the packages that look in the registry, and leave a copy in the System directory for packages that look in the path.

  • Page 40: Resolving File Conflicts Individually

    Conflict Detection and Resolution Click OK. The Resolving Conflicts dialog box appears, and conflicts are resolved. If there are few conflicts to resolve, the dialog box appears briefly. When conflict resolution is finished, view conflicts for that package. If conflicts appear, they could not be resolved with rules.
  • Page 41 Conflict Detection and Resolution such files without causing problems. The lower list box contains the conflicting files in other packages. In the upper list box, select one or more files and take one of the following actions. Guidelines for Resolving File Conflicts on page 35.

  • Page 42: Resolving Registry Conflicts

    Conflict Detection and Resolution When you resolve a conflict, the exclamation point to the left of the file name changes from red to white. To move the selected file to a private directory and change the file path in the package, click Move.

  • Page 43: Resolving Ini Conflicts

    Conflict Detection and Resolution In the Applications/Packages pane, select a package. The package’s conflicts appear in the Conflict List and are grouped by type. Resource Conflicts on page 16. If you do not see the conflicts you expected, select Conflicts menu > Filter and make sure the Errors and Registry Conflicts check boxes are marked.

  • Page 44: Restrictions On Resolving And Exporting Package Types

    Conflict Detection and Resolution If you are using package groups, select a group name in the Groups pane. The Applications/Packages pane displays only packages that are assigned to that group. In the Applications/Packages pane, select a package. The package’s conflicts appear in the Conflict List and are grouped by type. Resource Conflicts on page 16.

  • Page 45: Package Export After Conflict Resolution

    Conflict Detection and Resolution Group Policy Objects Conflicts between packages and Group Policy Objects are not typical conflicts that you can resolve by changing files or registry keys, rather, they are provided to inform you of packages that might override your group policies.

  • Page 46: Exporting A Single Package

    Conflict Detection and Resolution Export and recompile Export changes for all packages whose conflicts have been resolved. You also can have the installations recompiled automatically after exporting. Exporting and Recompiling Packages on page 47. In order for you to export a package: The original package installation must exist.

  • Page 47: Exporting And Recompiling Packages

    Conflict Detection and Resolution Overwrite existing installation Replaces the entire package installation with information in the Software Manager database. Merge changes with existing installation Adds only the conflict resolution changes to the existing installation. If you are exporting a Windows Installer package that you previously distributed to end users, select an option in Upgrade Type to change the installation so that it can function as an update.

  • Page 48: Conflictmanager Reports

    Conflict Detection and Resolution To export and recompile a package (Enterprise Management Server only.) If multiple databases are open, select a database in the Applications/Packages pane. Select Packages menu > Export and Recompile. The Export Changed Applications and Recompile dialog box appears. This lists all packages with conflict resolution changes that have not been exported.

  • Page 49: Generating A Conflictmanager Report

    Conflict Detection and Resolution Registry Conflicts By Key Lists all registry conflicts by registry key. The conflicts are grouped by registry key and arranged in each group by conflict level and application and package name. Generating a ConflictManager Report You can generate a ConflictManager report that displays in a report viewer window, from which you can save or print it.

  • Page 50: Saving A Conflictmanager Report Directly To A File

    Conflict Detection and Resolution Saving a ConflictManager Report Directly to a File You can generate and save a ConflictManager report to a file without opening it in the report viewer. You might do this if you want to generate a large report overnight. This involves creating an .INI file that contains the instructions for generating the report and then using a command line to generate the report.

  • Page 51: Interpreting The Conflict Level

    Conflict Detection and Resolution Interpreting the Conflict Level When you view a ConflictManager report in the report viewer, you can easily access a legend that explains the conflict level. Using the Report Viewer on page 50. If you save a report as a .CSV file, the conflict level appears as a number at the beginning of each conflict.

  • Page 52: Index

    Index Numerics unexpected 32 viewing 31 16-bit .DLLs 17 data source, select 9 Conflict Details pane database, Software Manager about 12 See Software Manager database refreshing 12 action, in resolution rule 24, 26 database, Wise Software Repository conflict detection See Software Manager database active database 10 during import 21, 30 date/time...
  • Page 53 file error 51 with components 38 permanent components, ignore with Resolve wizard 39, 40 conflicts 15 file hash with rules 26, 39 See hash value comparison predefined resolution rules 25 file size does not match 36 private directory 38, 40 filter, conflict display 33 process for resolving conflicts 29 KeyPath...
  • Page 54 automatically 39 system resource conflict 13 command unavailable 8 copying file 37 fixing component 41 test resolved package 29 individually 40 toolbar isolating files 38 ConflictManager 11 moving file 41, 42 transform process 29 cannot resolve or export 45 using latest file 41, 42 exporting to 47 with Resolve wizard 40 triggers...

This manual is also suitable for:

Conflictmanager

Table of Contents