1.

Preparation
AdminStudio 6 » AdminStudio Tutorial

Prior to running this tutorial, you need to install AdminStudio on a development machine. You also need to prepare a clean
machine on which you will repackage the setup used in this tutorial.

The tutorial is organized into four main steps: repackaging, enhancing the Windows Installer package, tuning, and identifying
and resolving conflicts. During each step, you save your output to existing folders included with the AdminStudio installation.

For purposes of this tutorial, <AdminStudio Directory> represents the directory in which AdminStudio is installed.

2. Repackaging
AdminStudio 6 » AdminStudio Tutorial » Repackager

The first step in the Application Migration/Predeployment process is to repackage a legacy setup. For purpose, you are going
to repackage PackageForTheWeb 3. This involves not only running the Repackaging Wizard to capture the data, but also
configuring options, excluding data, and building the repackaged setup into an InstallShield Editor project.

This section of the tutorial includes the following procedures:

 Launching Repackager Remotely

 Repackaging a Traditional Installation
 Customizing the Captured Data
 Building the InstallShield Editor Project and MSI Package

2.1 Launching Repackager Remotely

AdminStudio 6 » AdminStudio Tutorial » Repackager

The first step in this tutorial is to install the standalone version of Repackager on a production system, and then launch the
Repackager remotely from a clean system. A clean system is essential so that all changes are captured correctly and
ultimately converted into a Windows Installer package.

To launch the Repackager remotely:

1. On a production machine that does not contain AdminStudio, download and install a standalone version of
Repackager. To download the Repackager installation setup, go to the following URL:

http://support.installshield.com/kb/files/Q108601/setup.exe

When installation is complete, the Repackager executable will be located in the following directory on the
production machine:

\Program Files\InstallShield\Repackager\islc.exe

2. Share the Repackager directory on the production machine so it can be accessed from the network. This can
be done by right-clicking the directory in Windows Explorer and selecting Sharing from the context menu.

3. From your clean machine (where you will repackage a legacy setup), connect to the machine on which the
standalone version of Repackager is installed.

4. Navigate to the \Program Files\InstallShield\Repackager folder and launch islc.exe.

 5. After you have launched Repackager remotely, you need to launch the Repackaging Wizard, which you will use
to capture the PackageFromTheWeb setup. To do so, click the InstallShield Repackaging Wizard link on the
Start page in Repackager.

2.2 Repackaging a Traditional Installation

AdminStudio 6 » AdminStudio Tutorial » Repackager

The goal of this step is to repackage the setup into a Repackager project file, which can later be converted into a InstallShield
Editor project.

With the Repackaging Wizard launched as described in the tutorial topic Launching Repackager Remotely:

1. Launch the Repackaging Wizard as described in the tutorial topic Launching Repackager Remotely. The
Repackaging Wizard Welcome Panel opens.
2. Click Next. The Method Selection Panel opens.
3. In the Method Selection Panel, select Installation Monitoring and click Next. The Collect Product Information
Panel opens.
4. In the Collect Product Information Panel, provide product information as follows:
a.Click the Browse button (...) to the right of the Program File field and browse over the network to
<AdminStudio Directory>\Tutorial\Repackager\PackageForTheWeb 3 directory and select
PackageForTheWeb3.exe. When you return to the Collect Product Information Panel, the name of the
selected file appears in the Program File field, and information is automatically entered in the Product
Information area.

b.In the Product Information area, ensure the following values are entered:

Product Name PackageForTheWeb 3

Version 3.00

Product URL http://www.installshield.com

Support URL http://www.installshield.com

Company Name InstallShield Software Corporation

5. Click Next. The Set Target Project Information and Capture Settings Panel opens.
6. On the Set Target Project Information and Capture Settings Panel, click the Browse button (...) and navigate to
<AdminStudio Directory>\Tutorial\Repackager\Output.
7. Click Edit to change the capture settings. The Analysis Options dialog box opens.
8. In the Analysis Options dialog box, ensure Files, Shortcuts, INI files, and Registry data are selected, and
Deleted files, Non-.ini extensions, and Deleted registry data are cleared. The four selected capture types
ensure proper data is captured during repackaging; the three cleared capture types rarely occur, and can be
ignored for this tutorial.
9. Click OK to close the Analysis Options dialog box and return to the Set Target Project Information and Capture
Settings Panel.
10. Click Start. The Repackaging Panel opens displaying the repackaging progress.

