Symantec WISE VIRTUAL PACKAGE EDITOR 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0, WISE VIRTUAL PACKAGE EDITOR 7.0 SP2 Installation Manual
Page 1
Wise Virtual Package Editor Reference
Page 2
Wise Virtual Package Editor
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 7.0 SP2
Legal Notice
Copyright © 2010 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 Virtual Package Editor Reference 2
Page 3
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/or web-based support that provides rapid response and up-to-the-
minute information
z Upgrade assurance that delivers software upgrades
z Global support purchased on a regional business hours or 24 hours a day, 7 days a
week basis
z Premium service offerings that include Account Management Services
For information about Symantec’s support offerings, you can visit our web site at the
following URL:
www.symantec.com/business/support/
All support services will be delivered in accordance with your support agreement and the
then-current enterprise technical support policy.
Contacting Technical Support
Customers with a current maintenance agreement may access Technical Support
information at the following URL:
www.symantec.com/business/support/
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 information
z Problem description:
Error messages and log files
Wise Virtual Package Editor Reference 3
Page 4
Troubleshooting that was performed before contacting Symantec
Recent software configuration changes and network changes
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/business/support/
Customer service
Customer service information is available at the following URL:
www.symantec.com/business/support/
Customer Service is available to assist with non-technical questions, such as 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
Support agreement resources
If you want to contact Symantec regarding an existing support agreement, please
contact the support agreement administration team for your region as follows:
Asia-Pacific and Japan [email protected]
Europe, Middle-East, and Africa [email protected]
North America and Latin America [email protected]
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:
Wise Virtual Package Editor Reference 4
Page 5
Managed Services Managed services remove the burden of managing and
monitoring security devices and events, ensuring rapid response
to real threats.
Consulting
Services
Educational
Services
To access more information about Enterprise services, please visit our Web site at the
following URL:
www.symantec.com/business/services/
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 Virtual Package Editor Reference 5
Page 6
Contents
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Chapter 1: Introducing Wise Virtual Package Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
About Virtual Package Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
About Virtual Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
About Virtual Software Package Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
About Virtual Software Package Archive Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About Application Layers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
About Data Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
About Sublayers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
About User Maintenance of Virtual Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
About the Altiris SVS Applet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Updating the SVS Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Product Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chapter 2: Creating Virtual Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
About Installation Expert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Starting Virtual Package Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Creating a Virtual Package Editor Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Creating an Application Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Opening a Virtual Software Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Compiling a Virtual Software Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Product Details Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Files Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
About Installation Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Adding Files to a Virtual Software Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Adding Contents of Directories to a Virtual Software Package . . . . . . . . . . . . . . . . . . . . . . . . 23
Editing File Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Registry Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Adding Registry Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Importing Registry Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Delete Entries Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Exclusions Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Events Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Releases Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Creating a Virtual Software Package Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Editing an Archive File’s WiseScript Wrapper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Editing the WiseScript Wrapper Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Chapter 3: Capturing Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
About SetupCapture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Guidelines for Capturing an Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Setting Up a Clean Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Capturing an Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Wise Virtual Package Editor Reference 6
Page 7
Chapter 1
Introducing Wise Virtual Package Editor
This chapter includes the following topics:
z About Virtual Package Editor on page 7
z About Virtual Software Packages on page 8
z About Virtual Software Package Formats on page 8
z About Virtual Software Package Archive Types on page 9
z About Application Layers on page 10
z About Data Layers on page 10
z About Sublayers on page 11
z About User Maintenance of Virtual Software Packages on page 11
z About the Altiris SVS Applet on page 12
z Updating the SVS Drivers on page 12
z Product Documentation on page 13
About Virtual Package Editor
Virtual Package Editor is a complete and user-friendly tool for creating and editing a
Virtual Software Package
virtualization is a revolutionary approach to software management that lets y ou package
applications and data into managed units that can be installed as virtual layers. When
you create a VSP for your application, the end user can install it like any other
application without any special license.
To create a VSP, you normally use the various Installation Expert pages in Virtual
Package Editor. However, to virtualize an existing application, you can use the
SetupCapture tool that is available in Virtual Package Editor to capture it as a VSP.
Virtual Package Editor is included with the following products:
z Wise Installation Studio
z Wise Package Studio Professional
To use Virtual Package Editor, you must have the SVS Driver (Software Virtualization
Agent) installed. This driver is downloaded and installed when you install Wise
Installation Studio.
We recommend that before you use Virtual Package Editor, you become familiar with
Software Virtualization Solution.
For more information about Software Virtualization Solution (SVS), search for
Workspace Virtualization on the symantec.com Web site.
(VSP) that you can distribute to end users. Software
See also:
Wise Virtual Package Editor Reference 7
Page 8
About Installation Expert on page 14
About SetupCa pture on page 36
Updating the SVS Drivers on page 12
About Virtual Software Packages
A Virtual Software Package (VSP) contains files and registry keys l ike any other software
package. However, these files and registry keys are installed to a special area on the
hard drive. After the VSP is activated by the SVS Driver (Software Virtualization Agent),
the application becomes visible along with its files, directories, and settings. To the end
user, the virtualized application looks and behaves like any other application.
You create VSPs with Virtual Package Editor. In Windows Installer Editor, you can also
create a WiseScript wrapper that installs an .MSI into an SVS layer. In either case, the
VSP can be installed on a computer along with the SVS Driver runtime (an unlicensed
version of the driver).
See About the Installation of an .MSI into an SVS Layer on page 219.
The following are some of the benefits of creating VSPs:
z End users can easily and instantly repair your application if it is broken.
See About User Maintenance of Virtual Software Packages on page 11.
Introducing Wise Virtual Package Editor
z Your applications will not conflict with any other applications on the end user’s
computer and will not change the base Windows installation.
z End users will be able to install more than one version of your application on their
computer at the same time.
See also:
About Virtual Software Package Formats on page 8
About Virtual Software Package Archive Types on page 9
About Application Layers on page 10
About Data Layers on page 10
About Sublayers on page 11
About Virtual Software Package Formats
A Virtual Software Package (VSP) can be in one of the following formats:
virtual software layer A virtual software layer is the native SVS layer component.
When the output is a virtual software layer, the layer
appears in the Altiris SVS applet as soon as it is created.
Specify this format as your output type when you create a
VSP to use locally on your computer.
Wise Virtual Package Editor Reference 8
Page 9
Introducing Wise Virtual Package Editor
virtual software project
file (.WVP)
virtual runtime archive
file (.VRA)
virtual software archive
file (.VSA)
A .WVP file provides much more functionality than a virtual
software layer and lets you do the following that you
cannot do with a virtual software layer:
z Compile it into a .VRA file that can be distributed to
end users.
z Create a release for the archive file on the Releases
page.
See Releases Page on page 31.
z Add WiseScripts on the Events page to enhance its
functionality.
See Events Page on page 29.
z Maintain source path locations.
z Avoid capturing information that is specific to the
computer where the layer is created (example: userspecific SID data).
Specify this format as your output type when you create a
VSP to distribute to other users.
A .VRA file is generated when you compile a .WVP file or
when you export a virtual software layer from the Altiris
SVS applet. A .VRA file is portable and can be distributed to
end users. Before you distribute a .VRA file, use the
Releases page in Virtual Package Editor to create a release
for the archive file.
See Releases Page on page 31.
In Wise Installation Studio 7.0 SP1 or later, you cannot
create .VSA files with Virtual Package Editor. If you open a
.VSA, you are prompted to convert it to a .VRA file.
See also:
About Virtual Software Package Archive Types on page 9
About Virtual Package Editor on page 7
About the Altiris SVS Applet on page 12
About Virtual Software Package Archive Types
A Virtual Software Package (VSP) archive file is a portable package that lets you
distribute your VSP to others. In Virtual Package Editor, a VSP’s archive t ype is displayed
on the Product Details page.
The following are the VSP archive types:
virtual software archive
file (.VSA)
Wise Virtual Package Editor Reference 9
A .VSA file requires a licensed version of the SVS Driver
(Software Virtualization Agent) on the computer where it is
imported.
You can only create .VSAs in Wise Package Studio 7.0 and
later and Wise Installation Studio 7.0.
Page 10
Introducing Wise Virtual Package Editor
virtual runtime archive
file (.VRA)
In Virtual Package Editor, when you open an archive file that is not supported by that
edition of the editor, you are asked to convert it to a supported archive type. To save
changes to an archive file, you must first convert it to a supported format.
See Opening a Virtual Software Package on page 19.
About Application Layers
Virtual Package Editor lets you create a Virtual Software Package (VSP) that is an
application layer. An application layer contains all the files and registry settings that
make up a virtualized application.
Warning
When you create a VSP, be sure to set exclusions on the Exclusions page in Virtual
Package Editor. Exclusions prevent the loss of user data when a layer is reset.
See Exclusions Page on page 28.
A .VRA file can be imported with either a licensed or
unlicensed version of the SVS Driver.
You can only create .VRAs in Wise Installation Studio 7.0
SP1 or later.
Before you distribute a .VRA file, use the Releases page in
Virtual Package Editor to create a release for the archive
file.
See Releases Page on page 31.
Typically, one layer is created for each application. However, one layer can contain
multiple applications. Each layer is managed as a single entity.
You can create an application layer in the following ways:
z Use the SetupCapture tool to capture an existing application and use Installation
Expert to edit the package.
z Use the Installation Expert pages to create the package by adding files, registry
keys, and application settings.
You cann ot use Virtu al Package Editor to create a data layer or to add a data layer to an
application layer.
See also:
About Virtual Package Editor on page 7
Creating an Application Layer on page 17
About Data Layers on page 10
About Data Layers
A data layer captures data files into a dedicated data layer rather than having them
written to an application layer or the base file system. In Wise Installation Studio 7.0
SP1 and later, you cannot use Virtual Package Editor to create or open data laye rs. If
you open a virtual software archive file (.VSA) that contains a data layer, the data layer
Wise Virtual Package Editor Reference 10
Page 11
is not converted when the .VSA file is converted to a virtual runtime archive file (.VRA).
If you open a virtual software project file (.WVP) file that contains a data layer, the
inclusions in the data layer become exclusions.
See Opening a Virtual Software Package on page 19.
About Sublayers
On the Files, Registry, and Delete Entries pages of Virtual Package Editor, a sublayer
drop-down list appears. Before you select entries on these pages, select the sublay er to
which you want to add the entries. On the Files and Registry pages, you can mo ve items
from one sublayer to the other by right-clicking the file or registry value and selecting
Move to layer.
An SVS layer has the following sublayers:
Read-only The read-only sublayer contains all the files and settings
Writable The writable sublayer contains any files or settings that are
Introducing Wise Virtual Package Editor
that are not reset when the layer is reset. When you use
SetupCapture to capture an application, everything that is
captured is put in the read-only layer. When you create a
Virtual Software Package (VSP) using the Installation
Expert pages, you normally add files, registry keys, and
delete entries to the read-only sublayer. When a damaged
application is reset, any files or settings from the read-only
layer are restored.
added or changed by a user of a layer. When a layer is
reset, any data in the writable layer is deleted. In Virtual
Package Editor, you use this sublayer mainly for modifying
user specific settings, troubleshooting, or testing.
(Example: When testing a layer, you could add a .DLL to
the writable layer and then simply reset the layer to
remove it.)
Warning
When you create a VSP, be sure to set exclusions on the Exclusions page in Virtual
Package Editor. Exclusions prevent the loss of user data when a layer is reset.
See Exclusions Page on page 28.
About User Maintenance of Virtual Software
Packages
An end user can use Add/Remove Programs to remove or repair a Virtual Software
Package (VSP) that you create with Virtual Package Editor. The end user has the
following options when they click the Change/Remove button on Add/R emo ve Progr ams:
Remove Deletes the SVS layer along with the VSP.
Wise Virtual Package Editor Reference 11
Page 12
Repair Resets the SV S layer and returns the application to its
original state. Any customization that the end user made to
the application is lost when the layer is reset.
Note
If you use SetupCapture to capture an application, use the Registry page to delete any
uninstall registry keys. Uninstall registry keys can cause the Change/Remove button to
not appear with the application in the Add/Remove Programs list.
About the Altiris SVS Applet
The Altiris SVS applet is installed when you install Wise Installation Studio. It is avail able
from the Windows Control Panel and lets you import, export, and manage Virtual
Software Packages (VSPs). It is not installed on your end users’ computers when they
install your virtual applications.
When you create a layer and the output is a virtual software layer, the layer appears in
the Altiris SVS applet as soon as it is created. From the Altiris SVS applet, you can
export a layer to an archive file, which is a portable layer.
Introducing Wise Virtual Package Editor
To access help for the Altiris SVS applet, open the applet and press F1.
See also:
About Virtual Software Package Formats on page 8
About Virtual Software Package Archive Types on page 9
Updating the SVS Drivers
If updated versions of the SVS Drivers exist, you can download them from the Help
menu of Virtual Package Editor. This downloads the SVS Driver runtime, which is an
unlicensed version of the driver. It also downloads and installs the full version of the SVS
Driver (Software Virtualization Agent) and some other SVS related files. Wise
Installation Studio uses this full version for its features that use SVS functionality.
The SVS Driver runtime is used whenever you create an installation that installs an
application into an SVS layer and you choose to include the SVS Driver in the
installation. You can include the SVS Driver runtime in installations that you create in
Virtual Package Editor, Windows Installer Editor, and WiseScript Editor. You also have the
option to have the SVS Driver runtime downloaded when the installation runs on the end
user’s computer.
See Creating a Virtual Software Package Release on page 33, About the Installation of
an .MSI into an SVS Layer in the Windows Installer Editor Help, and Runtimes in the
WiseScript Package Editor Help.
To update the SVS Drivers
z In Virtual Package Editor, select Help > Download and install latest SVS...
If updated versions of the SVS Drivers exist, they are downloaded. The full version
of the SVS Driver and related files are then installed on your computer.
Wise Virtual Package Editor Reference 12
Page 13
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.
Reference Manual
All the material in the online help is also available in a .PDF-format reference manual,
which you can access by selecting Help menu > Reference Manual.
Getting Started Guide
Introducing Wise Virtual Package Editor
The Getting Started Guide contains system requirements and installation instructions.
You can access a .PDF version of the Getting Started Guide from the Windows Start
menu.
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.
Wise Virtual Package Editor Reference 13
Page 14
Chapter 2
Creating Virtual Software Packages
This chapter includes the following topics:
z About Installation Expert on page 14
z Starting Virtual Package Editor on page 16
z Creating a Virtual Package Editor Template on page 16
z Creating an Application Layer on page 17
z Opening a Virtual Software Package on page 19
z Compiling a Virtual Software Package on page 20
z Product Details Page on page 20
z Files Page on page 21
z Registry Page on page 25
z Delete Entries Page on page 27
z Exclusions Page on page 28
z Events Page on page 29
z Releases Page on page 31
About Installation Expert
Installation Expert is the Virtual Package Editor user interface. It lets you create and edit
Virtual Software Packages (VSP) and provides an easy-to-use, task oriented interface for
this process. Each page of Installation Expert lets you configure a specific aspect of the
package. The pages are organized into logical groups and listed in the order in which
you usually use them. When you start Virtual Package Editor, it opens to Installation
Expert.
See Starting Virtual Package Editor on page 16.
Wise Virtual Package Editor Reference 14
Page 15
Installation Expert
Creating Virtual Software Packages
Page Groups
Page Area
Compile
Page Groups
Pages are organized into page groups. Click the group name to expand or collapse its
pages. Click a page name to display that page.
Page Area
When you click a page name in a page group, the page area displays the page’s options.
Each page lets you define a specific aspect of the VSP. (Example: On the Files page, you
define what files are included in the package.) Complete only the pages that are
pertinent to your particular package, in any order.
z Use on the toolbar to navigate from page to page, or click the page name in
the list of pages.
z To display help for the current page, press F1.
Compile
Click the Compile button to compile a virtual software project file (.WVP) into a virtual
software archive file (.VRA) or to save a virtual software layer.
See Compiling a Virtual Software Package on page 20.
See also:
Product Details Page on page 20
Files Page on page 21
Wise Virtual Package Editor Reference 15
Page 16
Registry Page on page 25
Delete Entries Page on page 27
Exclusions Page on page 28
Events Page on page 29
Releases Page on page 31
Starting Virtual Package Editor
To use Virtual Package Editor, you must have the SVS Driver (Software Virtualization
Agent) installed. If this driver was not installed when you installed Wise Installation
Studio, you can install it when you start Virtual Package Editor.
To start Virtual Package Editor when the SVS Driver is installed
z From the Start menu, select Programs > Symantec > Wise Installation Studio >
Virtual Package Editor.
To start Virtual Package Editor when the SVS Driver is not installed
1. From the Start menu, select Programs > Symantec > Wise Installation Studio >
Virtual Package Editor.
2. When prompted to download and install the SVS Driver, click Yes.
Creating Virtual Software Packages
The SVS Driver downloads and installs.
3. When prompted to reboot your computer, click Yes.
A restart of your computer is required to complete the installation of the SVS Driv er.
4. After your computer restarts, restart Virtual Package Editor.
See also:
Creating an Application Layer on page 17
Creating a Virtual Package Editor Template
You can create a template that lets you define settings for installations that you create
with Virtual Package Editor. The template is then used by Virtual Package Editor if the
output is a virtual software project file (.WVP). This applies to VSPs that you create
using the pages in Virtual Package Editor and VSPs that you create by capturing an
existing application using SetupCapture.
To create a Virtual Package Editor template
1. In Virtual Package Editor, use the Installation Expert pages to add items to the
template.
Any items that you add to the template will be added to any new VSPs that you
create.
2. Select File > Save As and save the .WVP with the name template.wvp in the Virtual
Package Editor\Templates folder.
Wise Virtual Package Editor Reference 16
Page 17
Creating an Application Layer
Virtual Package Editor lets you create a Virtual Software Package (VSP) that is an
application layer. An application layer contains all the files and registry settings that
make up a virtualized application.
See About Application Layers on page 10.
You cann ot use Virtu al Package Editor to create a data layer or to add a data layer to an
application layer.
You can create a new application la yer usin g th e Installation Expert pages or capture an
existing application as an application layer. If you capture an existing application as an
application layer, you can then use Installation Expert pages to edit it. Whether you
create or capture an application layer, the output type can be either a virtual software
project file (.WVP) or a virtual software layer.
See About Virtual Software Package Formats on page 8.
To create an application layer with .WVP output
1. In Virtual Package Editor, use the Installation Expert pages to add files, registry
keys, and other functionality to the layer.
2. On the Release page, create a release for the application layer.
Creating Virtual Software Packages
3. Compile the installation.
To create an application layer with a virtual software layer output
1. In Virtual Package Editor, select File menu > New.
The New Virtual Package dialog box appears.
2. Complete the New Virtual Package dialog box.
In the Templates/Tools list, select Application.
In the Output type section, select Create virtual layer
Click OK.
3. Use the Installation Expert pages to add files, registry keys, and other functionality
to the layer.
4. On the Release page, create a release for the application layer.
5. Compile the installation.
To capture an application layer with SetupCapture
1. In Virtual Package Editor, select File menu > New.
The New Virtual Package dialog box appears.
2. Complete the New Virtual Package dialog box.
In the Templates/Tools list, select SetupCapture.
SetupCapture is a tool that lets you capture an existing application to create an
application layer.
In the Output type section, specify the type of output to create
Click OK.
The SetupCapture Welcome page appears.
Wise Virtual Package Editor Reference 17
Page 18
Creating Virtual Software Packages
3. Step through the SetupCapture wizard to capture the application.
See Capturing an Installation on page 37.
After you capture the application, the captured application’s package opens in
Virtual Package Editor.
4. Use the Installation Expert pages to edit the application layer.
5. On the Release page, create a release for the application layer.
6. Compile the installation.
See also:
About Installation Expert on page 14
Compiling a Virtual Software Package on page 20
Releases Page on page 31
Wise Virtual Package Editor Reference 18
Page 19
Opening a Virtual Software Package
In Virtual Package Editor, you can open any of the following:
virtual software layer A layer that has been imported into the Altiris SVS applet.
virtual runtime archive
file (.VRA)
virtual software
archive file (.VSA)
virtual software project
file (.WVP)
When you open a .VRA file, it becomes a .WVP file.
When you open a .VSA file, you are prompted to convert it
to a .VRA file. If you don’t convert a .VSA file when you
open it, you can convert it when you compile it. Y ou will not
be able to compile it until you convert it. If you open a .VSA
file that contains a data layer, the data layer is not
converted when the .VSA file is converted.
When you open and compile a .WVP file, a .VSA file is
generated.
You cannot open and edit a .WVP file that is a data layer.
When you open a .WVP file that contains a data layer, the
inclusions in the data layer become exclusions. If the data
layer contains files, those files are lost. When you open a
.WVP file that creates a .VSA file when compiled, you are
prompted to convert it.
Creating Virtual Software Packages
After you open a Virtual Software P ack age (VSP), y ou can use Install ation Expert to edit
it.
See About Installation Expert on page 14.
To open a .VSA, .VRA, or .WVP file
1. In Virtual Package Editor, click File > Open.
2. Specify a .VSA, .VRA, or .WVP file.
If you specify a .VSA or a .VRA file, the Import Virtual Archive dialog box appears.
3. If the Import Virtual Archive dialog box appears, specify a directory for the source
files and click OK.
4. If you specified a .VSA file, click Yes when prompted to convert it to a .VRA file.
5. If you specified a .WVP file, click Yes if you are prompted to convert it to a .VRA file.
To open a virtual software layer
1. In Virtual Package Editor, click File > Open Layer.
The Select Layer dialog box appears.
2. Select the layer and click OK.
3. If the layer was created by importing a .VSA file, click Yes when prompted to
convert the package to a .VRA file format.
See also:
Creating an Application Layer on page 17
Wise Virtual Package Editor Reference 19
Page 20
Creating Virtual Software Packages
Compiling a Virtual Software Package
When you compile a Virtual Software Package (VSP), what happens depends on the type
of output you selected for the VSP as follows:
virtual software layer The layer is saved. If the layer is activated, you are asked
to deactivate it to save the changes.
virtual software project
file (.WVP)
See About Virtual Software Package Formats on page 8.
If the compile fails, a Compile Failed dialog box appears that lists the errors that were
found during compile. This includes any syntax errors in WiseScripts that you ma y ha v e
added on the Events page.
If the output is a virtual software layer, any changes you make to the layer are saved
directly to the layer when you save or compile. If the output is .WVP file, any changes
you make to the project file are compiled into the .VRA when you compile.
See About Virtual Software Package Formats on page 8.
A virtual software archive file (.VRA) is generated. The
.VRA file has the same file name as the .WVP file.
To compile a virtual software package, do one of the following
z Click Compile at the lower right of the main window.
z On the Releases page, select one or more releases and click the Compile button at
the right of the Releases page. This compiles the selected releases.
z On the Releases page, in the Build column, check one or more releases and click the
Compile button at the bottom of the main window. This compiles the marked
releases.
Product Details Page
Use the Product Details page to enter general information about the application and to
specify when to activate the layer.
Select Product Details and complete the page:
z Name
Enter the name to use for this application. This is a required field and it appears in
the Add/Remove Programs list. The maximum length is 50 characters.
z Version
Enter the version number of the application.
z Manufacturer
Enter the manufacturer or publisher of the application.
z Archive Type
This displays the format of the Virtual Software Package (VSP). If you open a
package whose format is not supported and do not convert it, that unsupported
format displays until it is converted.
See About Virtual Software Package Archive Types on page 9.
Wise Virtual Package Editor Reference 20
Page 21
Files Page
Creating Virtual Software Packages
z Layer GUID
This displays the layer’s GUID. Each layer should have a unique GUID. If you
attempt to import a layer on a computer and another layer with the same GUID
already exists, the import will fail.
To change the GUID, click Generate.
If the output is a virtual software layer, this field is disabled.
See also:
About Installation Expert on page 14
About Virtual Software Package Archive Types on page 9
On the Files page, you specify the directories and files to be installed on the destination
computer. You can add files to the read-only or the writeable sublayer.
See About Sublayers on page 11.
Files page
Directories
available to your
computer.
Directories to
be installed on
the destination
computer.
The Windows directory represents the system
directory of the destination computer.
Working with the Files Page
z In the lower-left list box, use the right-click menu to expand or collapse the
directory structure, to hide or show empty directories, and to create, delete, or
rename directories.
Files in the
directory selected
on the left.
Files to be
installed on the
destination
computer.
z Drag directories or files to the page from Windows Explorer.
Wise Virtual Package Editor Reference 21
Page 22
Creating Virtual Software Packages
z Drag directories or files from the upper list boxes to the lower list boxes.
z Move a file to the other sublayer by right-clicking a file in the lower-right pane and
selecting Move to layer.
z Use the following buttons:
Add Contents
Add an entire directory and its contents to the package and filter the directory
using wildcards.
See Adding Contents of Directories to a Virtual Software Package on page 23.
Add File
Add files to the directory that is selected in the lower-left list box.
See Adding Files to a Virtual Software Package on page 23.
New Folder
Create directories to be installed on the destination computer.
Delete Folder
Remove a directory from the Virtual Software Package (VSP). This does not
delete the directory from the destination computer. If you try to delete a
directory that is specified on one of the Layer Settings pages, you will be
prompted to verify that you want to delete the directory.
Delete File
Remove a file from the VSP. This does not delete the file from the destination
computer.
Details
View details on the VSP’s files.
See Editing File Details on page 24
See also:
About Installation Directories on page 22
About Installation Expert on page 14
About Installation Directories
On the Files page, the following predefined directories appear in the lower-left list box:
z Program Files
Represents the Program Files directory on the destination computer.
z Windows
Represents the system directory (regardless of its actual name) on the destination
computer. Some standard directories are already created under Windows (example:
Fonts and Profiles).
You can add new directories on the Files page.
To install files into the user profile on the end user’s computer, add the files to a
directory in Windows\Profiles.
If the directory structure on your computer changes while you are assembling a Virtual
Software Package (VSP), change the source directories in the package.
If you delete a directory that has delete entries or exclusions associated with it, they will
also be removed.
Wise Virtual Package Editor Reference 22
Page 23
See also:
Files Page on page 21
Delete Entries Page on page 27
Exclusions Page on page 28
Adding Files to a Virtual Software Package
You use the Files page in Installation Expert to add files to a Virtual Software Package
(VSP).
To add files to a VSP
1. In Installation Expert, select the Files page.
2. From Sublayer, select a sublayer.
See About Sublayers on page 11.
3. If the directory where the file is to be added is not listed in the lower-left list box:
a. Select the directory under which the new directory should be created.
b. Click New Folder, enter a directory name, and click OK.
The directory you specify will be created on the destination computer if it does not
exist.
Creating Virtual Software Packages
4. In the lower-left list box, select the directory to which the file will be added.
5. In the upper list boxes, navigate to a file and double-click it or drag it to the lowerright list box. You can select multiple files.
If you try to add files to the Destination Computer icon or the Program Files
directory, you are prompted to first create a folder to hold the files.
The file is added to the selected folder and appears in the lower-right list box. If you
double-click the file, a File Details dialog box appears.
See also:
Editing File Details on page 24
Files Page on page 21
Adding Contents of Directories to a Virtual Software Package
You can add the entire contents of a directory to a Virtual Softw are Package (VSP) or use
wildcard filters to add only specified files in the directory.
1. In Installation Expert, select the Files page.
2. From Sublayer, select a sublayer.
See About Sublayers on page 11.
3. In the upper-left list box, select a directory whose contents you want to add.
4. In the lower-left list box, select a directory where you want to add the contents.
5. Click Add Contents.
The Add Contents dialog box appears.
6. Complete the dialog box:
Wise Virtual Package Editor Reference 23
Page 24
Creating Virtual Software Packages
Destination Directory
Enter the name of the directory that will hold the contents of the directory
you’re adding. If you don’t enter a directory name, the contents are added to
the directory that’s selected in the lower list box.
Include Wildcards, Exclude Wildcards
T o include or ex clude files based on specific criteria, enter a semicolon-delimited
list of wildcards. (Example: Enter *.EXE for all EXE files. A ? represents any one
character.) If you leave the wildcard fields blank, all files in the directory are
added.
Include Subdirectories
Mark this to add all the subdirectories within the directory you’re adding. The
wildcard settings apply to the subdirectories also.
7. Click OK.
The contents of the directory in the upper-left list box are added to the directory you
selected in the lower-left list box or to the directory you specified in the
Destination Directory field.
See also:
Files Page on page 21
Editing File Details
When you add a file to a Virtual Software Package (VSP), it inherits the attributes of the
original file. If you edit the attributes of a file in a package, the file reflects your edits
when it is installed on the destination computer.
To edit attributes for a single file
1. On the Files page, double-click a file in the lower-right list box.
2. Complete the dialog box:
The File Details dial o g box appears.
Long Filename
The name of the file as displayed on computers running Windows 95 and later.
Short Filename
The 8.3 file name as displayed in DOS or under older versions of Windows.
Specify the short name your application will look for if it is installed on a shared
network directory that doesn’t support long file names.
Source Pathname
The full path of the file on your computer. If you opened a virtual software layer ,
this field contains SVS variables.
See SVS Variables on page 163.
Read Only
Make the file read-only on the destination computer.
Hidden
System
Wise Virtual Package Editor Reference 24
Make the file hidden on the destination computer.
Designate this file as a system file on the destination computer.
Page 25
3. Click OK.
See also:
Files Page on page 21
Registry Page
Use the Registry page to specify the registry entries to be installed on the destination
computer. You can either add registry entries manually or import a registry file (.REG).
You can add registry entries to the read-only or the writeable sublayer.
If you use SetupCapture to capture an application, use the Registry page to delete any
uninstall registry keys. Uninstall registry keys can cause the Change/Remove button to
not appear with the application in the Add/Remove Programs list.
Registry page
Creating Virtual Software Packages
Registry keys
on your
computer.
Registry keys to
be created on
the destination
computer.
Registry values
in the key
selected on the
left.
Registry values
to be installed
on the
destination
computer.
Working with the Registry Page
z In the lower-left list box, use the right-click menu to expand or collapse the
directory structure, to hide or show empty directories, and to create, delete, or
rename directories.
z Move a registry key to the other sublayer by right-clicking a registry k ey value in the
lower-right pane and selecting Move to layer.
z Drag and drop keys and values on the Registry page, or use the following buttons:
Add Keys
Wise Virtual Package Editor Reference 25
Copy a registry key, including all its subkeys and values, from your computer to
the Virtual Software Package (VSP).
Page 26
Creating Virtual Software Packages
Add Values
Copy values from your computer to the VSP.
Add
Create a new key or import a registry file into the VSP.
Delete Key, Delete Value
Remove a registry key or value from the VSP.
Details
Edit registry key settings.
Note
SVS does not store data in the virtual HKEY_CLASSES_ROOT key. Instead, it stores it in
its real location under either HKEY_CURRENT_USER\Software\Classes or
HKEY_LOCAL_MACHINE\Software\Classes. At run time, Windows reads the SVS data for
active layers from these locations and properly renders HKEY_CLASSES_ROOT.
See also:
About Installation Expert on page 14
Adding Registry Keys
Use the Registry Page to add and edit registry keys and values and rename or delete
keys and values. However, you cannot rename or delete a root folder.
To add a registry key
1. In Installation Expert, select the Registry page.
2. From Sublayer, select a sublayer.
See About Sublayers on page 11.
3. Do one of the following:
In the lower-left list box, select the location for the key. Click Add and select
Double-click the registry key value in the lower-right list box.
The Registry Detai l s dialog box appears.
4. Complete the dialog box:
Root
Key
Key.
The top-level key in which the new key will be added. (Example:
HKEY_CURRENT_USER.) This is enabled only when you access the Registry
Details dialog box from the Add button.
To add a new key, click at the end of the existing text, and add a backslash and
the name of the new key. To create the entire key path, separate key names
with backslashes (\). Any keys in the path that do not already exist on the
destination computer are created. This is enabled only when you access the
Registry Details dialog box from the Add button.
Value Name
Wise Virtual Package Editor Reference 26
Enter the name of a new named value. You can use environment variables.
Page 27
Creating Virtual Software Packages
Data Value
Enter the data for the value. You can use environment variables.
Data Type
Select the type of data contained in the named value.
The associated Windows API data types are in parentheses below.
String
(REG_SZ) Identifies the value as an expandable string. To include a
property, enclose the property name in square brackets.
Unexpanded string
(REG_EXPAND_SZ) Identifies the value as a string that contains unexpanded
references to environment variables that are expanded when the value is
retrieved. Enclose the environment variables in single percent signs. For
example, %PATH%.
If you do not want the variable to be expanded, enclose it in double percent
signs. For example, %%WIN%%. This allows Windows system variables to
be embedded.
Double word
(REG_DWORD) Identifies the value as a 32-bit number in decimal notation.
Binary / Hex
(REG_BINARY) Identifies the value as a binary in hexadecimal notation. Do
not use spaces, commas, or other characters to separate the bytes.
Example: AD30C0A94020A8FC4C0008.
Quad Word
(REG_QWORD) Identifies the value as a 64-bit number.
5. Click OK.
Importing Registry Entries
You can import registry files (.REG) into a Virtual Software Package (VSP). RegEdit 4.0
and 5.0 formats are supported for importing.
To import a registry file
1. In Installation Expert, select the Registry page.
2. From Sublayer, select a sublayer.
See About Sublayers on page 11.
3. Click Add at the lower left of the Registry page and select Import.
4. In the dialog box that appears, specify a .REG file and click Open.
The contents of the selected registry file, along with all corresponding folders, are placed
in the appropriate root folder.
Delete Entries Page
Use the Delete Entries page to create deletion entries for an application. A deletion entry
hides a file that is on the computer when a layer is activated. The hidden file functions
as if it were deleted. When the layer is deactivated or deleted, the file reappears.
Wise Virtual Package Editor Reference 27
Page 28
Creating Virtual Software Packages
You can add multiple deletion entries to a package. You normally add a deletion entry to
the read-only sublayer.
When you add a delete entry, you must specify its type. You can specify the following
types of delete entries:
system You can only specify a system delete entry for system-
specific folders (example: Windows and Program Files). If
you specify a system delete entry for a user-specifi c folder,
an error message appears when you click OK.
user You can specify a user delete entry for any folder. A user
delete entry applies to every user (examp le : If you specify
a user delete entry for a file in My Documents, the file
appears deleted from My Documents for every user).
Warning
Be very careful when adding files to the Delete Entries page. Do not add files unless you
are sure that they are not used by another application.
To add a delete entry to a VSP
1. In Installation Expert, select the Delete Entries page.
2. From Sublayer, select a sublayer.
See About Sublayers on page 11.
3. Click Add.
The Delete Entry Details dialog box appears.
4. Select the directory that contains the file.
To add a new directory, select New Folder from the right-click menu and specify
the directory.
5. From Type, select the delete entry type.
6. In Filename, enter the name of the file.
You must specify a file name because a deletion entry cannot be a directory.
7. Click OK.
The entry appears on the Delete Entries page. You can add multiple delete entries.
See also:
About Installation Expert on page 14
Exclusions Page
Use the Exclusions page to specify directories or file types to exclude from a layer. Files
that meet the criteria specified on the Exclusions page are not saved in the layer, but are
saved in the base file system. Files that are excluded from a layer are not lost when the
layer is reset. Files that are not excluded from a layer are written to the lay er’s writeable
sublayer and are lost when the layer is reset.
Wise Virtual Package Editor Reference 28
Page 29
Creating Virtual Software Packages
An end user can reset a layer from Add/Remove Programs by selecting Repair on the
Maintenance Mode dialog box.
See About User Maintenance of Virtual Software Packages on page 11.
Example: If your application creates data files, you could create an excl usion for each of
your data file types. When an end user creates and saves application data files, the files
are not redirected to the layer. Instead, those files are saved in the base file system.
To exclude user profile directories from a layer on the end user’s computer, sele ct a
directory in Windows\Profiles.
When you use SetupCapture to capture an application’s installation, any file extensions
that have a file association with that application’s fi les will appear on the Exclusions page
automatically.
To add exclusions to a Virtual Software Package (VSP)
1. In Installation Expert, select the Exclusions page.
2. Click Add.
The Exclude Details dialog box appears.
3. To specify file extensions :
Events Page
a. Mark File extension.
b. Enter the file extension.
You can specify only one extension per exclusion. Do not include the period or
wildcard asterisk, as it will be interpreted as part of the file extension (example:
do not use .doc or *.doc).
4. To specify a directory:
a. Mark Directory.
b. Select the directory.
c. To exclude subdirectories, mark Exclude subdirectories. By default,
subdirectories are not excluded.
5. Click OK.
The exclusion is added to the list of exclusions. You can add multiple exclusions. To
delete or edit an entry, select Delete or Details from its right-click menu.
See also:
About Installation Expert on page 14
Use the Events page to configure command lines or WiseScripts to be executed when
layer events are triggered. This lets you add functionality to your Virtual Software
Package (VSP). You cannot add WiseScripts to a virtual software layer.
Examples: Set configuration options that are user-specific, display an end-user license
agreement, or evaluate the destination computer’s operating system and install .DLL
files specific to that operating system.
Wise Virtual Package Editor Reference 29
Page 30
Creating Virtual Software Packages
The events that appear in the Event drop-down list are related to actions you can
perform on layers. The events run either before or after these actions are performed on
the layer. Example: To run an event before the layer is activated, create a Pre Activate
event.
We recommend that you use WiseScripts instead of command lines because they have
much greater functionality. WiseScript is a high-level scripting language that
consolidates dozens or hundreds of lines of code into predefined script actions.
Note
If you add a WiseScript to a virtual software project file (.WVP) and then open its virtual
runtime archive file (.VRA), you will not be able to edit the WiseScript. In the .VRA file,
the event appears as a command line that runs the compiled WiseScript .EXE.
WiseScript includes a set of SVS-specific script actions. However, you normally would
not use the SVS script actions when you add a WiseScript on the Events page. Instead,
you would use the non-SVS script actions because you are working directly in a layer or
in a package that becomes a layer.
See About SVS Script Actions in the WiseScript Package Editor Help.
You can add mul tiple command lines or WiseScripts to a VSP. You can then use the Move
Up and Move Down buttons to change the order in which the command lines or
WiseScripts are executed.
To configure a command line
1. In Installation Expert, select the Events page.
2. From Event, select when the command line should run.
3. Click Add and select Command Line.
The Event Details dialog box appears.
4. Complete the dialog box:
a. In Command Line, enter the command line.
b. To have the action specified in the command line complete before proceeding,
mark Wait.
c. Click OK.
The command line appears on the Events page.
To configure a WiseScript
1. In Installation Expert, select the Events page.
2. From Event, select when the WiseScript should run.
3. Click Add and select WiseScript.
WiseScript Editor appears. A tab for the script appears below the Installation Script
pane. The tab is named after the event you selected on the Events page.
4. In the WiseScript Editor:
In the Description field, enter a unique description of the script. This
T o have the action spec ified in the WiseScript complete before proceeding, mark
Wise Virtual Package Editor Reference 30
description appears on the Events page.
Wait for this script to complete.
Page 31
5. When you finish editing the WiseScript, click OK.
Note
When you compile a .WVP file, the syntax of the WiseScript is validated. If the
WiseScript contains syntax errors, a Compile Failed dialog box appears and lists these
errors.
See also:
About Installation Expert on page 14
Releases Page
Creating Virtual Software Packages
To open an existing WiseScript, click Browse in the lower-left corner and specify
the script.
To create a new WiseScript, add actions from the Actions pane to the
Installation Script pane.
See About Script Editor in the WiseScript Package Editor Help.
The WiseScript appears on the Events page.
Before you distribute a virtual runtime archive file (.VRA) to end users, y ou must create
a release for the archive file. A release consists of a WiseScript .EXE wrapper that
contains the logic that is needed to install your application properly.
You use the Releases page in Virtual Package Editor to create a release for a .VRA file.
You can create any number of releases, but normally you would create a single release
for an archive file.
Before you use the Releases page, you should be familiar with the following:
z WiseScript project file (.WSE)
When you create a release for a .VRA file, a WiseScript project file (.WSE) is
created, which when compiled creates the .EXE wrapper. The .WSE file contains the
logic needed to install the .VRA file. You can edit this .WSE file from the Releases
page.
See Editing an Archive File’s WiseScript Wrapper on page 34.
By default, the .WSE file includes installation error messages and several installation
dialog boxes that appear when the end user runs the .EXE. It also includes the
installation’s maintenance mode dialogs that appear when the end user clicks the
application’s Change/Remove button in Add/Remove Programs.
See About User Maintenance of Virtual Software Packages on page 11.
z SVS Driver runtime
The SVS Driver runtime (an unlicensed version of the driver) or a compatible
version of the SVS Driver must be installed on the end user’s computer before a
.VRA file can be imported into an SVS layer. When you create a release for a .VRA
file, you can add the logic that is needed to install the SVS Driver runtime if a
compatible version of the driver is not found on the end user’s computer. You can
include the SVS Driver runtime with your installation or have it downloaded when
your installation runs.
See Creating a Virtual Software Package Release on page 33
Wise Virtual Package Editor Reference 31
Page 32
Creating Virtual Software Packages
The SVS Driver runtime does not appear in Add/Remove Programs on the end user’s
computer. The end user can do one of the following to remove the SVS Driver
runtime:
Run the following command line: Msiexec.exe /x {7D8DBB7C-1C55-4950-A107-
043C164F379A}.
Double-click the Software_Virtualization_Runtime.msi in the C:\Program
Files\Symantec\Setup Files\Software Virtualization Solution directory and s elect
the Remove option.
Warning
If the end user removes the SVS Driver runtime, any application that is installed
into an SVS layer will become non-functional.
You can download the latest SVS Driver runtime from the Help menu.
See Updating the SVS Drivers on page 12.
z Execution of the .EXE wrapper
When an end user runs the default WiseScript .EXE wrapper, the .EXE wrapper does
the following on their computer:
Determines whether the .VRA file has already been imported into an SVS layer
on the computer. If a .VRA file with the same GUID already exists, a message
informs the end user and the installation ends.
Displays installation dialogs.
Determines whether a compatible version of the SVS Driver (Software
Virtualization Agent) is installed.
If a compatible version of the SVS Driver is not found and if the logic to install
the SVS Driver runtime is not included in the release, the .EXE wrapper displays
an error message and the installation ends.
If a compatible version of the SVS Driver is not found and if the logic to install
the SVS Driver runtime is included in the release, the .EXE wrapper does one of
the following to install the SVS Driver.
If a full version of the SVS Driver is installed, a compatible full version is
downloaded and inst alled.
If you selected the option on the Release Details dialog to download the
driver, the SVS Driver runtime is downloaded and installed.
If you selected the option on the R elease Details dialog to incl ude the driv er,
the SVS Driver runtime is installed.
Prompts the end user to restart the computer if the SVS Driver was installed.
The computer must be restarted to complete the installation of the SVS Driver.
Creates an SVS layer for the .VRA file and imports the .VRA file into the layer.
Activates the virtual software layer.
Displays a Finish dialog.
The virtualized application then looks and behaves like any other application to the
end user.
z Install SVS Package WiseScript action
If you use the Install SVS Package action in WiseSc ript P ackage Editor and mark the
option to bind the WiseScript to a .WVP release, then that WiseScript appears as a
Wise Virtual Package Editor Reference 32
Page 33
release on the Releases page for that .WVP file. You can view the details of a bound
release on the Releases page, but you cannot edit them.
See Install SVS Package in the WiseScript Package Editor Help.
See also:
About Installation Expert on page 14
Creating a Virtual Software Package Release
Before you distribute a virtual runtime archive file (.VRA) to end users, y ou must create
a release for the archive file. The release consists of a WiseScript .EXE wrapper that
contains the logic needed to properly install the Virtual Software Package (VSP). This
WiseScript also installs the logic that lets the end user repair or remove the VSP from
Add/Remove Programs. You can also edit the WiseScript to add additional functionality.
See About User Maintenance of Virtual Software Packages on page 11.
See Editing an Archive File’s WiseScript Wrapper on page 34.
To create a new release
1. In Installation Expert, select the Releases page.
Creating Virtual Software Packages
2. Click Add.
If you have not yet saved the project as a .WVP file, you are prompted to save it.
You must save the project before you can add a release.
The Release Details dialog box appears.
3. Edit the default settings of the Release Details dialog box as needed.
Release Name
The default name of the release is the name of the .WVP file with Setup
appended. If the name contains spaces, then a space appears before Setup.
This name identifies this script on the Releases page. If you change the default
name of a new release, the name of the installation script file (.WSE) is also
changed accordingly. If you change the name of a previously created release,
the name of the installation script file does not change.
Installation Script File
The default location of the installation script file (.WSE) is the same directory as
the .WVP file. We recommend th at you do not c hange the default location of the
.WSE file. If you keep the .WVP file and its .WSE file in the same directory, you
can then move the installation files without losing any functionality. If you do
move the .WSE file, use the browse button to specify it.
By default the .WSE file has the same name as the name of the release. When
the .WSE file is compiled, the resulting WiseScript .EXE also has this name.
Install SVS Driver
This option installs the SVS Driver runtime (an unlicen sed version of the driv er )
on the end user’s computer if a compatible version of the driver is not found. An
SVS Driver is required on the end user’s computer in order to import and
activate the .VRA file.
Wise Virtual Package Editor Reference 33
Page 34
Note
If a full version of the SVS Driver (Software Virtualizati on Agent) is found on the
end user’s computer and it is not compatible, the latest full version of the driv er
is downloaded during installation regardless of the SVS Driver options that are
selected.
Include Driver
Mark this to include the SVS Driver runtime as part of the installation. This
option significantly increases the size of the installation.
Download Driver
Mark this to download the SVS Driver runtime when the installation runs.
This option significantly reduces the size of the installation. When this option
is selected, the end user sees a progress bar when the runtime is
downloaded. However, if the end user does not have an active Internet
connection and a compatible version of the SVS Driver is not already
installed on their computer, the installation fails.
4. Click OK.
The release appears on the Releases page.
5. To compile releases, do one of the following:
Creating Virtual Software Packages
Select one or more releases and click the Compile button at the right of the
Releases page. This compiles the selected releases.
In the Build column, check one or more releases and click the Compile button at
the bottom of the main window. This compiles the marked releases.
Also see:
Releases Page on page 31
Editing an Archive File’s WiseScript Wrapper on page 34
Editing an Archive File’s WiseScript Wrapper
When you create a release on the Releases page, a WiseScript wrapper is created for
your virtual runtime archive file (.VRA). This WiseScript wrapper contains the logic
needed to properly install your application. By default, the WiseScript wrapper also
includes several installation dialog boxes that appear when the end user runs the
compiled .EXE. It also includes maintenance mode dialog boxes that the end user can
access from Add/Remove Programs.
You can edit the WiseScript wrapper in WiseScript Package Editor and add any
functionality that is available in WiseScript Package Editor. This includes editing the
default dialog boxes or adding other dialog boxes.
You can also edit the template that creates the wrapper. Edit the template to apply
changes to every WiseScript wrapper.
See Editing the WiseScript Wrapper Template on page 35.
To edit an archive file’s WiseScript wrapper
1. In Installation Expert, select the Releases page.
2. Select the release.
3. Click Edit Script.
Wise Virtual Package Editor Reference 34
Page 35
The script opens in WiseScript Package Editor.
4. Edit the WiseScript.
5. Compile the WiseScript.
See About WiseScript in the WiseScript Package Editor Help.
Also see:
Releases Page on page 31
Creating a Virtual Software Package Release on page 33
Editing the WiseScript Wrapper Template
When you create a release on the Releases page, a WiseScript wrapper is created for
your virtual runtime archive file (.VRA). You can edit the template that creates the
wrapper. Edit the template to apply changes to every WiseScript wrapper.
See Creating a Virtual Software Package Release on page 33.
You can also edit each archive file’s WiseScript wrapper.
See Editing an Archive File’s WiseScript Wrapper on page 34.
Creating Virtual Software Packages
The name of the template file is VsaWrapper.wse
To edit the WiseScript Wrapper Template
1. Access the template’s directory.
2. Open the template in WiseScript Package Editor.
3. Edit the WiseScript.
4. Compile the WiseScript.
See About WiseScript in the WiseScript Package Editor Help. Also see:
Releases Page on page 31
Creating a Virtual Software Package Release on page 33
Wise Virtual Package Editor Reference 35
Page 36
Chapter 3
Capturing Applications
This chapter includes the following topics:
z About SetupCa pture on page 36
z Guidelines for Capturing an Installation on page 36
z Setting Up a Clean Machine on page 37
z Capturing an Installation on page 37
About SetupCapture
Use SetupCapture to capture an existing application as a Virtual Software Package
(VSP). SetupCapture can record all the changes performed by an installation and save
that information to a VSP. You can save the output as a virtual softw are layer or a virtual
software project file (.WVP).
After you capture a package, you can use Virtual Package Editor to edit it.
See also:
About Virtual Software Package Formats on page 8
Capturing an Installation on page 37
Guidelines for Capturing an Installation
Before using SetupCapture for the first time, read the following guidelines.
z You must have the SVS Driver (Software Virtualization Agent) installed and you
must restart your computer after installing the driver.
z Run SetupCapture on a clean machine.
See Setting Up a Clean Machine on page 37.
z Before you run SetupCapture, close all other applications, including background
services or applications (example: Norton AntiVirus).
z During a capture, SetupCapture tries to convert computer- and user-specific data in
the registry to generic data that will work on any computer. It does this by searching
for standard paths (example: C:\Winnt) and replacing them with Windows Installer
properties (example: [WindowsFolder]).
Part of this process includes searching for the computer name and currently loggedon user name. To make the search for computer and user names as accurate as
possible, make sure the computer name and user name on the capture com puter
are set to unique names four or more characters in length. Avoid having the user
name or computer name set to any common file or folder names. An example of a
unique user name is: repackage-1-user.
Wise Virtual Package Editor Reference 36
Page 37
To create a portable Virtual Software Package (VSP), we recommend that you save
the output as virtual software project (.WVP) file. This removes security identifiers
(SIDs) that are created under HKEY_USERS.
z During a capture, changes to an .INI file are recorded as a file change.
To make an .INI file dynamic, use the WiseScript Edit INI File Settings script action
on the Events page.
z When the layer is activated, the Windows API ExpandEventVariable converts a
registry key\value from an environment variable to the actual Windows value.
z After you capture an application, if any uninstall registry keys appear on the
Registry page in Virtual Package Editor, delete them. Uninstall registry keys can
cause the Change/Remove button to not appear for the application in the Add/
Remove Programs list. Without the Change/Remove button, the end user cannot
repair or uninstall the application.
See About User Maintenance of Virtual Software Packages on page 11.
Setting Up a Clean Machine
A clean machine is a computer containing only the operating system and its service
packs. Run all SetupCaptures on a clean machine. This makes repackaged installations
more resilient by making them less dependent on the existence of other applications. To
replicate the clean machine quickly and easily, use a drive imaging tool.
Capturing Applications
How to Set Up a Clean Machine
1. Perform a clean installation of an operating system on the computer you use for
capturing applications.
2. Install any service packs.
3. Install Windows Installer if it is not included with the operating system.
Capturing an Installation
¾ Requires SVS Driver on the SetupCapture comp uter.
SetupCapture records all the changes performed by an installation and can save that
information to a Virtual Software Package (VSP). You can save the output as a virtual
software layer or a virtual software project file (.WVP).
Before you capture an installation, close all other applications so that changes they
make are not captured. After you capture an installation, you can use Virtual Package
Editor to edit it.
To capture an installation
1. In Virtual Package Editor, select File menu > New.
The New Virtual Package dialog box appears.
2. Complete the New Virtual Package dialog box:
In the Templates/Tools list, click SetupCapture.
In Output Type, specify whether to create a virtual software layer or a .WVP
Wise Virtual Package Editor Reference 37
file.
Page 38
Capturing Applications
See About Virtual Software Package Formats on page 8.
Click OK.
The Welcome page of SetupCapture appears.
3. On The Welcome page, select the capture method.
Single Program Capture
This captures only the installations that you execute from the Execute
Installations page. You can execute one or multiple installations. Any other
activity on the computer is ignored. This is the preferred method for creating
VSPs.
Global Capture
This captures all changes that are made to the computer during the capture
process. Use this method to capture default application settings or application
updates after an installation is complete.
4. Click Next.
The Execute Installation page appears.
5. On the Execute Installation page, do the following:
a. In .EXE Name, specify the full path of the installation executable. To capture an
.MSI, click Browse and specify the .MSI.
If you specify an .MSI, it appears in Command Line with the appropriate
Windows Installer command-line options and msiexec.exe appears in .EXE
Name.
b. To run the installation with command-line options, enter them in Command
Line.
c. Click Execute.
The installation starts. Run the installation, installing the product as you want it
to be captured, and return to SetupCapture when the installation is finished.
d. (Optional.) If you selected Global Capture on the Welcome page, open the
application and set any preferences that you want set by default. Example: You
can set a default home page or custom security settings.
e. To run additional installations, repeat the preceding steps for each installation.
All installations that you run are added to the repackaged installation.
f. Click Next.
The End Installation Capture page appears.
6. Click Next.
The Finish page appears.
7. Complete the Finish page.
The summary information for the captured application appears on the Product
Details page in Virtual Package Editor. The value you enter for Name is also the
name of the VSP as it appears in the Altiris SVS applet. If the output of the captured
installation is a virtual project file (.WVP), you must also specify a directory for the
project’s source files.
8. Click Finish.
Wise Virtual Package Editor Reference 38
Page 39
Capturing Applications
The package is captured as a VSP and opens in Virtual Package Editor. What
happens to the package varies as follows:
If the output is a virtual software project file (.WVP), it is not saved until you
save it.
If the output is a virtual software layer, it is also imported into Altiris SVS applet
and activated.
See also:
About the Altiris SVS Applet on page 12
Wise Virtual Package Editor Reference 39
Page 40
Index
A
Altiris Software Virtualization Agent 7
See SVS Driver
Altiris SVS applet
about 12
application
executing from SetupCapture 38
name 20
application layer
about 10
capturing 17
creating 10, 17
removing 11
repairing 11
application template 17
archive type 20
about 9
converting 10
C
capturing an application
See SetupCapture
Change/Remove button
missing 37
clean machine
for SetupCapture 37
command line
in SetupCapture 38
on layer event 29
compile 20
D
data layers
about 10
Delete Entries page 27
deletion entry
creating 27
read-only sublayer 28
directory
adding 22
adding contents 23
excluding from layer 28
predefined 22
using wildcard to filter 23
documentation, Wise 13
drive imaging software 37
E
Event drop-down list 30
Events page 29
exclusion, layer 28
Exclusions page 28
execute installation from
SetupCapture 38
F
file
adding to package 23
attributes, changing 24
details 24
excluding from layer 28
hidden 24
multiple files, adding 23
name, changing 24
read-only 24
system file, designating 24
using wildcard to add 23
file name
long 24
short 24
Files page
about 21
adding directory 23
adding file 23
filter directories with wildcards 23
G
Getting Started Guide 13
global capture 38
H
help
about 13
Installation Expert 15
using 13
hidden file 24
I
imaging software 37
installation
capturing 37
capturing, see SetupCapture
executing for SetupCapture 38
installation directory
adding 22
predefined 22
Installation Expert
about 14
help 15
page groups 15
page navigation 15
L
layer
excluding directories, files 28
sublayer 11
layer GUID 21
M
manual, reference 13
manufacturer name 20
N
new features
Refer to Release Notes
new folder 22
O
operating system
clean 37
service pack 37
P
page
See Installation Expert
page groups, about 15
Product Details page 20
product version
See version, product
R
readme
See release notes
read-only file 24
read-only sublayer
about 11
deletion entry 28
read-write sublayer
See writeable sublayer
reference manual 13
REG file
importing 27
registry
data type 27
importing 27
key, creating 26
value, adding 26
Registry page 25
release
adding 33
creating 33
release notes 13
release script
editing 34, 35
Releases page
Wise Virtual Package Editor Reference 40
Page 41
about 31
S
service pack, on clean machine 37
SetupCapture
about 36
clean machine 37
executing installation 38
global capture 38
guidelines 36
running 37
single program capture 38
starting 37
summary information 38
single program capture 38
software virtualization 7
start Virtual Package Editor 16, 16
sublayer
about 11
Also see read-only sublayer
Also see writeable sublayer
drop-down list 11
SVS Agent
See SVS Driver
SVS Driver 7, 7
installing runtime 31
uninstalling runtime 31
updating 12
using runtime 12
system directory 22
system file, designating file as 24
system requirements, Wise product
Refer to Getting Started Guide
T
template
creating 16
virtual software project file 9
VRA file 9, 9
generating 9
opening 19
VSA file 9, 9
opening 19
VSP
about 8
adding files 23
compiling 20
creating release 33
formats 8
GUID 21
maintenance 11
opening 19
removing 11
repairing 11
saving 39
W
wildcard
adding files with 23
filtering directories 23
WiseScript Editor 30
WiseScript wrapper
about 31
adding 33
creating 33
editing 34, 35
WiseScript, on layer event 29
writeable sublayer
about 11
WVP file 9
about 9
opening 19
saving 39
V
version, product 20
Virtual Package Editor
about 7
starting 16, 16, 16
template, creating 16
virtual runtime archive file 9
virtual software archive
opening 19
virtual software archive file 9
virtual software layer
about 8
compiling 20
opening 19
virtual software packages
See VSP
virtual software project
about 9
compiling 20
opening 19
Wise Virtual Package Editor Reference 41
Loading...