Module 3: Creating a Windows Installer Package Contents Overview Introduction to Creating a Windows Installer Package Repackaging an Application by Using WinINSTALL LE Modifying a Repackaged Windows Installer Package 10 Troubleshooting 16 Best Practices 18 Lab A: Creating a Windows Installer Package by Using WinINSTALL LE 19 Review 27 Information in this document is subject to change without notice The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended to represent any real individual, company, product, or event, unless otherwise noted Complying with all applicable copyright laws is the responsibility of the user No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation If, however, your only means of access is electronic, permission to print one copy is hereby granted Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property  2000 Microsoft Corporation All rights reserved Microsoft, BackOffice, MS-DOS, Windows, Windows NT, and PowerPoint are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A and/or other countries Other product and company names mentioned herein may be the trademarks of their respective owners Project Leads and Instructional Designers: Mark Johnson, Jay Johnson (Write Stuff) Instructional Design Consultant: Susan Greenberg Instructional Design Contributors: H James Toland III (ComputerPREP, Inc), Andy Sweet (S&T OnSite), Robert Deupree (S&T OnSite) Lead Program Managers: Jeff Clark, Don Pattee Program Manager: Ryan Calafato Technical Contributors: Blain Barton, Ken Rosen, Peggy See, Greg Stemp (S&T OnSite), Tammy White Graphic Artist: Julie Stone (Independent Contractor) Editing Manager: Lynette Skinner Editors: Wendy Cleary (S&T OnSite), Thomas Blood (Volt Technical) Copy Editor: Karen Johnson (S&T Consulting) Online Program Manager: Debbi Conger Online Publications Manager: Arlo Emerson (Aditi) Online Support: Eric Brandt (S&T OnSite) Multimedia Development: Kelly Renner (Entex) Testing Leads: Sid Benavente, Keith Cotton Testing Developer: Greg Stemp (S&T OnSite) Courseware Testing: Data Dimensions, Inc Production Support: Carolyn Emory (S&T Consulting) Manufacturing Manager: Rick Terek (S&T OnSite) Manufacturing Support: Laura King (S&T OnSite) Lead Product Manager, Development Services: Bo Galford Lead Product Manager: Gerry Lang Group Product Manager: Robert Stewart Module 3: Creating a Windows Installer Package iii Instructor Notes Presentation: 30 Minutes Lab: 30 Minutes This module provides students with the knowledge and skills to create Windows Installer Packages for deploying Microsoft® Windows® 2000 Professional and applications by using WinINSTALL LE In the lab, students will have the opportunity to repackage an application for Windows Installer by using WinINSTALL LE At the end of this module, students will be able to: Describe the difference between a native Microsoft Windows Installer package and a repackaged Windows Installer package Repackage an application as a Windows Installer package by using the WinINSTALL LE third-party repackaging application Modify a Windows Installer package by using the WinINSTALL LE thirdparty repackaging application Materials and Preparation This section provides you with the required materials and preparation tasks that are needed to teach this module Required Materials To teach this module, you need the Microsoft PowerPoint® file 1567b_03.ppt Preparation Tasks To prepare for this module, you should: Read all of the materials for this module Complete the lab Practice all of the delivery tips Become familiar with the Microsoft OEM System Builder Program and Web site by registering at http://www.microsoft.com/oem/ Review the Technical section of the Web site and the preinstallation process of other operating systems Read the following technical white papers located on the Trainer Materials compact disc: • Using WinINSTALL LE to Repackage Applications for the Windows Installer • The Windows Installer Service • Automated Deployment Options • Microsoft Internet Explorer Corporate Deployment Guide iv Module 3: Creating a Windows Installer Package Module Strategy Use the following strategy to present this module: Introduction to Creating a Windows Installer Package Describe how Windows Installer packages use Windows 2000 Professional to install applications Introduce the concept of repackaging an application Describe how Windows Installer packages are distributed Repackaging an Application by Using WinINSTALL LE Explain how WinINSTALL LE can be used to repackage an application in a three-step process Explain the importance of using a clean computer when taking the Before snapshot Explain how to install and configure an application in advance of taking the After snapshot Discuss the importance of taking the After snapshot immediately after students have installed and configured their applications Describe how the Discover wizard creates the Windows Installer package Modifying a Repackaged Windows Installer Package Explain how students can use the VERITAS Software Console to modify the file set contained in a repackaged application Describe the steps for adding application shortcuts to the repackaged application Explain how to add and remove files from a Windows Installer package Explain how to add descriptive information to a Windows Installer package Troubleshooting Discuss useful troubleshooting strategies when creating a Windows Installer package Best Practices Discuss the best practices for creating a Windows Installer package Customization Information This section identifies the lab setup requirements for a module and the configuration changes that occur on student computers during the labs This information is provided to assist you in replicating or customizing Microsoft Official Curriculum (MOC) courseware Important The lab in this module is also dependent on the classroom configuration that is specified in the Customization Information section at the end of the Classroom Setup Guide for course 1567B, Preinstalling and Deploying Microsoft Windows 2000 Professional Module 3: Creating a Windows Installer Package v Lab Setup There are no lab setup requirements that affect replication or customization Lab Results The lab in this module requires that students work on two computers (Computer A and Computer B) Performing the lab in this module introduces the following configuration changes on Computer A: Installation of WinINSTALL LE Creation of a share to the folder containing the WinINSTALL LE files Installation of the Hypertext Markup Language (HTML) Help Workshop application Addition of a desktop shortcut to the HTML Help Workshop folder Performing the lab in this module introduces the following configuration changes on Computer B: Creation of the C:\Storage folder Creation of the Hhelp.msi file in the C:\Storage folder Module 3: Creating a Windows Installer Package Overview Slide Objective To provide an overview of the module topics and objectives Lead-in In this module, you will learn how to create a Windows Installer package by repackaging an application Introduction to Creating a Windows Installer Package Repackaging an Application by Using WinINSTALL LE Modifying a Repackaged Windows Installer Package Troubleshooting Best Practices At the end of this module, you will be able to: Describe the difference between a native Microsoft® Windows® Installer package and a repackaged Windows Installer package Repackage an application as a Windows Installer package by using the WinINSTALL LE third-party repackaging application Modify a Windows Installer package by using the WinINSTALL LE third-party repackaging application Module 3: Creating a Windows Installer Package Introduction to Creating a Windows Installer Package Slide Objective Windows 2000 Professional and Applications To introduce how a Windows Installer package is created Lead-in Windows Installer packages use Windows 2000 Professional to preinstall and deploy applications Reference Computer Repackaging Application A Repackaged Application Contains A Repackaged Application Contains Preconfigured Software Preconfigured Software Use a Third-Party Repackaging Use a Third-Party Repackaging Application to Repackage an Application to Repackage an Application Application Install the Package from Removable Install the Package from Removable Media or a Network Share Media or a Network Share Package Software Distribution Point Use the illustration on the slide to introduce the process of creating a Windows Installer package Refer to the student notes for supporting details Windows Installer packages provide a way to deploy an installed and preconfigured application to new or existing computers by using Windows 2000 Professional Some applications come with Windows Installer packages already created for them If you have an application that does not include a native Windows Installer package, you can create a Windows Installer package by repackaging the application Repackaging an application means creating a Windows Installer package for that application based on the installation and configuration of the application By using a Windows Installer package, you provide users with applications that can be easily deployed to new or existing computers, can perform self-diagnosis and repair, and can be cleanly and safely uninstalled Windows Installer is a service that runs on a client computer to manage applications When you repackage an application, you install and configure the application on a reference computer once, based on user needs The reference computer runs only Windows 2000 Professional, and the sole purpose of the reference computer is to provide a computer on which to configure and repackage an application Module 3: Creating a Windows Installer Package You create a repackaged application by using a third-party repackaging tool The package contains the preconfigured application folders, files, shortcuts, ini files, and registry keys It also contains the instructions for how to install or remove the application After repackaging an application, you can install the application automatically on a client computer Use the runonce command to install the application from a software distribution point Note Windows 2000 includes the WinINSTALL LE repackaging application, which is manufactured by VERITAS Software WinINSTALL LE is located in the Valueadd\3rdparty\Mgmt\Winstle folder on the Windows 2000 Professional compact disc For OEM system builders, see the Microsoft OEM System Builder Program Web site at http://www.microsoft.com/oem/ for specific instructions about obtaining WinINSTALL LE Module 3: Creating a Windows Installer Package Repackaging an Application by Using WinINSTALL LE Slide Objective To describe how WinINSTALL LE can be used to repackage an application in a three-step process Lead-in You use WinINSTALL LE to repackage an application that does not have a native Windows Installer package Take a Before Snapshot Take a Before Snapshot Install and Configure Install and Configure the Application the Application Take an After Snapshot Take an After Snapshot The Configuration Is The Configuration Is Recorded Recorded Run the Setup Program Run the Setup Program The Configuration Changes The Configuration Changes Are Recorded Are Recorded \ Describe the steps to repackage an application Refer to the student notes for supporting details If your application does not have a native package, you need to create a Windows Installer package by repackaging the application Before you repackage the application, the repackaging tool must determine which files Windows Installer needs to copy and which registry settings it must change to install the application Repackaging an application by using WinINSTALL LE is a three-step process: Take a Before snapshot The Before snapshot is a record of the hard disk configuration on the reference computer, including folders, files, icons and shortcuts, ini files, and registry entries The Discover wizard needs this information to determine what to include in the Windows Installer package Install and configure the application After creating a record of the original hard disk configuration, you install the application on the reference computer by using the Setup program of the application After installing the application, you configure the application the way that you want it deployed to users Take an After snapshot After installing the application, you take an After snapshot to create a second record of the hard disk configuration on the reference computer When the After snapshot is complete, the Discover wizard finishes creating the Windows Installer Important VERITAS Software recommends that you have a minimum of 250 megabytes (MB) of available hard disk space on the reference computer for the temporary files that are created during the repackaging process When you take the After snapshot, these temporary files are automatically deleted 14 Module 3: Creating a Windows Installer Package Removing Files To remove a file from a Windows Installer package, perform the following steps: In the VERITAS Software Console, click the package name, and then under Title, click Files The complete list of application files appears in the right pane Click the file name, and then click Delete If you are prompted for confirmation to delete the file, click OK The file is removed from the group of files that will be installed when you deploy the Windows Installer package This action does not remove the file from the software distribution point; it just ensures that the file will not be included with the application when it is installed Important Do not use the Remove tab to modify the file set for an application The Remove tab does not delete files from the file set of the application; instead, this tab specifies files that are to be deleted from the user’s computer when the package is installed Any file specified in this section will be removed when the package is invoked Incorrect use of the Remove tab could leave computers inoperable after users invoke a package Modifying File Attributes To modify file attributes, perform the following steps: In the VERITAS Software Console, click the package name, and then under Title, click Files The complete list of application files appears in the right pane Double-click the file name In the File Properties dialog box, change the attributes as needed Module 3: Creating a Windows Installer Package 15 Adding Descriptive Information Slide Objective To explain how to add descriptive information to a Windows Installer package Lead-in The VERITAS Software Console allows you to add descriptive information that will be available to users who access a Windows Installer package through Add/Remove Programs Explain how to use the VERITAS Software Console to add descriptive information to a Windows Installer file Delivery Tip Explain that adding descriptive information to a Windows Installer package is a way to extend support service to customers and clients Demonstrate how to add descriptive information to a repackaged application Save the changes, and then show students how they can gain access to this information VERITAS Software Console - [Windows® installer Package Editor] File Edit View Windows Help Windows® installer Package WinINSTALL Limited WinINSTALL Limited Summary Name: WinINSTALL Limited Edition (Release) Version: 1.0 “Friendly” Name “Friendly” Name { 5625CDD0-84AB-11D2-BAC4-00104B948 Manufacturer: VERITAS Software NSMG Title General For More Information For Files More Information Shortcuts Registry Services Online Support: http://support.veritas.com Phone: (800)-555-0100 Technical Support Technical Support You can add descriptive information, including a technical support telephone number or a Uniform Resource Locator (URL), to an existing Windows Installer package This information is available to users in Add/Remove Programs, which is located in Control Panel, by clicking the name of the application and then clicking support information To add descriptive information to a Windows Installer package, perform the following steps: In the VERITAS Software Console, open your msi file Click the package name, and then click General On the Summary tab, supply the following required information Option Required information Name Give the application a descriptive, intuitive name, such as Travel and Expense Account Reimbursement Program Do not use an executable file name, such as Trvexp.exe Online Support Provide the URL where users can obtain additional information about the application This information appears in Add/Remove Programs under support information Phone Provide users with a technical support telephone number Tip If your organization has its own technical support personnel, supply an internal technical support number and an internal Web address instead of the vendor-supplied URL and telephone number when you modify package files provided by third-party vendors 16 Module 3: Creating a Windows Installer Package Troubleshooting Slide Objective To provide possible solutions to common problems that may occur when installing a repackaged application Err or A Repackaged Application Causes Unrelated Changes A Repackaged Application Causes Unrelated Changes Err or A “Missing File” Error Appears When You Run an Application A “Missing File” Error Appears When You Run an Application Err or Installation Fails Because of “Internal Error 2098” Installation Fails Because of “Internal Error 2098” Err or You Receive an “Icon Extraction” Error During Installation You Receive an “Icon Extraction” Error During Installation Err or You Receive an “Unable to copy open file” Error Message You Receive an “Unable to copy open file” Error Message Lead-in Here are some suggestions for solving problems that may occur when installing a repackaged application Describe each problem listed on the slide and the possible solutions Refer to the student notes for supporting details The following table describes possible solutions to common problems that may occur when installing a repackaged application Problem Possible solution Installing a repackaged application causes system configuration changes unrelated to the application Repackage the application again In the process, be careful not to make any changes after configuring the application and before taking the After snapshot Any changes that you make to the configuration will become part of the Windows Installer package After installing a repackaged application, a “missing file” error message appears when you try to run the application Repackage the application on a computer with only Windows 2000 Professional installed If any other applications or utilities are installed, the Discover wizard may not detect all of the components needed to install and run the repackaged application Installation fails because of “Internal Error 2098.” Use the VERITAS Software Console to remove the registry entry (which is specified in the error message) from the msi file This error occurs if the package tries to write to a registry key that is not supported by Windows Installer When installing an application, you receive the “Icon extraction failed with error code 1813” error message Click OK, and proceed with the installation This error occurs because some applications (including Microsoft Office 97) reference a dll file that does not actually include icons as an icon source The error message will not result in a failed installation Module 3: Creating a Windows Installer Package 17 (continued) Problem Possible solution When taking a snapshot, you receive the “Unable to copy open file Abort, Retry, Ignore?” error message Click Ignore, and continue creating the Windows Installer package Before you deploy the package, open the msi file in the VERITAS Software Console, and remove the problem file from the package This error occurs if the Discover wizard tries to include an open file (typically a log file) when taking either the Before or the After snapshot 18 Module 3: Creating a Windows Installer Package Best Practices Slide Objective To describe the best practices for repackaging an application for Windows Installer Create Shortcuts Before Taking the After Snapshot Create Shortcuts Before Taking the After Snapshot Lead-in Here are some best practices for repackaging an application for Windows Installer Describe the best practices for repackaging an application for Windows Installer Limit Packages to One Application for Each msi File Limit Packages to One Application for Each msi File Contact VERITAS Software for Technical Support Contact VERITAS Software for Technical Support Consider the following best practices for repackaging an application for Windows Installer: Create Start menu or desktop shortcuts before taking the After snapshot This is easier than using the VERITAS Software Console to add these items Limit a package to one application per msi file Although it is possible to install multiple applications and repackage them into a single msi file, you lose the ability to deploy, upgrade, or remove those applications individually For additional support for using WinINSTALL LE to repackage applications, contact VERITAS Software at http://support.veritas.com Module 3: Creating a Windows Installer Package Lab A: Creating a Windows Installer Package by Using WinINSTALL LE Slide Objective To introduce the lab Lead-in In this lab, you will repackage an application by taking a Before snapshot of the hard disk configuration, installing and configuring an application, and then taking an After snapshot Explain the lab objectives Objectives After completing this lab, you will be able to: Install WinINSTALL LE Take a Before snapshot of a computer running Microsoft Windows 2000 Professional Install and preconfigure an application on a reference computer Take an After snapshot of a reference computer to create a Windows Installer package Install a repackaged application Verify the installation and configuration of an application Prerequisites Before working on this lab, you must be familiar with the process of repackaging an application as a Windows Installer package 19 20 Module 3: Creating a Windows Installer Package Lab Setup In this lab, you will work with a partner One partner (Partner A) will install WinINSTALL LE and share the installation folder The other partner (Partner B) will prepare the reference computer and then run WinINSTALL LE from Partner A’s computer to create a Windows Installer package Partner A will then install the repackaged application and verify the installation Record the name of each partner’s computer below: Name of Partner A’s computer: Name of Partner B’s computer: Scenario You must install the HTML Help Workshop application on every computer in the company Management wants the application to be preconfigured for the user and easy for the user to install As a result, you must specify a number of configuration parameters for HTML Help Workshop before you deploy it to ensure that the application functions properly Estimated time to complete this lab: 30 minutes Module 3: Creating a Windows Installer Package 21 Exercise Installing WinINSTALL LE Scenario Before packaging the application, you must set up a client computer (Computer A) and install WinINSTALL LE Goal In this exercise, you will install WinINSTALL LE from the Windows 2000 Professional compact disc, and then share the installation folder Tasks Detailed Steps Important: Only Partner A should perform this exercise Install WinINSTALL LE a Log on as Administrator with a password of password b If necessary, insert the Windows 2000 Professional compact disc into your CD-ROM drive c If necessary, click Exit to close the Microsoft Windows 2000 CD screen d In Windows Explorer, navigate to the CD-ROM\ValueAdd\3rdParty\Mgmt\Winstle folder (where CDROM is the drive letter of your CD-ROM drive), and then doubleclick SWIADMLE.MSI Windows Installer installs WinINSTALL LE e In Windows Explorer, share the C:\Program Files\VERITAS Software\Winstall folder with the default share name f Close Windows Explorer 22 Module 3: Creating a Windows Installer Package Exercise Taking a Before Snapshot Scenario To create a Windows Installer package, you first must capture the system configuration settings on the reference computer before installing any applications to be deployed Goal In this exercise, you will run the WinINSTALL Discover wizard to take a Before snapshot of the current system configuration of the reference computer Tasks Detailed Steps Important: Only Partner B should perform this exercise Take a Before snapshot a Log on as Administrator with a password of password b Click Start, and then click Run c In the Run dialog box, in the Open box, type \\computer_name\winstall\discoz.exe (where computer_name is the name of Partner A’s computer), and then click OK d In the WinINSTALL Discover wizard, click Next e In the Specify the name of the application for which you are building the installation box, type HTML Help Workshop f In the Specify the path and filename for the data file (.msi file) where the information on this installation will be kept box, type c:\storage\hhelp and then click Next g In the Create Directory dialog box, click Yes to verify the creation of the new folder The WinINSTALL Discover wizard prompts you to select a drive on which to store its temporary work files h Ensure that [-c-] is selected, and then click Next The wizard prompts you to select the drives to be scanned for changes i Under Available Drives, click [-c-], click Add, and then click Next The WinINSTALL Discover wizard prompts you to select the files and directories to exclude from the scan j Click Next to accept the default settings The wizard takes the Before snapshot k In the Launch Application Setup Program dialog box, click OK The Run Application Setup Program dialog box appears Do not close the dialog box Module 3: Creating a Windows Installer Package 23 Exercise Installing and Preconfiguring an Application Scenario After you have logged the configuration settings on the reference computer by taking a Before snapshot, you need to install and configure the application that you just installed to ensure that it functions properly after it is deployed Goal In this exercise, you will install the HTML Help Workshop application and specify the configuration settings the way you want Windows Installer to install it Tasks Detailed Steps Important: Only Partner B should perform this exercise Install the HTML Help Workshop application a Insert the Student Materials compact disc into the CD-ROM drive b In the Run Application Setup Program dialog box, in the File name box, type CD-ROM\labfiles\htmlhelp\htmlhelp.exe (where CD-ROM is the drive letter of the CD-ROM), and then click Open HTML Help Workshop 1.2 Setup starts c In the License Agreement dialog box, review the license agreement, and then click Accept d On the Welcome page, click Next e On the Select Destination Folder page, in the Location box, ensure that C:\Program Files\HTML Help Workshop appears, and then click Next f On the Choose Type of Setup page, ensure that Complete is selected, and then click Next g On the Select Program Item Group page, verify that Create a new submenu called is selected and that HTML Help Workshop appears, and then click Next h On the Personalize HTML Help Workshop page, in the Name box, type NWTraders and then click Next Setup installs HTML Help Workshop i In the HTML Help Workshop Setup message box, click OK 24 Module 3: Creating a Windows Installer Package (continued) Tasks Click Start, point to Program s, point to HTML Help Workshop, and then click HTML Help Workshop In HTML Help Workshop, on the File menu, click Preferences c In the HTML Help Workshop Preferences dialog box, select the Automatically load last project check box d Select the Enable sound in HTML Help Workshop check box, and then click OK e On the desktop, create a shortcut to the HTML Help Workshop folder a b Configure HTML Help Workshop Detailed Steps Close HTML Help Workshop a Click Start, point to Programs, right-drag HTML Help Workshop to the desktop, and then click Create Shortcut(s) Here A shortcut to the HTML Help Workshop folder appears on the desktop b Restart the computer Module 3: Creating a Windows Installer Package 25 Exercise Taking an After Snapshot Scenario The system configuration settings on the reference computer have changed with the installation of an application You need to capture the new system configuration settings and determine the differences from the original settings The differences between the two configurations form the basis of the Windows Installer package Goal In this exercise, you will use the WinINSTALL Discover wizard to take an After snapshot of the current system configuration and create a Windows Installer package You will also delete the HTML Help Workshop application from the reference computer and then share the folder containing the Windows Installer package Tasks Detailed Steps Important: Only Partner B should perform this exercise Take an After snapshot a Log on as Administrator with a password of password b Click Start, and then click Run c In the Run dialog box, in the Open box, type \\computer_name\winstall\discoz.exe (where computer_name is the name of Partner A’s computer), and then click OK d In the WinINSTALL Discover wizard, ensure that Perform the ‘After’ snapshot now is selected, and then click Next The wizard takes the After snapshot and creates a Windows Installer package The Conversion Successful message box appears, which may list warnings that indicate that the package includes references to absolute paths that may not be available on all computers, or that Universal Naming Convention (UNC)-only shortcuts are not supported You can ignore these messages e f Remove HTML Help Workshop and share the folder containing the Windows Installer package In the Conversion Successful message box, click OK In the After Snapshot Complete message box, click OK a In Control Panel, double-click Add/Remove Programs b Ensure that Change or Remove Programs is selected, ensure that HTML Help Workshop is selected, and then click Change/Remove c In the Uninstall dialog box, click Yes, and then in the Uninstall message box, click OK d Close Add/Remove Programs, and then close the Control Panel e On the Desktop, delete the HTML Help Workshop shortcut f Share the C:\Storage folder with the default share name g Close any open windows, and then log off 26 Module 3: Creating a Windows Installer Package Exercise Installing a Repackaged Application and Verifying the Installation Scenario After you create the Windows Installer package, you need to test it by running it on another computer on the network After you run the package, you need to verify that the application is configured properly Goal In this exercise, you will install the repackaged application and verify that it is installed and configured correctly Tasks Detailed Steps Important: Only Partner A should perform this exercise Install HTML Help Workshop a Log on as Administrator with a password of password, if necessary b Click Start, and then click Run c In the Run dialog box, in the Open box, type \\computer_name\storage\hhelp.msi (where computer_name is the name of Partner B’s computer), and then click OK Windows Installer installs HTML Help Workshop Verify the installation and configuration of HTML Help Workshop a On the desktop, verify that the shortcut to the HTML Help Workshop folder appears b Click Start, point to Programs, point to HTML Help Workshop, and then click HTML Help Workshop c On the File menu, click Preferences The HTML Help Workshop Preferences dialog box appears Notice that the preferences that your partner configured have been applied d Click Cancel, and then quit HTML Help Workshop e Close any open dialog boxes, and then log off Module 3: Creating a Windows Installer Package Review Slide Objective To reinforce module objectives by reviewing key points Lead-in The review questions cover some of the key concepts taught in the module Introduction to Creating a Windows Installer Package Repackaging an Application by Using WinINSTALL LE Modifying a Repackaged Windows Installer Package Troubleshooting Best Practices How you deploy an application that has no native Windows Installer package? Repackage the application Why is it important to create a Windows Installer package on a computer that does not have any applications or utilities other than Windows 2000 Professional installed on it? If the reference computer has any applications installed, the Discover wizard may not be able to identify all of the components required to install and run the application If the Discover wizard is unable to identify all of the necessary components, the package may be incomplete, which can cause it to fail When you repackage an application, what must you so that the repackaging tool can determine the files that Windows Installer needs to copy and the registry settings that it needs to change in order to install the application? Use the Discover wizard to take a Before snapshot of the computer configuration Configure the application, and then use the Discover wizard to take an After snapshot 27 28 Module 3: Creating a Windows Installer Package After taking a Before snapshot, how can you ensure that all changes have been recorded in the registry and that all files used by the application have been closed? Shut down and restart the reference computer How you add shortcuts on the desktop for applications that not include them? Before taking an After snapshot, you can create the shortcut manually After taking an After snapshot, open the msi file in the VERITAS Software Console, and then add the shortcut You want to provide help and technical support information in Add/Remove Programs to users who will install deployed software How can you add this information to packages that you create? Open the msi file in the VERITAS Software Console, click General, and then type the help and technical support information ... package and a repackaged Windows Installer package Repackage an application as a Windows Installer package by using the WinINSTALL LE third-party repackaging application Modify a Windows Installer. .. between a native Microsoft® Windows? ? Installer package and a repackaged Windows Installer package Repackage an application as a Windows Installer package by using the WinINSTALL LE third-party repackaging... you can create a Windows Installer package by repackaging the application Repackaging an application means creating a Windows Installer package for that application based on the installation and