When the initial system status analysis completes, the PackageForTheWeb 3 extraction Welcome Panel appears
prompting you to run the setup.
11. On the PackageForTheWeb3 extraction Welcome Panel, click Next to extract the program. After extracting
PackageForTheWeb, the PackageForTheWeb 3 Installation Welcome Panel appears.
12. On the PackageForTheWeb 3 Installation Welcome Panel, click Next. The License Agreement Panel opens.
 13. Read the license agreement. Accept the terms and click Next. The Customer Information Panel opens.
14. In the Customer Information Panel, enter your name and your organization's name. Click Next. The Destination
Folder Panel opens.
15. Click Next on the Destination Folder Panel. For this installation, allow PackageForTheWeb to install in its default
location. The Ready to Install the Program Panel opens.
16. From the Ready to Install the Program Panel, click Install. The Setup Status Panel opens.

When installation is complete, the InstallShield Wizard Complete Panel opens.

17. From the InstallShield Wizard Complete panel, ensure both options are cleared and click Finish. You are
returned to the Repackaging Panel and are prompted to analyze system status changes.
18. Click Process to complete the Repackaging process. When the Wizard finishes, the Summary Panel opens.
19. Click Finish.

2.3 Customizing the Captured Data

AdminStudio 6 » AdminStudio Tutorial » Repackager

After the Repackaging Wizard finishes, Repackager opens the PackageForTheWeb 3.irp file, which is the Repackager
project for the captured data. From Repackager, you can view the captured files, folders, shortcuts, and registry entries.
Notice that, despite configuring the Repackaging Wizard to capture INI file changes, none are recorded in the Repackager
project file. This is because there were no changes made to any INI files during the PackageForTheWeb setup.

For purposes of this tutorial, you are going to exclude one file which is unnecessary for the setup.

To eliminate the file from the setup you are building:

1. Click on Files and Folders to display the Files and Folders View.
2. Expand [ProgramFilesFolder].
3. Expand InstallShield.
4. Click on PackageForTheWeb 3. A list of files in that folder appears.
5. In the file list, click on Pftwwiz.chw.
6. Click Exclude.

When you build the Windows Installer package, Pftwwiz.chw will not be included in the MSI. However, if you find later that
the file is necessary, you can return to the Repackager project, reinclude it, and rebuild the MSI.

2.4 Building the InstallShield Editor Project and MSI Package

AdminStudio 6 » AdminStudio Tutorial » Repackager

Once you have finished configuring exclusions, you need to configure and build the InstallShield Editor project (.ism) and
Windows Installer package. This includes configuring advanced settings.

To configure advanced settings:

1. Click on Advanced Settings to display the Advanced Settings View.

2. Ensure all options are selected except for the following:

o Display only the Welcome dialog box during installation

o Use the language captured by Repackager as the language of the setup
o Map registry data to the appropriate ODBC tables
o Map NT Service events to the ServiceControl table
Once your advanced settings are configured, you can configure the repackaged output information and build the package and
InstallShield Editor project:
 To configure repackaged output settings and build:

1. Click on Repackaged Output to display the Repackaged Output View.

2. Ensure the InstallShield Editor Project is set to <AdminStudio Directory>\Tutorial\Repackager\Output\
PackageForTheWeb 3.ism.
3. Select the options to Create a Windows Installer package, and to build a compressed, single-file package. Clear
the Create a Setup.exe option.
4. Select to use the default InstallShield Editor template.
5. Click Build.

After the build finishes, the package and project are stored in <AdminStudio Directory>\Tutorial\Repackager\Output\
PackageForTheWeb 3.ism. Close Repackager (saving the Repackager project) and launch InstallShield Editor from the
AdminStudio Interface.

3. Modifying and Building a Windows Installer Installation

AdminStudio 6 » AdminStudio Tutorial » InstallShield Editor

InstallShield Editor, although primarily used in AdminStudio for converting Repackager output into Windows Installer
packages, is a full-featured authoring tool. Using it, you can create new Windows Installer packages, or open existing
Windows Installer packages and modify them, in addition to the workflow described in this tutorial. Consult InstallShield
Editor's online help for comprehensive authoring information.

