1. Manuals
  2. Brands
  3. Symantec Manuals
  4. Software
  5. WISE VIRTUAL PACKAGE EDITOR 8.0 - REFERENCE FOR WISE PACKAGE STUDIO...
  6. Reference

Symantec WISE VIRTUAL PACKAGE EDITOR 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Wise Virtual Package Editor Reference

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the WISE VIRTUAL PACKAGE EDITOR 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

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

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

  • Page 1 Wise Virtual Package Editor Reference...
  • Page 2 Copyright © 2009 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, and Altiris are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

  • Page 3: Technical Support

    The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates.
  • Page 4 Licensing and registration If your Symantec product requires registration or a license key, access our technical support Web page at the following URL: www.symantec.com/techsupp/ Customer service Customer service information is available at the following URL: www.symantec.com/techsupp/ Customer Service is available to assist with the following types of issues:...
  • Page 5 Consulting Symantec Consulting Services provide on-site technical Services expertise from Symantec and its trusted partners. Symantec Consulting Services offer a variety of prepackaged and customizable options that include assessment, design, implementation, monitoring, and management capabilities. Each is focused on establishing and maintaining the integrity and availability of your IT resources.

  • Page 6: Table Of Contents

    Contents Technical Support ............3 Chapter 1: Introducing Wise Virtual Package Editor .
  • Page 7 Index..............43 Wise Virtual Package Editor Reference...

  • Page 8: Chapter 1: Introducing Wise Virtual Package Editor

    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: About Installation Expert on page 15...

  • Page 9: About Virtual Software Packages

    Introducing Wise Virtual Package Editor About SetupCapture on page 38 Updating the SVS Driver on page 13 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.

  • Page 10: About Virtual Software Package Archive Types

    Introducing Wise Virtual Package Editor virtual software project A .WVP file provides much more functionality than a virtual file (.WVP) software layer and lets you do the following that you cannot do with a virtual software layer: Compile it into a .VSA file that can be distributed and imported on a client computer that has the SVS Driver.

  • Page 11: About Application Layers

    Introducing Wise Virtual Package Editor virtual runtime archive A .VRA file can be imported with either a licensed or file (.VRA) unlicensed version of the SVS Driver. You can only create .VRAs in Wise Installation Studio 7.0 SP1 or later. 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.

  • Page 12: About Sublayers

    Introducing Wise Virtual Package Editor When you use a data layer, the data is stored separately and is not deleted because a data layer cannot be reset. Provide a single, portable data store Data layers can provide a single source of user data files that can easily be exported to a virtual software archive file (.VSA) and moved or copied to a different computer.

  • Page 13: About User Maintenance Of Virtual Software Packages

    Introducing Wise Virtual Package Editor writeable sublayer. If Firefox becomes damaged and is reset, the application is returned to its original state (read-only sublayer) and the data in the writeable sublayer is lost. About User Maintenance of Virtual Software Packages If you use the Releases page to create a WiseScript-based installation for a Virtual Software Package (VSP), an end user can use Add/Remove Programs to remove or repair the VSP.

  • Page 14: Product Documentation

    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...

  • Page 15: Chapter 2: Creating Virtual Software Packages

    Chapter 2 Creating Virtual Software Packages This chapter includes the following topics: About Installation Expert on page 15 Starting Virtual Package Editor on page 17 Creating a Virtual Package Editor Template on page 17 Creating an Application Layer on page 18 Creating a Data Layer on page 19 Opening a Virtual Software Package...
  • Page 16 Creating Virtual Software Packages Installation Expert Page Area Page Groups 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.

  • Page 17: Starting Virtual Package Editor

    Creating Virtual Software Packages Registry Page on page 26 Delete Entries Page on page 28 Exclusions Page on page 29 Inclusions Page on page 31 Events Page on page 31 Data Layers Page on page 33 Starting Virtual Package Editor To use Virtual Package Editor, you must have the SVS Driver (Software Virtualization Agent) installed.

  • Page 18: Creating An Application Layer

    Creating Virtual Software Packages To create a Virtual Package Editor template 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.

  • Page 19: Creating A Data Layer

    Creating Virtual Software Packages 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. Step through the SetupCapture wizard to capture the application. Capturing an Installation on page 40.

  • Page 20: Opening A Virtual Software Package

    Creating Virtual Software Packages 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 When you open a .VRA file, you are prompted to convert it file (.VRA) to a .VSA file.

  • Page 21: Product Details Page

    Creating Virtual Software Packages 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.

  • Page 22: Files Page

    Creating Virtual Software Packages About Installation Expert on page 15 About Virtual Software Package Archive Types on page 10 Files Page 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. About Sublayers on page 12.

  • Page 23: About Installation Directories

    Creating Virtual Software Packages Add File Add files to the directory that is selected in the lower-left list box. Adding Files to a Virtual Software Package on page 24. New Folder Create directories to be installed on the destination computer. Delete Folder Remove a directory from the Virtual Software Package (VSP).

  • Page 24: Adding Files To A Virtual Software Package

    Creating Virtual Software Packages 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 In Installation Expert, select the Files page. From Sublayer, select a sublayer.

  • Page 25: Editing File Details

    Creating Virtual Software Packages Include Wildcards, Exclude Wildcards To include or exclude 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.

  • Page 26: Registry Page

    Creating Virtual Software Packages Files Page on page 22 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.

  • Page 27: Adding Registry Keys

    Creating Virtual Software Packages 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.

  • Page 28: Importing Registry Entries

    Creating Virtual Software Packages 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.

  • Page 29: Exclusions Page

    Creating Virtual Software Packages 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-specific folder, an error message appears when you click OK.
  • Page 30 Creating Virtual Software Packages layer is reset. Files that are not excluded from a layer are written to the layer’s writeable sublayer and are lost when the layer is reset. An end user can reset a layer from Add/Remove Programs by selecting Repair on the Maintenance Mode dialog box.

  • Page 31: Inclusions Page

    Creating Virtual Software Packages Inclusions Page Use the Inclusions page to specify directories or file types to include in a data layer. This page appears only when you have a data layer open. It does not appear for application layers. Files that meet the criteria specified on the Inclusions page are redirected to this layer.
  • Page 32 Creating Virtual Software Packages 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. The events that appear in the Event drop-down list are related to actions you can perform on layers.

  • Page 33: Data Layers Page

    Creating Virtual Software Packages In the Description field, enter a unique description of the script. This description appears on the Events page. To have the action specified in the WiseScript complete before proceeding, mark Wait for this script to complete. To open an existing WiseScript, click Browse in the lower-left corner and specify the script.

  • Page 34: Releases Page

    Creating Virtual Software Packages The Data Layer Details dialog box appears. Specify the .VSA file of the data layer. Click OK. The file path for the data layer appears on the Data Layers page. You can add multiple data layers to an application layer. Use the Move Up and Move Down buttons to change the order in which the data layers are installed.

  • Page 35: Creating A Virtual Software Package Release

    Creating Virtual Software Packages The virtualized application then looks and behaves like any other application to the end user. Install SVS Package WiseScript action If you use the Install SVS Package action in WiseScript Package Editor and mark the option to bind the WiseScript to a .WVP release, then that WiseScript appears as a release on the Releases page for that .WVP file.

  • Page 36: Editing An Archive File's Wisescript Wrapper

    Creating Virtual Software Packages Note Install SVS Driver options appear if you open a Virtual Software Package that was created with Wise Installation Studio that included these options. Click OK. The release appears on the Releases page. To compile releases, do one of the following: Select one or more releases and click the Compile button at the right of the Releases page.

  • Page 37: Editing The Wisescript Wrapper Template

    Creating Virtual Software Packages Editing the WiseScript Wrapper Template When you create a release on the Releases page, a WiseScript wrapper is created for your virtual software archive file (.VSA). You can edit the template that creates the wrapper. Edit the template to apply changes to every WiseScript wrapper. Creating a Virtual Software Package Release on page 35.

  • Page 38: Chapter 3: Capturing Applications

    Chapter 3 Capturing Applications This chapter includes the following topics: About SetupCapture on page 38 Guidelines for Capturing an Installation on page 38 Setting Up a Clean Machine on page 39 Starting SetupCapture on page 39 Capturing an Installation on page 40 About SetupCapture You can use SetupCapture to capture an existing application as a Virtual Software Package (VSP).

  • Page 39: Setting Up A Clean Machine

    Capturing Applications Part of this process includes searching for the computer name and currently logged- on 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 computer are set to unique names four or more characters in length.

  • Page 40: Capturing An Installation

    Capturing Applications In the Templates/Tools list, click SetupCapture. In Output Type, select whether to create a virtual software layer or a .WVP file. About Virtual Software Package Formats on page 9. Click OK. To start SetupCapture in Workbench In Wise Package Studio, do one of the following: On the Tools tab, double-click SetupCapture.
  • Page 41 Capturing Applications 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.
  • Page 42 Capturing Applications 10. On the SetupCapture Exclusions page: To display another type of item, select the type from Exclusion Type. Excluded item types are files and registry keys. To add an item back into the VSP, select it in the list and click Include. You might want to add an item if it is part of the installation that was captured.
  • Page 43 Index executing for SetupCapture 41 installation directory Altiris SVS applet Event drop-down list 32 adding 23 about 13 Events page 31 predefined 23 application exclusion, layer 29, 30 Installation Expert executing from SetupCapture 41 exclusion, SetupCapture 41 about 15 name 21 Exclusions page 29, 30 help 16 application layer...
  • Page 44 registry virtual software archive data type 27 opening 20 importing 28 virtual software archive file 10 key, creating 27 virtual software layer value, adding 27 about 9 Registry page 26 compiling 20 release opening 20 adding 35 virtual software packages creating 35 See VSP release notes 14...

This manual is also suitable for:

Wise virtual package editor 8.0

Table of Contents