Novell ADMINSTUDIO 9.5 User Manual page 1099

Pre-Conflict Detection Planning
Task: To perform pre-conflict detection planning
1. Create a new SQL Server Application Catalog database using the Create command on the AdminStudio
Interface Catalog menu. See
Note •
Application Catalog. See
Application
2. Use the OS Snapshot Wizard to generate snapshots for the desktop(s) used by your company. See
Capturing an OS
3. Use ConflictSolver to create the necessary groups in the database to match how you will distribute these
packages. See
4. Import all OS Snapshot(s) into ConflictSolver using the bulk import process, and copy these snapshots into
their appropriate groups. See
5. If you intend to do conflict detection with
package in Tuner or InstallShield Editor to correct any conflicts that are found), then pre-import all Merge
Modules that are used by your packages, ideally using the bulk import process. If you are not performing
conflict detection on merge modules, you do not need to import merge modules.
6. Find out how these packages will be distributed and used in your enterprise, and then decide which ACEs you
need to use during conflict detection.
Conflict Detection Processing
Task: To perform conflict detection processing
1. Perform validation. Validation errors may not be serious, but you should be aware of them. Because the results
of the ConflictSolver Validation Wizard are not persisted in the database, you can use another product, like
Microsoft Orca, to do your validation, if desired. See
2. Use the bulk import process to import your packages into a temporary working group.
3. Select your most critical, important application (perhaps for each group), and run validation and the source-
only ACEs (ACE04, ACE05, ACE06) on it. If the package passes evaluation, then move it from the working
group into its appropriate group. This package will represent the baseline against which all subsequent
packages will be checked against.
4. Select your next package and run conflict detection with the ACE rules that you have identified as important
against the group that this package will be assigned to. Evaluate the results and move the package into its
appropriate group. Repeat the process. See
AdminStudio 9.5 User Guide
Chapter 13: Identifying and Resolving Application Conflicts Using ConflictSolver
Creating New Application
If you have AdminStudio Enterprise Edition, you can also connect to the AdminStudio Enterprise Server
Connecting AdminStudio Client Tools to the AdminStudio Enterprise Server
Catalog.
Snapshot.
Adding Groups.
Application Manager Command-Line
ADS-0950-UG00
Catalogs.
ACE12 (meaning that you have access/rights to manipulate the MSI
Performing Validation.
Identifying and Resolving
Best Practices for Conflict Detection
Functionality.
Conflicts.
1099