This section of the tutorial includes the following procedures:

 Modifying the Project

 Adding a File and Setting the Key File
 Building the Release

3.1 Modifying the Project

AdminStudio 6 » AdminStudio Tutorial » InstallShield Editor

Once you use Repackager to create an .ism project, you can make customizations as necessary. For this tutorial, you are
going to add your name as the setup author, and add some authoring comments. You are also going to add a file to a
component and make it the key file.

To modify the project:

1. Launch InstallShield Editor from the AdminStudio Interface. The InstallShield Editor Start Page opens.
2. When InstallShield Editor opens, select Open from the File menu.
3. Browse to the <AdminStudio Directory>\Tutorial\Repackager\Output directory.
4. Select PackageForTheWeb 3.ism and click Open. The InstallShield Editor Installation Designer Tab opens.
5. Expand the Installation Information view in InstallShield Editor and select General Information. The
General Information View opens.
6. Select Project Properties from the General Information tree. Project Properties are listed.
7. Click in the Author Name field and enter your name.
8. Click in the Comments field and enter AdminStudio Tutorial.
9. From the File menu, select Save
3.2 Adding a File and Setting the Key File
AdminStudio 6 » AdminStudio Tutorial » InstallShield Editor

To add a file to an existing component and make it the key file:

1. In InstallShield Editor, expand the Organization view and select Components. The Components View opens.
2. From the Components tree, click and expand the Pftwwiz.chm component to display its views.
3. Click on the Files node below Pftwwiz.chm. The files associated with Pftwwiz.chm are listed.
4. In the File list, right-click and select Add.
5. Navigate to the <AdminStudio Directory>\Tutorial\Author\Files and select Keyfile.htm. Click Open.
6. If the Path Variable Recommendation dialog box opens, select the first option for the path variable and click OK.
Keyfile.htm appears in the File list.
7. Right-click Keyfile.htm and select Set Key File.
8. When prompted for confirmation, click Yes.

3.3 Building the Release

AdminStudio 6 » AdminStudio Tutorial » InstallShield Editor

Once you have made modifications to the InstallShield Editor project, you need to build it into a Windows Installer package
again to reflect those changes.

To build the release:

1. From the Build menu, select Build Release1.

2. Verify the build completes successfully by monitoring the information in the Build tab of the Output window.

When completed, the PackageForTheWeb 3.msi is located at:

<AdminStudio Directory>\Tutorial\Repackager\Output
3. Copy the PackageForTheWeb 3.msi to:
<AdminStudio Directory>\Tutorial\Author\Output
4. Close InstallShield Editor and launch Tuner from the AdminStudio Interface.

4. Customizing an Installation Using Tuner

AdminStudio 6 » AdminStudio Tutorial » Tuner

The Microsoft-recommended method of customizing Windows Installer-based installations is through a transform file. This
ensures that modifications are made outside of the base package. If you intend to deploy the same installation to different
sets of users with modifications of the installation, it is much easier to make the changes necessary in transform files, rather
than in the original Windows Installer package. This also protects the software vendor's original installation from being
modified incorrectly.

This section of the tutorial includes the following procedures:

 Opening the Package and Creating a Transform

 Prevalidation
 Customization
o Specifying Default Destination and Organization Information
o Configuring Features
o Adding Files to the Installation
 o Creating Shortcuts
o Configuring Add/Remove Programs Settings
 Postvalidation
 Packaging
 Further Customizations

4.1 Opening the Package and Creating a Transform

AdminStudio 6 » AdminStudio Tutorial » Tuner

To open the base Windows Installer package and create a new transform:

1. From AdminStudio, launch Tuner. The Welcome to Tuner View opens.

2. Select Create a new transform. The Create a New Transform View opens.
3. In the Base Windows Installer Package area, click Browse and navigate to the <AdminStudio
Directory>\Tutorial\Author\Output directory. Select the PackageForTheWeb 3.msi file and click Open.
4. In the Windows Installer Transforms area, click Browse and navigate to the <AdminStudio Directory>\
Tutorial\Tuner\Output directory and create a file called PFTW.mst. Click Save.
5. Ensure the Response Transform option is cleared.
6. Click Create. The Package Validation View opens.

4.2 Prevalidation
AdminStudio 6 » AdminStudio Tutorial » Tuner

