Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Related Manuals for Symantec WISE VIRTUAL PACKAGE EDITOR 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0
Summary of Contents for Symantec WISE VIRTUAL PACKAGE EDITOR 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0
- Page 1 Wise Virtual Package Editor Reference...
- Page 2 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.
-
Page 3: Technical Support
Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis 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. - 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/...
- 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: 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: Wise Virtual Package Editor Reference... -
Page 8: About Virtual Software Packages
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. -
Page 9: 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 .VRA file that can be distributed to end users. -
Page 10: 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. Before you distribute a .VRA file, use the Releases page in Virtual Package Editor to create a release for the archive file. -
Page 11: About Sublayers
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. Opening a Virtual Software Package on page 19. -
Page 12: About The Altiris Svs Applet
Introducing Wise Virtual Package Editor 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. Note If you use SetupCapture to capture an application, use the Registry page to delete any uninstall registry keys. -
Page 13: 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 14: Chapter 2: Creating Virtual Software Packages
Chapter 2 Creating Virtual Software Packages This chapter includes the following topics: About Installation Expert on page 14 Starting Virtual Package Editor on page 16 Creating a Virtual Package Editor Template on page 16 Creating an Application Layer on page 17 Opening a Virtual Software Package on page 19 Compiling a Virtual Software Package... - Page 15 Creating Virtual Software Packages Installation Expert 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.
-
Page 16: Starting Virtual Package Editor
Studio, you can install it when you start Virtual Package Editor. To start Virtual Package Editor when the SVS Driver is installed 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 From the Start menu, select Programs >... -
Page 17: Creating An Application Layer
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. About Application Layers on page 10. - Page 18 Creating Virtual Software Packages Step through the SetupCapture wizard to capture the application. Capturing an Installation on page 37. After you capture the application, the captured application’s package opens in Virtual Package Editor. Use the Installation Expert pages to edit the application layer. On the Release page, create a release for the application layer.
-
Page 19: 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, it becomes a .WVP file. file (.VRA) virtual software When you open a .VSA file, you are prompted to convert it... -
Page 20: Compiling A Virtual Software Package
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. -
Page 21: Files Page
Creating Virtual Software Packages 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. -
Page 22: About Installation Directories
Creating Virtual Software Packages Drag directories or files from the upper list boxes to the lower list boxes. Move a file to the other sublayer by right-clicking a file in the lower-right pane and selecting Move to layer. Use the following buttons: Add Contents Add an entire directory and its contents to the package and filter the directory using wildcards. -
Page 23: Adding Files To A Virtual Software Package
Creating Virtual Software Packages 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). -
Page 24: Editing File Details
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 To include or exclude files based on specific criteria, enter a semicolon-delimited list of wildcards. -
Page 25: Registry Page
Creating Virtual Software Packages 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. -
Page 26: Adding Registry Keys
Creating Virtual Software Packages Add Values Copy values from your computer to the VSP. 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. -
Page 27: Importing Registry Entries
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. -
Page 28: Exclusions Page
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). -
Page 29: Events Page
Creating Virtual Software Packages An end user can reset a layer from Add/Remove Programs by selecting Repair on the Maintenance Mode dialog box. About User Maintenance of Virtual Software Packages on page 11. Example: If your application creates data files, you could create an exclusion for each of your data file types. - 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.
-
Page 31: 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. When you finish editing the WiseScript, click OK. - Page 32 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 select 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.
-
Page 33: Creating A Virtual Software Package Release
Creating Virtual Software Packages 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... -
Page 34: Editing An Archive File's Wisescript Wrapper
Creating Virtual Software Packages Note If a full version of the SVS Driver (Software Virtualization Agent) is found on the end user’s computer and it is not compatible, the latest full version of the driver is downloaded during installation regardless of the SVS Driver options that are selected. -
Page 35: Editing The Wisescript Wrapper Template
Creating Virtual Software Packages The script opens in WiseScript Package Editor. Edit the WiseScript. 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). -
Page 36: Chapter 3: Capturing Applications
Chapter 3 Capturing Applications This chapter includes the following topics: About SetupCapture on page 36 Guidelines for Capturing an Installation on page 36 Setting Up a Clean Machine on page 37 Capturing an Installation on page 37 About SetupCapture Use SetupCapture to capture an existing application as a Virtual Software Package (VSP). -
Page 37: Setting Up A Clean Machine
Capturing Applications 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. 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. - Page 38 Capturing Applications About Virtual Software Package Formats on page 8. Click OK. The Welcome page of SetupCapture appears. On The Welcome page, select the capture method. Single Program Capture This captures only the installations that you execute from the Execute Installations page.
- 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.
-
Page 40: Index
Index Exclusions page 28 excluding directories, files 28 sublayer 11 execute installation from Altiris Software Virtualization Agent 7 SetupCapture 38 layer GUID 21 See SVS Driver Altiris SVS applet about 12 file manual, reference 13 application adding to package 23 manufacturer name 20 executing from SetupCapture 38 attributes, changing 24... - Page 41 about 31 virtual software project file 9 VRA file 9, 9 generating 9 opening 19 service pack, on clean machine 37 VSA file 9, 9 SetupCapture opening 19 about 36 clean machine 37 executing installation 38 about 8 global capture 38 adding files 23 guidelines 36 compiling 20...