Wise Virtual Package Editor Reference
Wise Virtual Package Editor Reference 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 their 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 EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC 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 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 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:
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:
Asia-Pacific and Japan [email protected]
Europe, Middle-East, and Africa [email protected]
North America and Latin America [email protected]
Wise Virtual Package Editor Reference 5
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.
Managed Services Managed services remove the burden of managing and
monitoring security devices and events, ensuring rapid response
to real threats.
Consulting
Services
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
Educational Services provide a full array of technical training,
security education, security certification, and awareness
communication programs.
Wise Virtual Package Editor Reference 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 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
(VSP) that you can distribute to end users. Software
virtualization is a revolutionary approach to software management that lets you 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.
See also:
Wise Virtual Package Editor Reference 8
Introducing Wise Virtual Package Editor
About Installation Expert on page 14
About SetupCapture on page 36
Updating the SVS Drivers on page 12
About Virtual Software Packages
A Virtual Software Package (VSP) contains files and registry keys like 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.
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 9
Introducing Wise Virtual Package Editor
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 type is displayed
on the Product Details page.
The following are the VSP archive types:
virtual software project
file (.WVP)
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: user-
specific SID data).
Specify this format as your output type when you create a
VSP to distribute to other users.
virtual runtime archive
file (.VRA)
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.
virtual software archive
file (.VSA)
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.
virtual software archive
file (.VSA)
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.
Wise Virtual Package Editor Reference 10
Introducing Wise Virtual Package Editor
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.
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 cannot use Virtual 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 layers. If
you open a virtual software archive file (.VSA) that contains a data layer, the data layer
virtual runtime archive
file (.VRA)
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.
Wise Virtual Package Editor Reference 11
Introducing Wise Virtual Package Editor
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 sublayer to
which you want to add the entries. On the Files and Registry pages, you can move 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:
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/Remove Programs:
Read-only The read-only sublayer contains all the files and settings
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.
Writable The writable sublayer contains any files or settings that are
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.)
Remove Deletes the SVS layer along with the VSP.
Wise Virtual Package Editor Reference 12
Introducing Wise Virtual Package Editor
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 available
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.
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.
Repair Resets the SVS 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.
Wise Virtual Package Editor Reference 13
Introducing Wise Virtual Package Editor
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
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. To access the release notes, select Release
Notes from the Symantec program group on the Windows Start menu.
Wise Virtual Package Editor Reference 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 15
Creating Virtual Software Packages
Installation Expert
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
Page Area
Page Groups
Compile
Wise Virtual Package Editor Reference 16
Creating Virtual Software Packages
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.
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 Driver.
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 17
Creating Virtual Software Packages
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 cannot use Virtual Package Editor to create a data layer or to add a data layer to an
application layer.
You can create a new application layer using the 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.
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 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 19
Creating Virtual Software Packages
Opening a Virtual Software Package
In Virtual Package Editor, you can open any of the following:
After you open a Virtual Software Package (VSP), you can use Installation 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
virtual software layer A layer that has been imported into the Altiris SVS applet.
virtual runtime archive
file (.VRA)
When you open a .VRA file, it becomes a .WVP file.
virtual software
archive file (.VSA)
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. You 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.
virtual software project
file (.WVP)
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.
Wise Virtual Package Editor Reference 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:
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 may have
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.
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.
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)
A virtual software archive file (.VRA) is generated. The
.VRA file has the same file name as the .WVP file.
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
/