The first step after creating the transform file is to run prevalidation on the original Windows Installer package. Tuner's
prevalidation process ensures the Windows Installer package you are customizing is valid according to a predetermined set of
guidelines. In most cases you will want to run prevalidation using Microsoft's Full MSI Validation Suite, a set of over 70
guidelines that ensure the package was created to Microsoft standards.

To begin prevalidation on the base Windows Installer package:

1. On the Tuner Package Validation View, select Prevalidation from the checklist to display the Prevalidation
View.
2. In the Evaluation File field, click the arrow and select Full MSI Validation Suite from the list, and ensure the
ICEs to Run field is set to All.
3. Select the Show "ERROR" messages check box, and clear both the Show "INFO" messages and Show
"WARNING" messages check boxes. If any errors occur during prevalidation, then the package fails the
validation process.
4. Click Start. Tuner begins the validation process, displaying its progress in the Output and Validation tabs of
the Output window.

When completed, a message appears indicating that the PackageForTheWeb 3.msi file has no validation
errors.

In the event that a Windows Installer package did have validation errors, it means that the package was not created to
Microsoft's guidelines. Consult the online help for information about handling invalid packages
4.3 Customization
AdminStudio 6 » AdminStudio Tutorial » Tuner

Tuner can be used for a wide variety of customizations, including changing default destination and organization information,
feature display and installation options, addition, modifications, and removal of files, INI files, registry information, and
shortcuts, and configuration of ODBC resources and NT services. Some of these modifications are more typical than others, so
this tutorial concentrates on those modifications.

4.3.1 Specifying Default Destination and Organization Information

AdminStudio 6 » AdminStudio Tutorial » Tuner

To specify default destination and organization information:

1. From the Tuner View List, expand Organization and select Product Properties to display the Product
Properties View.
2. Click on the value field for the Default Destination Path. Change the value to ProgramFilesFolder\
InstallShield\AdminStudio\6.0\PFTW. This becomes the default destination directory when you run the
setup.
3. In the Company Name value field, provide the name of your organization (up to 30 characters). This is the
default suggested organization when you run the setup.

The Default Destination Variable has been selected by the application vendor (or Repackager) for specific reasons.
Unless you have a substantial need to change it, you should avoid reassigning this value. Any changes have the
potential to seriously hamper the installation. In the event you do inadvertently change this value, select it from the grid
and click Reset to revert to the original value from the base Windows Installer package.

4.3.2 Configuring Features

AdminStudio 6 » AdminStudio Tutorial » Tuner

During customization, you can also change how features are presented during setup. For example, you may want a specific
feature installed by default, without giving a user the option to not install it from the Custom Setup panel during installation.

To configure this feature to work as described above:

1. On the Tuner View List, expand Organization and select Features from the View List. The Features View
opens.
2. Select PackageForTheWeb3NewFeature from the Features tree. Information for that feature is listed.
3. Enter "This feature is for the AdminStudio tutorial." in the Description field.
4. Click on the Visible property's value cell and change it to Not Visible.
5. Click on the Initial State property's value and change it to The feature is installed on the local drive.

With these configurations, this feature and all its associated files will always be installed on the target computer. The end user
will not have the opportunity to prevent the feature from installing because it will not be displayed in the Custom Setup panel
during installation.

4.3.3 Adding Files to the Installation

AdminStudio 6 » AdminStudio Tutorial » Tuner
One of the more common customizations to a setup is adding files. An example of when you might want to do this is if you
have a series of custom templates to include with the setup. You can configure these templates to be installed to the correct
location when the installation is performed.

To add files to the installation:

1. On the Tuner View List, expand System Configuration and select Files and Folders. The Files and Folders
View opens.
2. In the Source computer's directory tree pane, navigate to <AdminStudio Directory>\Tutorial\Tuner\
Files.
3. In the Destination computer's folders pane, right click on Destination Computer and select
ProgramFilesFolder from the Show Folder submenu (if ProgramFilesFolder is not visible). Expand this
folder until you see the PackageForTheWeb 3 folder. Select this folder.
4. Select the AdminStudioTutorial.htm and AdminStudioTutorial.txt files from the Source computer's files
pane and drag them to the Destination computer's files pane.

These files, which are not part of the original PackageForTheWeb installation, will be installed when this transform is used
with the base Windows Installer package.

