Novell ADMINSTUDIO 9.5 User Manual page 95

Table 2-4 • Best Practice ACEs
ACE Rule
ACE30
ACE31
ACE32
ACE33
AdminStudio 9.5 User Guide
Description
Checks to identify
components with different
ComponentIDs installing the
same key file to the same
directory. (A check for
KeyPath conflicts across
components.)
Checks to see if data exists in
the MoveFile MSI table that is
not being executed with an
associated MoveFiles action.
Checks entries in the Registry
table to identify any hard
coded paths in its Value field.
Checks to see if data exists in
the RemoveFile MSI table that
is not being executed with an
associated RemoveFiles
action.
ADS-0950-UG00
Result
If components with different
ComponentIDs installing the
same key file to the same
directory is identified, a
warning is generated.
If a package contains data in
the MoveFile table but not the
necessary actions to use this
data, a warning is generated.
If there are any hard coded
paths in the Value field of the
package's Registry table, a
warning is generated.
If a package contains data in
the RemoveFile table but not
the necessary actions to use
this data, a warning is
generated.
Chapter 2: Using the Process Assistant
ConflictSolver Process Assistant
CARD Resolution
If a product component is
installing a KeyPath file which
is also being installed by a
product with a different
Component Id, the KeyPath
ACE fails.
Consider whether a
MoveFiles action is needed
for your
InstallExecuteSequence
table. If so, open the MSI file
in InstallShield and add the
appropriate action to the
InstallExecuteSequence
table, or remove the unused
data from the MoveFile table.
Open the package file in
InstallShield Editor and
change any hard coded paths
in the Value field of the
Registry table to relative
paths.
Consider whether a
RemoveFiles action is needed
for your
InstallExecuteSequence
table. If so, open the MSI file
in InstallShield and add the
appropriate action to the
InstallExecuteSequence
table, or remove the unused
data from the RemoveFile
table.
95