Wise Package Studio Reference
Wise Package Studio
The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the
agreement.
Documentation version 8.0
Legal Notice
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 t heir respective owners.
The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse
engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec
Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES,
INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE
DISCLAIMED, EXCEPT TO THE E XTENT THAT SUCH DISCLAIMERS ARE HELD T O BE LEGALLY INV ALID . SYMANTE C CORPORATION SHALL NOT
BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS
DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to
restricted rights as defined in FAR Section 52.227-19 “Commercial Computer Software - Restricted Rights” and DFARS 227.7202, “Rights in
Commercial Computer Software or Commercial Computer Software Documentation”, as applicable, and any successor regulations. Any use,
modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government
shall be solely in accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com
Wise Package Studio Reference 2
Technical Support
Symantec Technical Support maintains support centers globally. Technical Support’s
primary role is to respond to specific queries about product features and functionality.
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.
Symantec’s maintenance offerings include the following:
z A range of support options that give you the flexibility to select the right amount of
service for any size organization
z Telephone and Web-based support that provides rapid response and up-to-the-
minute information
z Upgrade assurance that delivers automatic software upgrade protection
z Advanced features, including Account Management Services
For information about Symantec’s Maintenance Programs, you can visit our Web site at
the following URL:
www.symantec.com/techsupp/
Contacting Technical Support
Customers with a current maintenance agreement may access Technical Support
information at the following URL:
www.symantec.com/techsupp/
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be at the
computer on which the problem occurred, in case it is necessary to replicate the
problem.
When you contact Technical Support, please have the following information available:
z Product release level
z Hardware information
z Available memory, disk space, and NIC information
z Operating system
z Version and patch level
z Network topology
z Router, gateway, and IP address informa tion
z Problem description:
Error messages and log files
Troubleshooting that was performed before contacting Symantec
Recent software configuration changes and network changes
Wise Package Studio Reference 3
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:
z Questions regarding product licensing or serialization
z Product registration updates, such as address or name changes
z General product information (features, language availability, local dealers)
z Latest information about product updates and upgrades
z Information about upgrade assurance and maintenance contracts
z Information about the Symantec Buying Programs
z Advice about Symantec’s technical support options
z Nontechnical presales questions
z Issues that are related to CD-ROMs or manuals
Maintenance agreement resources
If you want to contact Symantec regarding an existing maintenance agreement, please
contact the maintenance agreement administration team for your region as follows:
Asia-Pacific and Japan customercare_apac@symantec.com
Europe, Middle-East, and Africa semea@symantec.com
North America and Latin America supportsolutions@symantec.com
Additional enterprise services
Symantec offers a comprehensive set of services that allow you to maximize your
investment in Symantec products and to develop your knowledge, expertise, and global
insight, which enable you to manage your business risks proactively.
Enterprise services that are available include the following:
Symantec Early
Warning Solutions
Managed Security
Services
These solutions provide early warning of cyber attacks,
comprehensive threat analysis, and countermeasures to prevent
attacks before they occur.
These services remove the burden of managing and monitoring
security devices and events, ensuring rapid response to real
threats.
Wise Package Studio Reference 4
Consulting
Services
Educational
Services
To access more information about Enterprise services, please visit our Web site at the
following URL:
www.symantec.com
Select your country or language from the site index.
Symantec Consulting Services provide on-site technical
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.
Educational Services provide a full array of technical training,
security education, security certification, and awareness
communication programs.
Wise Package Studio Reference 5
Contents
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Chapter 1: Introduction to Wise Package Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
About Wise Package Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Wise Package Studio Editions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Wise Package Studio Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Repackaging Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Advantages of the Windows Installer Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Starting Wise Package Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
If Your Logon Fails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Wise Package Studio Logon Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
The Workbench Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
The Projects Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
When a Project Has No Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
When a Project Has a Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
The Tools Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Resizing the Workbench Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
About the Wise Software Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Wise Package Studio Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
About the Share Point Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
How Source Files Are Indexed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Example: Populating the Share Point Subdirectories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Integration with Software Virtualization Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
About Virtual Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Wise Package Studio File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Wise Package Studio Status Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Product Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Chapter 2: Setting Up Wise Package Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Steps for Setting Up Wise Package Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Using the Initial Workbench Setup Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
About Wise Package Studio Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Integrating With Windows NT Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Creating Groups and Setting Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Predefined Security Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Creating Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Setting Software Manager and ConflictManager Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Setting SetupCapture Configuration Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Setting Database Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
License Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
About User Licensing Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Adding Serial Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
About Evaluation Serial Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Assigning Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Deleting Serial Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Workbench Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Activating Suppressed Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Setting Repository Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Wise Package Studio Reference 6
Chapter 3: Creating Projects, Processes, and Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
About Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Adding a New Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Duplicating or Deleting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
About Process Templates and Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
The Process Templates Setup Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Predefined Process Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
External Process Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Adding a New Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Adding Tasks to a Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Duplicating and Deleting a Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Importing and Exporting Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Organizing Tasks and Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
About Tool Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Adding a New Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Adding a Web Application as a Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Duplicating, Deleting, and Rearranging Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Help for Tasks and Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Adding Wise Package Studio Variables to Help Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Command Line Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Guidelines for Entering Command Line Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
About Command Line Options for Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Defining Command Line Options for Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Wise Package Studio Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Chapter 4: Repackaging Applications and Managing Projects . . . . . . . . . . . . . . . . . . . . 76
About the Project and Tools tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Using the Projects Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Using the Tools Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Connecting to a Web Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Managing Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Entering Project Tracking Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Assigning Users to Tasks in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Entering Time for Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Viewing Project Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Creating a To-Do List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Workbench Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Generating a Workbench Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Chapter 5: Wise Package Studio Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
About Wise Package Studio tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
List of Wise Package Studio tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
How Wise Package Studio tools interact with revision control. . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Application Isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Creating a Package That Isolates .EXEs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Specifying OS Compatibility for Isolation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Selecting Isolation Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
ApplicationWatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
ApplicationWatch Exclusion List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Creating a Package with ApplicationWatch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Command Line Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Creating a Command Line With the Command Line Builder . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Adding UI Options to Your Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Adding Logging Options to Your Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Wise Package Studio Reference 7
Adding Advertising Options to Your Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Adding a Repair Option to Your Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Editing Public Properties With a Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Applying Transforms With a Command Line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Applying or Removing Patches With a Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . 104
InstallTailor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
About InstallTailor Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Creating a Transform with InstallTailor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Editing InstallTailor Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Legacy Setup Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
SMS Conversion Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Converting an SMS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Novell Conversion Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Converting a Novell Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
WinINSTALL Conversion Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Converting a WinINSTALL Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
WiseScript Conversion Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Converting a WiseScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
InstallShield Professional Conversion Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Converting an InstallShield Professional Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
InstallShield .MSI Conversion Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Converting an InstallShield .MSI Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Altiris RapidInstall Package Conversion Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Converting an Altiris RapidInstall Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Package Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Creating a Package Definition File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Setting Exclusions in Package Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Patch Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
About Patch Sequencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Creating a Patch File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Specifying Previous Versions for Patches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Advanced Upgrade Version Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Adding a Digital Signature to a Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Specifying the Patch Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Specifying Advanced Patch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Specifying Patch Removal Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
UpgradeSync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Using UpgradeSync. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Web Capture Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Wise Task Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Using Wise Task Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Performing Server-Side Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Adding Files From the Wise Software Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Chapter 6: Package Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
About Package Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Validating Installation Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
About Customizing Validation Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Adding a Validation Module to Package Validation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Selecting Validation Rules to Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
About Rules That Call a Custom Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Adding a Rule That Calls a Custom Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
About Validation Rule Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Adding a Validation Rule Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Wise Package Studio Reference 8
Editing a Predefined Validation Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Predefined Validation Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Windows Vista/Windows 7 Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Chapter 7: Test Expert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
About Test Expert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Opening a Package in Test Expert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Setting Test Expert Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
About the Master Test Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Loading, Saving, and Clearing Results Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Installing an Installation Test into a Virtual Software Layer . . . . . . . . . . . . . . . . . . . . . . . . . 164
About Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Running a Test Case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
About Testing Groups of Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Setting Test Statuses and Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Determining Your Test Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Testing on Multiple Computers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Machine Capture Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Setting Directories to be Watched for Uninstall Tests . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Setting a File, Wildcard, or Directory to Be Ignored During U ninstall Tests . . . . . . . . . . . 170
Setting Registry Entries to be Ignored During Uninstall Tests. . . . . . . . . . . . . . . . . . . . . 171
Adding a User-Defined Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Test Case Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Installation Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
How to Run Installation Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Launch Conditions Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
OS Conditions Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Verify Installation Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Standard Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Check Internet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Check Network Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Database Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Execute Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Application Verification Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Class IDs Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
File Extensions Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Help Files Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
ODBC Data Sources Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Prog IDs Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Search Locations Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Services Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Shortcuts Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Application Execution Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
How to Run Application Execution Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Extra Files Test Case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Extra Registry Entries Test Case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
File Coverage Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Isolated Files Test Case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Registry Coverage Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Uninstall Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
How to Run Uninstall Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Created Files Test Case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Created Registry Entries Test Case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Destroyed Files Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Wise Package Studio Reference 9
Destroyed Registry Entries Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Residual Files Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Residual Registry Entries Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Chapter 8: Capturing Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
About Capturing Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
SetupCapture Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Configuring Settings in SetupCapture Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Selecting the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Setting General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Setting Directories to Watch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Exclusion List Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Building an Exclusion List Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Setting File and Folder Exclusions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Setting a File to Be Excluded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Setting a Directory to Be Excluded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Setting a File to Be Excluded Based on a Wildcard . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Converting User-Specific Files to Generic User Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Setting Registry Exclusions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Setting INI File Exclusions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
SetupCapture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Guidelines for Capturing an Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Setting Up a Clean Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Capturing an Installation in a Virtual Software Layer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Capturing an Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Specifying the Installation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Configuring SetupCapture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Selecting the Capture Methodology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Selecting a Virtual OS File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Beginning the SetupCapture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Using a Previous Scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Executing Installations to Be Captured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Editing SetupCapture Inclusions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Editing SetupCapture Exclusions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Finishing SetupCapture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Adding Merge Modules Instead of Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Configuring the Installation as a New Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Using SetupCapture With Virtual Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Guidelines for Virtual Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Creating a Virtual OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Using SetupCapture to Capture First Use Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
SOE Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Guidelines for Capturing the Standard Operating Environment. . . . . . . . . . . . . . . . . . . . . . . 243
SOE Snapshot Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Capturing the Standard Operating Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Capturing With Wise Web Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Files and Registry Entries Ignored During Captures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Chapter 9: Package Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
About Package Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Distribution Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Moving a Package into Microsoft Active Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Copying a Package to the Share Point Directory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Copying a Package to a Network Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Wise Package Studio Reference 10
Copying a Compiled Installation to an FTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Performing an Administrative Installation of a Windows Installer Package . . . . . . . . . . . . . . . . . . 257
Chapter 10: Preflight Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
About Preflight Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
The Preflight Deployment Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Connection to Preflight Deployment Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Creating a Preflight Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Viewing Results from Preflight Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Preflight Diagnostic Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Appendix A: Wise Package Studio Command Line Options. . . . . . . . . . . . . . . . . . . . . . 268
About Wise Package Studio command-line options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
Command Line Options for Application Isolation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Command Line Options for ApplicationWatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Command Line Options for Command Line Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Command Line Options for ConflictManager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Command Line Options for InstallTailor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Command Line Options for Legacy Setup Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Command Line Options for Linux Package Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Command Line Options for Mobile Device Package Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Command Line Options for Package Distribution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Command Line Options for Package Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Command Line Options for Package Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Command Line Options for Patch Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Command Line Options for Preflight Instrumentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Command Line Options for SetupCapture Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Command Line Options for SetupCapture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Command Line Options for SOE Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Command Line Options for Software Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Command Line Options for Test Expert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Command Line Options for UpgradeSync. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Command Line Options for Virtual Package Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Command Line Options for Windows Installer Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Command Line Options for WiseScript Package Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Appendix B: Feature Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Wise Package Studio Reference 11
Chapter 1
Introduction to Wise Package Studio
This chapter includes the following topics:
z About Wise Package Studio on page 12
z Repackaging Basics on page 14
z Starting Wise Package Studio on page 16
z The Workbench Interface on page 19
z About the Wise Software Repository on page 23
z Wise Package Studio Directories on page 24
z About the Share Point Directory on page 26
z Integration with Software Virtualization Solution on page 29
z Wise Package Studio File Types on page 31
z Wise Package Studio Status Types on page 33
z Product Documentation on page 33
About Wise Package Studio
Wise Package Studio® is a software packaging and application lifecycle management
solution that supports the needs of application deployment and desktop management
teams. Wise Package Studio provides a complete toolkit to support every phase of the
application lifecycle, including application integration, package quality assurance, and
release management. Use Wise Package Studio to:
z Improve the reliability of software installations, which reduces support costs and
increases end user productivity. Wise Package Studio provides the processes and
tools to effectively test an application prior to mass deployment.
z Enable faster and more reliable software rollouts by streamlining the process of
preparing applications for distribution. Wise Package Studio accomplishes this
through its project management tools, process automation, and built-in best
practices.
z Support corporate standardization. The process-oriented approach to repackaging in
Wise Package Studio helps standardize the repackaging process, while its complete
editing capabilities let you customize the way software is installed.
z Achieve a greater return on your Windows operating system investment. Wise
Package Studio provides complete capabilities for migrating applicati ons to Windows
Installer format, and customizing and validating Windows Installer packages.
z Manage every package used in your organization through each of its lifecycle
phases, whether it is undergoing customization, in production, or retired.
See also:
Wise Package Studio Reference 12
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.
See Feature Summary on page 290.
Standard Edition is a stand-alone packaging tool for individuals who prefer an ad hoc
approach to repackaging. It provides Windows Installer packaging and validation
functionality, helping organizations quickly and reliably migrate applications to the .MSI
standard.
Professional Edition is an advanced packaging solution. It provides core functionality for
advanced packaging, testing, and conflict management, and helps organizations support
application standardization using a process-oriented approach. Professional Edition
provides the starting point for adding extended functionality with the following modules:
z Enterprise Management Server is an enterprise application integration solution
designed for packaging teams that may be either centralized or distributed. It
provides advanced project management functionality and security, helping
organizations create and manage a formalized, enterprise-wide application
integration process.
Introduction to Wise Package Studio
z Quality Assurance covers all aspects of testing Windows Installer packages,
including an easy way to conduct multiple testing activities in both the lab and realworld environments.
Wise Package Studio Terminology
Wise Package Studio
A collection of tools for managing the application lifecycle.
Workbench
The interface you use to work on repackaging projects or to run tools such as
SetupCapture.
Project
Defines the job you need to accomplish. (Example: repackaging an application.) A
project lets you track information about the job, such as status, dates created and
modified, and notes. Using a project also lets you control the locations and names of the
files that are created and used during the project. In the Professional Edition, you can
associate a project with a process that defines the tasks to be performed.
Process
(Not available in Standard Edition.)
A list of tasks that you perform in order to complete a project. Wise Package Studio
contains predefined processes and you can create new processes as needed.
Task
(Not available in Standard Edition.)
Wise Package Studio Reference 13
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.
(Examples: Establish clean machine, Install software.)
Tool
An executable application that you use to accomplish a task. Wise Package Studio
includes predefined tools. In the Professional Edition, you can add new tools as needed.
Installation
z The compiled form of an installation, which is an .MSI or an .EXE.
z The project and source files that represent an installation that is created in a Wise
development tool. Example: a .WSI or .WSE with source files.
z What happens on the destination computer when a package is opened.
Package
An application that is created, manipulated, or repackaged in Wise Package Studio. A
package consists of:
z The distributable piece or pieces of an application (typically the installation file) and
instructions for running the installation when it is deployed (typically a command
line). A package might also contain additional files that should be distributed with
the installation (example: an informational text file). This information represents a
package definition.
z The source files associated with each package’s installation.
Application
A collection of similar packages in the Software Manager database. Example: Microsoft
Word is an application; Word 2003 and Word 2007 would be packages of that
application.
Repackaging Basics
Repackaging means changing or customizing a software installation to meet the needs
of an organization. Repackaging is a critical step in the application lifecycle management
that is supported by Wise Package Studio.
See About Wise Package Studio on page 12.
Why Should You Repackage?
z Create consistent and standardized, yet customized, installations.
Repackaging an installation so that it adheres to your organization’s standards
reduces the cost of supporting end users’ desktops.
z Create silent installations or limit the options available to end users.
This streamlines installations and promotes ease of application deployment.
z Migrate installations to the Windows Installer format.
Wise Package Studio Reference 14
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.
See Advantages of the Windows Installer Format on page 15.
What Should Not Be Repackaged?
Repackaging is not appropriate for certain types of applications:
z .MSI files
Installations that are already in .MSI format should not be repackaged. Instead, use
transforms to customize them. Transforms apply changes to the installation at run
time to tailor the installed application to the needs of a particular group of users. For
general information on transforms, see About Transforms in the Windows Installer
Editor Help.
z Windows Media Player, Microsoft Internet Explorer, antivirus software, and device
drivers
These types of applications make low-level changes to the operating system
involving Windows File Protection.
z Distributable components of an operating system, including service packs, OS
security updates, Internet Explorer, MDAC, or the Windows Installer service
These items are not repackaged because they break Windows security rules. The
Windows Installer service might not run or might be modified by these installations.
Service packs are not repackaged because it is difficult to capture all of the changes
made to the operating system, and a significant number of service pack files are
Microsoft file-protected. MDAC is not repackaged because it is a merge module.
Advantages of the Windows Installer Format
Wise Package Studio provides complete capabilities for migrating applications to
Windows Installer format. Using Windows Installer results in a solid, robust installation
that reduces the total cost of ownership and enables compliance with the Windows logo
program. Because Windows Installer is part of the operating system, it provides benefits
that are not available in traditional installation technology.
z Installation rollback
If a Windows Installer installation fails, Windows Installer can return the computer
to the precise state it was in before the installation. This includes restoring deleted
or overwritten files, registry keys, and other resources.
z Self-healing
(Also called automatic repair and self-repair.) Windows Installer can repair missing
components of the application without rerunning the installation. When an
application starts, Windows Installer checks a list of key files and registry entries. I f
it detects any problems, Windows Installer repairs the application using a cached
database that contains key paths to application components.
z Advertisement
(Also called install-on-demand and just-in-time installation.) Advertised features are
not installed but appear installed to the user. Only the entry points for the features
are installed. The first time a user invokes an advertised feature, it is installed.
Wise Package Studio Reference 15
Introduction to Wise Package Studio
z Customization
You can customize the behavior of an installation by creating transforms.
Transforms apply changes to the installation at run time to tailor the installed
application to the needs of a particular group of users.
z Componentization
Windows Installer uses components to group resources so they move as a unit. The
installation database tracks which applications require a particular component,
which files comprise each component, where each file is installed on the system,
and where component sources are located.
z Standardization
Windows Install e r uses consistent and reliable versi on rules, which pr ovide
consistent and reliable installations for all applications and prevent newer files from
being overwritten by older files. Windows Installer’s system-wide management of
shared resources prevents conflicts that can occur when uninstalling one application
removes files that are shared by other applications.
z Elevated privileges
You can install or advertise applications by using system-level privileges regardless
of the privileges of the user who is logged on to the computer.
z Easier deployment of application updates
Windows Installer provides built-in patching technology to update installed versions
of a Windows Installer-based application. Unlike full installations, a patch
installation contains only the information necessary to update an installed version of
the application.
During an upgrade, Windows Installer detects whether the application to be
upgraded was previously advertised or installed, and then removes it when
installing the newer version. Additionally, Windows Installer allows for some
migration of feature states from previously installed applications.
See also:
Repackaging Basics on page 14
Starting Wise Package Studio
To start Wise Package Studio
1. Select Start menu > Programs > Symantec > Wise Package Studio > Wise Package
Studio.
2. If the Wise Package Studio Logon dialog box appears, log on as instructed by your
Wise Package Studio administrator. (Not available in Standard Edition.)
See Wise Package Studio Logon Options on page 17.
If you cannot log on, one or more dialog boxes might appear.
See If Your Logon Fails.
3. Click OK.
The first time you start Wise Package Studio, Workbench opens to the Projects tab.
The Standard Edition opens a project named Sample Project; the Professional
Edition opens the Initial Workbench Setup project.
Wise Package Studio Reference 16
If Your Logon Fails
¾ Not available in Standard Edition.
You cannot log on to Wise Package Studio if:
z You have not configured the Wise Software Repository in the Wise Repository
z You have not been assigned a Wise Package Studio license.
Introduction to Wise Package Studio
Manager. See Configuring the Wise Software Repository in the Getting Started
Guide.
If a serial number is available, you might be assigned a serial number
automatically . If not, the Assign User Licensing dialog box appears. Mark one or
more check boxes for the licenses to assign.
With Enterprise Management Server, you cannot be assigned a serial number
automatically. The Wise Package Studio administrator must assign licenses.
If a serial number is not available, the Add Serial Number dialog box appears.
See Adding Serial Numbers on page 49.
If you entered a user name from a Windows NT account, and Security Setup
does not contain a security group that matches the domain group you belong
to, you are prompted to contact your Wise Package Studio administrator.
(Enterprise Management Server only.)
Wise Package Studio Logon Options
¾ Not available in Standard Edition.
When you start Wise Package Studio, the Wise Package Studio Logon dialog box
appears. Obtain your logon information from your Wise Package Studio administrator.
Your entries in this dialog box depend on the type of logon account you use.
See Options on the Wise Package Studio Logon dialog box.
Types of Wise Package Studio logon accounts
Logon account Usage Requirements
Workbench
account
This account is defined when you are
assigned a Wise Package Studio
license. Use it when:
z You do not have an Enterprise
Management Server license.
z The computer is not connected to
a Windows NT domain. Example:
When you use Wise Package
Studio on a lab computer.
None.
Wise Package Studio Reference 17
Logon account Usage Requirements
Current Windows
NT account
Windows NT
account
Log on to Wise Package Studio as the
currently logged-on Windows NT
user.
Log on to Wise Package Studio with a
Windows NT account. This account
can be different from the one that is
currently logged on to Windows. This
lets you log on to Wise Package
Studio from another computer,
including a remote computer.
z The computer must be connected to a
Windows NT domain.
z You must have an Enterprise Management
Server license.
z Security Setup must contain a security group
whose name matches a valid group in the NT
domain, and you must be defined in that
domain group. If you are in multiple NT
groups, you are logged on under the first valid
group that is encountered.
z The computer must be connected to a
Windows NT domain.
z The remote computer must have Wise Package
Studio installed.
z You must have an Enterprise Management
Server license.
z Security Setup must contain a security group
whose name matches a valid group in the NT
domain, and you must be defined in that
domain group. If you are in multiple NT
groups, you are logged on under the first valid
group that is encountered.
Introduction to Wise Package Studio
Options on the Wise Package Studio Logon dialog box
Option Workbench account entries Current NT account
entries
User Name z (Professional Edition) Type
your user name from User
Licensing Setup.
z (Enterprise Management
Server) Type your user
name from Security Setup.
Password (Enterprise Management Server
only) Type your password from
Security Setup.
Use Security From Click (Workbench Database). Leave the default. This
Always Use
Current Network
Login
Uncheck this check box. Check this check box.
Leave this box blank. Type your Windows NT
Leave this box blank. Type your password for
option is disabled when
you select the next
option.
When you start Wise
Package Studio in the
future, you are logged on
automatically.
Windows NT account
entries
user name for the
Windows NT domain.
the Windows NT domain.
Select the Windows NT
domain name.
Uncheck this check box.
Wise Package Studio Reference 18
The Workbench Interface
When you start Wise Package Studio , you see the Wor kbe nch 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. When you are not working on a project, use the Tools tab and doubleclick the tool’s icon.
The first time you start Wise Package Studio, it opens to the Projects tab. Thereafter, it
opens to the last tab in which you worked and the last project you had open, if any. In
the left pane of Workbench, you can switch b etween the Projects tab and Tools tab by
clicking the appropriate tab or by using the shortcut keys Alt+P and Alt+T respectively.
The Description tab in the right pane displays help text about the active task or tool.
Click a task or tool in the left pane to display its help. If a task is associated with a tool,
you can toggle between the task help and the tool help. To do so, click the View Tool
Help/View Task Help link in the upper right of the right pane. The right pane is visible
only when you are in full screen mode.
For information about Workbench display modes, see Resizing the Workbench Pane on
page 22.
Introduction to Wise Package Studio
The Projects Tab
On the Projects tab, you select a project from Active Project. The left pane of the
Projects tab displays either tools or tasks, depending on whether the active project is
associated with a process.
See When a Project Has No Process on page 20 and When a Project Has a Process on
page 20.
The right pane of the Projects tab contains the following tabs:
z Description
Displays help text for the active task or tool.
z Details
Displays Project Setup information for the current project.
With Enterprise Management Server, additional tabs appear:
z Project Management
Lets you record information about a project so you can manage it and track its
progress. You can enter project information, enter time spent on each task, and
assign users to specific tasks in a project. Users can run only the tasks that have
been assigned to them.
See Managing Projects on page 80.
z Metrics
Displays a record of all events that have occurred for the current project.
Information is recorded when a user works on a task or marks or clears a task’s
check box. The Metrics tab can also contain notes about each event.
See Viewing Project Metrics on page 83.
Wise Package Studio Reference 19
Workbench resizing
tools.
Introduction to Wise Package Studio
z To Do
Displays a record of to-do items that have been created for the current project. Todo items are entered by users and represent actions that must be taken while
working on the project.
See Creating a To-Do List on page 84.
With Enterprise Management Server, Security Setup determines whether you have
access to the Projects tab.
When a Project Has No Process
Projects can use an ad hoc approach that does not include a process. When a project
does not have a process, the left pane of the Projects tab displays all available tools. To
use a tool, click the Run link to the right of the tool. You do not have to use the tools in
any particular order.
Active Project shows
the project on which
you are working.
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. The edition or module you
purchase determines whether other tabs are available for managing the
project.
When a Project Has a Process
¾ Not available in Standard Edition.
When a project is associated with a process, the left pane of the Projects tab displays
the project’s tasks. When a task involves running a tool, you run the tool by clicking the
Run link to the right of the tool. When you complete a task, you mark the task’s check
box.
Wise Package Studio Reference 20
Workbench resizing
tools.
Active Project shows
the project on which
you are working.
Process tasks.
Introduction to Wise Package Studio
When a task is
associated
with a tool,
click this link
to toggle
between task
help and tool
help.
The Description tab displays help text for the active task. When you run a Web
application tool, it opens in the Description tab. The edition or module you
purchase determines whether other tabs are available for managing the
project.
The Tools Tab
The Tools tab displays all available tools, organized in functional groups. These include
the predefined tools and, in the Professional Edition, any tools you have added. When
you click a tool name, the tool’s help text appears in the Description tab in the right
pane. To run a tool, double-click the tool name.
With Enterprise Management Server, Security Setup determines whether you have
access to the Tools tab.
Wise Package Studio Reference 21
Workbench resizing
tools.
Available tools.
Introduction to Wise Package Studio
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.
Full screen mode
Maximizes the Workbench window , displaying both the right and left panes.
Workbench always opens in full screen mode. When you start a tool from
this mode, Workbench changes to side by side mode unless you marked
Run all tools in Full Screen Mode in Workbench Preferences. W or kbench
changes back to full screen mode when you close all Workbench tools.
Side by side mode
Hides the right pane and decreases the width of the left pane to make room
for a tool window or dialog box. Workbench changes to side by side mode
when you start a tool or run a task. The window size and position in this
mode are retained from session to session.
Stay on top mode
Hides the right pane and changes the left pane to a small window that
floats on top of all other windows. The window size and position in this
mode are retained from session to session.
Wise Package Studio Reference 22
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.
The Wise Software Repository consists of:
z Share point directory
Contains shared Wise Package Studio files and shared resources that are used to
create Windows Installer installations. It also contains source files for packages in
the Software Manager database. All Wise Software Repository databases are
associated with a specific share point directory.
See About the Share Point Directory on page 26.
z Workbench database
Stores information that Wise Package Studio creates and uses. Examples: project,
process, tool, and security information. A repository can contain only one
Workbench database.
Introduction to Wise Package Studio
z Software Manager database
Contains all software packages and other resources that are used by an
organization. Other resources include: merge modules, device drivers, Group Policy
Objects, and standard operating system environment snapshots. A repository can
contain multiple Software Manager databases.
See About the Software Manager Database in the Software Manager Help.
z Wise Services database
(Formerly named Preflight database.) Stores the following data that is generated
and used by Wise services:
Tasks that are managed by the Wise Task Manager. Examples: importing
packages; running the Merge Module Wizard; compiling .MSI or .WSI packages
in Software Manager; remotely compiling packages in Windows Installer Editor.
(Quality Assurance module only .) The resu lts that are generated from deploying
preflight packages, which are made with Package Instrumentation. These
results are used by the Preflight Data Collector and Preflight Analysis Web
applications.
A repository can contain only one Wise Services database.
See also:
Wise Task Manager on page 141
About Preflight Deployment on page 259
Multiple Repositories
z In a large enterprise with multiple teams, each team might use a different share
point directory and Wise Software Repository. Because a Wise Package Studio
server can be associated with only one active repository at a time, each team must
install their repository on a different server.
Wise Package Studio Reference 23
Introduction to Wise Package Studio
z 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.
A Wise Package Studio client can connect to any Wise Software Repository that it can
access. To change a client’s default repository, use the Workbench Preferences dia log
box > Repository tab and specify the share point that is associated with an active Wise
Software Repository.
For configuration recommendations, see Additional Wise Package Studio Configurations
in the Getting Started Guide.
Benefits of Maintaining Package Information in the Wise Software
Repository
z Maintain a complete inventory of all applications used in your organization and store
all packages and their source files in a centralized location.
z Manage each package throughout its lifecycle—from integration to testing and
deployment through retirement.
z Maintain the status of each package in the repository and avoid problems typically
caused by mixing production packages with those in development. Examples:
accidentally deploying a package that is not ready for use, or unintentionally
changing a proven production package.
z Reduce conflicts between applications before deployment, producing reliable, error-
free deployments and reducing help desk calls.
When corporate developers have the Enterprise Edition of Wise for Windows Installer or
Wise for Visual Studio .NET, they can use the Wise Software Repository to manage
shared resources and ensure they always use the correct versions of shared resources.
Wise Package Studio Directories
Files that are used and created by Wise Package Studio are organized in several
directories. In the Standard Edition, they are subdirectories of the Wise Package Studio
application directory. In the Professional Edition, they are subdirectories of the share
point directory, which lets multiple users share the files.
If your organization uses the Enterprise Edit ion of Wise for Windows Installer, the share
point directory might contain ad ditional information that is unique to that product.
The Wise Package Studio installation also contains subdirectories that are specific to
Windows Installer Editor. For descriptions of those subdirectories, see Installation
Resources and Their Locations in the Windows Installer Editor Help.
Warning
Do not edit or delete the contents of the Wise Package Studio directories outside Wise
Package Studio or other Wise tools. Doing so will cause problems in Workbench,
Software Manager, and ConflictManager and can result in loss of data.
Wise Package Studio Reference 24
Introduction to Wise Package Studio
Directory Contents
000, 001, and so on
(Not available in Standard
Edition.)
Available Packages
(Not available in Standard
Edition.)
Custom Actions See Installation Resources and Their Locations in the Windows Installer Editor
Languages See Installation Resources and Their Locations in the Windows Installer Editor
Merge Modules See Installation Resources and Their Locations in the Windows Installer Editor
Projects Project information, including installation files, SetupCapture reports, and
Source files that are associated with each package’s installation. The
subdirectories are numbered sequentially. These subdirectories are created when:
z You distribute a package to the share point directory.
z You import a package into the Softw are Manager database, and you distribute
source files.
See How Source Files Are Indexed on page 27 and About .QUE Files in the
Software Manager Help.
Provides a centralized location for storing all packages that are available for
deployment, keeping them separate from packages that are still in development.
A separate subdirectory, named application\package, is created for each package.
This subdirectory contains the compiled installation file, which is read-only, and
any files needed for the installation, such as external .CAB files or SMS package
definition files. This subdirectory is created when you change the package’s status
to Available.
Help.
Help.
Help.
transform files. Information for each project is stored in a separate subdirectory.
You define the subdirectory name when you create the project. The subdirectory is
created the first time you open the project on the Projects tab.
Package definition files (.WPF) and their defined files. Each package definition file
is stored in its own subdirectory. This subdirectory has a Files subdirectory where
the files specified in the package definition file are copied.
Reports
(Not available in Standard
Edition.)
Resources See Installation Resources and Their Locations in the Windows Installer Editor
Scripts
(Not available in Standard
Edition.)
The Report.ini file, which stores information about the predefined reports and,
with Enterprise Management Server, any report customizations.
The ReportConfig.ini file, which is used when saving a ConflictManager report
directly to a file without it opening in a report viewer.
Help.
Temporary .QUE files representing packages that have been distributed but not
imported into the Software Manager database. See About .QUE Files in the
Software Manager Help.
This directory also contains the package installation file when:
z You distribute a package that is not part of a Workbench project.
z You import a package into the Software Manager database.
With Enterprise Management Server, the Scripts directory also stores information
about package subscriptions.
Wise Package Studio Reference 25
Introduction to Wise Package Studio
Directory Contents
TaskFiles
(Not available in Standard
Edition.)
Templates See Installation Resources and Their Locations in the Windows Installer Editor
Themes See Installation Resources and Their Locations in the Windows Installer Editor
Validation Predefined validation modules (.CUB files) that are used by Package Validation.
Virtual OS
(Not available in Standard
Edition.)
Workbench Help text files for all processes, tasks, and tools, both predefined and those you
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
operation that is managed by the Wise Task Manager. You can safely delete these
files for tasks that have a status of Completed.
Help.
Help.
Provides a centralized location for Virtual OS files (.WOS) that are used for virtual
captures and the Universal Import feature of Software Manager.
create. Predefined help text files are in HTML format.
(Standard Edition only .) This directory might also contain database tables, in .DAT
format. The database tables store setup data for projects, processes, tools,
security groups, and users. They also store project management information,
metrics, and to-do lists. Do not edit the database files directly.
About the Share Point Directory
¾ Not available in Standard Edition.
During the Wise Package Studio - Professional installation, you specify a share point
directory. The default directory name is Wise Share Point, however, you can change the
name at installation time.
For recommendations on where to locate the share point directory, see Choosing the
Location for the Share Point Directory in the Getting Started Guide.
Each Wise Software Repository and its databases are associated with a unique share
point directory. To change the default repository and its associated share point
directory:
z (Client installations.) Use the Workbench Preferences dialog box > Repository tab.
z (Server installations.) Use the Wise Repository Manager.
Share point directory contents
z Workbench projects.
z Workbench tool and task help files.
z Installation files for the packages you create and work with in Wise Package Studio .
Examples: .MSI. WSI, .WSE, .EXE, and so on.
z Resources that are used to create Windows Installer installations. Examples:
installation templates, component rules, language files, and so on.
z Predefined Workbench reports.
Wise Package Studio Reference 26
Introduction to Wise Package Studio
z Temporary .QUE files representing packages that have been distributed but not
imported into the Software Manager database.
z Source files of installations you import into the Software Manager database.
z Package definition files (.WPF) that are created with Package Definition and all of
the files specified by the definition file.
z .INI files used to generate reports.
z Log files and .INI files associated with the tasks in Wise Task Manager.
See Wise Package Studio Directories on page 24.
If your organization uses the Enterprise Edit ion of Wise for Windows Installer, the share
point directory might contain ad ditional information that is unique to that product.
Deleting files from the share point directory
Warning
Do not edit or delete the contents of the Wise Package Studio directories outside Wise
Package Studio or other Wise tools. Doing so will cause problems in Workbench,
Software Manager, and ConflictManager and can result in loss of data.
A common question is “Can I clean up the share point by deleting unused source files?”
The answer is no. It is too difficult to know which files are safe to delete. Also,
ConflictManager lets you revert resolved packages to their original state, but if you
delete a package’s original files, you cannot revert.
The only recommended way to delete files from the share point directory is to delete the
entire package from the Software Manager database. When you do so, you can delete
the package’s source files from the share point subdirectories (000, 001, and so on), if
those files are not referenced by any other application. See Deleting a Package in the
Software Manager Help.
How Source Files Are Indexed
¾ Not available in Standard Edition.
A sequentially-numbered directory structure is created under the share point directory
to store occurrences of installation source files when:
z You distribute a package to the share point directory.
z You import a single package or multiple packages to the Software Manager
database, and you distribute source files.
An index file named wamdb.idx, located in the share point directory , records the location
of the source files. Because files are indexed, distributing source files to the share point
eliminates storage of duplicate files and results in smaller storage requirements than if
you distribute to a network directory.
Example:
Suppose you have three pac kages, each c ontaining a v ersion of report. dll. Th e first ti me
you distribute a package containing report.dll, the file is placed in the share point’s
000\001 directory. If you distribute another package containing the same version of
report.dll, the file is not saved a second time, but a counter is set for that file in
wamdb.idx. If you distribute a third package that uses a different version of report.dll,
Wise Package Studio Reference 27
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.
When you follow the process in a typical Windows Installer repackaging project, files and
directories are created in the share point directory as follows.
What You Do What Happens
Create and open a project A subdirectory for the project is created in the share point’s Projects
directory. Example: share point\Projects\Project_Name
Create the package installation file The package installation file (.WSI) is placed in the Projects
subdirectory.
Compile the package from within the
process
Example: to run Package Validation.
Distribute to the share point directory
The compiled file (.MSI or .EXE) is placed in the Projects
subdirectory. This is considered a temporary installation.
z A numeric directory structure (000\001, and so on) is created
to hold the installation’s source files.
z A temporary .QUE file is created in the share point Scripts
subdirectory.
Import to the Software Manager database
Resolve conflicts The resource information in the Software Manager database is
Export from ConflictManager and
recompile
Run a task to make the package available
z The .QUE file is deleted.
z Package and resource information is added to the Software
Manager database. The installation file remains in the Projects
directory and the Software Manager database references that
location.
z Paths in the installation file are changed to reference the new
source locations (000\001, and so on).
changed. Example: You might change the package to use a newer
version of report.dll.
The original installation in the Projects directory is changed.
Example: The path is changed to refer to the newer version of
report.dll.
z The package status is changed to Available.
z A subdirectory for the package is created in the share point
Available Packages directory. (Example: Available
Packages\Application Name\Package Name\) The final compiled
installation file and any other files needed for installation are
placed in this subdirectory. The installation file is set to readonly.
See also:
About the Share Point Directory on page 26
Wise Package Studio Reference 28
Introduction to Wise Package Studio
How Source Files Are Indexed on page 27
Integration with Software Virtualization Solution
¾ Not available in Standard Edition.
About Software Virtualization Solution
Software Virtualization Solution (SVS) is a revolutionary approach to software
management. By placing applications and data into managed units called virtual
software packages, you can instantly activate , deactivate, or reset applications. Instead
of running the installation of an application on a client computer, you simply deploy and
activate a virtualized application. When an application needs repair, you reset it to its
original state. It also lets you completely avoid conflicts between applications, without
altering the base Windows installation. You can also host multiple versions of the same
application on a computer, so that you can roll out and test a new version without
removing the old version.
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. Wise Package Studio also incorporates the software virtualization
technology into two of its tools to greatly enhance their capabilities.
See About Virtual Software Packages on page 30.
Several script actions in the WiseScript editing tools specifically deal with virtual
software packages. You can use these script actions to mana g e and update the virtual
software packages that you create.
In Wise Package Studio, you work with virtual software packages in the following
formats:
z Virtual software layer
z Virtual software archive file (.VSA), which is a portable version of a virtual software
layer
z Virtual software project file (.WVP), which is a project file that you compile to create
a .VSA file
Software Virtualization Agent
The Software Virtualization Agent is installed when you install Wise Package Studio. You
must have the agent installed to do the following:
z Use the Virtual Package Editor
z Import .VSA files into Software Manager
z Use SetupCapture to capture an application as a virtual software package
z Work in a virtual layer in SetupCapture and Test Expert.
The agent is not required to create SVS enabled packages in Software Manager.
The agent must also be installed on any desktop computer on which you will use
virtualized packages.
Wise Package Studio Reference 29
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:
z Software Manager
Software Manager lets you enable packages that are in the Wise Software
Repository for the Software Virtualization Solution (SVS). You can enable .MSI
packages or any type of package that has an associated package definition file.
When an SVS enabled package is installed on a target computer where the Software
Virtualization Agent is present, the enabled package can create a virtual software
layer, install the package into the layer, and save and activate the layer. If the
Software Virtualization Agent is not present, the package is installed normally. An
SVS enabled package retains any configuration logic of the installation. (Example: If
the original installation contains a prerequisite that checks for a specific version of
the .NET Framework runtime and installs it if needed, this is retained in the enabled
package.)
See About SVS Enabled Packages in the Software Manager Help.
Introduction to Wise Package Studio
z SetupCapture
SetupCapture lets you convert an existing .EXE or .MSI installation into a virtual
software package. You can run SetupCapture from within Virtual Package Editor or
as a stand-alone tool to capture the installation. Y ou can then edit the package with
Virtual Package Editor. A virtual software package created with SetupCapture does
not retain any of the installation’s configuration logic.
See About SetupCapture in the Virtual Package Editor Help.
z Virtual Package Editor
Virtual Package Editor lets you edit any virtual software package. You can edit the
contents of a layer, exclude data from a layer, and add deletion entries or data
layers. You can also add command lines or WiseScripts to be executed when a
layer’s events are triggered.
See About Virtual Package Editor in the Virtual Package Editor Help.
Virtual Package Editor also lets you create a new package as a virtual software
layer. You can create an application layer or a data layer. When you create a layer,
the output for that layer can be a virtual software layer or virtual software project
file (.WVP). When you compile a .WVP file, it generates a .VSA file.
See Wise Package Studio File Types on page 31.
Distribution and management of virtual software packages
After you create a virtual software package, you can use Package Distribution to
distribute it to a network directory or an FTP server. You also can import virtual software
packages (.WVP and .VSA) into Software Manager for purposes of impact and risk
assessment.
Because there is no need to detect conflicts between a virtual software package and
other packages, ConflictManager does not generate conflicts for these packages. By
default, virtual software packages do not appear in ConflictManager, but you can change
the conflict filtering options to display them.
Wise Package Studio Reference 30
The WiseScript Script Editor has a set of script actions that you can use to manage, edit,
find, and create virtual software layers. Each of these script actions has SVS (Software
Virtualization Solution) in its name. For your convenience, these script actions are
grouped by default under the SVS Items title bar.
See About SVS Script Actions in the WiseScript Editor or WiseScript Package Editor Help.
Workbench tools that use software virtualization technology
z When you capture a package with SetupCapture using the SmartMonitor or
Snapshot method, you can perform the capture in a virtual layer.
z 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.
See About the Altiris SVS Applet in the Virtual Package Editor Help.
Wise Package Studio File Types
In Wise Package Studio, you can create and edit different types of Windows Installer and
WiseScript installation packages. In addition, there are distinct file types for Windows
Installer merge modules, patch files, transforms, and virtual software packages. Each
extension is described below.
Introduction to Wise Package Studio
Extension Description
.CAB Cabinet file, which consists of multiple files compressed into one. A Windows Mobile
device installation consists of a single, self-extracting .CAB file, which is generated by
the CabWiz program from an information file (.INF).
.EXE Installer file, either created by you or obtained from a software vendor.
You create a WiseScript .EXE by compiling a WiseScript project file (.WSE) in
WiseScript Editor or WiseScript Package Editor.
You create a Windows Installer .EXE by usi ng Windows Installer Editor to place an .MSI
file inside an .EXE file.
See Setting Build Options for a Release in the Windows Installer Editor Help.
.INF Device information file, which specifies directories, files, settings, and configurations
that are used to install a mobile device application. An .INF file is the project file
format in the Mobile Device Package Editor, and is compiled to a .CAB file.
.LPR (Not available in Standard Edition.) Linux project, which describes a Linux installation.
You edit an .LPR in Linux Package Editor and compile it to a shell file (.SH).
.MSI Windows Installer database, which is a distributable installation. The .MSI extension is
associated with the Windows Installer executable, MSIExec.EXE. When an .MSI is
opened, Windows Installer executes it, th ereby installing the app lication. Y ou can open
and edit an .MSI in Windows Installer Editor. However, options that have to do with
creating an .MSI, such as those on the Releases, Release Settings, and Media pages,
are unavailable.
Wise Package Studio Reference 31
Introduction to Wise Package Studio
Extension Description
.MSM Windows Installer merge module, which is a pre-compiled library of components (files,
registry changes, and other system changes) that installs a discrete part of your
application. It cannot be run alone, but must be merged with an .MSI during the .MSI
compile.
See About Merge Modules in the Windows Installer Editor Help.
.MSP Windows Installer patch, which updates an existing installed application. Patches
contain only the differences between the old and new versions of an application. Yo u
create a patch installation with the Patch Creation tool, which creates an .MSP file that
you distribute to end users.
.MST Windows Installer transform, which changes a Windows Installer package at run time
and must be applied from the command line.
See About Transforms in the Windows Installer Editor Help.
.PCP Windows Installer patch project, which describes and compiles to a Windows Installer
patch. A .PCP file is created from the Patch Creation tool.
.SH (Not available in Standard Edition.) Linux installation shell, which acts as a “wrapper”
to the installation RPM. The shell file is compiled from the Linux project file (.LPR).
.SOE (Not available in Standard Edition.) File created by SOE Snapshot when it captures a
standard operating environment (SOE). You can import an .SOE into the Software
Manager database to represent a baseline machine in your organization.
.VSA (Not available in Standard Edition.) A virtual software archive file created by the
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.
See About the Altiris SVS Applet in the Virtual Package Editor Help.
.WOS (Not available in Standard Edition.) A Virtual OS file created by the Virtual OS Creation
utility.
.WPF (Not available in Standard Edition.) A Wise package definition file (.WPF), which
defines what is needed to install a package.
.WSE (Not available in Standard Edition.) WiseScript project. This file extension is unique to
Wise products. You can open and edit a .WSE in WiseScript Editor or WiseScript
Package Editor and compile it to create a corresponding .EXE.
.WSI Windows Installer project, which describes an .MSI but does not store contents. It is in
the same format as an .MSI. You edit a .WSI in Windows Installer Editor and compile it
to the corresponding .MSI. The .WSI file is smaller than an .MSI and you can set
multiple options for the output of the .MSI.
.WSM Windows Installer merge module project, which describes an .MSM, but does not store
merge module contents. You edit a .WSM in Windows Installer Editor and compile it to
the corresponding .MSM.
See About Merge Modules in the Windows Installer Editor Help.
.WVP (Not available in Standard Edition.) A virtual software project file that compiles to a
.VSA file in the Virtual Package Editor. You can use SetupCapture to capture an
application and save the output as a .WVP file. You can also create a .WVP file in the
Virtual Package Editor.
Wise Package Studio Reference 32
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. To set the status, change the Status field in Project Setup.
With Enterprise Management Server, a project can have any of nine statuses: Open,
Analyzing, Packaging, Validating, Testing, Deconflicting, Complete, Closed, and On Hold.
Use the ones that meet your corporate standards. To set the project status:
z Select a status in the Project Management tab in Workbench, or
z Complete a task that has a status entered in the Update project status upon
task completion to field in Process Templates Setup, or
z Change the Status field in Project Setup
Use the project status to filter projects in the Active Project list in Workbench. You set
the filter criteria in Workbench Preferences.
Introduction to Wise Package Studio
Package Status
(Not available in Standard Edition.)
Indicates the state of packages in the Software Manager database. Use the package
status to determine whether a package can be deployed to end users.
A package can have any of three statuses: Under Development, Av ailable, or Re tired. To
set the package status, either change the Status field in the Software Ma nager P ackage
pane or run Software Manager as a task that uses a command-line option to change the
status automatically.
Use the package status to filter the display of packages in ConflictManager.
See Changing the Package Status in the Software Manager Help.
Product Documentation
This documentation assumes that you are proficient in the use of the Windows operating
system. If you need help using the operating system, consult its user documentation.
Use the following sources of information to learn about this product.
Online Help
The online help contains detailed technical information and step-by-step instructions for
performing common tasks.
Access help in the following ways:
z To display context-sensitive help for the active window or dialog box, press F1.
z To select a help topic from a table of contents, index, or search, select Help menu >
Help Topics.
Wise Package Studio Reference 33
Introduction to Wise Package Studio
Reference Manuals
All the material in the online help is also available in a .PDF-format reference manual,
which you can access by selecting Help menu > Re ference Manual.
The following tools have separate manuals: ConflictManager, Linux Package Editor,
Mobile Device Package Editor, Software Manager, Virtual Package Editor, Windows
Installer Editor, and WiseScript Package Editor.
Getting Started
The Getting Started Guide contains system requirements, installation in structions, and a
tutorial. You can access a .PDF version of the Getting Started Guide from the Windows
Start menu.
The installation and repository management sections of the Getting Started Guide are
also available as online help. In the Wise Repository Manager, select Help menu > Help
Topics, or click the Help button on any of the Wise Package Studio installation dialog
boxes.
Release Notes
The product release notes cover new features, enhancements, bug fixes, and known
issues for the current version of this product. T o access the release not es, 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. In Wise for Windows Installer, select Help
menu > Windows Installer SDK Help.
Version 4.5 of the Windows Installer SDK Help is provided. If you have obtained a later
version, links from the Wise product documentation to the Windows Installer SDK Help
might not work.
Wise Package Studio Reference 34
Chapter 2
Setting Up Wise Package Studio
This chapter includes the following topics:
z Steps for Setting Up Wise Package Studio on page 35
z About Wise Package Studio Security on page 38
z License Management on page 47
z 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
Package Studio and its tools.
Follow the steps below to set up Wise Package Studio. Depending on your organization’s
requirements, you might need to perform additional setup steps, or you might be able to
skip some of these steps.
To perform the steps that require a Wise Package Studio tool, run the tool from the
Tools tab or the Projects tab. In the Professional Edition, you can use the predefined
project named Initial Workbench Setup, which contains tasks that help you perform
these steps.
See Using the Initial Workbench Setup Project on page 38.
To set up Wise Package Studio
1. Define company standards.
Define and document standards for repackaging applications.
Examples:
The privileges under which applications are installed.
What you need to do to incorporate inventory or licensing control within your
environment.
How you register files.
What file versions are approved.
How to handle duplicate files. For example, what do you want to do when you
install an application, and a file in the installation already exists on the
destination computer? Do you want to alw ays overwrit e if the file being installed
is newer than the existing file, or always install all files regardless of version?
If you do not already have corporate standards, you can use the Microsoft Windows
application specification as a starting point. Search for “Application Specification for
Microsoft Windows” in the MSDN Library (msdn.microsoft.com/library). After you
define your standards, document them in a text processing program.
2. Configure licensing. (Not available in Standard Edition.)
Wise Package Studio Reference 35
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.
See Assigning Licenses on page 50.
With Enterprise Management Server, you must add users in Security Setup.
See Creating Users on page 41.
3. Configure security. (Enterprise Management Server only.)
Determine how your users can use Wise Package Studio.
To perform this step, select Edit menu > Security to create security groups and
assign permissions to each group. Then create users and assign them to groups. To
provide an additional level of security, your database administrator can set
permissions on tables in the Workbench and Software Manager databases.
See About Wise Package Studio Security on page 38.
4. Define SetupCapture standards.
Define standards for capturing installations with SetupCapture. Customize
configuration settings that will be used each time SetupCapture is run.
To perform this step, run SetupCapture Configuration.
See SetupCapture Configuration on page 202.
5. Capture standard operating environment. (Not available in Standard Edition.)
You can capture, or mak e a snapshot of, the standard operating environment (SOE)
of a baseline computer. This lets you find conflicts between applications and the
SOE.
To perform this step, run SOE Snapshot and then use Software Manager to import
the snapshot into the Software Manager database.
See SOE Snapshot on page 242 and Package Import in the Software Manager Help.
Warning
Predefined templates are read-only. Editing them is not recommended, because they
might be overwritten during Wise Package Studio upgrades. Instead, save customized
templates with different names.
6. Customize Windows Installer template.
By default, when you create a new Windows Installer package, Windows Installer
Editor opens a project file configured with commonly-used default settings. This
default project file is based on a template that you can customize.
To perform this step, run Windows Installer Editor and open the file Windows
Application.wsi, 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.
7. Customize merge module template.
By default, when you create a new Windows Installer merge module, Windows
Installer Editor opens a file configured with commonly-used default settings. This
default merge module file is based on a template that you can customize.
Wise Package Studio Reference 36
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.
8. Customize WiseScript template. (Not available in Standard Edition.)
By default, when you create a new WiseScript package, WiseScript Package Editor
contains a basic installation script. This default script is based on a template that
you can customize.
To perform this step, run WiseScript Package Editor and open the file Empty
Project.wse, which typically is located in the WiseScript Editor\Templates directory.
Save the customized template with a new name.
See Creating and Editing Installation Templates in the WiseScript Package Editor
Help.
9. Define ConflictManager settings. (Not available in Standard Edition.)
Define conflict settings, which determine the type of conflicts that are detected and
the files and registry keys that are excluded from conflict detection. Also decide
whether to use conflict resolution rules and, if so, decide which predefined rule sets
to use.
To perform this step, run ConflictManager. Select Setup menu > Conflict Settings
and edit the default settings based on your corporate standards. Then select Setup
menu > Conflict Resolution Rules and edit the predefined rule sets or create new
rule sets (optional).
See About Conflict Settings and Conflict Resolution Rules in the ConflictManager
Help.
10. Set preferences.
Set preferences to control the behavior of Workbench and several other tools.
To perform this step, select Edit menu > Preferences in Wise Package Studio. Then
set any options as needed.
See Workbench Preferences on page 52.
Also set preferences in:
Windows Installer Editor.
See Setting Options in the Windows Installer Editor Help.
WiseScript Package Editor. (Not available in Standard Edition.)
See Setting Preferences in the WiseScript Editor Help.
Software Manager. (Not available in Standard Edition.)
See Setting Software Manager Preferences in the Software Manager Help.
When you complete these setup steps, you can begin to use Wise Package Studio.
Wise Package Studio Reference 37
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 processoriented approach.
The tasks in the Initial Workbench Setup project mirror the steps for setting up Wise
Package Studio.
See Steps for Setting Up Wise Package Studio on page 35.
To set up Wise Package Studio
1. Start Wise Package Studio.
2. Click the Projects tab.
3. If the Initial Workbench Setup project does not appear, select it from Active
Project.
4. Do the following for each task, in order:
Setting Up Wise Package Studio
a. Select the task and read the help text that appears in the right pane. If the task
is associated with a tool, you can display help text for the tool by clicking the
View Tool Help link in the upper right of the right pane.
b. If a Run link appears to the right of a task, it means that the task is associated
with a tool. Click the Run link to start the tool, then use the tool as needed to
perform the task.
c. As you finish each task, mark the check box to the left of the task to indicate
that the task is complete. Tasks that are associated with tools are set up to be
marked complete automatically.
About Wise Package Studio Security
¾ Enterprise Management Server only.
You can set sever al levels of securit y to determine how your users can use Wise Package
Studio.
Built-in security
Use Security Setup to control user access to Wise Package Studio tools and functions
within tools. In Security Setup, you create security groups and assign permissions for
each group.
See Creating Groups and Setting Permissions on page 39.
Examples:
z Restrict access to Process Templates Setup
z Prevent certain users from using the Tools tab
z Allow access to ConflictManager, but restrict access to ConflictManager functions
such as resolving conflicts and deleting applications
Wise Package Studio Reference 38
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.
See 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. (Example:
Setting certain tables to read-only prevents users from changing database tables to
bypass the built-in security in Workbench.)
See Setting Database Security on page 46.
Project task access
You can assign users to specific project tasks. When users work on a project, they can
perform only the tasks assigned to them.
See Assigning Users to Tasks in a Project on page 81.
Integrating With Windows NT Security
Setting Up Wise Package Studio
¾ The Workbench database must contain at least one Enterprise Management
Server license.
In a Windows NT environment, you can integrate Wise Package Studio security with
Windows security in several ways:
z During logon, a user can specify how to validate their logon by selecting from a list
of Windows NT domains.
z A user can log on to Wise Package Studio with their current Windows NT us er name.
When the user starts Wise Package Studio, they are logged on to Wise Package
Studio automatically.
z In Security Setup, instead of creating users individually, you can import an entire
group of users from an NT domain. (Enterprise Management Server only.)
When a user logs on with a Windows NT account, or when they use the c urren t networ k
logon, Security Setup must contain a securi ty group whose name matches a v alid group
in the NT domain, and the user must be defined in that domain group.
Recommendations:
z Set up Windows NT domain groups according to Wise Package Studio functions.
Example: repackagers, managers, team leaders.
z A user should be in only one Package Studio-related NT group. If a user is in
multiple NT groups, they are logged on under the first valid group encountered.
Creating Groups and Setting Permissions
¾ Enterprise Management Server only.
Use Security Setup to create and edit security groups. A security group consists of a
group name and a series of permission settings. You use the settings to specify:
Wise Package Studio Reference 39
Setting Up Wise Package Studio
z Whether members of the group can view tabs and edit the project, process, and tool
setups in Workbench.
z Which tools members of the group can use.
z 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.
Wise Package Studio contains three predefined security groups.
See Predefined Security Groups on page 41.
To create groups and set permissions
1. In Wise Package Studio, select Edit menu > Security.
The Security Setup dialog box appears.
2. Right-click in the left pane and select Add > Group.
A new group appears in the list in the left pane and is selected in the right pane.
3. In Name in the right pane, type the name to use for this group.
If you want users to log on with a Windows NT user name, Security Setup must
contain a group whose name matches a valid group in the NT domain.
See Integrating With Windows NT Security on page 39.
4. In Permissions:
a. Mark options to allow access to areas of Wise Package Studio.
No Access
Members of this group cannot access the selected area.
View
Members of this group can display the selected area but cannot make
changes.
Edit
Members of this group can add to or change information in the selected
area.
b. Under the Workbench Settings folder, mark check boxes to allow access to
Workbench tabs. At least one of these check boxes must be marked.
c. Mark check boxes under the following folders to allow access to specific
functions in these tools:
Software Manager Settings.
See Setting Software Manager and ConflictManager Security on page 43.
ConflictManager Settings.
See Setting Software Manager and ConflictManager Security on page 43
SetupCapture Configuration Settings.
See Setting SetupCapture Configuration Security on page 44.
5. In the Tools list, mark the check boxes to allow access to individual tools. The list
includes predefined tools as well as tools you create.
The new group is saved when you create or select another group or user or when you
click Close.
Wise Package Studio Reference 40
Setting Up Wise Package Studio
After you create a group, you can assign users to it.
See 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. It contains one
predefined user named Admin.
Unassigned
Users are added or moved to this group when:
z You add a user without assigning a license.
z You delete a group that contains users.
z You unassign all licenses from a user.
Creating Users
z A user has a license other than Professional Edition, Quality Assurance, or
Enterprise Management Server.
Users in this group cannot log on to Wise Package Studio. Y ou should reassign any users
that are placed in the Unassigned group. To do so, you must assign them at least one
license.
Wise Users
This group is reserved for users who have a license for Professional Edition or Quality
Assurance, but not Enterprise Management Server.
Users are added or moved to this group when:
z You add a user with a license for Professional Edition or Quality Assurance.
z A user has a license for Professional Edition or Quality Assurance and Enterprise
Management Server, and you delete or unassign the Enterprise license.
¾ Enterprise Management Server only.
Use Security Setup to create and edit users. A user has a user name, a password , and a
security group assignment. The user name and password are used to log on to Wise
Package Studio. The group assignment determines the user’s access to Wise Package
Studio tools and functions within tools.
A quick way to add multiple users is to import users from an NT group.
Wise Package Studio has one predefined user, Admin, which is assigned to the WPS
Administrator group. You can edit the Admin user but you cannot edit the WPS
Administrator group.
Wise Package Studio Reference 41
Setting Up Wise Package Studio
To add a user
1. Select Edit menu > Security.
The Security Setup dialog box appears.
2. In the left pane, right-click a group and select Add > User.
The Assign User Licensing dialog box appears.
3. 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.
If the Assign User Licensing dialog box indicates that no licenses are available, you
must add serial numbers. Click OK. The user is added to the Unassigned group
because users without a license cannot be added to any other group. Exit Security
Setup and add one or more serial numbers.
See Adding Serial Numbers on page 49.
4. In Name in the right pane, enter the name this user should use when logging on to
Wise Package Studio. In a Windows NT environment, you can enter the user’s
Windows NT user name.
5. In Password, enter a unique password for this user to use when logging on to Wise
Package Studio. This should be different from the user’s Windows NT password,
because you should not store NT passwords in the Workbench database.
6. In a Windows NT environment, you can enter the user’s domain in Domain. When
the user starts Wise Package Studio while logged on to this domain, they are logged
on to Wise Package Studio automatically.
7. From Group, select the security group to assign this user to.
The new user is saved when you create or select another group or user or when you
click Close.
To import users from an NT group
This creates users in the Workbench database with the same user names as users in the
Windows NT group you import. This is different from when a user logs on with their
domain logon.
See Integrating With Windows NT Security on page 39.
If you import a Windows NT group multiple times, additions to the NT group are added
to the Workbench database, however, removals from the NT group are not removed
from the Workbench database.
1. Select Edit menu > Security.
The Security Setup dialog box appears.
2. In the left pane, right-click a group and select Add > Import NT Group.
The NT Group Import dialog box appears.
3. Complete the dialog box and click OK:
Domain
NT Group
Wise Package Studio Reference 42
Select the domain from which to import the users.
Select the domain group of users to import.
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.
4. 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. Licenses are assigned to users in
order.
If there are not enough licenses, the users that do not get license assign ments
are added to the Unassigned group.
Any user that is not assigned an Enterprise Management Server license is added
to the Wise Users group.
Setting Software Manager and ConflictManager Security
¾ Enterprise Management Server only.
Security Setup contains settings that allow access to specific functions in Software
Manager and ConflictManager.
Recommended process
1. Organize Software Manager and ConflictManager users into security groups
according to the level of permissions you want to grant them.
Mark This Check
Box in Security
Setup
Database
Administration
Examples:
Administrator. Usually the database administrator.
Workbench Users . User s who r epackage a pplications and manage confli cts. You
might create a separate group for team leaders, if you want to give them access
to more functions than other users.
Management. Supervisors and managers who need to view conflicts, create
groups, and view reports.
2. Create the groups in Security Setup.
See Creating Groups and Setting Permissions on page 39.
3. Decide which areas of the ConflictManager interface to enable for each group. See
the following tables for recommendations.
4. In the Security Setup dialog box:
a. In the Tools list, mark Software Manager and ConflictManager.
b. In the Permissions list, mark or clear check boxes under the Software
Manager Settings and ConflictManager Settings folders.
Recommended security settings for Software Manager
Allows Access to Set for
Admin
Delete database contents,
compress database, edit Network
Index Properties
X
Set for
Leaders
Set for
Users
Set for
Managers
Wise Package Studio Reference 43
Setting Up Wise Package Studio
Mark This Check
Box in Security
Setup
Package
Subscriptions
Group Setup Create, edit, and delete package
Import Packages Import packages X X X
Delete Packages Delete packages from the database X X
Change Package
Properties
Manage Meta Data
Fields
Edit Meta Data Values Edit meta data values in both
Change Package
Status
Add/Edit Package
Definitions
Allows Access to Set for
Admin
Add and edit subscriptions; refresh
subscriptions
groups; set group properties;
remove packages from groups
Edit the Package Attributes dialog
box (except meta data); create and
edit package relationships
Add and edit meta data fields X X
Software Manager and
ConflictManager
Change the Package Status in the
Package pane
Define packages using Package
Definition
XX
XX XX
XX X
XX X
XX
XX X
Set for
Leaders
Set for
Users
Set for
Managers
Recommended security settings for ConflictManager
Mark This Check
Box in Security
Setup
Conflict Setup Edit conflict settings; edit conflict
Resolve Conflicts Resolve; resolve with rules X X
Export Packages Export; export and recompile X X X
Change Resource
Properties
Allows Access to Set for
Admin
XX X
resolution rules
Edit the Properties dialog box X X X
Set for
Leaders
Setting SetupCapture Configuration Security
¾ Enterprise Management Server only.
SetupCapture and SOE Snapshot use settings from a configuration file to determine
certain aspects of the capture, such as what directories are examined for changes and
what files and registry entries are excluded by default. When no security is set, users
can use and edit any local configuration file or the configuration file in the share point
directory.
Set for
Users
Set for
Managers
Wise Package Studio Reference 44
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.
Mark the following check boxes under the SetupCapture Configuration Settings folder:
z Allow Non-Shared Configuration File
Lets users select a file other than the one in the share point directory to use during
SetupCapture and SOE Snapshot.
Mark this check box to:
Let users select any local configuration file by clicking the Change button in
SetupCapture.
Let users edit any local configuration file by clicking the Settings button in
SetupCapture.
Let users edit any local configuration file in SetupCapture Configuration.
Clear this check box to force users to use the configuration file on the share point
for all SetupCaptures and SOE Snapshots.
z Modify Configuration File on Share Point
Lets users edit the shared configuration file in the share point directory. Limit this
permission if you plan to develop a global configuration file and maintain its
integrity for all captures.
Mark this check box to:
Let users select the configuration file in the share point directory by clicking the
Change button in SetupCapture, and then edit it by clicking the Settings button.
Let users edit the configuration file in the share point directory in Set upCapture
Configuration.
Clear this check box to create a comprehensive configuration file in the share point
directory and prevent changes to it.
Items disabled by SetupCapture Configuration settings
Item Where it Appears When it is Disabled
Change button Welcome page of
SetupCapture,
SetupCapture
Configuration, and SOE
Snapshot
Allow Non-Shared Configuration File is cleared
Wise Package Studio Reference 45
Setting Up Wise Package Studio
Item Where it Appears When it is Disabled
Settings button Welcome page of
SetupCaptur e and SOE
Snapshot
Use configuration file on
share point option
Exclude Globally button Exclusions page of
SetupCapture Configuration Workbench tool Both Allow Non-Shared Configuration File and
Configuration File page of
SetupCapture
Configuration
SetupCaptur e and SOE
Snapshot
z Both Allow Non-Shared Configuration File
and Modify Configuration File on Share
Point are cleared
Or
z 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
Note
If this button is disabled, the user can select th e Do
not change current configuration file option on
the Welcome dialog box to enable it. Any changes
they then make to the configuration settings apply
to the current capture only. The Do not change
current configuration file option is enabled only if
the user has permission to use the Se tupCapture
Configuration tool.
Allow Non-Shared Configuration File is marked
and Modify Configuration File on Share Point is
cleared
Modify Configuration File on Share Point is
cleared
Modify Configuration File on Share Point are
cleared
Setting Database Security
To provide an additional level of security, your database administrator can set
permissions on tables in the Workbench and Software Manager databases. This is not
required, but is an option if you are concerned about unauthorized users changing
database tables outside Wise Package Studio.
Note
The following recommendations assume that you are a database administrator familiar
with creating and maintaining a SQL Server database. We do not offer technical support
for SQL Server or SQL Server Express.
Recommended database permissions
The administrator should have read/write permission for all tables.
Warning
Setting permissions that are more strict than the following recommendations can result
in database errors.
Wise Package Studio Reference 46
Setting Up Wise Package Studio
Database Tables Permission to set for users other
than administrator
Workbench GroupBits
Read-only
Workbench UserPassword Read/write if users can change their own
Workbench All other tables Read/write
Software Manager All tables Read/write
To set database security in SQL Server and SQL Server Express
Use SQL Server Enterprise Manager to set permissions on each table in the Workbench
and Software Manager databases. You set permissions by either user or group,
depending on whether you have set up database security groups. These groups are
different from the groups in Security Setup in Wise Package Studio.
License Management
¾ Not available in Standard Edition
The flexible licensing model in Wise Package Studio lets organizations purchase the Wise
Package Studio configuration that best meets their requirements. When you purchase
Wise Package Studio, you receive one or more serial numbers. Each serial number
represents one or more licenses for a specific edition, module, or bundle of Wise
Package Studio.
GroupTools
SecurityGroups
UserGroups
This prevents users from bypassing the
built-in security in Wise Package Studio.
passwords; otherwise read-only
Wise Package Studio is licensed per-user rather than per-machine. This means that a
user can log on to Wise Package Studio from any computer that has Wise Package
Studio installed.
Serial numbers and license assignments are stored in the Workbench database.
Therefore, if a user selects a different share point directory (in W orkbench Preferences),
and thus a different Workbench database, that user must have a different license
assignment in the Workbench database that they change to.
Users must be assigned a license for each edition and module of Wise Package Studio
that they will use. Examples:
z Company A has a repackaging team of five. Only three people need to do
repackaging. The other two people are quality assurance testers. This company
purchases three licenses of Professional Edition and two licenses of Quality
Assurance.
z Company B has a repackaging team of 10. All 10 need to do repackaging and
conflict management. They require project management capabilities and user
security . This compan y purchases 10 licenses of Professional Edition and 10 licenses
of Enterprise Management Server.
Wise Package Studio Reference 47
Setting Up Wise Package Studio
z 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.
1. Add serial numbers to the Workbench database. The licenses that these serial
numbers represent are considered available.
See Adding Serial Numbers on page 49.
2. With Enterprise Management Server, create groups in Security Setup.
See Creating Groups and Setting Permissions on page 39.
3. Add users and assign available licenses to users.
See Assigning Licenses on page 50
With Enterprise Management Server, also see Creating Users on page 41
Typically, you use User Licensing Setup to add and assign licenses. However, to
facilitate the process, license assignments can also be made:
z When an unassigned user logs on to Wise Package Studio. (Professional Edition
only. With Enterprise Management Server, the Wise Package Studio administrator
must assign licenses.)
The first time an unassigned user logs on to Wise Package Studio, if a license is
available, they are prompted to select a license. If no license is available, they are
asked to add a serial number. The user and license assignments are added to the
Workbench database.
z In Security Setup, when you add a user or group of users. (Enterprise Management
Server only.)
About User Licensing Setup
¾ Not available in Standard Edition.
User Licensing Setup provides a central location for managing Wise Package Studio
licenses.
To access User Licensing Setup, select Edit menu > User Licensing.
In the User Licensing Setup dialog box, you can:
z Add serial numbers to the Workbench database.
See Adding Serial Numbers.
z Assign and unassign licenses to users.
See Assigning Licenses on page 50.
z Delete serial numbers.
See Deleting Serial Numbers on page 51.
Wise Package Studio Reference 48
Adding Serial Numbers
¾ Not available in Standard Edition.
Before you can assign licenses to users, you must add serial number s to the Workbench
database. Use the Add Serial Number dialog box, which appears:
z During logon, if the user logging on has not been assigned a serial number, and no
serial numbers are available. (Professional Edition only. With Enterprise
Management Server, the Wise Package Studio administrator must assign licenses.)
z During logon to an evaluation version of Wise Package Studio, if the user clicks the
Add Production Serial Number button on the Evaluation Central dialog box or the
Evaluation Notice dialog box.
See About Evaluation Serial Numbers.
z In User Licensing Setup.
Select Edit menu > User Licensing. On the User Licensing Setup dialog box, click
Add Serial Numbers.
This is the easiest way to enter multiple serial numbers. Do this when you first set
up Wise Package Studio, when you purchase additional licenses, or when you
purchase upgrades.
Setting Up Wise Package Studio
Note
You cannot add production seri al number s to an evaluation version of Wise Package
Studio from User Licensing Setup. Add them from the Evaluation Centr al dialog box,
which appears when you log on to an evaluation version.
On the Add Serial Number dialog box, you can import a license file containing multiple
licenses. A license file is a text file with the extension .WLC and the following format:
serial number=user name.
Example:
XXXX-XXXX-XXXX-XXXX=maryk
The user name is optional; however, if it is included, the serial number assignment is
made when you import the file. With Enterprise Management Server, the users are
added to the Unassigned group.
To add serial numbers
1. Access the Add Serial Number dialog box as described above.
2. On the Add Serial Number dialog box, do either of the following:
In the Serial Number field, enter a 16-character serial number and click Add.
Click Browse and select a .WLC file.
The serial numbers you add are listed on the dialog box. If you import a .WLC file
that contains license assignments, the assigned users are listed also.
3. If you entered an upgrade serial number, the Previous Serial Number dialog box
appears. Enter the serial number of the previous version and click OK.
4. Click OK on the Add Serial Number dialog box.
If you added a serial number for an edition or module that contains a Web
application (Professional Edition, Quality Assurance, or Enterprise Management
Wise Package Studio Reference 49
About Evaluation Serial Numbers
An evaluation serial number cannot be added to a database that contains production
serial numbers.
An evaluation serial number expires when the evaluation time period elapses. When you
log on with an expired serial number, the Evaluation Notice dialog box appears.
z If a production serial number is available, you are assigned a serial number and
z If a serial number is not available, the Add Serial Number dialog box appears.
You cannot add production serial numbers to an evaluation version of Wise Package
Studio from User Licensing Setup. Add them from the Wise Package Studio Evaluation
dialog box, which appears when you log on to an evaluation version.
When you add a production serial number to an evaluation version, all evaluation
licenses are deleted.
Assigning Licenses
Setting Up Wise Package Studio
Server), you must install the Web application. See Installing Web Applications in the
Wise Package Studio Getting Started Guide.
logged on.
¾ Not available in Standard Edition.
Users must be assigned a license for each edition or module of Wise Package Studio
they will use. You assign licenses to users in User Licensing Setup. With Enterprise
Management Server, you also can assign licenses in Security Setup.
Before you can assign licenses to users, you must add serial number s to the Workbench
database.
See Adding Serial Numbers on page 49.
With Enterprise Management Server, you must add users in Security Setup.
See Creating Users on page 41.
To assign licenses in User Licensing Setup
1. Select Edit menu > User Licensing.
The User Licensing Setup dialog box appears. The upper pane lists the licenses in
the current Workbench database, and the lower pane lists the licenses that are
available to be assigned.
2. Click Assign Licenses.
3. In the upper pane of the Assign Licenses dialog box, select one or more users.
If the user you want is not listed, click Add User and enter the user name.
When you select a user, that user’s existing license assignments appear as marked
check boxes in the lower pane. When you select multiple users, and some of the
selected users have a particular license assignment, that check box is marked and
shaded.
4. In the lower pane, mark one or more check boxes for the licenses to assign to the
selected users.
Wise Package Studio Reference 50
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).
See Predefined Security Groups on page 41.
5. When you finish assigning licenses, click OK.
6. With Enterprise Management Server, you might need to move the new user to
another group in Security Setup after you assign licenses. Example: When you add
a user without assigning a license, the user is added to the Unassigned group. After
you assign a license, you can move the user to a different group.
To assign licenses in Security Setup
¾ Enterprise Management Server only.
1. Select Edit menu > Security.
The Security Setup dialog box appears.
2. In the left pane, right-click a user and select Modify License.
The Assign User Licensing dialog box appears.
3. Mark one or more check boxes to assign licenses to the user and click OK.
4. You might need to move the new user to another group in Security Setup after you
assign licenses. Example: When you add a user without assignin g a license, the user
is added to the Unassigned group. After you assign a license, you can move the user
to a different group.
Deleting Serial Numbers
¾ Not available in Standard Edition.
You can delete serial numbers from the W ork bench database, which means they will not
be available for assignment to users. Example: If you are converting an evaluation
version of Wise Package Studio to a production version, you can delete any evaluation
serial numbers.
To delete serial numbers
1. Select Edit menu > User Licensing.
The User Licensing Setup dialog box appears.
2. Click Delete Serial Numbers.
The Delete Serial Number dialog box appears.
3. Select one or more serial numbers to delete and click OK. The serial number is
deleted.
4. Click Close on the User Licensing Setup dialog box.
If the deleted serial number was assigned to a user, that user might be moved to a
different group or the Unassigned group. (Enterprise Management Server only.)
Example:
Suppose a user has licenses for Professional + Enterprise Management Server + Quality
Assurance.
Wise Package Studio Reference 51
z If you delete the Quality Assurance serial nu mber, the user is not moved to another
group.
z If you delete the Enterprise serial number, the user is moved to the Wise Users
group.
See Predefined Security Groups on page 41.
Workbench Preferences
Set preferences to control the behavior of Workbench. All preference settings affect only
the current user on the local computer.
Select Edit menu > Preferences. Complete the General tab (described below), or click
another tab for:
z Activating Suppressed Prompts on page 53
z Setting Repository Preferences on page 53
Setting General Preferences
z Active Project Filter
Specify which projects appear on the Projects tab. You can display all projects or
only open projects. With Enterprise Management Server, two additional options let
you display all projects in which the next task is assigned to you, or all projects
containing a task assigned to you.
Setting Up Wise Package Studio
z Run all tools in Full Screen Mode
This does not apply to tools that have wizard interfaces.
z Create backup copy during save
Mark this to have a new backup file created every time you save a file in either
Windows Installer Editor or WiseScript Package Editor. This check box also appears
in the preferences for each editor; this global setting affects the settings in the
individual editors.
The backup file name consists of the current file name plus a number. (Example: if
the current file name is Sample.wsi, the backups are named Sample1.wsi,
Sample2.wsi, and so on.) Only the file you are working on is backed up. (Example:
if you open a .WSI and save it, the corresponding .MSI is not backed up.) Use
caution with this option if you are working with large installation files; if you save
often, your disk space will quickly become depleted.
z Enter actual hours by
(Enterprise Management Server only.) Mark an option to specify whether you will
enter hours completed on the Project Management tab for the entire project or for
individual tasks.
z Allow Connection Attempts to Web Applic at io n s
When you run a Web application tool, and Workbench cannot connect to the
computer that is hosting Web application, the Connection Failed dialog box appears
and might continue to appear as you use Workbench.
Mark this check box to allow connection attempts and activate the Connection Failed
dialog box. Clear it to prevent connection attempts and disable the dialog box.
If you mark the Prevent Connection Attempts to Web Applications check box
on the Connection Failed dialog box, this check box is cleared.
Wise Package Studio Reference 52
See 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.
To reactivate a prompt, select it and click Activate.
Setting Repository Preferences
¾ Not available in Standard Edition.
(Client installations only.) Use the Repository tab on the Workbench Preferences dialog
box to connect to a different Wise Software Repository (the share point directory and
any databases associated with it).
Note
Changing the share point directory or a specific path does not copy resources to the new
location. Typically, you will specify a share point or path that is already in use.
Setting Up Wise Package Studio
To connect to a different repository
(Client installations only.) You can connect to a different repository by specifying the
share point that is associated with it.
When you change the default share point, you are logged off and prompted to log on.
Because serial numbers and license assignments are stored in the Workbench database,
you must have a different license assignment in the Workbench database that you
change to.
1. Select Edit menu > Preferences.
2. On the Workbench Preferences dialog box, click the Repository tab.
3. Click Browse.
4. On the Browse for Folder dialog box, browse to an existing share point directory and
click OK.
The Wise Software Repository that is associated with that share point becomes your
default.
To change the default Wise Software Repository for a server installation, use the Wise
Repository Manager . See Managing the Wise Software Repository in the Getting Started
Guide.
Wise Package Studio Reference 53
Chapter 3
Creating Projects, Processes, and Tools
This chapter includes the following topics:
z About Projects on page 54
z About Process Templates and Tasks on page 58
z About Tool Setup on page 66
z Help for Tasks and Tools on page 70
z Command Line Options on page 72
z Wise Package Studio Variables on page 75
About Projects
Wise Package Studio is project-oriented. A project defines the job you need to
accomplish. (Example: repackaging an application.) Each project lets you record
information about that job, including where project files are stored and what the project
files are named. This provides greater control over the project files and simplifies the job
for users.
Project creation
Use Project Setup to create a project for each new job. When you create a project, you
enter information about the project and specify where project files are stored and how
project files are named. With Enterprise Management Server , Securi ty Setup determines
whether you have access to Project Setup.
See Adding a New Project on page 55.
Project editing
The predefined projects cannot be edited.
With Enterprise Management Server, each project has an owner. The owner can be a
user, a group, or none. When you assign an owner to a project, you limit who can edit
the project.
Project process
In the Professional Edition, a project can be associated with a process. A process is a
series of tasks that, when completed, result in a repackaged software installation. Using
a process provides consistency in your repackaging and ensures that the project is
performed according to corporate standards. When you create a project and assign a
process to it, a copy of the original process template is stored with the project. You can
change the process within a specific project without changing the original process
template.
See About Process Templates and Tasks on page 58.
With Enterprise Management Server, you can create a project that uses a process from
an external database. If the external process uses any user-defined Workbench tools or
Wise Package Studio Reference 54
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.
See External Process Templates on page 60.
Project usage
To work on a project, you use the Projects tab.
See Using the Projects Tab on page 76.
Project information as variables
The information stored with the project provides values for the Wise Package Studio
variables. (Example: The File Name field in Project Setup provides the value for the
variable [FileName].)
See Wise Package Studio Variables on page 75.
Adding a New Project
To add a new project
1. Select Edit menu > Project.
Creating Projects, Processes, and Tools
The Project Setup dialog box appears.
2. Right-click in the left pane and select Add.
A new project appears in the project list in the left pane.
3. In the project entry fields in the right pane, specify the following:
Project Name
Enter a unique name for this project. Do not use the following special
characters: / \ : * < > |
Project Directory
Specify the directory in which to store all files associated with this project. If
multiple users will work on this project, enter a network directory. You can add
Wise Package Studio variables to the path.
See Wise Package Studio Variables on page 75.
The default project directory is [Sharepoint]\Projects\[ProjectName]. If you
change the default project directory, yo ur changes are s av ed and u sed the next
time you create a project. Example: If you change the project directory to
C:\Projects, the next time you create a new project, the project directory will be
C:\Projects\[ProjectName].
Status
Set project status.
In the Standard and Professional Editions, a project can be Open or Closed. The
only way to change project status in those editions is in this field.
Wise Package Studio Reference 55
With Enterprise Management Server, a project can have any of nine statuses.
Typically, you should use the Project Management tab to maintain project
status.
See Managing Projects on page 80.
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.
Application Name
Enter the name of the application. If your company is using Software Manager,
this name will be used to identify this installation package in the Software
Manager database. If the Software Manager database already contains a
version of this application, enter the name exactly as it appears there. If this is
a new application, enter a unique name. If this project creates a Windows
Installer package, it will have this application name when it is opened in
Windows Installer Editor (on the Product Details page) and Software Manager.
Package Name
Enter a package name to distinguish this installation from others with the same
application name. A package can represent a version of a single application or a
component of a larger suite. (Example: The Adobe Acrobat application might
contain two packages, Acrobat 8.0 and Acrobat 9.0. The Microsoft Office
application might contain packages named Office 2003 and Office 2007.) If your
company is using Software Manager, this name will be used to identify this
installation package in the Software Manager database. If this project creates a
Windows Installer package, it will have this package name when it is opened in
Windows Installer Editor (on the Product Details page) and Software Manager.
File Name
Enter the name to use for all files that are created and used by the tasks in this
project. An appropriate extension is appended to each type of file. (Example: If
you enter Sample here and run SetupCapture, a file named Sample.wsi is
created.) If you give a project a file name and directory that matches that of an
existing project, when you try to close the Project Setup dialog box you will
receive a warning that you must change one of those values.
Vendor Package
Specify the name and location of the compiled executable (.EXE) or .MSI that
you are going to repackage. You can use a variable to represent the path. If the
package is in either the project directory or the share point directory, the
[ProjectDir] or [Sharepoint] variable automatically replaces that portion of the
directory when you browse to select a vendor package.
Project Owner
(Enterprise Management Server only.) Click and select an owner for the
project from the Select Owner dialog box. The groups and users that appear in
the Select Owner dialog box are created in Security Setup. See Creating Groups
and Setting Permissions on page 39.
The owner can be a user, a group, or none. When you assign an owner to a
project, you limit who can edit the project.
Owner W ho Can Edit the Project
user That user and anyone in the WPS Administrator group
group Any user in that group or the WPS Administrator group
none Any user
Wise Package Studio Reference 56
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.
Process
(Not available in Standard Edition.) Select the process to associate with this
project. With Enterprise Management Server, if you are connected to an
external database, this list includes processes from the external database.
External processes have (External) appended to their names.
When you select a process, a copy of the original process template is stored
with the project. If you select an external process, and you reopen the project
later, the process does not have (External) appended to its name anymore
because the project contains a copy of the external process.
To change the process for this project only, click Edit to the right of Process.
Making changes here does not affect the original process template or any other
projects that use the same process template.
Warning
If you change the process or select a different process after work on this project
has begun, any existing task data will be lost.
Notes
Enter any additional information about the project.
4. To undo all changes you made to the new project, right-click the project in the left
pane and select Revert. You cannot revert after clicking another project.
5. Save the new project by clicking Close or by creating or selecting another project on
the Project Setup dialog box.
See also:
External Process Templates on page 60
Duplicating or Deleting a Project
Use Project Setup to duplicate or delete a project. Access Project Setup by selecting Edit
menu > Project.
With Enterprise Management Server, Security Setup determines whether you have
access to Project Setup.
To duplicate a project
In Project Setup, right-click a project and select Duplicate. A copy of the project appears
at the end of the project list. Tasks are copied from the duplicated project, not from the
original process template. The new project is saved when you click Close or click another
project.
See Adding a New Project on page 55.
Wise Package Studio Reference 57
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.
What is a process?
A process is a series of tasks you perform to complete a project. A process provides a
logical, consistent approach to repackaging. You can set up a process and associate it
with any number of projects. This saves time, reduces training requirements, and lets
you apply a consistent methodology to similar projects.
With Enterprise Management Server, each process has an owner group. Only members
of the owner group or the WPS Administrator group can edit a process.
What is a task?
A task is a single step to be performed in a process. A task can be associated with a
Workbench 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. You can organize
tasks into parent tasks and subtasks.
About predefined processes
Wise Package Studio contains predefined processes that are based on industry best
practices. View the predefined processes to see if they meet y our need s. If not, y ou can
duplicate one and customize the copy for your organization, or you can create a new
process.
See Predefined Process Templates on page 59.
About creating and editing processes
Use Process Templates Setup to create and edit processes and tasks. When you create a
new process, you add tasks and organize them into a logical order. You can also
duplicate a process, copy tasks between processes, export processes to files, import
process files, and delet e processes and tasks. Changing a process template does not
affect existing projects that use the template.
When you create a project and associate a process with it, a copy of the original process
template is stored with the project. You can change the process within a specific project
without changing the original process template.
See Adding a New Project on page 55.
The Process Templates Setup Interface
¾ Not available in Standard Edition.
You create processes and tasks in Process Templates Setup. To access this, select Edit
menu > Process Templates.
Wise Package Studio Reference 58
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 userdefined processes.
(Enterprise Management Server only) If you are co nnected to an external database, yo u
also see processes from the external database, which have (External) appended to their
names.
In the process list in the left pane of Process Templates Setup, processes and their tasks
are displayed in a tree structure. Expand and collapse processes to view tasks and
subtasks by using the Expand, Expand All, and Collapse commands from the right-click
menu.
Click a process or task in the left pane to display its detail in the right pane. This is
where you define the process and its tasks. The right pane also contains a text editor,
where you can create or link to a help file for tasks you define.
See also:
External Process Templates on page 60
Predefined Process Templates
Creating Projects, Processes, and Tools
¾ Not available in Standard Edition.
Wise Package Studio contains predefined processes that are based on industry best
practices. To see the predefined pr ocess templates, select Edit menu > Process
Templates.
Predefined process template names are gray because they cannot be changed. This
allows for updates and enhancements to the predefined process templates in future
releases. However, you can duplicate them and customize the copies. You can also copy
tasks from predefined process templates to processes you create.
The predefined process templates are:
Workbench configuration This process is associated with the project Initial
Workbench Setup, which leads you step-by-step
through the setup of your Wise Package Studio
environment. Normally, you only need to perform
this process once, when you first install the product.
You might repeat this process if your corporate
standards change.
See Using the Initial Workbench Setup Project on
page 38.
Repackage for Windows
Installer
Leads you through the steps needed to repackage an
installation as a Windows Installer package.
Wise Package Studio Reference 59
This process works with a single .MSI having the
default project file name. If you create multiple
releases for a package, you should either customize
the process for that project to perform tasks on all
.MSIs that are compiled, or write a macro to change
the names of the additional .MSIs to the default file
name.
Repackage into .VSA format Leads you through th e steps needed to re package an
Repackage using WiseScript Leads you through the steps needed to rep ackage an
Customize MSI using
transform
Installation Quality
Assurance
For details, click the Workbench Projects tab and click a task in the left pane to display
its help.
External Process Templates
Creating Projects, Processes, and Tools
installation as a Virtual Software Package. This
process creates a virtual software archive file (.VSA).
installation as a WiseScript.
Customizes an existing Windows Installer package by
creating a transform file. This is typically done to
eliminate end user interaction during the installation.
The results of this process are a transform file and a
shortcut to apply the transform to the base Windows
Installer package.
Leads you through the steps needed to test a
Windows Installer pac kage. (Quality Assurance only.)
¾ Enterprise Management Server only.
You can maintain a separate, or external Wise Software Repository whose Workbench
database contains master process templates that you have customized to meet your
organization’s standards. You then connect to that database from one or more other
repositories so that users of those repositories have access to the master templates.
This ensures that all users across your organization use the same standard, approved
processes.
Use Wise Repository Manager to connect to an external database by selecting the share
point directory with which it is associated. See Connecting to an External Workbench
Database in the Getting Started Guide.
When the connection is made, the process templ ates in that database become visible in
Workbench, and the predefined process templates in the local database become
unavailable. If the external share point is disconnected or otherwise unavailable, then
the predefined process templates in the local repository become available. Process
templates that users create in their local database are always available.
Wise Package Studio Reference 60
How external processes appear in Process Templates Setup
Adding a New Process
¾ Not available in Standard Edition.
Creating Projects, Processes, and Tools
Processes created by local users
Master processes from the
external database
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. Part of
creating a process is adding and arranging tasks.
With Enterprise Management Server:
z Security Setup determines whether you have access to Process Templates Setup.
z You can create process templates in a master database, to be used by multiple
repackaging teams across your organization.
z You can create processes in a regional database, to be used only by members of a
specific team.
To add a new process
1. Select Edit menu > Process Templates.
The Process Templates Setup dialog box appears.
2. Right-click in the left pane and select Add > Process.
A new process appears in the list on the left, with process entry fields on the right.
3. In Process Name, type the name for this process.
4. In Process Notes, enter a brief description.
5. (Enterprise Management Server only.) In Owner Group, specify a security group to
restrict editing of this process. Only members of the owner group or the WPS
Administrator group can edit this process. If you specify None, then anyone can
edit this process.
6. Add tasks to this new process.
See Adding Tasks to a Process on page 62.
Wise Package Studio Reference 61
7. 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.
See Organizing Tasks and Processes on page 66.
Adding Tasks to a Process
¾ Not available in Standard Edition.
Tasks are activities that must be performed to complete a process. Tasks can run
Workbench tools, installed applications such as Microsoft Word, or any other executable
programs. Tasks can also be manual, meaning they represent activities, such as
analyzing the vendor package, that do not require a program to be run. Header tasks do
not represent things the user has to do, instead, they act as informational headings for
sets of subtasks.
Use Process Templates Setup to add tasks to a process and associate them with tools or
other programs as needed. The tasks in a process should be listed in the order in which
they must be performed. You can rearrange tasks after creating them
See Organizing Tasks and Processes on page 66.
Creating Projects, Processes, and Tools
With Enterprise Management Server, Security Setup determines whether you have
access to Process Templates Setup.
Note
You can copy a task from any process into processes that you create. Because
predefined processes are read-only, you cannot copy tasks into them, but you can copy
tasks from them. When you copy a task, any help associated with that task is not
copied; the new task refers to the original help file. Use the right-click menu in Process
Templates Setup to copy and paste tasks.
To add a task to a process
1. Select Edit menu > Process Templates.
The Process Templates Setup dialog box appears.
2. Right-click a process in the left pane and select Add > Task.
A new task appears below the process, with details at the right.
3. In Task Name, enter the name for this task.
4. In Type, define the type of task:
Header
The task is an informational heading for a set of subtasks and does not require
the user to do anything. Example: The header Package Testing is a heading for
a group of subtasks.
Manual
Wise Package Studio Reference 62
Header tasks appear in bold type and do not have check boxes or Run links.
The task does not require the user to run a program or tool within Wise Package
Studio. Example: It might require the user to review the results of the
preceding task.
Manual tasks do not have Run links.
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.
See 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. The list displays the predefined
Workbench tools as well as any other tools you have added in Tool Setup.
Options
(Optional.) Enter command-line options to change the default behavior of
this tool or application.
See Guidelines for Entering Command Line Options on page 72 and Defining
Command Line Options for Tools on page 73.
Other EXE
The task requires the user to run a program other than a Workbench tool. On
the Projects tab, clicking this task’s Run link runs the program’s executable.
Example: You could set up this task to run reimaging software.
When you select this option, the following fields appear:
EXE
Specify an executable on a local or network drive that this task should run. If
you enter one that is on your local drive, other users who run this task must
have the same executable stored in the same directory on their computers.
Options
(Optional.) Enter command-line options to change the default behavior of
this tool or application.
See Guidelines for Entering Command Line Options on page 72.
Pre-defined Application
This task requires the user to run a program other than a Workbench tool.
When this task is displayed on the Projects tab, clicking its Run link starts the
application. Example: If the purpose of this task is to document results, you can
set up this task to run Microsoft Word.
When you select this option, the following fields appear:
Application
This list contains all applications installed on your computer. Select the
application that this task should run. Other users who run the task you
create must have the same application installed on their computers,
otherwise, the task will not run.
Options
(Optional.) Enter command-line options to change the default behavior of
this tool or application.
5. To prevent users from running tasks out of order, mark Verify that the file exists
before the tool is launched. Do this if the file referenced in this task’s commandline options must exist before the user can run the tool or program associated with
this task. (The file name must be the last option in the command line.) Example: If
Wise Package Studio Reference 63
See Guidelines for Entering Command Line Options on page 72.
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.
This check box does not appear if this is a manual task.
6. If this tool requires an up-to-date, compiled installation program, mark Compile
the package before the tool is launched. Example: If you are creating a task to
distribute the final version of a Windows Installer package, you need to distribute
the most current .MSI. When this check box is marked, the package installation is
compiled before starting the tool if no compiled installation exists, or if the compiled
file (.MSI, .MSM, or .EXE) is older than its associated project file (.WSI, .WSM, or
.WSE, respectively).
7. (Enterprise Management Server only.) From Update project status upon task
completion to, select the status the project should have when this task is
completed. Example: Suppose this task is “Resolve conflicts” and the next task is
“Test package.” When the “Resolve conflic ts” task is completed, you can change the
project’s status to Testing.
If you select <Do not change> , the project’ s status will not change when this task
is completed.
This drop-down list does not appear if this is a header task.
8. (Optional.) Specify or enter help text to appear when a user clicks this task on the
Projects tab. Mark one of the following options.
See Help for Tasks and Tools on page 70.
HTML
Mark this option if you have already created a help text file in a Web browsercompatible format such as .HTM or .ASP. When you mark this option, the
Location field appears.
Rich Text
Mark this option to create and edit the help text in .RTF format.
9. Save the new task by clicking Close or by clicking another task in Process Templates
Setup.
Duplicating and Deleting a Process
¾ Not available in Standard Edition.
You can duplicate any process in Process Templates Setup. The predefined processes
cannot be modified, so to use a variation of one of the predefined processes, you must
duplicate it and modify the copy.
When you duplicate a process, any task help files associated with that process are not
duplicated; the new tasks refer to the original help files. However, if you edit a help file
within the new process, a new help file is created.
You also can delete processes from Process Templates Setup, but only processes that
you have created, not predefined processes.
With Enterprise Management Server:
Wise Package Studio Reference 64
Creating Projects, Processes, and Tools
z Security Setup determines whether you have access to Process Templates Setup.
z 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.
Processes that are copied from an external database are placed in the Local
Processes tree in Process Templates Setup. Subsequent changes made to the
corporate process template will not affect your local copy.
z You cannot edit or delete an external process template.
To duplicate a process
1. Select Edit menu > Process Templates.
The Process Templates Setup dialog box appears.
2. Right-click a process in the process list and select Duplicate.
A copy of the process appears at the end of the process list.
3. Select the copy to modify it.
4. Save the new process by clicking Close or by clicking another process in Process
Templates Setup.
To delete a process
1. Select Edit menu > Process Templates.
The Process Templates Setup dialog box appears.
2. Right-click a process in the process list and select Delete.
Deleting a process template does not affect any existing projects, because each project
contains its own a copy of the process. Deleting a process cannot be undone.
Importing and Exporting Processes
In Process Templates Setup, you can export a process template to a file (.WPR) and you
can import a process template from a file. Example: You might create a process
template in one Workbench database, export it, and then import it into another
Workbench database. This lets you maintain a standard set of process templates across
multiple distributed teams.
Note
With Enterprise Management Server, you can duplicate processes from an external
database, which lets you more easily share standard process templates across
databases.
See External Process Templates on page 60.
To export a process
1. Select Edit menu > Process Templates.
The Process Templates Setup dialog box appears.
2. Right-click a process in the process list and select Export to File.
3. In the Save As dialog box that appears, specify a file name with the extension .WPR
and click Save.
Wise Package Studio Reference 65
The .WPR file is created.
To import a process
1. Select Edit menu > Process Templates.
The Process Templates Setup dialog box appears.
2. Right-click in the process list and select Import From File.
3. In the Open dialog box that appears, specify the .WPR file to import and click Open.
The process appears in the process list.
Organizing Tasks and Processes
¾ Not available in Standard Edition.
The arrangement of tasks in a process represents the order in which the tasks are
typically performed. You can change the task order in Process Templates Setup. You
also can change the order of processes in the process list, but this only affects the
display; it does not affect the use of the processes. You cannot reorganize tasks in a
predefined process.
Creating Projects, Processes, and Tools
Note
You cannot move a task outside its process. To put a task in a different process, copy
and paste it using the right-click menu.
You can cr eate a task hi er arch y, with parent tasks and subtasks. To see an example of a
task hierarchy, expand any of the predef ined processes in the process list. When you
create a task hierarchy, you might want to set up the first level of tasks as header tasks
and use them to organize sets of subtasks.
See Adding Tasks to a Process on page 62.
With Enterprise Management Server, Security Setup determines whether you have
access to Process Templates Setup.
To rearrange tasks or processes
1. Select Edit menu > Process Templates.
The Process Templates Setup dialog box appears.
2. Click a task or process and click a move tool ( ).
3. Save the updated process by clicking Close or by clicking another task in the Process
Templates Setup dialog box.
About Tool Setup
¾ Not available in Standard Edition.
A tool is an executable application that you use to accomplish a task. In the Tools tab,
you use a tool by double-clicking its icon. In the Projects tab, you use a tool by clicking
the Run link to the right of the tool or the task that is associated with the tool.
Wise Package Studio contains predefined tools that should meet most of your needs.
Wise Package Studio Reference 66
See 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 th at tool. Creating a tool for
programs you use often lets you standardize the way that tool is used. You use Tool
Setup to create, edit, duplicate, and delete tools.
When you create a tool, you can enter command-line options that affect how the
program runs.
See About Command Line Options for Tools on page 73.
With Enterprise Management Server, Security Setup determines whether you have
access to Tool Setup.
Adding a New Tool
¾ Not available in Standard Edition.
If you routinely use a third-party program in your processes, you can create a tool to
run that program. This lets you use the tool in multiple tasks and processes without
having to re-enter command-line options and other tool information each time.
Example: If many of your processes require the user to use Microsoft Word, you can
create a tool that runs Word.
Creating Projects, Processes, and Tools
With Enterprise Management Server, Security Setup determines whether you have
access to Tool Setup. You also can use Security Setup to allow or restrict access t o tools
you crea te.
See Creating Groups and Setting Permissions on page 39.
To add a new tool
1. Select Edit menu > Tools.
The Tool Setup dialog box appears.
2. Right-click in the dialog box and select Add.
A new tool appears, with details at the right.
3. Specify the following tool properties:
Name
Type the name for this tool.
Tool Group
Select the group to which to assign this tool. This determines the location of the
new tool on the Tools tab. This field is unavailable for predefined tools.
Tool Type
Select the type of tool you are creating:
Predefined Application
This tool runs an application, such as Microsoft Word or Notepad, that is
installed on your computer.
Wise Package Studio Reference 67
When you select this option, the Application list appears. This list contains
most applications installed on your computer. Select the application this tool
runs. Users who run this tool must have the same application installed on
their computers, otherwise, the tool will not run.
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. You can specify a path relative to the location of
Workbench.exe. If the executable is on the local drive, other users who run
this task must have the same executable stored in the same directory on
their computers. Icon shows the icon that is associated with this tool.
Browse to select a new icon. If you change it, other users mu st h ave access
to the new icon file.
Web Application
This tool runs a Web application in the right pane of Workbench.
See Adding a Web Application as a Tool on page 68.
Command Line
Enter command-line options to change the default behavior of this tool.
See Guidelines for Entering Command Line Options on page 72 and About
Command Line Options for Tools on page 73.
Hide from Tools tab in Workbench
Mark this check box to hide this tool in the Tools tab. When you hide a tool, you
still can associate it with a task, but users cannot start it from the Tools tab.
This prevents users from running the wrong tool accidentally and from using
tools that should only be used from within a process. You also can use this
check box to hide predefined tools that your company never uses. This option
does not affect tasks associated with that tool or the display of tools in the
Projects tab.
4. (Optional.) Specify or enter help text to appear when a user clicks this tool on the
Tools tab. Mark one of the following options.
See Help for Tasks and Tools on page 70.
HTML
Mark this option if you have already created a help text file in a Web browsercompatible format such as .HTM or .ASP. When you mark this option, the
Location field appears.
Rich Text
Mark this option to create and edit the help text in .RTF format.
5. Save the new tool by clicking Close or by clicking another tool in Tool Setup.
Adding a Web Application as a Tool
¾ Not available in Standard Edition.
You can run a Web application from within Workbench by adding it as a tool.
To add a Web application as a tool
1. Add a new tool.
Adding a New Tool on page 67.
2. From the Tool Type drop-down list, select Web Application.
Wise Package Studio Reference 68
Creating Projects, Processes, and Tools
3. 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
4. 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.
5. Mark Allow Local Override of URL to let users specify a new URL in the
Connection Failed dialog box that appears when Workbench cannot connect to the
computer that is hosting this Web application. The new URL is stored in the user’s
registry instead of the Workbench database. If you clear this check box, then only
users who have security access to Tool Setup can specify a new URL, because doing
so changes the URL for all users.
6. When you change the URL for an existing tool, mark Set URL for All Users to save
the new URL in the database and apply the change to all users who do not have a
local override. If you clear th is check box, the URL is changed in your registry and
does not affect other users.
If Allow Local Override of URL is cleared, this is marked by default and cannot be
changed.
7. Complete the tool entry.
See Adding a New Tool on page 67.
Duplicating, Deleting, and Rearranging Tools
¾ Not available in Standard Edition.
Use Tool Setup to duplicate, delete, or rearrange tools.
When you duplicate a tool, any help file associated with that tool is duplicated also.
With Enterprise Management Server, Security Setup determines whether you have
access to Tool Setup.
To duplicate a tool
1. Select Edit menu > Tools.
The Tool Setup dialog box appears.
2. Right-click a tool and select Duplicate.
A copy of the tool appears at the end of the tool list.
See Adding a New Tool on page 67.
3. Save the new tool by clicking Close or by clicking another tool in Tool Setup.
To delete a tool
Warning
Do not delete a tool that is associated with any tasks because it disables the task and
prevents you and other users from running it.
1. Select Edit menu > Tools.
The Tool Setup dialog box appears.
2. Right-click a tool and select Delete.
Wise Package Studio Reference 69
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.
1. Select Edit menu > Tools.
The Tool Setup dialog box appears.
2. Select a tool and click or .
3. Save the new tool order by clicking Close or by clicking another tool in Tool Setup.
This only affects the display; you can always use the tools in any order. This does not
affect the display of tools on the Projects tab.
Note
No matter where you move a tool in Tool Setup, it will not be displayed outside its tool
group unless you change the Tool Group field.
Help for Tasks and Tools
Creating Projects, Processes, and Tools
¾ Not available in Standard Edition.
The Description tab in the right pane of the Projects and Tools tabs displays help text on
the currently selected task or tool. If you create a process, tool, or task, you can write
help in HTML or .RTF format and associate the help file with the task or tool. W rite HTML
format help outside Workbench. You can write .RTF format help text directly in
Workbench.
With Enterprise Management Server, Security Setup determines whether you have
access to Process Templates Setup and Tool Setup.
Using HTML for help
In Process Templates Setup or Tool Setup, mark the HTML option and in the Location
field that appears, enter one of the following:
z If the help file is located in the Workbench directory under your share point
directory, enter the file name. You do not have to include the full path.
z If the help file is not located in the Workbench directory, enter the full path
(Example: C:\Development\MyHelp.htm). To browse for the file, click Options and
select Browse.
z Enter a URL (Example: www.Company.com/MyHelp.htm).
z If a help file is already specified, you can edit it; click Options and select Edit. The
file opens in your default HTML editor or in Notepad.
Using rich text for help
In Process Templates Setup or Tool Setup, mark the Rich Text option to show a simple
text editor for authoring in .RTF format. The help text you associate with a tool or task is
saved in the Workbench directory under your share point directory.
Wise Package Studio Reference 70
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. Click this to open a
standard Windows Insert Object dialog box, where you can select the
object to insert.
Available objects can vary depending on the computer. If you add an object
that other users do not have on their computers, they will not see the
object in the help text.
Edit with WordPad
If Microsoft WordPad is installed on your computer, click this tool to open
the help text as a WordPad document. This lets you use WordPad
formatting and other features to create and edit the text. When you save
the file and close WordPad, the updated help text appears in the help text
editor.
Edit with Word
If Microsoft Word is installed on your computer, click this tool to open the
help text as a Word document. This lets you use more advanced Word
features to create and edit the text. However, because the help file is saved
in Rich Text Format, some of the formatting, such as tables, might not be
saved. When you save the file and close Word, the updated help text
appears in the help text editor.
Note
When you edit with either WordPad or Word, you cannot do anything else in Wise
Package Studio until you save the text file and close WordPad or Word.
See also:
Adding Wise Package Studio Variables to Help Text
Adding Wise Package Studio Variables to Help Text
¾ Not available in Standard Edition.
You can add a Wise Package Studio variable to tool or task help, whether the help is in
HTML or .RTF format. When the help is displayed in Workbench, the value of the variable
is displayed.
Example:
Suppose one of your processes contains a task to run SetupCap ture and create a
Windows Installer project file. To have the help text for that task display the file’s
location and name, add the following variables to the help text:
[ProjectDir]\[ProjectName].wsi
Wise Package Studio Reference 71
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.
See Wise Package Studio Variables on page 75.
Command Line Options
¾ Not available in Standard Edition.
You can use comm and- li ne options to change the w a y a tool or task runs in Workbench.
Example: You can s et an option that causes Windows Installer Editor to open the default
project package automatically. Enter command-line options when you create a tool in
Tool Setup or when you create a task in Process Templates Setup.
See About Wise Package Studio command-line options on page 268 and Guidelines for
Entering Command Line Options.
Creating Projects, Processes, and Tools
Most predefined tools require a command-line option to run. In general, you should not
change the command-line options of predefined tools, or the tool might not run
properly.
To customize the way a predefin ed tool runs, it is best to add command-line options
when you associate that tool with a task in Process Templates Setup. There, you can
select from predefined command-line options for that tool. These predefined options
have plain English descriptions that make it easier to understand what each commandline option does. You can define options for the predefined tools or for any tool you
create.
See Defining Command Line Options for Tools on page 73.
Warning
Changing an existing command-line option affects all existing projects and processes
that use that option.
Guidelines for Entering Command Line Options
When you add a new tool or when you add tasks to a process, you can enter commandline options to apply to the tool that runs (optional). In Process Templates Setup, you
add command-line options to the Options field. In Tool Setup, you add command-line
options to the Command Line field.
See About Command Line Options for Tools on page 73.
Follow these guidelines when entering command-line options:
z If there is a right-arrow button next to Options or Command Line, you can click
the button and select a Wise Package Studio variable.
See Wise Package Studio Variables on page 75.
z If there is a Define button next to Options or Command Line, you can define a
new command-line option.
Wise Package Studio Reference 72
See Defining Command Line Options for Tools on page 73. After defining a
command-line option, it appears in Options.
z 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.
See About Wise Package Studio command-line options on page 268.
z If you are working with a tool that is not included in Workbench, see the program’s
documentation for information about its command-line options. Example: If you
select Word as the tool, you can enter a command-line opt ion to pass the document
name when Word is opened, so that Word opens the named document.
z If the command-line option contains a path or file name, enclose it in quotation
marks.
About Command Line Options for Tools
When you create a tool, you can enter command-line options that affect how the
program runs. Command-line options you enter in Tool Setup affect the tool’s behavior
every time the tool is run from the Tools tab, and in every task that uses that tool.
Therefore, in T ool Setup, you should enter only the minimum command-line options that
are required to run the tool. To produce more specific tool behavior on the task level,
you can enter command-line options in Process Templates Setup, when you create a
task that runs a tool.
Creating Projects, Processes, and Tools
Example:
Package Distribution requires the following option to run:
workbench.exe /tool="Package Distribution"
That is the option specified in Tool Setup. Adding the option /tgt=23 to the command
line runs Package Distribution and selects the option to dist ribute to a network directory.
Because you will not want to distribute to a network every time you run Package
Distribution, the /tgt=23 option is added to a task in Process Templates Setup rather
than to the tool in Tool Setup.
Defining Command Line Options for Tools
¾ Not available in Standard Edition.
See Guidelines for Entering Command Line Options on page 72.
To define a command line for a tool
1. Access the Tool Configuration dialog box in any of the following ways:
In Workbench, select Edit menu > Tool Configuration.
In Tool Setup or Process Templates Setup, right-click and select Tool
Configuration.
In Process Templates Setup, select any tool, make sure Task Type is set to
Workbench Tool, and click Define next to Options. When you access the
dialog box this way, you can only edit options for the currently displayed tool.
The Tool Configuration dialog box appears.
2. From Tool, select the tool to define options for. The list contains both predefined
tools and tools you create.
Wise Package Studio Reference 73
3. Click Add.
A new option appears at the end of Options.
4. 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.
See About Wise Package Studio command-line options on page 268 and
Guidelines for Entering Command Line Options on page 72.
Auto Task Checking
Select a method for automatically completing tasks associated with this tool.
Do not mark task complete when tool finishes
The task check box is not marked automatically.
Always mark task complete when tool finishes
The task check box is marked the first time the tool closes—even if you
cancel it—regardless of whether it ran successfully.
Creating Projects, Processes, and Tools
Mark task complete if tool finishes successfully
The task check box is marked only when the tool is closed normally. If the
tool has a wizard interface, the wizard must be completed through the final
page. Canceling the tool does not mark the task complete.
Note
This option does not work for user-defined tools because it requires a return
code from the application.
Mark task complete if following file changes
The task check box is marked only when the file specified in the File Path
field changes. Example: If you have a task that runs InstallTailor, you might
want it to be marked complete only when the transform file is created.
When you select this option, the File Path field appears. Enter the path to
the file that must be changed or created in order for the task check box to
be marked. Because this tool can be a ssociat ed with tas ks in man y different
projects, you should use Wise Package Studio variables. Example: If this
tool is Microsoft Word, you might enter [ProjectDir]\[FileName].doc to
represent the document that is created in the project directory with the
project file name.
5. To move the new option to a different place in the options list, select the option and
click Move Up or Move Down.
6. Click OK.
The next time a user associates this tool with a task in Process Templates Setup, the
new command-line option will be available.
Wise Package Studio Reference 74
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
in:
z Command-line options for tools associated with an application or other .EXE in
Process Templates Setup and Tool Setup.
See Adding Tasks to a Process on page 62, Adding a New Tool on page 67, and
About Wise Package Studio command-line options on page 268.
z Help text (Rich Text or HTML) in Process Templates Setup and Tool Setup.
See Help for Tasks and Tools on page 70.
z The Project Directory and Vendor Package fields in Project Setup.
The value for most variables is obtained from information in Project Setup. Some
variables are not available in all Wise Package Studio editions and modules.
Available variables
Creating Projects, Processes, and Tools
[ApplicationName] The current project’s Application Name field in
Project Setup
[FileName] The current project’s File Name field in Project
Setup
[Notes] The current project’s Notes field in Project Setup
[PackageName] The current project’s Package Name field in
Project Setup
[PackageStudioDir] The directory in which Wise Package Studio is
installed
[ProductVendor] The current projects’s Product Vendor field in
Project Setup
[ProjectDir] The current project’s Project Directory field in
Project Setup
[ProjectName] The current project’s Project Name field in Project
Setup
[Sharepoint] The current share point directory specif ied on the
Workbench Preferences dialog box > Repository tab
[SoftwareManagerDSN] The Software Manager database that is associated
with the current share point directory
[VendorPackage] The current project’s Vendor Package field in
Project Setup
[WorkbenchDSN] The Workbench database that is associated with the
current share point directory
Wise Package Studio Reference 75
Chapter 4
Repackaging Applications and Managing Projects
This chapter includes the following topics:
z About the Project and Tools tabs on page 76
z Using the Projects Tab on page 76
z Using the Tools Tab on page 78
z Connecting to a Web Application on page 79
z Managing Projects on page 80
z Viewing Project Metrics on page 83
z Creating a To-Do List on page 84
z Workbench Reports on page 85
About the Project and Tools tabs
To repackage or test applications in Wise Package Studio, you use either the Project tab
or the Tools tab. Both tabs let you run the tools that create, modify, and verify
packages.
With Enterprise Management Server, the right pane of the Projects tab contains
additional tabs to help you manage projects. These include the Project Management,
Metrics, and To Do tabs.
See:
Using the Projects Tab on page 76
Using the Tools Tab on page 78
Using the Projects Tab
Use the Projects tab to work on projects that you create in Project Setup. See About
Projects on page 54.
When you create a project, you can associate it with a process. (See About Process
Templates and Tasks on page 58.) If you associate a project with a process, you can
take advantage of the process-oriented approach to repackaging applications in Wise
Package Studio, which provides consistency in your repackaging and ensures that
projects are performed according to corporate standards. If a project is associated with
a process, the Projects tab displays the tasks that make up the process.
If you don’t associate a project with a process, the Projects tab displays the Workbench
tools, which you can use in any order. Because tools on the Project tab are associated
with a project, you have greater control of the name and location of the job’s files than
you do when working with tools on the Tools tab.
Wise Package Studio Reference 76
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.
1. Click the Projects tab or press Alt+P.
2. 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.
The project name appears in Active Project, and its tasks appear in the left pane.
Tasks that do not have check boxes are informational headers used to group
subtasks. If a task is unavailable, it means you do not hav e a license to use the tool
associated with it. With Enterprise Management Server, it might also mean you do
not have permission to use the task’s tool or the task has not been assigned to you.
3. Starting with the first task that has a check box, do the following for each task, in
order:
a. Click the task, then click the Description tab to display the task’s help text. If
the View Tool Help hotlink appears in the upper right of the Description tab,
click it to access the tool’s help text.
b. If a Run link appears to the right of a task, the task is associated with a tool.
Click the Run link to run the tool.
Note
When you click the Run link, if the tool program cannot be found on your
computer, a dialog box appears that lets you browse for the program. Wise
Package Studio records the location you specify so it can find the program the
next time you run that tool.
When you run a tool from the Projects tab, the tool might skip dialog boxes or
populate fields based on command-line options defined in Process Templates
Setup. Example: The task Edit package might run Windows Installer Editor and
open the project’s package file.
c. If a task is not associated with a tool, do what the task describes. Example:
Install Software.
d. As you finish each task, mark the check box to the left of the task to indicate
that the task is complete. Tasks that are associated with tools can be marked
complete automatically, if the tool’s command-line option is set up to do so.
See Defining Command Line Options for Tools on page 73.
4. When the entire project is finished, you can change its status.
In the Professional Edition, change the Status field in Project Setup to Closed.
With Enterprise Management Server, change the Status field on the Project
Management tab to Complete, or set up the last task in the process to change
the status automatically. You set task options in Process Template Setup.
See Adding Tasks to a Process on page 62.
Wise Package Studio Reference 77
Repackaging Applications and Managing Projects
To work on a project without a process
1. Click the Projects tab or press Alt+P.
2. 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.
The project name appears in Active Project, and the tools appear in the left pane.
3. Click a tool name to display the tool’s help text.
4. To run a tool, click the Run link to the right of the tool name.
When you run a tool from the Projects tab, you might not be prompted for file
names or locations, because they usually are defined with the project.
To hide or show a tool window when it runs
z When a tool runs, the Run link changes to a Hide link. To minimize the tool window,
click the Hide link.
z When a tool window is hidden, the link changes to Show. To restore the tool window
to its last size and position, click the Show link.
For information about using specific tools, see:
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
About WiseScript in the WiseScript Package Editor Help
Using the Tools Tab
The Tools tab displays all available tools and lets you use the tools in any order. You
might use the Tools tab to perform a single task or a series of tasks without creating a
project.
With Enterprise Management Server, Security Setup determines whether you have
access to the Tools tab.
To run a tool from the Tools tab
1. Click the Tools tab or press Alt+T.
The tool names and icons appear. Click a tool name to display the tool’s help text.
2. To run a tool, double-click the tool name.
If a tool is not displayed or is unavailable, it means you do not hav e a license to use
it. With Enterprise Management Server, it might also mean you do not have
permission to use it.
For information about using specific tools, see:
Wise Package Studio Reference 78
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
About WiseScript in the WiseScript Package Editor Help
Connecting to a Web Application
A Wise Package Studio task or tool can run a Web application whose URL is defined in
Tool Setup. When Workbench cannot connect to the computer that is hosting the Web
application, the Connection Failed dialog box appears.
z The URL field displays the path to the W eb application. If this field is enabled, and if
the Web application is on multiple servers, y ou can specif y a new UR L. 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
Specifying a new URL might change the URL for other users. See below.
z If you do not specify a new URL, the Connection Failed dialog box might continue to
appear as you use Workbench. To prevent future connection attempts and disable
the dialog box, mark Prevent Connection Attempts to Web Applications.
To activate the dialog box, select Edit menu > Preferences > General tab and mark
the Allow Connection Attempts to Web Applic at ion s check box.
What happens when you specify a new URL?
The Allow Local Override of URL check box in Tool Setup determines what happens
when you specify a new URL.
z If the check box is marked, the new URL is stored in your registry instead of the
Workbench database. Therefore, it does not change the URL for other users.
z If the check box is cleared, the new URL is stored in the Workbench database and
changes the URL for all users.
Why is the URL field unavailable?
z The Allow Local Override of URL check box in Tool Setup is cleared.
And
z You have a license for Enterprise Management Server and you do not have
permission to access Tool Setup.
Because specifying a new URL without a local override changes the URL for all users,
only users with permission to edit tools have this ability.
Wise Package Studio Reference 79
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. You can also generate several Workbench reports that use
this information.
To use the Project Management tab, see:
z Entering Project Tracking Information
z Assigning Users to Tasks in a Project on page 81
z Entering Time for Tasks on page 82
Entering Project Tracking Information
¾ Enterprise Management Server only.
Security Setup determines whether you have access to the Project Management tab.
Repackaging Applications and Managing Projects
Note
To edit a project’s tracking information, you must be the project owner, a user in the
owner group, or a user in the WPS Administrator group. Y ou cannot edit project tracking
information for the predefined projects: Sample Project and Initial Workbench Setup.
You can make a duplicate of these projects and edit them.
See Duplicating or Deleting a Project on page 57.
To enter project tracking information
1. Click the Projects tab or press Alt+P.
2. From Active Project, select a project that is associated with a process.
3. In the right pane, click the Project Management tab.
4. Complete the tab:
Project Owner
This field displays the owner assigned in Project Setup. To change the owner,
click and select an owner from the Select Owner dialog box. The owner can
be a user, a group, or none. If you select a user, a dialog box appears asking
you if you want to assign all the project’s task to that user.
Priority
Select High, Medium, or Low.
Status
Select a status if it does not get updated automatically.
Wise Package Studio Reference 80
You can have a status updated automatically upon the completion of certain
task.
See Adding Tasks to a Process on page 62.
A project can have any of nine statuses; use th e ones that meet your cor porate
standards.
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.
Current Target Date
If you determine that the project will be completed before or after the
estimated completion date, specify the new target date.
Actual Completion Date
This is pre-filled when Status is changed to Complete.
Estimated Hours
Enter the number of hours you estimate the project will take to complete.
Hours Completed
Enter the total number of hours that have been spent on the project. The Enter
actual hours by field in Workbench Preferences determines how the hours are
entered:
If Project is marked, you enter the total number of hours for the project,
updating the entry as work on the project progresses.
If Task is marked, you enter the actual hours for individual tasks and the
total of the task hours is entered here automatically.
See Entering Time for Tasks on page 82.
Remaining Hours
After work on the project begins, use this field to record the number of hours of
work that remain. Example: Suppose you originally estimated the project to
take 40 hours, and you’ve completed 20 hours. H owever, because you know the
remaining tasks will take 30 hours, you enter 30 hours here. This provides a
more realistic number in the % Completed field.
% Completed
If Remaining Hours is blank,
% Completed = Hours Completed / Estimated Hours
If Remaining Hours has a value,
% Completed = Hours Completed / (Hours Completed + Remaining Hours).
Assigning Users to Tasks in a Project
¾ Enterprise Management Server only.
Repackaging jobs are often performed by a team. (Example: The project manager
creates and assigns the project. An integrator might analyze and customize the existing
package. A repackager might perform the integration testing, and a tester might verify
the package and finish the project.) On the Project Management tab, you can assign
users to specific tasks in a project.
All tasks in the predefined projects are assigned to the user Admin. All tasks in a new
project are initially assigned to the user who created the project.
Security Setup determines whether you have access to the Project Management tab.
Wise Package Studio Reference 81
Repackaging Applications and Managing Projects
To assign users to tasks in a project
1. Click the Projects tab or press Alt+P.
2. From Active Project, select a project that is associated with a process.
3. In the right pane, click the Project Management tab.
The tasks for the selected project appear.
4. Select one or more tasks to assign.
5. Click Assign User and select a user from the button menu.
Only the tasks assigned to the current user are enabled. Tasks assigned to other users
are visible but unavailable.
You can filter the projects so that only projects whose next task is assigned to you or
only projects that have any task assigned to you appear in Active Project. Options for
the project filter are set on the General Preferences dialog box.
See Setting General Preferences on page 52.
You can run the Assignments by User report to see how many tasks are assigned to
each user.
See Workbench Reports on page 85.
Entering Time for Tasks
¾ Enterprise Management Server only.
On the Project Management tab, you can enter the time spent on tasks. This provides
data for determining the difference between estimated and actual time spent on project
tasks. Having historical data will help improve the accuracy of estimates for future
repackaging projects. You can view this information in the Project Variance report.
See Workbench Reports on page 85.
Security Setup determines whether you have access to the Project Management tab.
To enter time for a task
1. Click the Projects tab or press Alt+P.
2. From Active Project, select a project that is associated with a process.
3. In the right pane, click the Project Management tab.
The tasks for the selected project appear.
4. Double-click a task.
The Task Details dialog box appears.
5. In Actual Hours, enter the time spent on this task. Up to two decimal places are
allowed.
Don’t use the value from the Measured Hours column that gets recorded
automatically. This represents only the time it takes to run the tool for a task, but a
task might involve activities in addition to running the tool. Example: Suppose you
need to test the package’s launch conditions on different operating systems. The
Metrics tab will record the amount of time the Test Expert tool runs, but it will not
record the time you spend reimaging the test machines.
Wise Package Studio Reference 82
6. 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.
The Metrics tab in the right pane of the Projects tab displays a record of all events that
have occurred for the current project. This includes how much of the project has been
completed, how many tasks remain, the time spent on the project to date, the sequence
in which tasks were performed, who worked on each task, and how long each task took
to complete. Because the Metrics tab records information each time a task is run, you
can investigate false starts and task failures. When a project is completed, you can use
its metrics information to help you estimate future projects.
The Metrics tab is available only for projects that have processes. Security Setup
determines whether you have access to the Metrics tab.
Project-level information
The following information is displayed at the top of the Metrics tab:
Repackaging Applications and Managing Projects
z Actual Start Date
If the first task is associated with a tool, the st art date is recorded when a user fi rst
clicks the Run link for that task. If the first task is manual, the start date is recorded
when the user marks the task’s check box or moves to the next task.
z Actual Completion Date
The date when the last task in the project is marked complete.
z Elapsed Time
The total amount of time (in HH:MM:SS format) the project has been open in the
Active Project list. This will not match the Total Measured Time because it does
not measure the time for manual tasks, or a user might have the project open
without working on a specific task.
z % of Tasks Completed
The number of tasks completed divided by the total number of tasks.
z # of Tasks Remaining
The number of tasks that are not complete.
z Total Measured Time
The total of the measured times for all tasks, in HH:MM:SS format.
Task-level information
The list section of the Metrics tab displays an entry for each task in the project.
Information for a manual task entry is recorded when the task’s check box is marked or
cleared, or when the user moves to the next task. Information for a tool-related task
entry is recorded when the task’s Run link is clicked, or when the task’s check box is
marked or cleared.
Each time a task that is associated with a tool is run, a tool entry appears as a child of
the task entry. To display tool entries, click the plus sign to the left of a task entry. To
Wise Package Studio Reference 83
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. To view or edit notes, click the link in the Notes column.
Interpreting a task’s status
z If a task’s tool is run and finished, or if its check box is marked, the task’s Result is
Completed.
z If a task’s check box is cleared, the Result is blank for the task entry and Failed for
the tool entry.
Creating a To-Do List
¾ Enterprise Management Server only.
The To Do tab in the right pane of the Projects tab displays to-do items for the current
project. Members of the repackaging team create the to-do items and can assign them a
user and due date. When an item’s due date has passed, it is displayed in red.
To-do items differ from tasks in that they are unique to a project. They might represent
actions that don’t warrant being entered as a task, or issues that arise during the
project. (Example: Suppose the first task in your project is Analyze vendor package and
a later task is Test package. The person who performs the analysis task can make notes
about issues discovered during the analysis, and enter to-do items to record specific
things the tester needs to do during the testing task.) In a project that has no process,
you can use the to-do list to provide general guidelines for the users who will be working
on the project.
Repackaging Applications and Managing Projects
Information on the To Do tab is used to generate the To Do List report.
See Workbench Reports on page 85.
Security Setup determines whether you have access to the To Do tab.
To create a to-do list
1. Click the Projects tab or press Alt+P.
2. From Active Project, select a project.
3. Click the To Do tab.
4. On the first line of the list, click Click here to add a new item and type the to-do
item.
5. To assign the item to a user, click the User Name column and select a user.
6. To assign a due date to the item, click the Due Date column and select a date.
7. When you finish entering the to-do information, click outside the to-do item.
The item is added to the end of the to-do list.
To sort the to-do list, click any column heading.
To delete a to-do item, right-click the item and select Delet e.
To mark a to-do item as complete, mark the ch eck box to th e left of the item .
Wise Package Studio Reference 84
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.
Workbench Reports
Report Name Available in What This Report Does
Process
Documentation
Project Overview Enterprise
Project Details Enterprise
Project Variances Enterprise
Assignments by User Enterprise
To Do List Enterprise
Security Setup Enterprise
Professional
Edition
Management
Server
Management
Server
Management
Server
Management
Server
Management
Server
Management
Server
Provides an overview of all Workbench processes by listing the
tasks, tools, and options in each process.
Use this report to document and compare Workbench processes.
Not available from the Management Reports Web Application.
Lists general information about all Workbench projects.
A repackaging team leader can use this report to get an overview of
current projects.
Provides information about specific Workbench projects.
It contains the same information as the Project Overview report but
also lists each project’s tasks, the user assigned to each task, and
each task’s status. A project leader can use this report to check the
status of individual tasks for a project.
Lists project estimated and actual completion dates and times and
their variances.
You can generate this report for all projects or projects with a
particular status. Use this report to help improve the accuracy of
estimates for future projects.
Lists each user’s assigned projects with the number of their
assigned and complete d tasks for each project.
Repackagers can use this report to identify the projects assigned to
them. A repackaging team leader can use this report to assess the
workload balance among the members of the repackaging team.
Lists all items on the To Do list for each project.
Not available from the Management Reports Web Application.
Lists by group the user name and domain names of those with Wise
Package Studio user permissions.
The person responsible for Workbench security can use this report
to get a list of the users assigned to each security group.
Wise Package Studio Reference 85
Generating a Workbench Report
To generate a Workbench report
¾ Not available in Standard Edition.
1. From the Reports menu, select a report.
The report opens in the report viewer window.
2. 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.
Save the report by clicking Save As in the lower right of the report viewer
window. You can save a report in HTML, XML, or CSV format.
Print the report by clicking Print in the lower right of the report viewer window.
Perform a text search by clicking within the report and typing Ctrl+F.
To generate a report through the Management Reports Web
application
Repackaging Applications and Managing Projects
¾ Enterprise Management Server only.
1. In your browser, enter the URL for Management Reports.
The Management Reports URL is http://server name/Wise_Management_Reports,
where server name is the name of the IIS server. Obtain the server name from your
administrator.
2. From Select a report to generate, select a report.
The report opens in the Web report viewer window.
If you have problems using the Management Reports, ensure that you have met the
system requirements for Web applications that are listed in the Wise Package Studio
Getting Started Guide.
Wise Package Studio Reference 86
Chapter 5
Wise Package Studio Tools
This chapter includes the following topics:
z About Wise Package Studio tools on page 87
z List of Wise Package Studio tools on page 87
z How Wise Package Studio tools interact with revision control on page 89
z Application Isolation on page 89
z ApplicationWatch on page 94
z Command Line Builder on page 97
z InstallTailor on page 105
z Legacy Setup Conversion on page 110
z Package Definition on page 123
z Patch Creation on page 128
z UpgradeSync on page 138
z Web Capture Conversion on page 141
z Wise Task Manager on page 141
z Adding Files From the Wise Software Repository on page 144
About Wise Package Studio tools
Run Wise Package Studio tools from the Tools tab or the Projects tab.
z On the Tools tab, the tools are organized to correspond to the phases of the
application management lifecycle. To run a tool, double-click the tool name.
z On the Projects tab, you click the Run link to the right of the tool or, in a project
with a process, to the right of the task associated with the tool.
When you run a tool from the Projects tab, the tool might skip pages or populate fields
based on command-line options defined in Process Templates Setup. Example: The task
Edit package might run Windows Installer Editor and open the project’s package file.
Note
When you specify a .WSI or .WSE file in certain tools, the file is compiled if necessary. If
any files cannot be read, or if other errors are encountered during the compile, a dialog
box listing the errors appears. Open the package in its editor (Windows Installer Editor
or WiseScript Package Editor), fix the errors, and rerun the tool.
List of Wise Package Studio tools
z Application Isolation. (Not available in Standard Edition.)
Wise Package Studio Reference 87
Wise Package Studio Tools
z ApplicationWatch.
z Command Line Builder.
z 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. (Not available in Standard Edition.)
z Impact and Risk Assessment, which lets you quickly assess the potential impact of
deploying a package (usually a hotfix or security patch) without performing
extensive testing. It also lets you determine which isolated files are at risk of being
missed by an update or patch and ensure that they are updated. See Impact and
Risk Assessment in the Software Manager Help. (Not avail able in Standard Edition.)
z InstallTailor.
z Legacy Setup Conversion.
z Linux Package Editor, which lets you use a Windows computer to create packages
that install software on Linux computers. See About Linux Package Editor in the
Linux Package Editor Help.
z Mobile Device Package Editor, which lets you create an .INF file and compile it to
one or more .CAB files that install a mobile device application. See About Mobile
Device Package Editor in the Mobile Device Package Editor Help.
z Package Definition.
z Package Distribution.
z About Package Validation.
z Patch Creation.
z Preflight Analysis. See Viewing Results from Preflight Deployment on page 263.
z Preflight Instrumentation. See Creating a Preflight Package on page 262.
z SOE Snapshot on page 242. (Not available in Standard Edition.)
z SetupCapture.
z SetupCapture Configuration.
z Software Manager, which provides the interface for working with packages in the
Software Manager database. See About Software Manager in the Software Manager
Help. (Not available in Standard Edition.)
z About Test Expert. (Quality Assurance module only.)
z UpgradeSync.
z Virtual Package Editor, which lets you create and edit a virtual software layer, a
virtual software project (.WVP) file, or a virtual software archive (.VSA) file. See
About Virtual Package Editor in the Virtual Package Editor Help. (Not available in
Standard Edition.)
z Web Capture Conversion. (Not available in Standard Edition.)
z Windows Installer Editor, which is a development system for creating and editing
Windows Installer installation packages (.WSI, .MSI). See About Windows Installer
Editor in the Windows Installer Editor Help.
z WiseScript Editor, which is a script authoring environment that lets you create
powerful .EXEs to use as custom actions in a Windows Installer installation. In
Wise Package Studio Reference 88
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.
z WiseScript Package Editor, which is a development system for creating and editing
installation packages based on the Wise scripting language (WiseScript™). See
About WiseScript in the WiseScript Package Editor Help. (Not available in Standard
Edition.)
z Wise Task Manager.
The MSI to WSI Conversion tool and Import Visual Basic, C#, or J# tools are available
from the Tools menu in Windows Installer Editor. See About Windows Installer Editor
tools in the Windows Installer Editor Help.
How Wise Package Studio tools interact with
revision control
When you specify a file that is under revision control in Software Manager, the tool you
are using checks the file’s revision control status. This table shows what the tool does
for each revision control status.
If the file is Wise Package Studio tool does this
Not under revision control Opens the file
Checked in Asks if you want to check out the file
Checked out by you Opens the file
Checked out by another user Displays message saying the file is
You can view a package’s revision control status in the Application/Package Summary
pane in Software Manager.
See Revision Control in the Software Manager Help.
Application Isolation
¾ Not available in Standard Edition.
If you click Yes, the tool checks out the
file and opens it.
checked out by another user and is
unavailable
Application Isolation™ provides a quick and easy way to isolate applications with their
shared .DLL or .OCX files (support files). It isolates the .EXE files in an installation by
placing their dependent, shared .DLLs and .OCXs inside the application directory or,
optionally, in the WinSxS directory.
Application Isolation ensures that an application always uses the version of shared files
with which it was installed. It prevents overwriting of previous versions of shared
Wise Package Studio Reference 89
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.
Warning
Isolation does not work on all applications. Applications must be written according to
Microsoft programming guidelines. (Example: If an application contains hard-coded
paths to support files, isolation might not work.) Because ApplicationWatch records the
support files accessed by an installation, use it to determine if the application follows
Microsoft programming guidelines for accessing files.
See ApplicationWatch on page 94.
If you cannot use Application Isolation, use ConflictManager instead, which resolves
conflicts rather than isolates applications.
Because Application Isolation has the potential to change the location of files within your
installation and to change the feature and component layout of the installation
database, test the package thoroughly after using Application Isolation.
For further reading
See Isolated Components in the Windows Installer SDK Help.
In the MSDN Library (msdn.microsoft.com/library), search for the following terms:
Assembly manifest
Isolated components
Isolated applications
Creating a Package That Isolates .EXEs
¾ Not available in Standard Edition.
Create a package that isolates. EXEs to isolate applications with their shared .DLL or
.OCX files (support files). You can sav e the results of the application isolation as an .MSI
or an .MST.
Make sure your .MSI is complete or nearly complete so all files that need to be isolated
are present in the package.
To create a package that isolates .EXEs
1. Do one of the following:
On the Projects tab, click the Run link to the right of the task or tool associated
with Application Isolation. Isolation will be run on the default project file. This
tool might skip pages or populate fields based on command-line options defined
in Process Templates Setup.
On the Tools tab, double-click Application Isolation.
2. If the Specify Target Installation File page appears, complete it:
Wise Package Studio Reference 90
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.
Base MST file
Specify a transform to apply to the installation.
3. On the Welcome page, mark your isolation method:
Use manifests to isolate application files
Adds .MANIFEST files to your installation. Manifests, a .NET technology, use
metadata to describe in detail the relationships between an .EXE and its .DLL
and .OCX files. You can specify that some support files are accessed from the
application directory and some are not. This method of isolation only works
when the installation is installed on a computer using Windows XP or later.
Use Windows Installer Isolated Components to isolate application files
This method of isolation offers less flexibility than manifests, but runs on more
operating systems. Support files are placed in the application directory along
with a .LOCAL file, which informs the operating system to access the .EXE’s
support files from the application directory.
4. On the Welcome page, mark your isolation type:
Automatically isolate application files
This option automatically isolates all applications with all support files in the
installation. Example: Suppose your installation contains Sample1.EXE,
Sample2.EXE, and Sample3.EXE, and also contains four .DLLs stored in the
System32 directory. All four .DLLs will be copied to the application directory,
and if any of the three .EXEs call any of the .DLLs, the system will direct the
.EXEs to the isolated copies of the .DLLs in the application directory instead of
the ones in the System32 directory.
Manually choose which files to isolate with which applications
If you mark this, an additional page appears that lets you manually choose
which support files to isolate with which .EXE files. Example: If you isolate
Sample1.EXE with a specific version of the file comctrl32.DLL, then a copy of
comctrl32.dll will be isolated in the application directory along with
Sample1.EXE. When Sample1.EXE calls comctrl32.dll, the system will direct it to
the isolated copy.
5. On the Welcome page, click Next.
6. If you chose manifests, the Select OS Compatibility page appears.
a. Mark options for Operating System Support and Side-by-Side Assembly Type.
b. To have a copy of the isolated files installed in their original location, mark that
option.
c. Specify the extracted files directory.
See Specifying OS Compatibility for Isolation on page 93.
7. If you chose Windows Installer isolated components, the Select Isolation Options
page appears.
a. Mark whether files should be moved to enable more comprehensive isolation.
Wise Package Studio Reference 91
Wise Package Studio Tools
b. Mark whether to add support for self-repair of isolated files.
See Selecting Isolation Options on page 94.
8. Click Next in either the Select OS Compatibility or Select Isolation Options page.
9. If you specified the option to manually select which files to isolate, the Select Files
to Isolate page appears.
a. From Select Files to Isolate From, select what kind of installation files should
appear in the right list box.
Typically, you only isolate .DLLs and .OCXs that are in shared locations, such as
the System32 directory. However, to isolate other files, select All files in
shared locations to view any type of file in a shared directory or All files to
view all files in the installation.
b. From Appl ic at ion(s) to be Isolated, select one or more .EXE files.
c. In Files to Isolate for Selected Applications(s), mark the files that should
be isolated with the selected .EXEs.
Note
If, on the Select Isolation Opti ons page, you chose not to mov e files to different
features, then when you select an .EXE, you see only files in the same feature
as the .EXE.
d. Click Next when finished specifying isolation relationships.
10. If you chose to use manifests for isolation and to store files in the WinSxS directory,
the Digital Signature Information page appears. You must digitally sign fi les that are
stored in the WinSxS directory. Enter paths to the digital signing files you obtained
from your digital signature provider such as Verisign and click Next.
11. On the Perform Isolation page, click Next.
Isolation is performed, which might take a few minutes. Then the Isolation Report
page appears, showing you the changes made to the installation to implement
isolation.
12. After reviewing the changes, click Next on the Isolation Report page.
The Isolation Complete page appears.
13. In Updated Windows Installer File, specify whether to save the updated
Windows Installer file as an .MSI or an .MST. You can also change the default name,
which is the original file name with “_Isolated” appended.
If you specified an .MST in Installation Pathname on the Specify Target
Installation File page, you can specify the same .MST in Updated Windows
Installer File to append the results of the application isolation to the .MST. If you
specify an existing .MST in Updated Windows Installer file, but not the same .MST
you specified in Installation Pathname, the result s of the application isolation will
overwrite the existing .MST.
14. Click Finish.
After you isolate an installation, do not add .EXE, .DLL, or .OCX files. The addition of
files might nullify the isolation you performed.
Wise Package Studio Reference 92
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
1. 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
later, an installation using manifests will not run on any other operating system.
This option lets you work around this limitation by configuring the i nstallation so
that it is compatible with any operating system. It creates an installation file
with two copies of your installation. One is run if the operating system is
Windows XP or later with isolation taking place using manifests. The other is run
on all other operating systems with no isolation. This option significantly
increases the size of the installation.
Support Windows XP or later only
This option creates an installation that runs only on Windows XP or later and
uses manifests for isolation.
Wise Package Studio Tools
2. Mark the assembly type:
Create private side-by-side assemblies in application directory
Files and manifests, which together form assemblies, are installed to the
application directory if they are isolated.
Create shared side-by-side assemblies in WinSxS directory
Isolated assemblies are stored in the Wi nSxS directory, a global directory in the
Windows directory for the side-by-side isolation of files. It provides a shared
location, yet manages the isolation of files by comparing the digital signatures
of files to determine differences. Files in the WinSxS directory must be digitally
signed.
3. To also install the isolated files in their original location, such as System32, mark
Place copy of isolated files in their original location for application not
written to support isolation.
This prevents the application from breaking in the event that the application you are
isolating does not support isolation. Example: If it uses hard coded paths to access
support files.
4. From Extracted Files Directory, select a directory for the isolated files.
Isolated files are extracted and saved in this directory. When the installation is
subsequently saved and compiled, these files are pulled from the new direct ory, not
the original directory
.
Wise Package Studio Reference 93
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:
1. From Feature Options, mark one of the following options:
Move files into the same feature as necessary and then isolate
When isolation is performed, files are moved up to parent features as needed
until the .EXE and its support files are located in the same feature. Example:
With automatic isolation, .EXEs and their support files are moved up in the
hierarchy until they all reside in the same feature. With manual isolation, you
can isolate any .EXE in your installation with any support file, and when
isolation is performed, the files are moved as needed.
Isolate only those files that are already in the same feature as the
application .EXE
When isolation is performed, only .EXEs and their support files that reside in the
same feature are isolated with each other. Example: Suppose Sample.EXE and
Sample.DLL are in the same feature and you chose automatic isolation of files.
When isolation is performed, Sample.EXE and Sample.DLL are isolated with
each other. But if they were in different features, they would not be isolated
with each other. If you chose manual isolation, only files in the same feature as
the .EXE appear on the Select Files to Isolate page.
2. From Repair Support for Isolated Files, mark one of the following options:
Wise Package Studio Tools
Do not add repair support for isolated fi les
Isolated files in the installation do not have self-repair.
Install isolated files in their original location
Isolated files are installed in the application directory and in their original
location, such as System32. The installation adds a component that facilitates
repair of the files in the application directory. When the application needs to be
repaired, Windows Installer looks for the files in both the system directory and
the application directory.
Install isolated files in the application directory only
Isolated files are installed in the application directory but not in the system
directory . When the application is started, Windows Installer looks for the file in
the application directory.
If copies of the isolated file are also installed in other directories, then the
installation creates component ID registry entries to refer to the other locations
of the file. When the application needs to be repaired, Windows Installer looks
for the file in the application directory and in any other directories referenced in
the registry.
ApplicationWatch
ApplicationWatch™ monitors your computer as you execute an application or run an
installation and determines which .DLL, .OCX, and .EXE files were accessed. It then adds
Wise Package Studio Reference 94
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. SetupCapture produces a
complete record of the files and system changes made during installation, while
ApplicationWatch records only the .DLL, .OCX, or .EXE files that are accessed during
execution or installation of an application.
Note
ApplicationWatch cannot monitor 16-bit applications.
ApplicationWatch Exclusion List
Some files, such as system .DLL files, that are used during execution of a application are
unrelated to the actual application. Because such files should not be added to the
resulting package, ApplicationWatch™ uses an exclusion list to determine which files to
ignore.
When you create a Windows Installer-based installation (.WSI or .MSI) with
ApplicationWatch, a built-in exclusion list is used that cannot be changed. It contains
operating-system related files that are accessed during the normal course of operating a
computer and that typically have nothing to do with a specific application.
Wise Package Studio Tools
Likewise, when you create a WiseScript installation (.WSE) with ApplicationWatch
(Professional Edition only), a built-in exclusion list is used. Though you cannot access
this built-in list, you can add exclusions to it. To do this, open WiseScript Package Editor
and select Edit menu > Preferences. In Preferences, enter the .DLLs to ignore in the
System .DLLs to Exclude list.
Creating a Package with ApplicationWatch
ApplicationWatch produces a Windows Installer or WiseScript package. (WiseScript is
not available in Standard Edition.)
(Professional Edition only .) When y ou work in a project with no process, the Proj ects tab
displays two ApplicationWatch tools: ApplicationWatch (Windows Installer) that makes
the target file a Windows Installer package and ApplicationWatch (WiseScript) that
makes the target file a WiseScript package.
Note
ApplicationWatch cannot monitor 16-bit applications.
To watch an application
1. Close all other applications so that the files they access are not added to the
installation.
2. Do one of the following:
On the Projects tab, click the Run link to the right of the task or tool associated
with ApplicationWatch. The package that is created will be saved with the
default project name. This tool might skip pages or populate fields based on
command-line options defined in Process Templates Setup.
Wise Package Studio Reference 95
Wise Package Studio Tools
On the Tools tab, double-click ApplicationWatch.
3. 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. The ApplicationWatch results will be
stored in this file.
Add/Update Resources in Existing Installation
If you specified an existing installation in Target Installation, mark this to add
to or update the resources in the existing installation instead of overwriting
them.
4. Complete the Run Application page:
Application Path
Specify the full path of the application executable to run.
Command Options
Enter any command-line options to apply to the executable. Refer to the source
application’s documentation for applicable command-line options.
5. Click Execute, which starts the source application.
6. In the source application, use all possible features except printing. If you are
watching an installation, run the installation through to completion.
Use as many of the application’s features as possible to ensure that files used by
rarely-used features are recorded. Do not use the application to print, because
printing accesses Windows operating system and printer-specific files.
7. Close the application, return to the Run Application page, and click Next.
In the Standard Edition, the Finish page appears. Click Finish and skip the next
steps.
In the Professional Edition, the ApplicationWatch Inclusions page appears. It
displays all files that were used during execution of the watched application.
These files will be added to the new package file that is created, if you do not
choose to remove them.
8. To exclude a file from the package, select it and click Exclude.
9. Click Next on the ApplicationWatch Inclusions page.
10. The ApplicationWatch Exclusions page appears. It displays all the files that are
excluded from the new package. This includes files you excluded on the Inclusions
page and files in the exclusion list.
See ApplicationWatch Exclusion List on page 95.
11. To include a file in the new installation that is currently excluded, select it and click
Include.
12. Click Finish on the ApplicationWatch Exclusions page.
If a file that is part of a merge module is added, the Files in Merge Modules dialog
box appears. It prompts you to add the merge module and, if necessary, download
it.
See Adding Merge Modules Instead of Files on page 232.
Wise Package Studio Reference 96
If a file that is used by a package in the Wise Software R epository is added, the Files
in Repository dialog box appears and prompts you to add a version of the file that is
in the repository.
See Adding Files From the Wise Software Repository on page 144.
13. If you created a .WSI or .MSI, open the new installation in Windows Installer Editor.
If you created a .WSE file, open it in WiseScript Package Editor.
The files that were accessed by the source application are added to the Files page. If
you use this information as a starting point for developing a complete installation,
compile and test the installation thoroughly to verify that it operates correctly.
Warning
Some of the files that are listed on the Files page might be platform-specific or nondistributable Windows system files. If you are not sure whether it is safe to deplo y a file,
check with Microsoft developer documentation before deploying these files to end users.
Command Line Builder
Command Line Builder helps you create command lines for starting or updating
Windows Installer packages without an extensive knowledge of command-line switches.
You select the appropriate options for the package, and the utility creates an error-free
command line for an optimal installation or update.
Wise Package Studio Tools
Command lines let you change the behavior of a package to account for different work
environments and end user requirements. You can specify the following:
UI Options Windows Installer provides package developers the ability to
create user interfaces with multiple levels of functionality.
Using a command line, you can control what level of
functionality the end user sees during the installation.
Logging Options Windows Installer records errors and events in log files. The
diagnostic information Windows Installer writes to these
logs can help you understand the cause of a failed
installation. You can build a command line to specify the
logging options you require for each package.
Advertising Options Windows Installer can advertise the availability of an
application to end users and other applications without
actually installing the application. If an application is
advertised, only the interfaces required for loading and
starting the application are presented to the end user or
other applications. If an end user or an application activates
the advertised interface, Windows Installer loads the
necessary components. This option can save time and disk
space.
Repair Options Windows Installer uses the REINSTALL property to repair
installed components. Command-line options vary from
reinstalling a minimum set of files to reinstalling all files,
including registry entries.
Public Properties Windows Installer changes the value of public properties to
address specific installation requirements.
Wise Package Studio Reference 97
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.
Patches The PATCH property is a list of patches that Windows
Installer applies to a package during installation or to an
installed application. The MSIPATCHREMOVE property is a
list of patches that Windows Installer uninstalls from an
application. Windows Installer 3.0 or later is required to
remove patches or to apply multiple patches.
Creating a Command Line With the Command Line Builder
Use the Command Line Builder to create a command line to start or update a Windows
Installer package.
For a description of the types of command-line options you can build, see Command
Line Builder on page 97.
To create a command line
1. Start the Command Line Builder in either of two ways:
On the Projects tab, click the Run link to the right of the task or tool associated
with Command Line Builder.
On the Tools tab, double-click Command Line Builder.
The Welcome page appears.
2. In the Select File section, select the type of file to run with the command line:
MSI Package (*.msi)
MSI Package wrapped in a Wise .EXE (*.exe)
3. In the File Location section, specify the file to be run with the command line. To
run a patch (.MSP) without an installation, leave this field blank.
4. Click Next.
The Define Command Line page appears.
Note
Although you can enter a command-line in the Command Line field, we
recommend that you use the options provided in this utility for an optimal, errorfree installation.
5. Select an Install Mode. These options, with the exception of Update, are available
only if you specified a file in the File Location section on the Welcome page.
Install
Advertised
Wise Package Studio Reference 98
Installs or configures the installation package. Select this option to remove
patches.
Advertises the installation to the destination computer.
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.
6. Depending on the install mode you select, additional buttons appear on the page.
Following are the buttons that appear and how you can use them to modify the
command line:
UI Options
Make the installation run in silent mode and set the user interface level.
See Adding UI Options to Your Command Line on page 100.
Logging Options
Generate a log when the installation is run and select logging options.
See Adding Logging Options to Your Command Line on page 101.
Advertising Options
Advertise applications and apply a transform to the advertised package.
See Adding Advertising Options to Your Command Line on page 102.
Repair Options
Repair installed files.
See Adding a Repair Option to Your Command Line on page 103.
Edit Properties
Change the value of public properties.
See Editing Public Properties With a Command Line on page 104.
Apply Transforms
Apply transforms to the installation package using the TRANSFORMS property.
See Applying Transforms With a Command Line on page 104.
Add/Remove Patches
Add or remove patches using the PATCH or MSIPATCHREMOVE properties.
See Applying or Removing Patches With a Command Line on page 104.
7. When you finish modifying the command line, click Next on the Define Command
Line page.
The Finish page appears, displaying the command line you built.
8. Do one of the following:
Click Execute to run the command line.
Click Create Shortcut to create a shortcut file (.LNK), specify the file, and click
Click Copy Command Line to copy the command line to the clipboard.
9. Click Finish.
Wise Package Studio Reference 99
Save.
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.
To add UI options to a command line
1. On the Define Command Line page, click UI Options.
See Creating a Command Line With the Command Line Builder on page 98.
The UI Options dialog box appears.
2. To enable the UI Options check boxes, mark Set User Interface level.
3. By default, qn - No UI is marked in the All Windows Installer versions section.
To set user interface level options for all versions of Windows Installer, mark the
appropriate options in this section.
qn - No UI
Displays no user interface during the installation.
qb - Basic UI
Displays built-in modeless dialog boxes that show progress messages during
the installation.
Note
Modal dialog boxes require user input whereas modeless dialog boxes don’t.
qr - Reduced UI
Displays authored modeless dialog boxes and built-in modal error-message
boxes during the installation.
qf - Full UI
Displays both modal and modeless dialog boxes that have been authored into
the internal user interface, and built-in modal error-message boxes during the
installation.
qn+ - No UI
Displays no user interface, except for a modal dialog box at the end of the
installation.
qb+ - Basic UI
Displays built-in modeless dialog boxes that show progress messages during
the installation and a modal dialog box at the end of the installation.
qb- - Basic UI
Displays built-in modeless dialog boxes that show progress messages and no
modal dialog boxes during the installation.
4. If you mark the qb, qb+, or qb- option, then the Hide the Cancel Button check
box is enabled. Check this to add the ! switch to the command line, which removes
the Cancel button from the installation dialog boxes.
5. To set User Interface level options for Windows Installer 3.0 only, mark one of the
following options in the Windows Installer 3.0 only section. This overrides any
options you mark in the All Windows Installer versions section.
Wise Package Studio Reference 100
Loading...