4.3.4 Creating Shortcuts

AdminStudio 6 » AdminStudio Tutorial » Tuner

Another common customization to make with Tuner is to create additional shortcuts. These can be to files in the original
Windows Installer package, to files added during your customization, or to files already on the target system. In this example,
you are going to create a shortcut to Notepad in the PackageForTheWeb 3 folder.

To create the shortcut:

1. On the Tuner View List, expand System Configuration and select Shortcuts. The Shortcuts View opens.
2. Click on the folder where you want to add the shortcut. In this case, you are going to place the shortcut in the
PackageForTheWeb 3 folder in ProgramFilesFolder. However, since the ProgramFilesFolder is not
displayed in the Shortcuts View, right-click on the top-level Shortcuts folder and select ProgramFilesFolder
from the Show Folder submenu.
3. Expand ProgramFilesFolder, then InstallShield Software Corporation, so you can see the
PackageForTheWeb 3 folder.
4. Right-click the PackageForTheWeb 3 folder and select New Shortcut. Name this shortcut Notepad.
5. When Tuner displays the properties for the new shortcut, perform the following configurations:
a.Select the Icon property and click the Change Icon button in the pane below the properties grid.
b.Click Browse, navigate to the Windows directory, and double-click Notepad.exe.
c. Select one of the icons and click OK.
d.Change the Target Type to File from file system.
e.In the Target row, enter the value WindowsFolder\Notepad.exe.
f. Double-click the Run value and select Normal window from the drop-down menu.

When the installation is installed, this shortcut will be placed in the PackageForTheWeb 3 folder on the target system.

4.3.5 Configuring Add/Remove Programs

AdminStudio 6 » AdminStudio Tutorial » Tuner

Windows 2000 and XP provide additional functionality to the Add/Remove Programs control panel. Tuner enables you to
modify settings pertaining to this in your customization. In this example, you are going to disable the control panel setting
that allows users to modify a setup after it has been installed.

To set the Modify property in for Add/Remove Programs:

 1. From the Tuner View List, expand Application Configuration and select Add/Remove Programs to display the
Add/Remove Programs View.
2. Double-click the Value field to the right of the Disable Modify Button property.
3. From the drop-down menu, select Yes.

When this installation and transform are run on a Windows 2000 or XP operating system, users will not be permitted to use
the Modify function for this setup in the Add/Remove Programs dialog box.

4.4 Postvalidation
AdminStudio 6 » AdminStudio Tutorial » Tuner

After you have performed customizations, and prior to packaging the base Windows Installer package and transform, you
need to postvalidate it. This ensures that your transform did not introduce validation issues that were not present in the base
Windows Installer package. In some circumstances, you can use a transform to correct validation errors identified during
prevalidation. However, in this example, you are only concerned that you did not introduce errors within the transform.

To postvalidate the combination of the base Windows Installer package and transform file:

1. On the Tuner View List, expand Package Preparation and select Postvalidation. The Postvalidation View
opens.
2. Ensure that the ERROR box is checked, but the WARNING and INFO boxes are unchecked.
3. Select Full MSI Validation Suite as the Evaluation File.
4. Click Start. Messages will appear in the Output and Validation tabs of the Output window.

When postvalidation completes, you are informed that the combined Windows Installer package and transform are valid
according to Microsoft guidelines.

4.5 Packaging
AdminStudio 6 » AdminStudio Tutorial » Tuner

In the final part of this tutorial, you will package the original Windows Installer package and transform into a single
executable file (Setup.exe). This file will begin the installation, including all modifications you made.

To package the Windows Installer installation and transform:

1. In Tuner, select Packaging Wizard from the Project menu. The Packaging Wizard Location Panel opens.
2. Select the Network Location option and set the location to <AdminStudio Directory>\Tutorial\Tuner\
Output\Packaged. Click Next. The Setup.exe Panel opens.
3. Click the Create Installation Launcher box, and check both the include engine boxes. This ensures that,
should the Windows Installer engine not be installed on the target system, that it will be installed so that
installation of your package can occur. Click Next. The SMS Panel opens.
4. In the SMS Panel, ensure all boxes are unchecked and click Next.The Packaging Summary Panel opens.
5. Review the selected options and click Finish.The Packaging tab of the Output window displays the packaging
progress.

