Duplicate Package Tab

ConflictSolver is included with FLEXnet AdminStudio Professional and Enterprise Editions.

When you import a package into the ConflictSolver Application Catalog database, ConflictSolver checks specific identifiers that are selected on the Duplicate Package Tab to determine if that package has already been imported.

If ConflictSolver determines that you are attempting to import a duplicate package (based upon the selected identifiers), the Product Name Change Dialog Box appears, where you are given the opportunity to enter a name of your choosing to identify the duplicate package before the package is imported.

If ConflictSolver is performing a bulk import or reimport, it still identifies duplicate packages using the user-specified criterion. However, ConflictSolver will generate a unique displayed product name and allow the import to proceed without prompting the user.

Duplicate Package Tab Properties
Option	Description
PackageCode Property	Identifier of package product was installed from. No two non-identical .msi files should ever have the same package code.
ProductCode Property	Unique identifier for the particular product release, represented as a string GUID, for example {12345678-1234-1234-1234-123456789012}.
Product Language	The language the installer should use for any strings in the user interface that are not authored into the database.
ProductVersion	Version of the product in string format. The format of the string is: major.minor.build.
List of Transform Files	A list of the transformations associated with this package import operation.
[None Selected]	If you do not select any of these five identifiers, ConflictSolver checks the ProductName Property identifier to determine if a package is a duplicate.
Duplicate Package Naming Syntax	When it identifies a duplicate package, Application Manager generates a new name for that package using the syntax specified in this field. The default syntax is: [Manufacturer]_[ProductName] This means that if Application Manager encountered a duplicate package, it would pre-pend the duplicate's Product Name with the Manufacturer's name and, if necessary, append the Product Name with numbers. For example, the second time that PowerPoint is imported, its name would be changed to: Microsoft Corporation_PowerPoint To change the default naming syntax, edit this field. This generated name is displayed on the Product Name Change Dialog Box, and it is the name that will be displayed in the product tree on the left side of the ConflictSolver Main View. Changing this "display" name does not change the ProductName Property that appears in the title bar of the ConflictSolver Product View.

Example of Importing a "Duplicate" Package

One common reason why you might want to import the same package into your Application Catalog database more than once would be if you wanted to use FLEXnet AdminStudio 7.5 Tuner to create custom installation SKUs of a common MSI package to distribute to different departments in your organization, each installation including certain features that are appropriate for the department and excluding certain features that are not appropriate. For example, if you were distributing a copy of Microsoft Office, you could add transforms to the Microsoft Office MSI package so that:

Therefore, you might want to import the same package into your database more than once, each time with a different set of transformations. What happens when you import the package the second time depends upon the identifiers you selected on the Duplicate Package Tab. In this example:

If you select the List of Transform Files and ProductCode identifiers on the Duplicate Package Tab of the Options dialog box, ConflictSolver will not identify these two packages as duplicate, even though they have the same ProductCode, because they have a different set of transformations. Therefore, the Product Name Change dialog box will not appear, and the package will be imported with the same display name as the first package.

If you only select the ProductCode identifier on the Duplicate Package Tab of the Options dialog box, ConflictSolver will identify the second package as a duplicate because the two packages have the same ProductCode, and the Product Name Change dialog box will appear.

The options that you select on the Duplicate Package tab of the Options dialog box apply globally to all packages that you attempt to import; you cannot apply different identifiers to different packages. Also, since these options are saved in the FLEXnet AdminStudio Shared Directory, everyone using FLEXnet AdminStudio at your organization who shares the same directory will share the same Duplicate Package options.