Novell ADMINSTUDIO 9.5 User Manual page 1599

Hide thumbs Also See for ADMINSTUDIO 9.5:

Table of Contents

Change the destination of the component that installs the file in the MSI package

Open a transform file or MSI package in InstallShield Editor.

Once the project is open, navigate to the Components view, and select the component that contains the file

causing the conflict.

In order to quickly find the component name, go to the File Table via the Direct Editor view and search for the

file name. Then, check the component column for the component name.

Select the Destination field of the component from the Property grid and change it to a new destination.

that the application will still work using the new destination.

Select Save As from the File menu and save the changes as a Windows Installer Transform (.mst) file.

Open ConflictSolver and reimport this package with its transform file into your Application Catalog, and then

use the Conflict Wizard to check it against ACE23 again.

ACE 24 checks to see if registry entries with the same registry hive, key, and value name have the same data type

and value. If a registry entry with the same registry hive, key, and value name in a package is found in both the

source and target package, but the registry entry has a different data type or value, ACE24 fails.

The ACE24 Error String is displayed in the following format:

The registry entry [REGISTRY_ENTRY] in [PACKAGE1] conflicts with the same registry entry in the

[COMPONENT] in [PACKAGE2].

ACE24 can be used in conflict analysis when MSI Package, OS Snapshot File, or Marimba NCP File data

types are selected as either source or target packages. However, if you specify only Marimba NCP Files as your

source packages, ACE23 and ACE24 will be the only ACEs that you can select on the Conflict Options Panel of

the Conflict Wizard. All other ACEs will be unavailable.

Import support for Marimba Native Channel Packager (.ncp) files is included with the AdminStudio

Enterprise Edition.

AdminStudio 9.5 User Guide

Changing the destination may cause the application to break. Before changing the destination, verify

ADS-0950-UG00

Chapter 20: Analyzing Installations Prior to Deployment

Predeployment Test Reference

Troubleshooting