The executable, and all necessary files, are now stored at <AdminStudio Directory>\Tutorial\Tuner\Output\
Packaged.

4.6 Further Customizations

AdminStudio 6 » AdminStudio Tutorial » Tuner
Tuner is capable of many customizations not included in this tutorial. For example, your package may contain ODBC
resources, NT Services, or INI files that need configuration. Additionally, you may want to modify the files installed, or even
change registry settings. Tuner provides flexibility to create these types of customizations depending on your individual
needs. Please review the Customizing Installations section of this online help system for further details.

Identifying and Resolving Conflicts

AdminStudio 6 » AdminStudio Tutorial » ConflictSolver

ConflictSolver can identify and resolve conflicts that exist between multiple Windows Installer packages, ensuring proper
functioning of installations.

This section of the tutorial includes the following procedures:

 Opening ConflictSolver and Connecting to the Application Catalog

 Configuring ConflictSolver Options
 Creating a Group and Importing a Package
 Identifying Conflicts
 Resolving Conflicts and Reimporting the Package
 Checking for Conflicts a Second Time

Opening ConflictSolver and Connecting to the Application Catalog

AdminStudio 6 » AdminStudio Tutorial » ConflictSolver

The first step in using ConflictSolver is to launch it and connect to an Application Catalog. For purposes of this tutorial, use
the sample Access-based Application Catalog included with ConflictSolver, which contains information about common
Windows Installer packages.

To open ConflictSolver and connect to the Application Catalog:

1. From AdminStudio, launch ConflictSolver. The ConflictSolver Group View opens.

2. From the Catalog menu, select Connect. The Connect to Application Catalog dialog box opens.
3. In the Connect to Application Catalog dialog box, click the Recent tab and select the Sample database.
4. Click Open.

Configuring ConflictSolver Options

AdminStudio 6 » AdminStudio Tutorial » ConflictSolver

Before importing the package into the database and identifying conflicts, you need to configure the ConflictSolver options
pertaining to import, and conflict identification.

To configure these options:

1. In ConflictSolver, select Options from the Tools menu. The General tab of the Options dialog box opens.
2. Click Resolution to display the Resolution Tab.
3. Ensure the Perform resolutions against a transform file option is selected.
4. Click Conflicts to display the Conflicts Tab.
 5. Ensure that both Suppress options are unchecked. This enables you to see all messages about conflicts.
6. Under Predefined and Custom ACE Rules, select Conflict Types to have ConflictSolver check for all conflicts
by default.
7. Click OK to close the Options dialog box.

Creating a Group and Importing the Package

AdminStudio 6 » AdminStudio Tutorial » ConflictSolver

Once you have configured the default options, you can create a new group and import the package and transform into
ConflictSolver. You can then run conflict identification against it.

To create a new group:

1. On the ConflictSolver Products View, right-click on the root Groups node and select New Group.
2. Name the new group AdminStudio Tutorial.
3. Press Return.
To import the Windows Installer package and associated transforms:

1. Right-click the AdminStudio Tutorial group, point to Import select MSI Package. The Import Wizard MSI
Source Information Panel opens.
2. Next to the Select an MSI file field, click Browse, navigate to <AdminStudio Directory>\Tutorial\
Author\Output, and select PackageForTheWeb 3.msi.

3. Click the button in the Transforms area.

4. In the Transforms area, click Browse (...) and navigate to <AdminStudio Directory>\Tutorial\Tuner\
Output and select PFTW.mst.
5. Click Next. The Summary Panel opens.
6. Review the options selected in the Summary Panel and click Finish.

The Import process displays its progress in the Import tab of the Output Window.

Identifying Conflicts
AdminStudio 6 » AdminStudio Tutorial » ConflictSolver

Once you have imported the package and transform, you should identify conflicts between it and other packages in the
Application Catalog. For this tutorial, you are going to look for component conflicts between your package and Acrobat Reader
5.0.

To identify conflicts:

