Page 1 Wise Package Studio Reference...
Page 2 Copyright © 2009 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, and Altiris are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
Page 3: Technical Support
The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates.
Page 4 Licensing and registration If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/techsupp/ Customer service Customer service information is available at the following URL: www.symantec.com/techsupp/ Customer Service is available to assist with the following types of issues:...
Page 5 Consulting Symantec Consulting Services provide on-site technical Services expertise from Symantec and its trusted partners. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment, design, implementation, monitoring, and management capabilities. Each is focused on establishing and maintaining the integrity and availability of your IT resources.
Page 6: Table Of Contents
Contents Technical Support ............3 Chapter 1: Introduction to Wise Package Studio .
Page 7 Chapter 3: Creating Projects, Processes, and Tools ......54 About Projects ............54 Adding a New Project .
Page 8 Adding Advertising Options to Your Command Line......102 Adding a Repair Option to Your Command Line ......103 Editing Public Properties With a Command Line .
Page 9 Editing a Predefined Validation Rule ......... 155 Predefined Validation Modules .
Page 10 Destroyed Registry Entries Test Case ........198 Residual Files Test Case .
Page 11 Copying a Compiled Installation to an FTP Server........256 Performing an Administrative Installation of a Windows Installer Package .
Page 12: Chapter 1: Introduction To Wise Package Studio
Chapter 1 Introduction to Wise Package Studio This chapter includes the following topics: About Wise Package Studio on page 12 Repackaging Basics on page 14 Starting Wise Package Studio on page 16 The Workbench Interface on page 19 About the Wise Software Repository on page 23 Wise Package Studio Directories on page 24...
Page 13: Wise Package Studio Editions
Introduction to Wise Package Studio Repackaging Basics on page 14 Wise Package Studio Editions Wise Package Studio is available in two editions, each designed to fulfill the needs of a particular type of user. The edition you purchase determines what features are available to you.
Page 14: Repackaging Basics
Introduction to Wise Package Studio A single step to be performed in a process. A task can be associated with a Wise Package Studio tool or a third-party program. (Example: Microsoft Word or a drive imaging program.) Other tasks might not be associated with a tool or program, but might be something that you need to perform during the course of the process.
Page 15: Advantages Of The Windows Installer Format
Introduction to Wise Package Studio Many software installations are not in Windows Installer (.MSI) format. Repackaging those installations lets you take advantage of the Windows Installer features. In addition, Active Directory deployment requires .MSI format. Advantages of the Windows Installer Format on page 15.
Page 16: Starting Wise Package Studio
14 Starting Wise Package Studio To start Wise Package Studio Select Start menu > Programs > Symantec > Wise Package Studio > Wise Package Studio. If the Wise Package Studio Logon dialog box appears, log on as instructed by your Wise Package Studio administrator.
Page 17: If Your Logon Fails
Introduction to Wise Package Studio If Your Logon Fails Not available in Standard Edition. You cannot log on to Wise Package Studio if: You have not configured the Wise Software Repository in the Wise Repository Manager. See Configuring the Wise Software Repository in the Getting Started Guide.
Page 18 Introduction to Wise Package Studio Logon account Usage Requirements Current Windows Log on to Wise Package Studio as the The computer must be connected to a NT account currently logged-on Windows NT Windows NT domain. user. You must have an Enterprise Management Server license.
Page 19: The Workbench Interface
Introduction to Wise Package Studio The Workbench Interface When you start Wise Package Studio, you see the Workbench interface, from which you do most of your repackaging work. The left pane of Workbench contains the Project and Tools tabs, which you use to work on projects or run tools. When you are working on a project, you use the Projects tab and select the project from Active Project.
Page 20: When A Project Has No Process
Introduction to Wise Package Studio To Do Displays a record of to-do items that have been created for the current project. To- do items are entered by users and represent actions that must be taken while working on the project. Creating a To-Do List on page 84.
Page 21: The Tools Tab
Introduction to Wise Package Studio Workbench resizing tools. When a task is associated with a tool, click this link Active Project shows to toggle the project on which between task you are working. help and tool help. Process tasks. The Description tab displays help text for the active task. When you run a Web application tool, it opens in the Description tab.
Page 22: Resizing The Workbench Pane
Introduction to Wise Package Studio Workbench resizing tools. Available tools. The Description tab displays help text for the active tool. When you run a Web application tool, it opens in the Description tab. Resizing the Workbench Pane The toolbar contains resizing tools that let you resize the left Workbench pane and hide the right pane.
Page 23: About The Wise Software Repository
Introduction to Wise Package Studio About the Wise Software Repository Not available in Standard Edition. The Wise Software Repository™ is a collection of software packages, resources and information about those resources, project management information, and quality assurance data used by organizations as part of the repackaging process. This scalable repository provides a centralized point for managing software packages at any stage of deployment.
Page 24: Wise Package Studio Directories
Introduction to Wise Package Studio A single Wise Package Studio server can contain multiple repositories. However, only one repository can be active at a time. To change the active repository on a Wise Package Studio server, open the repository in the Wise Repository Manager.
Page 25 Introduction to Wise Package Studio Directory Contents 000, 001, and so on Source files that are associated with each package’s installation. The subdirectories are numbered sequentially. These subdirectories are created when: (Not available in Standard Edition.) You distribute a package to the share point directory. You import a package into the Software Manager database, and you distribute source files.
Page 26: About The Share Point Directory
Introduction to Wise Package Studio Directory Contents TaskFiles Log files and .INI files associated with tasks in the Wise Task Manager, which are given a .TMP extension. This directory is created the first time you run an (Not available in Standard operation that is managed by the Wise Task Manager.
Page 27: How Source Files Are Indexed
Introduction to Wise Package Studio Temporary .QUE files representing packages that have been distributed but not imported into the Software Manager database. Source files of installations you import into the Software Manager database. Package definition files (.WPF) that are created with Package Definition and all of the files specified by the definition file.
Page 28: Example: Populating The Share Point Subdirectories
Introduction to Wise Package Studio the file is stored in a second directory, 000\002. The result is a set of all the unique source files used by all the packages in the Software Manager database. Example: Populating the Share Point Subdirectories Not available in Standard Edition.
Page 29: Integration With Software Virtualization Solution
For more information about Software Virtualization Solution (SVS), search for Workspace Virtualization on the symantec.com Web site. Working with virtual software packages in Wise Package Studio You can use Wise Package Studio to create, edit, manage, and distribute virtual software packages.
Page 30: About Virtual Software Packages
Introduction to Wise Package Studio About Virtual Software Packages Not available in Standard Edition. Creation of virtual software packages In Wise Package Studio, you can use the following tools to create a virtual software package: Software Manager Software Manager lets you enable packages that are in the Wise Software Repository for the Software Virtualization Solution (SVS).
Page 31: Wise Package Studio File Types
In Test Expert, you can install and run a package in a virtual layer. When you finish the capture or testing operations, you can use Symantec SVS applet to delete or deactivate the virtual layer and restore the computer to its original state.
Page 32 Virtual Package Editor when you compile a .WVP file. A .VSA file is a portable virtual software package that becomes a virtual software layer when it is imported into Symantec SVS applet. A .VSA file is also created when you export a virtual software layer from Symantec SVS applet.
Page 33: Wise Package Studio Status Types
Introduction to Wise Package Studio Wise Package Studio Status Types Use the different statuses in Wise Package Studio to manage your packages and projects. Project Status Indicates the state of projects in Workbench. In the Standard and Professional Editions, a project can have either of two statuses: Open or Closed.
Page 34 The product release notes cover new features, enhancements, bug fixes, and known issues for the current version of this product. To access the release notes, select Release Notes from the Symantec program group on the Windows Start menu. Windows Installer SDK Help (Windows Installer Editor only) You can get technical details about Windows Installer from its own help system, which is written by Microsoft for a developer audience.
Page 35: Chapter 2: Setting Up Wise Package Studio
Chapter 2 Setting Up Wise Package Studio This chapter includes the following topics: Steps for Setting Up Wise Package Studio on page 35 About Wise Package Studio Security on page 38 License Management on page 47 Workbench Preferences on page 52 Steps for Setting Up Wise Package Studio Setting up Wise Package Studio consists of defining your corporate repackaging standards and applying those standards to various settings and templates in Wise...
Page 36 Setting Up Wise Package Studio Assign licenses that let users use Wise Package Studio. To perform this step, select Edit menu > User Licensing. Add users, add licenses, and assign licenses. Assigning Licenses on page 50. With Enterprise Management Server, you must add users in Security Setup. Creating Users on page 41.
Page 37 Setting Up Wise Package Studio To perform this step, run Windows Installer Editor and open the file Merge Module.wsm, which typically is located in the Windows Installer Editor\Templates directory. Save the customized template with a new name. See Creating and Editing Installation Templates in the Windows Installer Editor Help.
Page 38: Using The Initial Workbench Setup Project
Setting Up Wise Package Studio Using the Initial Workbench Setup Project Not available in Standard Edition. A predefined project named Initial Workbench Setup leads you through the setup of Wise Package Studio. Using this project ensures that you do not skip any important steps and helps you become familiar with the Workbench interface and its process- oriented approach.
Page 39: Integrating With Windows Nt Security
Setting Up Wise Package Studio After you create groups, you create users, assign licenses, and assign users to groups. The group assignment determines the user’s access to Wise Package Studio tools and functions within tools. Creating Users on page 41. Database security To provide an additional level of security, your database administrator can set permissions on tables in the Workbench and Software Manager databases.
Page 40 Setting Up Wise Package Studio Whether members of the group can view tabs and edit the project, process, and tool setups in Workbench. Which tools members of the group can use. Whether members of the group can use specific areas of Wise Package Studio. Example: Options under the Software Manager Settings folder allow access to specific functions in Software Manager.
Page 41: Predefined Security Groups
Setting Up Wise Package Studio After you create a group, you can assign users to it. Creating Users on page 41. Predefined Security Groups Enterprise Management Server only. The following security groups are predefined and cannot be deleted. WPS Administrator This group has permissions for all options and cannot be changed.
Page 42 Setting Up Wise Package Studio To add a user Select Edit menu > Security. The Security Setup dialog box appears. In the left pane, right-click a group and select Add > User. The Assign User Licensing dialog box appears. Mark one or more check boxes to assign licenses to the user and click OK. A new user appears in the list in the left pane and in the user entry fields in the right pane.
Page 43: Setting Software Manager And Conflictmanager Security
Setting Up Wise Package Studio Assign serial numbers after import Mark this to assign licenses to these users immediately. If you clear this check box, the users are added to the Unassigned group without license assignments. If the Assign User Licensing dialog box appears, mark one or more check boxes for the licenses to assign to the users and click OK.
Page 44: Setting Setupcapture Configuration Security
Setting Up Wise Package Studio Mark This Check Allows Access to Set for Set for Set for Set for Box in Security Admin Leaders Users Managers Setup Package Add and edit subscriptions; refresh Subscriptions subscriptions Group Setup Create, edit, and delete package groups;...
Page 45 Setting Up Wise Package Studio In Security Setup, you can set permissions that govern the configuration file used for SetupCapture and SOE Snapshot. The permissions selectively enable and disable certain user interface items, such as buttons and options. To access Security Setup, see Creating Groups and Setting Permissions on page 39.
Page 46: Setting Database Security
Setting Up Wise Package Studio Item Where it Appears When it is Disabled Settings button Welcome page of Both Allow Non-Shared Configuration File SetupCapture and SOE and Modify Configuration File on Share Snapshot Point are cleared Allow Non-Shared Configuration File is marked, and Modify Configuration File on Share Point is cleared, and the configuration file in the share point directory is selected...
Page 47: License Management
Setting Up Wise Package Studio Database Tables Permission to set for users other than administrator Workbench GroupBits Read-only GroupTools This prevents users from bypassing the built-in security in Wise Package Studio. SecurityGroups UserGroups Workbench UserPassword Read/write if users can change their own passwords;...
Page 48: About User Licensing Setup
Setting Up Wise Package Studio Company B (the same company as above) decides to start doing quality assurance testing. They assign one person to do quality assurance in addition to their repackaging duties. This company purchases one license of Quality Assurance. Process for assigning licenses Following is an overview of the steps you take to assign licenses.
Page 49: Adding Serial Numbers
Setting Up Wise Package Studio Adding Serial Numbers Not available in Standard Edition. Before you can assign licenses to users, you must add serial numbers to the Workbench database. Use the Add Serial Number dialog box, which appears: During logon, if the user logging on has not been assigned a serial number, and no serial numbers are available.
Page 50: About Evaluation Serial Numbers
Setting Up Wise Package Studio Server), you must install the Web application. See Installing Web Applications in the Wise Package Studio Getting Started Guide. About Evaluation Serial Numbers An evaluation serial number cannot be added to a database that contains production serial numbers.
Page 51: Deleting Serial Numbers
Setting Up Wise Package Studio To unassign a license, clear the check box. When you unassign a license, the user might be moved to a different group or the Unassigned group (Enterprise Management Server only). Predefined Security Groups on page 41. When you finish assigning licenses, click OK.
Page 52: Workbench Preferences
Setting Up Wise Package Studio If you delete the Quality Assurance serial number, the user is not moved to another group. If you delete the Enterprise serial number, the user is moved to the Wise Users group. Predefined Security Groups on page 41.
Page 53: Activating Suppressed Prompts
Setting Up Wise Package Studio Connecting to a Web Application on page 79. Activating Suppressed Prompts To reactivate prompts that you previously suppressed, select Edit menu > Preferences. On the Workbench Preferences dialog box, click the Prompts tab. Example: If an alert dialog box had a check box labeled Don’t show this message again, and you marked it, the prompt would appear here.
Page 54: Chapter 3: Creating Projects, Processes, And Tools
Chapter 3 Creating Projects, Processes, and Tools This chapter includes the following topics: About Projects on page 54 About Process Templates and Tasks on page 58 About Tool Setup on page 66 Help for Tasks and Tools on page 70 Command Line Options on page 72 Wise Package Studio Variables...
Page 55: Adding A New Project
Creating Projects, Processes, and Tools command-line options that are not already in your database, the tool and command-line definitions are copied to your database. Changes to an external process template do not affect existing local projects created with that template. External Process Templates on page 60.
Page 56 Creating Projects, Processes, and Tools When you change the status in Project Setup, it is changed in the Project Management tab as well, and vice versa. When a project has no process, the Project Management tab is unavailable and you must change the status here. Product Vendor Specify the company that produces the application.
Page 57: Duplicating Or Deleting A Project
Creating Projects, Processes, and Tools In an organization with mixed Professional and Enterprise Management Server licenses, when a user with a Professional Edition license creates a project, the Project Owner field does not appear. However, if a user with an Enterprise Management Server license opens that project, the Project Owner field appears and defaults to the Admin user.
Page 58: About Process Templates And Tasks
Creating Projects, Processes, and Tools To delete a project In Project Setup, right-click a project and select Delete. You cannot undo project deletion. Deleting a project removes the project record from the Workbench database. It does not delete any files, such as installation files, that are related to the project. About Process Templates and Tasks Not available in Standard Edition.
Page 59: Predefined Process Templates
Creating Projects, Processes, and Tools At the top of the left pane of Process Templates Setup is a drop-down list that lets you filter the process list to view all processes, only predefined processes, or only user- defined processes. (Enterprise Management Server only) If you are connected to an external database, you also see processes from the external database, which have (External) appended to their names.
Page 60: External Process Templates
Creating Projects, Processes, and Tools Repackage into .VSA format Leads you through the steps needed to repackage an installation as a Virtual Software Package. This process creates a virtual software archive file (.VSA). Repackage using WiseScript Leads you through the steps needed to repackage an installation as a WiseScript.
Page 61: Adding A New Process
Creating Projects, Processes, and Tools How external processes appear in Process Templates Setup Processes created by local users Master processes from the external database Adding a New Process Not available in Standard Edition. If the predefined processes do not meet your needs or if you require additional processes, you can use Process Templates Setup to create a new process.
Page 62: Adding Tasks To A Process
Creating Projects, Processes, and Tools Save the new process by clicking Close or by clicking another process or task in the Process Templates Setup dialog box. You can rearrange tasks after creating them. Organizing Tasks and Processes on page 66. Adding Tasks to a Process Not available in Standard Edition.
Page 63 Creating Projects, Processes, and Tools Workbench Tool The task requires the user to run a Workbench tool. On the Projects tab, clicking this task’s Run link starts the tool. About Wise Package Studio tools on page 87. When you select this option, the following fields appear: Tool Select the tool this task will start.
Page 64: Duplicating And Deleting A Process
Creating Projects, Processes, and Tools the previous task runs SetupCapture, and this task runs WiseScript Package Editor, you cannot run this task unless you’ve run SetupCapture to create the script file. If the tool associated with this task creates the file, clear the check box. Example: Clear the check box if this task is SetupCapture, which creates an installation package.
Page 65: Importing And Exporting Processes
Creating Projects, Processes, and Tools Security Setup determines whether you have access to Process Templates Setup. You can duplicate processes from an external database, which places a copy in your local Workbench database, along with any user-defined Workbench tools or command-line options used in the process that are not already in your database.
Page 66: Organizing Tasks And Processes
Creating Projects, Processes, and Tools The .WPR file is created. To import a process Select Edit menu > Process Templates. The Process Templates Setup dialog box appears. Right-click in the process list and select Import From File. In the Open dialog box that appears, specify the .WPR file to import and click Open. The process appears in the process list.
Page 67: Adding A New Tool
Creating Projects, Processes, and Tools List of Wise Package Studio tools on page 87. If you routinely use a third-party program in your processes, you can create a tool to run that program, then add a task to your processes to run that tool. Creating a tool for programs you use often lets you standardize the way that tool is used.
Page 68: Adding A Web Application As A Tool
Creating Projects, Processes, and Tools Other EXE This tool runs a program other than an installed application, or an application executable that is installed on a network drive. When you select this option, EXE and Icon appear. In EXE, specify the executable file on a network or local drive.
Page 69: Duplicating, Deleting, And Rearranging Tools
Creating Projects, Processes, and Tools In URL, enter the full path to the Web application, including the name of the computer on which the application resides. Example: http://computer_name/virtual_directory/application.asp Icon shows the icon that is associated with this tool. Browse to select a new icon. Other users must have access to the new icon file you select.
Page 70: Help For Tasks And Tools
Creating Projects, Processes, and Tools Deleting a tool cannot be undone. As an alternative, you can hide it from view in the Tools tab by marking its Hide from Tools tab in Workbench option. To rearrange tools The tools appear on the Tools tab in the same order they appear in Tool Setup. Select Edit menu >...
Page 71: Adding Wise Package Studio Variables To Help Text
Creating Projects, Processes, and Tools Type directly in the help text editor to author help. The text editor provides common formatting tools you can use to format the help text. The help text editor also contains the following tools: Insert Object Inserts an object, such as an image, into your help text.
Page 72: Command Line Options
Creating Projects, Processes, and Tools When the user displays the process in the Projects tab, the values of [ProjectDir] and [ProjectName] are displayed (Example, V:\Wise Share Point\Projects\Application1\Application1.wsi). Note When you display tool help in the Tools tab, the values for project-related variables are not displayed because the tools are not associated with projects.
Page 73: About Command Line Options For Tools
Creating Projects, Processes, and Tools Defining Command Line Options for Tools on page 73. After defining a command-line option, it appears in Options. If you are working with a predefined Workbench tool, the Options field changes to a drop-down list and you can select a predefined command-line option. About Wise Package Studio command-line options on page 268.
Page 74 Creating Projects, Processes, and Tools Click Add. A new option appears at the end of Options. Complete the lower section of the dialog box: Name Type a description of the tool. (Example: If this command-line option opens a Word document, enter Open default document.) Command Line (Optional.) Enter command-line options to change the default behavior of this tool or application.
Page 75: Wise Package Studio Variables
Creating Projects, Processes, and Tools Wise Package Studio Variables In some areas of Wise Package Studio, you can use Wise Package Studio variables to represent files, directories, and other information. (Example: You can use the [Sharepoint] variable to represent the current share point directory.) Variables are used Command-line options for tools associated with an application or other .EXE in Process Templates Setup and Tool Setup.
Page 76: Chapter 4: Repackaging Applications And Managing Projects
Chapter 4 Repackaging Applications and Managing Projects This chapter includes the following topics: About the Project and Tools tabs on page 76 Using the Projects Tab on page 76 Using the Tools Tab on page 78 Connecting to a Web Application on page 79 Managing Projects on page 80...
Page 77 Repackaging Applications and Managing Projects With Enterprise Management Server, Security Setup determines whether you have access to the Projects tab. To work on a process-oriented project Not available in Standard Edition. Click the Projects tab or press Alt+P. From Active Project, select a project that is associated with a process. A project is associated with a process when a process is selected in the Process field in Project Setup.
Page 78: Using The Tools Tab
Repackaging Applications and Managing Projects To work on a project without a process Click the Projects tab or press Alt+P. From Active Project, select a project that has no process. A project has no process when None is selected in the Process field in Project Setup.
Page 79: Connecting To A Web Application
Repackaging Applications and Managing Projects List of Wise Package Studio tools on page 87 About Capturing Applications on page 201 About ConflictManager in the ConflictManager Help About Linux Package Editor in the Linux Package Editor Help About Mobile Device Package Editor in the Mobile Device Package Editor Help About Software Manager in the Software Manager Help About Virtual Package Editor in the Virtual Package Editor Help About Windows Installer Editor in the Windows Installer Editor Help...
Page 80: Managing Projects
Repackaging Applications and Managing Projects Managing Projects Enterprise Management Server only. Use the Project Management tab in the right pane of the Projects tab to record information about a project at various stages of its lifecycle. You can then manage and track the project’s progress.
Page 81: Assigning Users To Tasks In A Project
Repackaging Applications and Managing Projects Note You also can update the project status in Project Setup. When you change the status in Project Setup, it is changed in the Project Management tab as well, and vice versa. Estimated Completion Date Specify the date on which you expect the project to be completed.
Page 82: Entering Time For Tasks
Repackaging Applications and Managing Projects To assign users to tasks in a project Click the Projects tab or press Alt+P. From Active Project, select a project that is associated with a process. In the right pane, click the Project Management tab. The tasks for the selected project appear.
Page 83: Viewing Project Metrics
Repackaging Applications and Managing Projects Click OK. The hours appear in the Actual Hours column. If Enter actual hours by in Workbench Preferences is set to Task, the sum of the task hours appears in Hours Completed. Viewing Project Metrics Enterprise Management Server only.
Page 84: Creating A To-Do List
Repackaging Applications and Managing Projects expand or collapse all the tool entries, right-click anywhere in the list and select Expand All or Collapse All. You cannot edit or delete the task or tool entries, but you can enter notes for each task entry.
Page 85: Workbench Reports
Repackaging Applications and Managing Projects Workbench Reports Not available in Standard Edition. Workbench contains reports that provide information about Workbench processes and projects. In Enterprise Management Server, the Management Reports Web application lets managers of repackaging teams generate predefined Workbench reports without purchasing additional Wise Package Studio licenses.
Page 86: Generating A Workbench Report
Repackaging Applications and Managing Projects Generating a Workbench Report To generate a Workbench report Not available in Standard Edition. From the Reports menu, select a report. The report opens in the report viewer window. From the report viewer window, you can do the following: View the date and time when the report was generated in the lower left of the report.
Page 87: Chapter 5: Wise Package Studio Tools
Chapter 5 Wise Package Studio Tools This chapter includes the following topics: About Wise Package Studio tools on page 87 List of Wise Package Studio tools on page 87 How Wise Package Studio tools interact with revision control on page 89 Application Isolation on page 89 ApplicationWatch...
Page 88 Wise Package Studio Tools ApplicationWatch. Command Line Builder. ConflictManager®, which helps you solve the problem of conflicting files and registry entries that often occur on end user computers, letting you avoid problems when deploying packages throughout your organization. See About ConflictManager in the ConflictManager Help.
Page 89: How Wise Package Studio Tools Interact With Revision Control
Wise Package Studio Tools addition to being available in Workbench, WiseScript Editor is embedded within Windows Installer Editor and appears when you create a custom action that calls a WiseScript. WiseScript Editor shares documentation with WiseScript Package Editor. See About WiseScript in the WiseScript Package Editor Help.
Page 90: Creating A Package That Isolates .Exes
Wise Package Studio Tools components, and ensures that other applications do not overwrite your version of shared components. This lets you proactively eliminate potential conflicts with other applications. Application Isolation operates on Windows Installer installation files and transform files. You can save the output of Application Isolation as an .MSI or, to avoid violating a license agreement by changing the .MSI, you can save the output as an .MST.
Page 91 Wise Package Studio Tools Installation Pathname Specify an installation in which to isolate .EXE files and click Next. You can specify an .MSI, an .MST, an .MSM, a .WSI, or a .WSM. If you specify an .MST, you can choose the same .MST in Updated Windows Installer File on the Isolation Complete page to append the results of the application isolation to that .MST, rather than overwriting it.
Page 92 Wise Package Studio Tools Mark whether to add support for self-repair of isolated files. Selecting Isolation Options on page 94. Click Next in either the Select OS Compatibility or Select Isolation Options page. If you specified the option to manually select which files to isolate, the Select Files to Isolate page appears.
Page 93: Specifying Os Compatibility For Isolation
Wise Package Studio Tools Specifying OS Compatibility for Isolation Not available in Standard Edition. In Application Isolation, the Select OS Compatibility page appears only if you chose to use manifests as the Isolation Method. Complete the page as follows: To specify OS compatibility for isolation Mark the operating system(s) to support: Support prior operating systems also Because manifests are a .NET technology that work only on Windows XP or...
Page 94: Selecting Isolation Options
Wise Package Studio Tools Selecting Isolation Options Not available in Standard Edition. To select isolation options In Application Isolation, the Select Isolation Options page appears only if you chose to use Windows Installer Isolated Components as the Isolation Method. Complete the page as follows: From Feature Options, mark one of the following options: Move files into the same feature as necessary and then isolate...
Page 95: Applicationwatch Exclusion List
Wise Package Studio Tools these files to a new installation. You can use this tool for informational purposes or to facilitate the creation of a new installation. ApplicationWatch produces a Windows Installer or WiseScript package. (WiseScript is not available in Standard Edition.) To completely recreate an installation, if you have the setup program that installed the application, use SetupCapture instead of ApplicationWatch.
Page 96 Wise Package Studio Tools On the Tools tab, double-click ApplicationWatch. If the Specify Target Installation File page appears, complete the page and click Next: Target Installation Specify the full path of a new or existing .MSI or .WSI file. In the Professional edition, you also can specify a .WSE file.
Page 97: Command Line Builder
Wise Package Studio Tools If a file that is used by a package in the Wise Software Repository is added, the Files in Repository dialog box appears and prompts you to add a version of the file that is in the repository. Adding Files From the Wise Software Repository on page 144.
Page 98: Creating A Command Line With The Command Line Builder
Wise Package Studio Tools Transforms The TRANSFORMS property is a list of transforms that Windows Installer applies when installing a package. Additional transform files (.MST) can be included in the package. These files can be corporate templates or other company-specific materials that are required by the end user.
Page 99 Wise Package Studio Tools Repair Repairs an application that is installed on the destination computer. Network Install Extracts the files in the installation package to a network location. Uninstall Uninstalls the installation package. Update Updates the installation package by applying patches. This is only available if you left the File Location section on the Welcome page blank.
Page 100: Adding Ui Options To Your Command Line
Wise Package Studio Tools Adding UI Options to Your Command Line The Command Line Builder lets you create a command line that sets UI options, which determine how much the end user interacts with the installation. See User Interface Levels in the Windows Installer SDK Help. You can set UI options for all versions of Windows Installer or for Windows Installer 3.0 only.
Page 101: Adding Logging Options To Your Command Line
Wise Package Studio Tools Quiet - No UI Displays no user interface during the installation. Passive - display a progress bar but no other prompts or messages Note These options are enabled only if Windows Installer 3.0 or later is installed on your computer.
Page 102: Adding Advertising Options To Your Command Line
Wise Package Studio Tools v - Verbose output Logs more detailed information about each event or error. + - Append to existing file Appends the log to an existing log file. ! - Flush each line to the log i - Status messages w - Non-fatal warnings a - Start up of actions Logs actions as they are started.
Page 103: Adding A Repair Option To Your Command Line
Wise Package Studio Tools Click Advertising Options. The Advertising Options dialog box appears. Complete the dialog box: m - Advertise to all users of machine u - Advertise to the current user t - Applies transform to advertised package Add a transform to the advertised installation. In the field below the check box, specify the transform file to include in the installation.
Page 104: Editing Public Properties With A Command Line
Wise Package Studio Tools Editing Public Properties With a Command Line For information on public properties, see Public Properties in the Windows Installer SDK Help. To edit public properties with a command line On the Define Command Line page, select Install or Network Install from Install Mode.
Page 105: Installtailor
Wise Package Studio Tools Prior to Windows Installer 3.0, you could only remove a patch by uninstalling the entire application. Beginning with Windows Installer 3.0, you can remove a single patch or a set of patches in any order without uninstalling the application. See Removing Patches and Uninstallable Patches in the Windows Installer SDK Help.
Page 106: About Installtailor Changes
Wise Package Studio Tools those selections. Because the installation is only simulated, no changes are actually made on your computer. Examples: Set certain features to be installed for a particular group of end users. Change the default target directory for all users that install an application within the corporate environment.
Page 107: Creating A Transform With Installtailor
Wise Package Studio Tools Editing InstallTailor Changes on page 108. Any changes that you make to the captured changes appear in the transform that InstallTailor creates. Creating a Transform with InstallTailor Note You cannot use InstallTailor™ to create a transform for an application that is already installed on your computer.
Page 108: Editing Installtailor Changes
Wise Package Studio Tools To add a value for a property, directory custom action, or feature, click Add and then select the appropriate command from the Add menu. Editing InstallTailor Changes on page 108. On the Capture Complete page, enter the following: If you are working with a process, Transform file name is set to [ProjectDir]\[ProjectName].mst, and Shortcut name is set to [ProjectName].
Page 109 Wise Package Studio Tools To add a property value to the transform On the Captured Changes page, click Add and on the Add menu, click Property Value. On the Property Value dialog box, enter the following and then click OK: Name Select the property from the list, which contains all the properties that are in the installation but do not appear in the Captured Changes list.
Page 110: Legacy Setup Conversion
Wise Package Studio Tools Legacy Setup Conversion Use Legacy Setup Conversion to convert the following types of setup programs into Windows Installer packages: Microsoft SMS (.IPF or SMS Conversion Guidelines on page 110 and .EXE) Converting an SMS Installation on page 111. Novell ZENWorks®...
Page 111: Converting An Sms Installation
Wise Package Studio Tools Only the installation of files, registry changes, and other system changes are converted. Custom dialog boxes, custom logic, and other settings are not converted. All the files that are available to the original installation must be available to the converted Windows Installer package at the same locations.
Page 112: Novell Conversion Guidelines
Wise Package Studio Tools occurred. (Example: An error occurs when files that were referenced by the source installation cannot be found.) To obtain a record of any conversion errors, click Save Errors or Print Errors. Click Finish. More errors might appear at this point, which have to do with saving in Windows Installer format.
Page 113: Converting A Novell Installation
Wise Package Studio Tools [Application Working Directory] [Application Custom Folder] [Inventory Disk] The Flag line in the [FileCopy] section of an .AXT file is ignored because it doesn’t apply to a Windows Installer package. Note If the Novell file you import was originally created with Novell snAppShot, the file extensions (.FIL) of source files may prevent file associations in COM registry keys from being assigned to the same component as the associated files.
Page 114: Wininstall Conversion Guidelines
Wise Package Studio Tools When the process is finished, the Conversion Complete page appears. It shows the results of the conversion and lists any errors or problems that might have occurred. (Example: If files referenced by the source installation could not be found, an error is displayed.) To obtain a record of the conversion errors, click Save Errors or Print Errors.
Page 115: Converting A Wininstall Installation
Wise Package Studio Tools The WinINSTALL Preinstall and Postinstall scripts might not convert correctly. Legacy Setup Conversion tries to convert them to Execute Program custom actions in MSI Script in Windows Installer Editor or to Execute Program script actions in Script Editor in WiseScript Package Editor. However, the actions might not be configured properly.
Page 116: Wisescript Conversion Guidelines
Wise Package Studio Tools Replace @Wininstall With If source paths in the WinINSTALL text file contain the variable @Wininstall, specify the value of the variable here. The value you specify replaces all instances of @Wininstall located in source paths. Replace @Server With If source paths in the WinINSTALL text file contain the variable @Server, specify the value of the variable here.
Page 117: Converting A Wisescript
Wise Package Studio Tools Converting a WiseScript To convert a WiseScript Before converting a script, open it and delete all Display Billboard, Display Graphic, and Add Icon script actions from the script. Do one of the following: On the Projects tab, click the Run link to the right of the task or tool associated with Legacy Setup Conversion.
Page 118: Installshield Professional Conversion Guidelines
Wise Package Studio Tools 10. Open the resulting package in Windows Installer Editor to view the converted file and to resolve reported problems. Pages in Installation Expert, such as the Files page, are populated based on the contents of the source installation. If you converted a .WSE, files are referenced from their original locations.
Page 119: Installshield .Msi Conversion Guidelines
Wise Package Studio Tools If the Select Source Format page appears, mark InstallShield® Professional and click Next. Complete the Specify Files page: Source Installation Specify the full path of the .IPR file to convert. Target Installation Specify the full path of a new or existing .WSI or .MSI in which to save the converted installation.
Page 120: Converting An Installshield .Msi Installation
Wise Package Studio Tools Exposes SQL Server configuration information Guidelines If you try to convert an .EXE and the conversion fails, use SetupCapture to repackage the installation. The conversion could fail because the .EXE: Is not an InstallShield .EXE. Does not contain an .MSI. If you try to convert an .MSI and the conversion fails, use Windows Installer Editor to customize the package.
Page 121: Altiris Rapidinstall Package Conversion Guidelines
Wise Package Studio Tools Open the converted installation in Windows Installer Editor. Mark this option to open the converted installation in Windows Installer Editor when the conversion is finished. You must use the Target Installation Browse button to enable this option. To remove certain parts of the installation from the conversion process, click Advanced on the Specify Files page.
Page 122: Converting An Altiris Rapidinstall Package
Wise Package Studio Tools Guidelines If default values were not provided for each user defined variable in a RapidInstall package (RIP), the converted .MSI package may fail. If a RIP did not specify a package title, a title is generated for the .MSI package using the file name of the RIP.
Page 123: Package Definition
Wise Package Studio Tools Package Definition Not available in Standard Edition. A Wise package definition file defines what is needed to install a package. At a minimum, this is a command line. However, it can also be the installation file itself, additional command lines, or any file that needs to be installed.
Page 124: Creating A Package Definition File
Wise Package Studio Tools Change a command line for a package that is already in the Software Manager database. See About Package Definition in the Software Manager Help. See also: Process for Deploying a Group in the Software Manager Help. Creating a Package Definition File Not available in Standard Edition.
Page 125 Wise Package Studio Tools Add Directory Adds the entire contents of the directory you select in the upper-left pane. If you select a file in the upper-right pane, it adds the entire contents of that file’s directory. Files and directories that are in the exclusions list are not added. The files with their paths appear in the lower pane.
Page 126 Wise Package Studio Tools If the file is this type Then do this A Microsoft hotfix that is in the We recommend that you first run the hotfix with the /? command-line package definition option to display a list of the command-line options for that particular hotfix.
Page 127: Setting Exclusions In Package Definition
Wise Package Studio Tools Setting Exclusions in Package Definition Not available in Standard Edition. You can specify files and directories to be ignored by Package Definition, which reduces the size of the package for distribution. You can exclude: A file. A directory.
Page 128: Patch Creation
Wise Package Studio Tools Note If you exclude a file or directory that is under a user profile, the user profile name is replaced with a variable that always represents the current user profile name. To apply the changes to this package definition file only, mark the check box at the bottom of the page.
Page 129: About Patch Sequencing
Wise Package Studio Tools If you compiled the installation as an .EXE, you need the .MSI for the installation because Patch Creation does not operate on .EXE files. The .MSI is created in the same directory as the .EXE during compile. Patching assemblies in the Global Assembly Cache Windows Installer 3.0 or later.
Page 130: Creating A Patch File
Wise Package Studio Tools Patch Updates Family Sequence Application1 Application2 Application1 Application1 Application2 These patches would be applied to the applications in this order: Family 100: A, C, D Family 200: B, D See also: Specifying the Patch Sequence on page 136 Patch Creation on page 128 Sequencing Patches and MsiPatchSequence Table in the Windows Installer SDK Help...
Page 131 Wise Package Studio Tools To add a previous version, click Add, complete the Previous Version Details page, and click OK. Specifying Previous Versions for Patches on page 133. If you are prompted to run an administrative installation, click Yes. The patch creation process, which is executed by the Microsoft-provided file PATCHWIZ.DLL, operates on uncompressed files only.
Page 132 Wise Package Studio Tools 13. Complete the Compile Patch page: Output .MSP file Specify a full path for the patch file that you distribute to end users. Advanced Settings Click Advanced to display the Advanced Patch Settings dialog box. Complete the dialog box and click OK.
Page 133: Specifying Previous Versions For Patches
Wise Package Studio Tools If the patch file could not be created, use this log file to determine the source of the error. See also: Patch Creation on page 128 About Patch Sequencing on page 129 Removing Patches in the Windows Installer SDK Help Specifying Previous Versions for Patches To specify previous versions for patches Access the Previous Version Details page.
Page 134: Advanced Upgrade Version Details
Wise Package Studio Tools of the package being upgraded. In most cases, you should select the relationship Base Version must be = Installed Version. This means that the previous version you used to create this patch must match the version installed on the destination computer.
Page 135: Adding A Digital Signature To A Patch
Wise Package Studio Tools Adding a Digital Signature to a Patch Windows Installer 3.0 or later only. Use the Specify Digital Signature Settings page to add an Authenticode digital signature to a patch file. Frequently, updating an application requires more privileges than that of a standard user, and only the administrator has sufficient privileges to run the update.
Page 136: Specifying The Patch Sequence
Wise Package Studio Tools To add a digital signature to a patch In the Patch Creation tool, on the Specify Upgrade Version page, mark Add a Digital Signature to the Patch and click Next. Creating a Patch File on page 130. Complete the Specify Digital Signature Settings page: Web URL Enter your organization’s Web site address.
Page 137: Specifying Advanced Patch Settings
Wise Package Studio Tools 20 (sequences are generated in increments of 10). If the selected patch belongs to multiple families, the first family found is used. Sequence Within Family Enter a number to specify the order in which this patch should be applied, relative to other patches in this patch family.
Page 138: Specifying Patch Removal Settings
Wise Package Studio Tools Create a log file Mark this to create a log file containing details of the patch creation. If an error occurs in the process, refer to this file for information about what caused the error. The log file has the same name you gave to the output .MSP file with the extension .LOG, and is in the same directory.
Page 139: Using Upgradesync
Wise Package Studio Tools Changes the PackageCode, ProductCode, and ProductVersion properties if necessary. Aligns component GUIDs. If GUIDs or key paths for the same component don’t match between the new and old .MSI, the component could inadvertently get deleted because Windows Installer does not recognize the components as being the same.
Page 140 Wise Package Studio Tools Small Update Select this to ship this package as a patch or reinstall. Small updates generally contain minimal updates such as changes to the contents of files. This option changes the package code. Minor Upgrade Select this to ship this package as a patch or reinstall. Minor upgrades generally contain changes such as new or removed features, files, or other items.
Page 141: Web Capture Conversion
Wise Package Studio Tools Web Capture Conversion Not available in Standard Edition. When you use Wise Web Capture, the file that results from the capture is an encrypted .MSI, with the extension .MSI_. You cannot open or install this encrypted file, but you can use Web Capture Conversion to decrypt it.
Page 142: Using Wise Task Manager
Wise Package Studio Tools Cancel the tasks of managed operations. You can cancel only the tasks of operations that you run. View a task’s log file to resolve problems if the task fails. View information about a task, including: Its status. Whether the task will be performed locally or on the Wise Package Studio server.
Page 143: Performing Server-Side Operations
Wise Package Studio Tools Log File Displays the log file’s location and any messages that were generated. If a task fails, use the Log File tab to determine the problem. If a task does not generate a log file, this tab does not appear. To change the tasks that appear, click Options on the Wise Task Manager dialog box.
Page 144: Adding Files From The Wise Software Repository
Wise Package Studio Tools Adding Files From the Wise Software Repository Not available in Standard Edition. The Files in Repository dialog box appears when a file that is used by a package in the Wise Software Repository is added to an installation. It might appear when you use SetupCapture, Legacy Setup Conversion, or ApplicationWatch.
Page 145: Chapter 6: Package Validation
Chapter 6 Package Validation This chapter includes the following topics: About Package Validation on page 145 Validating Installation Packages on page 146 About Customizing Validation Modules on page 148 Predefined Validation Modules on page 157 Windows Vista/Windows 7 Validation on page 158 About Package Validation Package Validation checks Windows Installer packages for errors based on rules in one or more validation modules.
Page 146: Validating Installation Packages
Package Validation Validating Installation Packages Use Package Validation to verify installation packages using predefined or customized validation modules. If you run Package Validation from the Tools tab, you can select a single package file or you can select a folder. If you select a folder, Package Validation can check all the .MSI or .MSM files in the folder.
Page 147 Package Validation The Performing Validation dialog box appears. Note The Windows Vista/Windows 7 Compatibility Checks validation module takes longer to run than others due to the nature of its validation checks. When the validation is complete, the View / Correct dialog box appears for single installation files and the View dialog box appears for multiple files.
Page 148: About Customizing Validation Modules
Package Validation Note The Correct button is not enabled when an issue is found by a custom action rule. Depending on how the custom action is written, the problem might be fixed automatically when it’s found, or you might need to fix the problem manually. 10.
Page 149: Selecting Validation Rules To Use
Package Validation If the Specify Target Installation File or Folder dialog box appears, select an installation file or folder and click Next. Click Customize on the Welcome dialog box. The Customized Validation Rules dialog box appears. Validation Files lists the predefined validation modules and any validation modules you’ve added.
Page 150: About Rules That Call A Custom Action
Package Validation Note When customizing a predefined validation module, customize a copy of the .CUB file to retain the original file. To select validation rules to use Do one of the following: On the Projects tab, click the Run link to the right of the task or tool associated with Package Validation.
Page 151: Adding A Rule That Calls A Custom Action
Package Validation Example: Suppose you want to check packages for hard-coded references to C:\ or D:\ and replace those references with the Windows Installer directory property INSTALLDIR. To do this, write a VBScript to find and replace the references and then display a message.
Page 152: About Validation Rule Sets
Package Validation Click Add to the right of the Validation Rules list and select DLL Rule, EXE Rule, or VBScript Rule. A details dialog box appears. Enter a unique name and description to identify this rule when it appears in the Validation Rules list.
Page 153: Adding A Validation Rule Set
Package Validation The underlined values in the conditions and actions might be truncated on the screen. When you include the action to display text, errors found by a custom rule set are displayed in the View / Correct or View dialog box. The error text is displayed with the question mark icon ( ).
Page 154 Package Validation The Conditions dialog box appears. In Which condition(s) do you want to check, mark conditions in the order they should be checked. The conditions you mark appear in the Rule description list. 10. If a condition contains underlined text, click the underlined text to open the Rule Details dialog box and specify its value.
Page 155: Editing A Predefined Validation Rule
Package Validation The Customized Validation Rules dialog box reappears, and the new rule set is displayed at the end of the Validation Rules list with its check box marked. 18. To add more rules to this validation module, either repeat this procedure or see Adding a Rule That Calls a Custom Action on page 152.
Page 156: Predefined Validation Modules
Package Validation Predefined Validation Modules Package Validation contains predefined validation modules that perform the tests described below. Windows 2000 Application Specification Logo Runs logo.cub, which is provided by Microsoft as part of its Windows 2000 logo verification program. The tests in logo.cub are a subset of the tests in darice.cub, therefore, running both tests at the same time might result in duplicate errors.
Page 157: Windows Vista/Windows 7 Validation
Windows Vista or later operating system and specify the full path to WiseVistaIce.cub. Example: "C:\Program Files\Symantec\Wise Package Studio\bin\getwrpitems.exe" "C:\Wise Share Point\Validation\wisevistaice.cub" The GetWRPItems.exe utility deletes the contents of both tables and rebuilds them based on the WRP information on your computer.
Page 158 Package Validation the rebuilt files, run the utility on the edition of the operating system that your installations target. Wise Package Studio Reference...
Page 159: Chapter 7: Test Expert
Chapter 7 Test Expert This chapter includes the following topics: About Test Expert on page 159 Opening a Package in Test Expert on page 160 About Test Cases on page 164 Test Case Reference on page 172 Installation Tests on page 173 Standard Tests on page 177 Application Verification Tests...
Page 160: Opening A Package In Test Expert
Test Expert If you create your own test cases, you must run them manually outside Test Expert. Opening a Package in Test Expert Quality Assurance module only. To test a Windows Installer package or group of packages, open it in Test Expert. Ideally, testing is done on a clean machine with all other applications closed to prevent interference with test results.
Page 161: Setting Test Expert Preferences
Test Expert The Select Transforms dialog box appears. Click Add and specify the transform. Specify additional transforms if necessary. The transforms are applied to the package in the order they appear in the list. To rearrange the order, select a transform and click Move Up or Move Down. Click OK in the Open Application/Package dialog box.
Page 162 Test Expert Right pane of Test Expert Opens the test plan for a Windows Installer package or group. Master Test Plan. Click Test Plan Details to display the master test plan in the right pane. Test Groups. Only groups that contain test cases are shown.
Page 163: Loading, Saving, And Clearing Results Files
Test Expert Master Test Plan view in Test Expert Test Case Statistics for the test cases Test Item Statistics for the test items that make in the Test Case column. up test cases. File Information appears if a package is open.
Page 164: Installing An Installation Test Into A Virtual Software Layer
When you run an installation test, you can install the package into a virtual software layer. After you finish testing the package, you can use the Symantec SVS applet to delete or deactivate the virtual software layer. If you run the uninstall tests, the layer is deleted.
Page 165: Running A Test Case
Test Expert Test case view in Test Expert Buttons. Use the buttons that appear here to start tests. Statistics area Test Case. When you select summarizes the a test case, its test items test items for the appear in the lower-right currently displayed pane.
Page 166: About Testing Groups Of Packages
Test Expert About Testing Groups of Packages Running a test case for a Software Manager group is slightly different from running a test case for a single package. When a group is open, you see a Package drop-down list at the top of Test Expert. This lists the packages in the group.
Page 167 Test Expert Test case and test item statuses in Test Expert Status of Test Case. Set the overall status of the selected test case, which, in this example, is File Extensions. Status of Test Cases. This shows the overall status for each test case.
Page 168: Determining Your Test Environment
Test Expert Determining Your Test Environment Quality Assurance module only. You can use Test Expert to run tests on a clean machine, a baseline machine, or both. The test environment you choose depends on your organization’s requirements. A clean machine contains only the operating system, service packs, and runtimes of a typical computer in your organization.
Page 169: Machine Capture Settings
Test Expert To test on multiple computers Make sure the package to be tested is in the share point directory. Perform a Server installation of Wise Package Studio on a server. Perform a Client installation of Wise Package Studio Client on the testing computers. This installs only the shortcuts and support files needed to run Wise Package Studio.
Page 170: Setting A File, Wildcard, Or Directory To Be Ignored During Uninstall Tests
Test Expert To set directories to be watched for uninstall tests Start Machine Capture by clicking Install or Install As in Test Expert. The Welcome dialog box appears. Click Settings. On the Machine Capture Settings dialog box, click the Directories to Watch tab. Add directories to watch: Click Add.
Page 171: Setting Registry Entries To Be Ignored During Uninstall Tests
Test Expert In File/Wildcard, do one of the following: Specify a file. Specify a wildcard for part of the file name. Enter * to represent any number of characters, or enter ? to represent any single character. You can enter multiple wildcards separated by semicolons.
Page 172: Adding A User-Defined Test Case
Test Expert Click OK. To edit an exclusion, double-click it in the list. See also: Setting Directories to be Watched for Uninstall Tests on page 169 Setting a File, Wildcard, or Directory to Be Ignored During Uninstall Tests on page 170 Uninstall Tests on page 193 Adding a User-Defined Test Case...
Page 173: Installation Tests
Test Expert Standard Tests on page 177 Check Internet Connection on page 178 Check Network Location on page 178 Database Connectivity on page 179 Execute Program on page 180 Application Verification Tests on page 180 Class IDs Test Case on page 181 File Extensions Test Case on page 182 Help Files Test Case...
Page 174: How To Run Installation Tests
Test Expert When you run an installation test, you can install the package into a virtual software layer. Installing an Installation Test into a Virtual Software Layer on page 164. During installation tests, you can run Machine Capture to create a pre-installation snapshot of the computer.
Page 175 Test Expert If the Software Virtualization Agent is installed on the computer, the Welcome dialog box of the Installation Test wizard appears. Otherwise, the Machine Capture dialog box appears. If the Welcome dialog box appears, specify whether to install the application into a virtual software layer and click Next.
Page 176: Launch Conditions Test Case
Test Expert See also: Setting Test Statuses and Details on page 166 Launch Conditions Test Case on page 176 OS Conditions Test Case on page 176 Verify Installation Test Case on page 177 Launch Conditions Test Case Quality Assurance module only. If Test Expert detects launch conditions in a package, the Launch Conditions test case appears.
Page 177: Verify Installation Test Case
Test Expert Use the Verify Installation test case to install the package on the required operating system. Run the application execution tests. If the application performs as expected, the component was probably installed correctly. To verify whether a component was installed, open the .MSI, determine its component GUID, and then search the registry for that component GUID.
Page 178: Check Internet Connection
Test Expert results. Standard tests are stored in the repository and are not available without a repository, such as with the Standard Edition. Requirements Each standard test must be set up with relevant parameters. Because standard tests are stored in the repository, they are shared among team members. See also: Check Internet Connection on page 178...
Page 179: Database Connectivity
Test Expert Requirements The current user profile must have a valid network connection and appropriate permissions. To set up and run the test case Select the Check Network Location test case in the left pane of Test Expert. Click Add. The Check Network Location dialog box appears.
Page 180: Execute Program
Test Expert Use the Edit button to change a test item configuration. Use the Delete button to remove a test item. To run the test item, select its check box and click Execute. Execute Program Quality Assurance module only. Use this test case to run any executable program. You can use WiseScript Editor, WiseScript Package Editor, or another development environment to create a wide variety of tests in executable form.
Page 181: Class Ids Test Case
Test Expert See also: Class IDs Test Case on page 181 File Extensions Test Case on page 182 Help Files Test Case on page 183 ODBC Data Sources Test Case on page 184 Prog IDs Test Case on page 184 Search Locations Test Case on page 185 Services Test Case...
Page 182: File Extensions Test Case
Test Expert File Extensions Test Case Quality Assurance module only. If Test Expert detects file extensions in a package, the File Extensions test case appears. This test creates a list of verbs associated with each extension in the package. It prompts you to select a file of the type being tested.
Page 183: Help Files Test Case
Test Expert To verify that the application accepts the command-line option and argument, run it from the command line. If it fails from the command line, the command-line option and argument are incorrect, or the program is not coded to accept them. See also: About Test Cases on page 164...
Page 184: Odbc Data Sources Test Case
Test Expert ODBC Data Sources Test Case Quality Assurance module only. If Test Expert detects ODBC data sources in a package, the ODBC Data Sources test case appears. Use it to check whether an ODBC data source has been created correctly and whether the data source is accessible.
Page 185: Search Locations Test Case
Test Expert Click Execute. Test Expert examines the ProgID descriptions, tries to create objects based on those ProgIDs, and then marks each test as either passed or failed. When the tests are finished, the dialog box closes and the statuses are displayed in the Status column.
Page 186: Services Test Case
Test Expert To troubleshoot failures To see the returned error, double-click an item and look in the Test Details field on the Test Item Details dialog box. If a search location does not exist or is not accessible, either open the package and remove the search location, or work with your system administrator to make the location accessible to the lowest privilege level on which you expect the installation to run.
Page 187: Shortcuts Test Case
Test Expert Shortcuts Test Case Quality Assurance module only. If Test Expert detects shortcuts in a package, the Shortcuts test case appears. This test verifies that shortcuts in the installation are attached to a valid target file and that the target opens when the shortcut is opened.
Page 188 Test Expert would want to do so, because running each test requires a complete exercise of the application’s functions. During application execution tests, an Application Monitor window appears. A series of graphs represent the percentage of items that have been accessed so far during testing. For details of each graph, see the individual test case descriptions.
Page 189: How To Run Application Execution Tests
Test Expert File Coverage Test Case on page 191 Isolated Files Test Case on page 192 Registry Coverage Test Case on page 193 About Test Cases on page 164 How to Run Application Execution Tests This procedure applies to all application execution tests. Note A security setting in Windows Vista or later operating system prevents application execution tests from working.
Page 190: Extra Files Test Case
Test Expert Typically, you will select an .EXE, but you can also select any other file type. (Example: If the package installs an HTML help system, you might open an .HTM or .ASP file.) To open non-.EXE files, change Files of type to All Files. When the application starts, exercise all functions of the application.
Page 191: Extra Registry Entries Test Case
Test Expert and the system error that resulted. In general it is not an error if an application accesses shared files. It could become a problem if the application depends on the file but makes no attempt to install it if it is missing. The Application Monitor window shows the extra files accessed as a percentage of the number of files that are installed.
Page 192: Isolated Files Test Case
Test Expert time, the test items for every test case in the Application Execution Tests group are updated simultaneously. Before you run this test, close all applications other than Wise Package Studio and Test Expert, including all background applications and services that might access files or registry entries on the testing computer.
Page 193: Registry Coverage Test Case
Test Expert Registry Coverage Test Case Quality Assurance module only. The Registry Coverage test case in Test Expert monitors the testing computer as you exercise the features of the application. It then records what installed registry entries are accessed during application execution. Because all application execution tests are run at the same time, the test items for every test case in the Application Execution Tests group are updated simultaneously.
Page 194: How To Run Uninstall Tests
Test Expert You can configure Machine Capture settings to limit the areas of the computer that are captured in the snapshot. Machine Capture Settings on page 169. Installation tests and uninstall tests do not appear if you opened a cached copy of an .MSI.
Page 195: Created Files Test Case
Test Expert Note Rerunning the uninstall replaces previous uninstall test results. An uninstall is performed, and then the Welcome dialog box of Machine Capture appears. On the Welcome dialog box, click Next. The Capturing Machine State dialog box appears and the scan begins, which takes a few moments.
Page 196: Created Registry Entries Test Case
Test Expert examine custom actions that appear in MSI Script. Sometimes custom actions call processes during installation that result in created files. If the package creates files that should be removed on uninstall, you can set the package to remove them, as long as the files have fixed names. To do this, open the package in Windows Installer Editor.
Page 197: Destroyed Files Test Case
Test Expert Destroyed Files Test Case Quality Assurance module only. The Destroyed Files test case in Test Expert shows files that existed on the computer before installation, but were missing after uninstall. Note Uninstall tests do not appear if a group is open. After uninstall tests are run, the test case list is populated with destroyed files and all statuses are set to Pending.
Page 198: Destroyed Registry Entries Test Case
Test Expert Destroyed Registry Entries Test Case Quality Assurance module only. The Destroyed Registry Entries test case in Test Expert shows registry entries that existed on the computer before installation, but were missing after uninstall. After uninstall tests are run, the test case list is populated with destroyed registry entries and all statuses are set to Pending.
Page 199: Residual Registry Entries Test Case
Test Expert and all statuses are set to Pending. Review the list and select the status for each test item. Note Uninstall tests do not appear if a group is open. Because all uninstall tests are run at the same time, the test items for every test case in the Uninstall Tests group are updated simultaneously.
Page 200 Test Expert residual registry value. If Leave installed on uninstall is marked, the registry value is set to never uninstall. Clear the check box. See also: How to Run Uninstall Tests on page 194 About Test Cases on page 164 Wise Package Studio Reference...
Page 201: Chapter 8: Capturing Applications
Chapter 8 Capturing Applications This chapter includes the following topics: About Capturing Applications on page 201 SetupCapture Configuration on page 202 SetupCapture on page 216 Using SetupCapture With Virtual Capture on page 237 Using SetupCapture to Capture First Use Settings on page 240 SOE Snapshot on page 242...
Page 202: Setupcapture Configuration
Capturing Applications SetupCapture Configuration SetupCapture Configuration lets you edit and create configuration files that control how SetupCapture and SOE Snapshot work. You select the configuration file when you run SetupCapture or SOE Snapshot. SetupCapture Configuration does not apply when the captured application is saved as virtual software package or when using Wise Web Capture.
Page 203: Configuring Settings In Setupcapture Configuration
Capturing Applications See also: Configuring Settings in SetupCapture Configuration on page 203 Configuring Settings in SetupCapture Configuration Use SetupCapture Configuration to edit and create configuration files that control how SetupCapture and SOE Snapshot work. SOE Snapshot uses only the exclusions settings. Do one of the following: On the Projects tab, click the Run link to the right of the task or tool associated with SetupCapture Configuration.
Page 204 Capturing Applications Run Applications / Reboot. Run any applications that might be executed by an installation (examples: Internet Explorer, Notepad) and then restart the computer to ensure a complete exclusion list. Leave the Run Applications / Reboot page open as you restart. Do not close it or click Cancel.
Page 205: Selecting The Configuration File
Capturing Applications Selecting the Configuration File Configuration files control how SetupCapture and SOE Snapshot work. You select the configuration file from: SetupCapture or SOE Snapshot. The specified configuration file controls how SetupCapture or SOE Snapshot works during the current session. SetupCapture Configuration.
Page 206 Capturing Applications The General Settings dialog box appears: During SetupCapture Configuration. When you run SetupCapture and click Settings on the Welcome page. If the Settings button is unavailable, you might not have permission to change settings. Setting SetupCapture Configuration Security on page 44.
Page 207 Capturing Applications Capture non-Microsoft ODBC information In most cases, you can leave this check box cleared. If this check box is cleared, ODBC information is added to the ODBC driver table (in Windows Installer packages) or added as an Install ODBC Driver action (in WiseScript packages). If you mark this check box, ODBC information is added as registry entries instead.
Page 208: Setting Directories To Watch
Capturing Applications Convert registry entries into advertising info Try to create a package that supports advertising. SetupCapture will convert registry entries to advertising information. It converts only those registry entries that are considered to be advertising information. The registry entries themselves are not added to the package.
Page 209: Exclusion List Guidelines
Capturing Applications The recommended setting is the root drive (C:\) with Include Sub-directories turned on, which means that the entire hard drive will be watched for changes. This provides the most complete record of file changes by capturing all changes made on the system. However, the problem with watching the entire drive is that you might capture changes that have nothing to do with installation, those that occur in the normal course of operating a computer.
Page 210: Building An Exclusion List Automatically
Capturing Applications Changes that occur during installation that are unrelated to the actual installation. Example: If the installation displays a readme file in Internet Explorer, then several changes are made in the Internet Explorer directory that are the result of the readme file being opened, but are unrelated to the actual installation.
Page 211: Setting File And Folder Exclusions
Capturing Applications Leave the Run Applications / Reboot page open as you restart. Do not close it or click Cancel. After restart, SetupCapture Configuration reopens to the Run Applications / Reboot page. Click Next. The End Exclusion Capture page appears. Click Next.
Page 212: Setting A Directory To Be Excluded
Capturing Applications Setting SetupCapture Configuration Security on page 44. File and Folder Exclusions might already contain entries. Items with a question mark icon were added by the exclusion list building process. Items without a question mark icon were already in the exclusion list. Click Add.
Page 213: Setting A File To Be Excluded Based On A Wildcard
Capturing Applications In Directory, specify a directory. This causes SetupCapture to ignore files in the top level of this directory. You can use environment variables surrounded by percent signs (%) to specify paths. If you specify a path that contains user- specific data, a variable is inserted in place of the user-specific data.
Page 214: Converting User-Specific Files To Generic User Files
Capturing Applications To actually skip scanning of the subdirectories, also mark Do Not Scan this directory and subdirectories. Click OK to return to the SetupCapture Configuration dialog box. Items that you specify will be ignored if they change during a capture while this configuration file is in effect.
Page 215: Setting Ini File Exclusions
Capturing Applications In the left pane, select a registry key. To exclude a particular value, click the value name in the right pane. To exclude an entire registry key, click the <ignore entire subtree> entry in the right pane. You might do this if one registry key contains several excluded values.
Page 216: Setupcapture
Capturing Applications Exclusion List Guidelines on page 209 SetupCapture SetupCapture® records all the changes performed by an installation and saves that information to a new Windows Installer, WiseScript, or virtual software package. (The ability to create a WiseScript or virtual software package is not available in Standard Edition.) For information on saving a captured application as a virtual software package, see About SetupCapture in the Virtual Package Editor Help.
Page 217 Capturing Applications In the Professional Edition, you can use Virtual Capture to simulate a clean machine. Before using Virtual Capture, read the guidelines in Using SetupCapture With Virtual Capture on page 237. You can capture an installation in a virtual software layer and then delete or deactivate the layer and restore the computer to its original state.
Page 218: Setting Up A Clean Machine
Capturing Applications Look for environment variables in the Features or Components tabs of Setup Editor. (Windows Installer packages only.) Setting Up a Clean Machine A clean machine is a computer containing only the operating system and its service packs. A baseline machine is a computer with the operating system, basic system software, and additional applications that are installed on every computer in your organization.
Page 219: Capturing An Installation In A Virtual Software Layer
Windows Installer or WiseScript package. All changes made to the computer when you capture the installation are put into the layer. You can then use the Symantec SVS applet to delete or deactivate the layer and restore the computer to its original state.
Page 220 Capturing Applications project name. This tool might skip pages or populate fields based on command- line options defined in Process Templates Setup. On the Tools tab, double-click SetupCapture. If the SetupCapture Type page appears, select the type of capture to perform. SetupCapture This performs a typical SetupCapture, which captures the changes made by an installation.
Page 221 Capturing Applications change the configuration file, mark the check box Do not change current configuration file. See: Setting General Settings on page 205 Setting Directories to Watch on page 208 Setting File and Folder Exclusions on page 211 Setting Registry Exclusions on page 214 Setting INI File Exclusions on page 215...
Page 222 Capturing Applications SmartMonitor: Monitoring begins. Snapshot: Your computer is scanned, unless you are using the previous initial scan. Do not work on the computer during the scan. The Execute Installation page appears. 12. On the Execute Installation page, do the following: Specify the full path of the installation executable in .EXE Name.
Page 223: Specifying The Installation File
Capturing Applications 17. Enter summary information for the repackaged installation. This information will appear in the corresponding fields on the appropriate Installation Expert pages in Windows Installer Editor or WiseScript Package Editor. Finishing SetupCapture on page 230. 18. (Windows Installer packages only.) You can save the results from this SetupCapture to a specific feature.
Page 224: Configuring Setupcapture
Capturing Applications installation file is created in the directory you specify and it references the copied source files. For a .WSI, .MSI, or .WSE, this lets you immediately reimage the test computer and move the entire installation to another computer. The file that was specified in Target Installation is still created, but it references the installed source files, not the copied source files.
Page 225 Capturing Applications Note A security setting in Windows Vista or later operating system prevents the Virtual Capture and SmartMonitor methods from working. When you try to use either method, a prompt appears and provides the option to disable the security restriction. If you choose to disable the security restriction, the following registry setting is set: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows>LoadAppInit_DLLs=1...
Page 226: Selecting A Virtual Os File
Capturing Applications It does not capture overwriting of existing registry keys. .INI file changes are handled differently—if an .INI file is in the Windows directory, changes to it are recorded as an .INI file change. If an .INI file is outside the Windows directory, the entire .INI file is added instead of just editing the file.
Page 227: Using A Previous Scan
Capturing Applications Virtual Capture™ If you selected the existing Virtual OS, the Virtual OS is cleaned. This means that installed remnants from the last capture are removed from the Virtual OS directory and registry structure. If you selected a .WOS file, it is expanded onto your computer as a Virtual OS directory and registry structure.
Page 228: Executing Installations To Be Captured
Capturing Applications Executing Installations to Be Captured On the Execute Installation page, specify and run one or more installations. The installations are recorded and their changes are added to the repackaged installation that results from the capture. This page appears during SetupCapture. Capturing an Installation on page 219.
Page 229: Editing Setupcapture Exclusions
Capturing Applications Using the SetupCapture Inclusions page: To display another type of item, select the type from Inclusion Type. Included items are separated into the following types: files, registry keys, .INI files, and shortcuts. To remove an item from the repackaged installation, select it in the list and click Exclude.
Page 230: Finishing Setupcapture
Capturing Applications Capturing an Installation on page 219. The icons to the left of the items indicate how the items are affected by the installation: Item is added by the installation. Item is changed or updated by the installation. Item is removed by the installation. Using the SetupCapture Exclusions page: To display another type of item, select the type from Exclusion Type.
Page 231 Capturing Applications Entry Windows Installer Editor WiseScript Package Editor Version Field: Version Field: Installation Version Page: Product Details Page: General Information Manufacturer Field: Manufacturer Field: Company Name Page: Product Details Page: General Information Completing the Finish page Enter information in the following fields: Name The name of the application or software package.
Page 232: Adding Merge Modules Instead Of Files
Capturing Applications If files in the captured installation depend on certain merge modules, the Download Redistributables wizard appears. Use the Wise Web Site option to download those merge modules, which should be pre-selected. See Downloading Redistributable Files in the Windows Installer Editor Help. If a file that is part of a merge module is added, the Files in Merge Modules dialog box appears.
Page 233: Configuring The Installation As A New Feature
Capturing Applications Hide; Replace files with merge modules matching version Avoid seeing this dialog box in the future and always replace files with the corresponding merge modules. This turns the dialog box off for all instances in which it would normally appear. Hide;...
Page 234 Capturing Applications Parent This list contains all features in the installation. To change the feature’s parent, and therefore the feature tree, select from this list. This lets you change the feature tree in Installation Expert or in Setup Editor instead of editing tables. Target Platform Specify the platform on which this feature should be installed.
Page 235 Capturing Applications Always install this feature Set the feature’s level value to 1, which means that it gets installed by default for either Typical or Complete. Custom Set the feature’s installation level value yourself. Example: If you want a feature to be installed for a Complete installation, but not for a Typical installation, set a custom level value that’s greater than 3 and less than or equal to 1000.
Page 236 Capturing Applications Advertising Specify the default setting for how this feature supports advertising. If a feature is advertised, it is not installed, but it appears to be installed to the end user. Example: the end user might see shortcuts or menu options for an advertised feature, or the system might have certain entry points to the feature, such as a registered file extension, that can start installation-on-demand of an advertised feature.
Page 237: Using Setupcapture With Virtual Capture
Capturing Applications Using SetupCapture With Virtual Capture Not available in Standard Edition. Use Virtual Capture to capture on a non-clean machine while achieving clean machine results. This eliminates the need to reimage your computer between each SetupCapture. You also can eliminate the need to reimage a clean machine by capturing applications in a virtual software layer.
Page 238: Guidelines For Virtual Capture
Capturing Applications How the Virtual OS Works A virtual OS consists of a simulated directory structure and a simulated area of the registry. The complete clean machine is duplicated in this directory and registry structure, which takes a substantial amount of free disk space. When SetupCapture runs an installation, all files and registry entries are redirected to the simulated directory structure and registry, preventing changes from actually happening on your computer.
Page 239: Creating A Virtual Os
Capturing Applications See also: Using SetupCapture With Virtual Capture on page 237 Creating a Virtual OS on page 239 Creating a Virtual OS Not available in Standard Edition. Before you use SetupCapture with Virtual Capture, use the Virtual OS Creation utility to create a Virtual OS.
Page 240: Using Setupcapture To Capture First Use Settings
Capturing Applications Using SetupCapture With Virtual Capture on page 237 Using SetupCapture to Capture First Use Settings You can capture the changes made by an .MSI-based application the first time it is started on a computer after being installed. (Example: preferences, serial numbers that are required on first use, and so on.) The computer must have a freshly installed application, which has not yet been started.
Page 241 If you mark this, all changes made to the computer when you set first use settings are put into a virtual software layer. You can then use Symantec SVS applet to delete or deactivate the layer and restore the computer to its original state.
Page 242: Soe Snapshot
Capturing Applications 11. On the First Use Settings Inclusions page, to remove an item from the transform, select it in the list and click Exclude. The Exclude Globally button causes it to be excluded from future captures. To display another type of item, select the type from Inclusion Type.
Page 243: Guidelines For Capturing The Standard Operating Environment
Capturing Applications Guidelines for Capturing the Standard Operating Environment Not available in Standard Edition. Capture on a baseline machine that has the operating system and the applications that are installed for every user or every user in a department. If you only want to capture the operating system, capture on a clean machine.
Page 244: Capturing The Standard Operating Environment
Capturing Applications Capturing the Standard Operating Environment Not available in Standard Edition. Use SOE Snapshot to capture a computer’s standard operating environment (SOE). Before you run SOE Snapshot, see Guidelines for Capturing the Standard Operating Environment on page 243. Note Before you run SOE Snapshot, you can run SetupCapture Configuration to create a configuration file to be used by SOE Snapshot.
Page 245: Capturing With Wise Web Capture
Capturing Applications Edit the inclusions as needed: From Inclusion Type, select the type of inclusion to display. To exclude an item from the SOE Snapshot, select the item and click Exclude. To add an item to the exclusion list for the current configuration file, select the item and click Exclude Globally.
Page 246 Capturing Applications The file that results from the capture is an encrypted .MSI, with the extension .MSI_. You cannot open or install this encrypted file, but you can decrypt it on a computer that has Wise Package Studio installed. Requirements Version 2.0 of the .NET Framework must be installed on the server.
Page 247: Files And Registry Entries Ignored During Captures
Capturing Applications Files and Registry Entries Ignored During Captures A computer typically contains system files and registry entries that should not be included in the capture of an application or standard operating environment. Some of these files are Wise product-specific and others are computer-specific. What is Excluded from SetupCapture, SOE Snapshot, and the Test Expert Machine Capture? Items that are listed in the WisePSSC.ini file, which is located in the Windows or...
Page 248 Capturing Applications Windows\Installer\* Windows\Security\* Windows\Debug\* Windows\CSC\* Windows\Prefetch\* Windows\Applog\* Windows\LastGood\* Windows\System32\Config\* Windows\System32\Wbem\Logs\* Windows\System32\Wbem\Repository\* Windows\System32\Catroot\* Windows\System32\Catroot2\* Program Files\Windows Update\* Recycler\* Recycled\* System Volume Information\* The following items are hard-coded to be ignored by SetupCapture and the Text Expert Machine Capture but not SOE Snapshot. However, they might be in the predefined exclusion list in WisePSSC.ini.
Page 249: Chapter 9: Package Distribution
Chapter 9 Package Distribution This chapter includes the following topics: About Package Distribution on page 249 Distribution Methods on page 250 Moving a Package into Microsoft Active Directory on page 250 Copying a Package to the Share Point Directory on page 252 Copying a Package to a Network Directory on page 254 Copying a Compiled Installation to an FTP Server...
Page 250: Distribution Methods
Package Distribution distribute installable files only (examples: .MSI or .EXE files) from the Software Manager database. Therefore, when you run Package Distribution from Software Manager, the options to distribute to the share point directory and to distribute a project file are not available.
Page 251 Package Distribution Other requirements: Active Directory must be set up on the computer that is running Wise Package Studio. You must have privileges to make changes in the Active Directory management console of an Active Directory server. If distributing from the Projects tab or Software Manager, the share point directory must have been specified during installation using UNC or mapped drive notation.
Page 252: Copying A Package To The Share Point Directory
Package Distribution GPO Name Enter a unique name for the Group Policy Object to be created. Adhere to Microsoft Group Policy Object naming conventions. Settings Set the package to be deployed per machine or per user. This determines where an application’s configuration information is stored. Deployment Method If you selected Per User above, you can set the package to be assigned or published.
Page 253 Package Distribution Note If you add files to a package that has been distributed to the share point directory, you are prompted to add the new files to the share point. If you do so, the .QUE file for that package is reset and you must re-import the package in Software Manager.
Page 254: Copying A Package To A Network Directory
Package Distribution Windows Installer Editor, go to the Media page, and view the Compression Option on the Media Details dialog box. Application Name and Package Name are pre-filled except for virtual software packages and when distributing a package from WiseScript Package Editor. These names will be assigned to the package when it is imported into the Software Manager database.
Page 255 Package Distribution You run Package Workbench Distribution from: Software Manager Other requirements: To copy a .WSI with its .PDF or .SMS file or to copy a .WSE with its .ZAP, .PDF, or .SMS file, select the Installation option on the Distribution Method dialog box.
Page 256: Copying A Compiled Installation To An Ftp Server
Package Distribution Destination File Name (Optional.) This appears if you specified a Windows Installer package. Enter an alternate name for the file that is saved to the network directory. Do not include a file extension. Click Finish. Copying a Compiled Installation to an FTP Server When you are ready to deploy a package to end users, you can use Package Distribution to copy the package installation to an FTP server.
Page 257: Performing An Administrative Installation Of A Windows Installer Package
Package Distribution If this option is not available, you might not have met the criteria listed at the beginning of this topic. Click Next. If necessary, the installation file is saved and compiled. The FTP Server page appears. Complete the page: FTP Server Address The address of the FTP server to transfer the package files to.
Page 258 Package Distribution Other requirements: Does not apply to WiseScript packages. Not available if distributing a preflight package (generated with Preflight Instrumentation tool.) To perform an administrative installation Do one of the following: On the Projects tab, click the Run link to the right of the task or tool associated with Package Distribution.
Page 259: Chapter 10: Preflight Deployment
Chapter 10 Preflight Deployment This chapter includes the following topics: About Preflight Deployment on page 259 The Preflight Deployment Process on page 261 Connection to Preflight Deployment Tools on page 261 Creating a Preflight Package on page 262 Viewing Results from Preflight Deployment on page 263 Preflight Diagnostic Tests on page 265...
Page 260 Preflight Deployment Creating a Preflight Package on page 262. Preflight Analysis The Preflight Analysis tool in Workbench is a Web application that shows the results of the preflight package. Viewing Results from Preflight Deployment on page 263. Preflight Data Collector Preflight Data Collector is a Web application that receives the data from the preflight package, unpacks it, and inserts it into the Wise Services database.
Page 261: The Preflight Deployment Process
Preflight Deployment The Preflight Deployment Process Quality Assurance module only. Phase 1: Preflight package: Installation changes Use Preflight disabled. Instrumentation to Tests added to evaluate Package to Preflight the installation create a preflight deploy package Your environment. package based on a computer package that you plan to deploy.
Page 262: Creating A Preflight Package
Preflight Deployment Web applications. Typically, the URL for the Data Collector Web application would be something like this: http://IIS_Server/Wise_Managed_Enterprise/wisewebservice.dll Note If the package runs on a remote computer, you might need to provide a fully qualified domain name for the IIS server, depending on network and remote computer configuration.
Page 263: Viewing Results From Preflight Deployment
Preflight Deployment See Opening an Installation Package in the Windows Installer Editor Help. If you select any type of package other than an .MSI, you should open it from the repository.This means it has to be imported to Software Manager. On the Projects tab, click the Run link to the right of the task or tool associated with Preflight Instrumentation.
Page 264 Preflight Deployment On the Tools tab, double-click Preflight Analysis. On the Projects tab, click the Run link to the right of the task or tool associated with Preflight Analysis. Preflight Analysis opens. Use the links and buttons provided to view results and navigate.
Page 265: Preflight Diagnostic Tests
Preflight Deployment Windows 2003 Server IIS Configuration If you install Preflight Web applications on a Windows 2003 IIS server, make sure IIS 6.0 is configured to allow ISAPI and ASP, which is prohibited by default. See also: Connecting to a Web Application on page 79 Connection to Preflight Deployment Tools on page 261...
Page 266 Preflight Deployment Files Installed Reports the number of files that would be installed on the computer and also reports the total number of files contained in the package. Example: If a file is slated to be installed, but does not get installed because the same file already exists, then the cause might be the versioning rules that apply to that file.
Page 267 Preflight Deployment Patch Existence Checks if the patch being tested already is already installed on the computer. If it is, this test fails. This test only applies if the package being tested is a patch. Registry Security - Read Cycles through the registry entries that are installed and queries the target computer for permissions to access them.
Page 268: Appendix A: Wise Package Studio Command Line Options
Appendix A Wise Package Studio Command Line Options This chapter includes the following topics: About Wise Package Studio command-line options on page 268 Command Line Options for Application Isolation on page 269 Command Line Options for ApplicationWatch on page 271 Command Line Options for ConflictManager on page 273 Command Line Options for Command Line Builder...
Page 269: Command Line Options For Application Isolation
Wise Package Studio Command Line Options Most predefined Workbench tools require a command-line option in order to run. Example: To run ApplicationWatch, you must use the following command-line option: workbench.exe /tool="ApplicationWatch" In general, you should not change the command-line options of a predefined tool, or the tool might not run properly, if at all.
Page 270 Wise Package Studio Command Line Options Option Results /d211 Isolate using Windows Installer isolated components. Isolate automatically. Move files so .EXE and support files are in the same feature. /d212 Isolate using Windows Installer isolated components. Isolate automatically. Only isolate .EXEs and support files that are within the same feature.
Page 271: Command Line Options For Applicationwatch
Wise Package Studio Command Line Options Desired behavior Example command line Run isolation on the default project .MSI path\wfwi.exe /d "[ProjectDir]\[FileName].msi" and prompt for the file name of the isolated .MSI. Run isolation on the default project .MSI path\wfwi.exe /d="[ProjectDir]\[FileName]_Isolated.msi" and save the output file with _Isolated "[ProjectDir]\[FileName].msi"...
Page 272: Command Line Options For Command Line Builder
Wise Package Studio Command Line Options Examples The following table shows how you would use the options above to run this tool, using variables to provide information required by the program. Wise Package Studio Variables on page 75. Note These examples are shown as they would be entered at the command prompt. When you define a command-line option in Tool Setup, you do not need to include the .EXE in the command line.
Page 273: Command Line Options For Conflictmanager
Wise Package Studio Command Line Options Command Line Options for ConflictManager The following table lists the command-line option you can use with Manager.exe to run ConflictManager. See About ConflictManager in the ConflictManager Help. Option Results /D="DSN_name" Specify the Software Manager database to use in ConflictManager. Place the DSN name or the [Database] variable within quotation marks after the equals sign.
Page 274: Command Line Options For Legacy Setup Conversion
Wise Package Studio Command Line Options Examples The following table shows how you would use the options above to run this tool, using variables to provide information required by the program. Wise Package Studio Variables on page 75. Note These examples are shown as they would be entered at the command prompt. When you define a command-line option in Tool Setup, you do not need to include the .EXE in the command line.
Page 275 Wise Package Studio Command Line Options Option Results /src="path\file_name" Specify the source file of the project to convert, which will populate Source Installation on the Specify Files dialog box. Place the full path and file name (or appropriate variables) within quotation marks after the equals sign.
Page 276: Command Line Options For Linux Package Editor
Wise Package Studio Command Line Options Option Results /p:password Specify the RIP edit password. This is required if the RIP was created with an edit password. Skips to the Performing Migration dialog box of the conversion wizard. Only the Performing Migration dialog box appears, which displays the progress of the conversion.
Page 277: Command Line Options For Mobile Device Package Editor
Wise Package Studio Command Line Options Note These examples are shown as they would be entered at the command prompt. When you define a command-line option in Tool Setup, you do not need to include the .EXE in the command line. Desired behavior Example Command-line Open the default project file...
Page 278: Command Line Options For Package Relationships
Wise Package Studio Command Line Options Option Results /src="path\file_name" Specify the name of the file to distribute, which will populate Source Installation on the Specify File to Distribute dialog box. Place the full path (or appropriate variables) of the output file within quotation marks after the equals sign.
Page 279: Command Line Options For Package Validation
Wise Package Studio Command Line Options Option Results Required option to access the Package Relationships dialog box. Examples The following table shows how you would use the option above to access the Package Relationships dialog box, using variables to provide information required by the program.
Page 280: Command Line Options For Patch Creation
Wise Package Studio Command Line Options Desired behavior Example command line Validate the default project path\wfwi.exe /g "[VendorPackage]" vendor package. Command Line Options for Patch Creation The following table lists the command-line option you can use with wfwi.exe to run Patch Creation.
Page 281: Command Line Options For Setupcapture
Wise Package Studio Command Line Options Command Line Options for SetupCapture The following table lists the command-line options you can use with workbench.exe to run SetupCapture. About Capturing Applications on page 201. Option Results /tool="SetupCapture" Required option to run SetupCapture. /tgtfmt= Specify the type of installation file to create.
Page 282 Wise Package Studio Command Line Options Option Results /src=45="path" Use this option with an .MSI or .WSI file. The “4” causes the source files from the captured installation to be copied to a network directory. The “5” indicates that the paths to these files should be written as relative paths, relative to the .MSI/ .WSI location.
Page 283: Command Line Options For Soe Snapshot
Wise Package Studio Command Line Options Desired behavior Example command line Save the capture results in a .WSI file path\workbench.exe /tool="SetupCapture" /z2 / with the default project file name and app="[ApplicationName]" /pack="[PackageName]" / location; overwrite an existing project k="[VendorPackage]" /qa="[ApplicationName]" / installation file, if one exists.
Page 284: Command Line Options For Software Manager
Wise Package Studio Command Line Options Desired behavior Example command line Save the results in a file named path\wfwi.exe /r3 "[ProjectDir]\SOESnapshot.soe" SOESnapshot.soe in the default project directory. Command Line Options for Software Manager The following table lists the command-line options you can use with Manager.exe to run Software Manager.
Page 285: Command Line Options For Test Expert
Wise Package Studio Command Line Options Desired behavior Example command line Change the status of the default path\Manager.exe /x=2 /A="[ApplicationName]" /P="[PackageName]" / project package, in the default D="[Database]" database, to Available. Command Line Options for Test Expert The executable that runs Test Expert is TestExpert.exe. There are no options for running the executable.
Page 286: Command Line Options For Windows Installer Editor
Wise Package Studio Command Line Options You can use variables to provide a file to act upon, as shown in the following table. Wise Package Studio Variables on page 75. Note These examples are shown as they would be entered at the command prompt. When you define a command-line option in Tool Setup, you do not need to include the .EXE in the command line.
Page 287 Wise Package Studio Command Line Options Option Results /yr2 Open Windows Installer Editor and execute the Resolve with Rules command. Append the following to the command line to specify the data source, group, and rule set: DSN|Group|Rule Name Examples The following table shows how you would use the options above to run this tool, using variables to provide information required by the program.
Page 288: Command Line Options For Wisescript Package Editor
Wise Package Studio Command Line Options Desired behavior Example command line Compile the default project path\wfwi.exe /c "[ProjectDir]\[FileName].wsi" installation. Create or edit a new merge path\wfwi.exe /n "[ProjectDir]\[FileName].msm" module in the default project directory with the default project file name. Edit the default project path\wfwi.exe "[ProjectDir]\[FileName].wsi"...
Page 289 Wise Package Studio Command Line Options Examples The following table shows how you would use the options above to run this tool, using variables to provide information required by the program. Wise Package Studio Variables on page 75. Note These examples are shown as they would be entered at the command prompt. When you define a command-line option in Tool Setup, you do not need to include the .EXE in the command line.
Page 290: Appendix B Feature Summary
Appendix B Feature Summary Wise Package Studio is available in two editions, Professional and Standard, each designed to fulfill the needs of a particular type of user. The version you purchase determines what features are available to you. With the Professional Edition, you can add modules that provide additional functionality: Enterprise Management Server and Quality Assurance.
Page 291 Feature Summary Feature Edition or Module Software Manager Professional or Quality Assurance with Professional Test Expert Quality Assurance UpgradeSync Standard or Professional Virtual Package Editor Professional Web Capture Conversion Professional Windows Installer Editor Standard or Professional Wise Task Manager Professional Wise Web Capture Professional WiseScript Editor, accessible from Windows Installer Editor...
Page 292 Feature Summary Feature Edition or Module Edit items to be included and excluded from the package resulting from the Professional ApplicationWatch Legacy Setup Conversion Convert WinINSTALL installations to a Windows Installer package (.WSI/.MSI) Standard or Professional Convert WinINSTALL installations to a WiseScript (.WSE) Professional ConflictManager ConflictManager tool, including rules-based and wizard-based conflict...
Page 293 Feature Summary Feature Edition or Module Add current user registry keys to a separate feature during SetupCapture Standard or Professional Virtual Capture, which creates a Virtual OS file of a clean machine, allowing you Professional to perform SetupCaptures on a non-clean machine. Software Manager Revision Control—protect and track packages.
Page 294: Index
Index Symbols Application Specification for Windows in SetupCapture 228 XP 156 Command Line Builder _VistaProtectedFiles, rebuilding 157 application verification tests 180 advertising option 102 _VistaProtectedRegKeys, command-line options 272 ApplicationName variable 75 rebuilding 157 logging option 101 ApplicationWatch 94 not available 78 Numerics command-line options 271 patches 104...
Page 295 about 88 calling with validation rule 151 converting to Windows command-line options 273 isolating 89 Installer 116 defining settings 37 defined 31 documentation, Wise 33 not available 78 isolating 89 domain logon 18 permissions 43 running as task 63 domain, Windows 42 restricting access 43 execute installation from download redistributables 232...
Page 296 task names 59 inclusions report, SetupCapture 229, directory 93 method 91 group, security of applications 90 assigning user 42 index, database 27 on Windows XP 93 creating 39 INF file, mobile device 31 options 94 defined 39 INI file OS compatibility 93 from NT domain 39 capturing as regular file 229 report 92...
Page 297 LPR file 31 MSM file testing 159 Also see merge module Package Code 128 defined 32 package definition MSP file Machine Capture about 123 Also see patch configuration file 169, 202 creating 124 directories to watch 169 defined 32 exclusions 127 how created 128 during installation test 174 ignoring files 127...
Page 298 preparing for 138 troubleshooting results 264 editing 55 project file 32 URLs 262 elapsed time 83 removing from destination using Citrix 264 file location 25, 55 computer 138 viewing results 263 file name 56 removing from installation 104 history 83 Preflight Analysis sequence, specifying 136 hours completed 81...
Page 299 converting 122 baseline machine 218 conversion guidelines 121 buttons disabled 45 readme converting 122 clean machine 218 See release notes command-line options 281 RTF help text 70 rebooting from SetupCapture common items to exclude 209 Configuration 204 rule configuration file 202, 224 See validation rule reference manual 34 deletion, capturing 206...
Page 300 subdirectories 24 standard tests 177 editing test details 166 temporary file 25, 27 files ignored 247 standards where to locate 26 in virtual software layer 164 company repackaging 35 Machine Capture settings 169 Sharepoint variable 75 SetupCapture 36 not available 78 shortcut start Wise Package Studio 16 on multiple computers 168...
Page 301 running with shortcut 108 calling .EXE 151 with Preflight 265 calling custom action 150 tutorial Windows Application.msi 36 calling VBScript 151 Refer to Getting Started Guide Windows Installer condition 154 administrative installation 257 creating 150, 153 advantages 15 editing predefined 155 capturing installation to 219 Unassigned group 41 selecting 149...
Page 302 file, defined 32 WiseScript Editor XPlogo.cub 156 about 88 command-line options 288 not available 78 ZAP file, copying 255 WiseScript Package Editor about 89 command-line options 288 not available 78 WiseVistaIce.cub 157 WLC file 49 Word, editing help text 71 WordPad, editing help text 71 Workbench about 19...

This manual is also suitable for:

Wise package studio 8.0

Symantec WISE PACKAGE STUDIO 8.0 - REFERENCE V1.0 Reference

Technical Support

Chapter 1: Introduction to Wise Package Studio

Chapter 2: Setting up Wise Package Studio

Chapter 3: Creating Projects, Processes, and Tools

Chapter 4: Repackaging Applications and Managing Projects

Chapter 5: Wise Package Studio Tools

Chapter 6: Package Validation

Chapter 7: Test Expert

Chapter 8: Capturing Applications

Chapter 9: Package Distribution

Chapter 10: Preflight Deployment

Appendix A: Wise Package Studio Command Line Options

Appendix B Feature Summary

Index

Quick Links

Related Manuals for Symantec WISE PACKAGE STUDIO 8.0 - REFERENCE V1.0

Summary of Contents for Symantec WISE PACKAGE STUDIO 8.0 - REFERENCE V1.0