1. In ConflictSolver select Conflict Wizard from the Conflicts menu. The Conflict Wizard Welcome Panel opens.
2. On the Welcome panel, click Next. The Source Type Panel opens.
3. On the Source Type Panel, select Internal Application Catalog package and click Next. The Source Package
Panel opens.
4. In the Source Package panel, select PackageForTheWeb 3 (v3.00) from the AdminStudio Tutorial group.
Click Next. The Target Information Panel opens.
5. In the Target Information Panel, ensure only Adobe Acrobat Reader v5.0 (located in the Common group) is
selected. Click Next. The Conflict Options Panel opens.
6. In the Conflict Options Panel, click Clear All, and then select Components.
7. Ensure both the Run Resolution and Generate Options options are cleared.
8. Click Next. The Summary Panel opens.
 9. Review the settings for the Conflict Wizard and click Finish.

Messages for conflict identification are displayed in the Conflicts tab in the Output window.

When finished, you find that ACE04 and ACE06 conflicts exist between the PackageForTheWeb 3.msi/PFTW.mst
transform combination and Adobe Acrobat Reader v5.0. You can now resolve the conflicts.

Resolving Conflicts and Reimporting the Package

AdminStudio 6 » AdminStudio Tutorial » ConflictSolver

Once conflicts have been identified, you can resolve some conflicts automatically in the Conflicts view. Others may need
manual resolution using InstallShield Editor or Tuner. For this tutorial, all conflicts can be resolved manually.

To resolve identified conflicts:

1. Select the Conflicts view for PackageForTheWeb 3 (v3.00).

2. Notice in the Resolution Options area that a transform file is designated as the location to save all resolutions.
This is because you elected to use transforms for resolutions when setting up ConflictSolver options.
3. Change the Conflict Information list to Component Conflicts. This displays conflict details for each
component conflict identified. Expand each of the ACEs listed in this view to read specific information about the
conflicts.
4. Click Resolve All. The CARD Resolution Options dialog box appears prompting you to make a selection to
determine how conflict resolution will proceed.

The CARD Resolution Options dialog box only appears if the Maximize user flexibility in selecting
resolutions option is selected on the Resolution Tab of the Options dialog box.

5. Select Pftwwiz.chm and click OK. The Resolution Details dialog box opens, listing the proposed CARD
resolutions that will be made to the package.

The Resolution Details dialog box only appears if the Preview and approve all resolutions option is
selected on the Resolution Tab of the Options dialog box. If this option is not selected, this dialog box
does not appear. If you do not want this dialog box to appear, select the Don't show this dialog
again check box on the dialog box. This is equivalent to unselecting the Preview and approve all
resolutions option on the Resolution Tab of the Options dialog box.

6. Select all of the CARD resolutions click Approve. The identified conflicts are resolved.
7. Change the Conflict Information list back to Summary.

You can now reimport the package. This includes the PFTW.mst transform, as it is considered to be part of the original
package. The reimport also includes the PackageForTheWeb 3.mst transform which contains the resolutions you made.

To reimport the package and transforms:

With Summary selected in the Conflict Information list, click Reimport.

Checking for Conflicts a Second Time

AdminStudio 6 » AdminStudio Tutorial » ConflictSolver
Although optional, it is generally a good practice to check that the conflicts you automatically resolved were resolved
correctly. Doing so involves running the Conflict Wizard a second time and checking the package and resolution transform for
conflicts.

To verify conflicts have been resolved:

1. Select Conflict Wizard from the Conflicts menu.

2. On the Welcome Panel, click Next.
3. On the Source Type Panel, select Internal Application Catalog package and click Next.
4. On the Source Package Panel, select PackageForTheWeb 3 (v3.00) from the AdminStudio Tutorial group.
Click Next.
5. On the Target Information Panel, ensure only Adobe Acrobat Reader v5.0 (located in the Common group) is
selected. Click Next.
6. In the Conflict Options Panel, click Clear All, and then select Components.
7. Ensure both the Run Resolution and Generate Options options are cleared.
8. Click Next.
9. Review the settings for the Conflict Wizard on the Summary Panel and click Finish.

The messages about the conflict identification process are displayed in the Conflicts Tab of the Output Window. When
finished, you find that no conflicts remain.

Conclusion
AdminStudio 6 » AdminStudio Tutorial

This tutorial is by no means comprehensive; rather, it is designed as an introduction to the AdminStudio workflow for many
administrators. It is entirely possible that some aspects of AdminStudio will be used daily, while others infrequently. The
flexibility of AdminStudio ensures that—no matter what your needs are—you have the tools to address your application
migration needs.