Sei sulla pagina 1di 99

Symantec Workspace Virtualization 6.1 SP6 User's Guide

Symantec Workspace Virtualization 6.1 SP6 User's Guide

Symantec Workspace Virtualization 6.1 SP6 User's Guide

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: 6.1 SP6

Legal Notice

Copyright © 2010 Symantec Corporation. All rights reserved.

Symantec and the Symantec Logo 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.

This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party ( Third Party Programs ). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Legal Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Symantec product for more information on the Third Party Programs.

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

Printed in the United States of America.

10 9 8 7 6 5 4 3 2 1

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 support offerings include the following:

A range of support options that give you the flexibility to select the right amount of service for any size organization

Telephone and/or Web-based support that provides rapid response and up-to-the-minute information

Upgrade assurance that delivers software upgrades

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:

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 support agreement may access Technical Support information at the following URL:

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:

Product release level

Hardware information

Available memory, disk space, and NIC information

Operating system

Version and patch level

Network topology

Router, gateway, and IP address information

Problem description:

Error messages and log files

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:

Customer service

Customer service information is available at the following URL:

Customer Service is available to assist with non-technical questions, such as the following types of issues:

Questions regarding product licensing or serialization

Product registration updates, such as address or name changes

General product information (features, language availability, local dealers)

Latest information about product updates and upgrades

Information about upgrade assurance and support contracts

Information about the Symantec Buying Programs

Advice about Symantec's technical support options

Nontechnical presales questions

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

Europe, Middle-East, and Africa

North America and Latin America

Contents

Technical Support

4

Chapter 1

Introducing Symantec Workspace

About Workspace Virtualization

Virtualization

11

11

Solving Problems with Workspace Virtualization

12

Provisioning and deprovisioning applications is disruptive to the user and time consuming

12

Recovering a damaged application is time consuming

12

Conflicting applications are difficult or impossible to manage

12

Migrating to new application versions requires significant testing and planning; takes a long time to execute and rollback is difficult

13

How Workspace Virtualization works

13

About file and registry redirection

13

About Virtual Software Layers

15

About Extensible Package Format (XPF) files

16

Virtual Software Layer architecture

16

Chapter 2

Planning for the use of Virtual Software

About working with virtual software packages

Packages

17

17

Virtual software package workflow

18

What you can virtualize using the Workspace Virtualization Agent

19

How to prevent the loss of application data

19

Where you can use Virtual Software Packages

21

How the Workspace Virtualization Agent affects security

21

Rights to modify a virtual software package

22

Rights to user-specific data

22

Rights to start programs

23

About handling duplicate services

23

About multiple concurrent user support

23

8 Contents

Chapter 3

Installing the Symantec Workspace Virtualization Agent

25

Supported platforms for the Workspace Virtualization Agent

25

Installing the Workspace Virtualization Agent

26

Installing the Workspace Virtualization Agent silently

27

What the Workspace Virtualization Agent installs

28

Upgrading the Workspace Virtualization Agent

30

Uninstalling the Workspace Virtualization Agent

30

Troubleshooting Workspace Virtualization Agent installations

30

Cleaning up a failed Workspace Virtualization Agent installation

31

Removing the WMI Provider

31

Uninstalling the Agent in Runtime Mode

32

Chapter 4

Creating virtual software layers

33

About the creation of virtual software layers

33

Types of virtual software layers

34

Methods for capturing virtual software layers

34

Creating an application layer using single program capture

35

Creating an application layer using global capture

37

Adding an application to an existing layer

38

Creating a data layer

40

Creating an empty layer

41

Chapter 5

Editing virtual software layers

43

Configuring a virtual software layer to start automatically

44

Activating a virtual software layer using a desktop shortcut

44

Editing the files in a virtual software layer

45

Editing the registry settings of a virtual software layer

46

Editing a data layer

46

Adding exclude entries to virtual software layers

47

Adding a layer exclude entry

48

Adding a global exclude entry

49

Adding a global user profile exclude entry

50

Ignoring the global exclude list for a single layer

50

Transferring global excludes to another computer

50

Adding a delete entry to a virtual software layer

51

About updating a virtual software layer

52

Updating a virtual software layer

53

Creating a layer patch to update a virtual software layer

54

Renaming a virtual software layer

55

Contents 9

Chapter 6

Managing virtual software layers

57

About the management of virtual software layers

57

Actions you can perform to manage layers

58

Exporting a virtual software layer to an archive file

59

Importing a virtual software archive file

60

Activating and deactivating virtual software layers

61

Resetting application layers

61

Deleting virtual software layers

62

Testing a virtual software layer

63

Interoperability with antivirus scanners

64

Hiding the FSLRDR redirection areas

65

Viewing the properties of a virtual software layer

65

Viewing variables used in a virtual software layer

66

Chapter 7

Layer operations

67

Hide a layer from other layers or from the operating system

67

Add a layer dependency

68

Deactivate on last process exit

69

Clone a layer

69

Keep all data in layer

69

Capture changes made by non-virtualized applications

70

Chapter 8

Technical reference

71

About system variables

71

SVSCMD command-line parameters

72

SVSCMD parameter flags

77

SVSCMD command-line examples

79

Virtual software layer attributes

82

How layer prioritization works

84

How to set the HKCR priority of a layer

86

Windows Management Interface

86

VirtualSoftwarePackage class

86

VirtualSofwareSublayer class

89

Using WMI

90

Workspace Virtualization functions

91

WMI sample scripts

93

OnEvent actions

94

10 Contents

Chapter

1

Introducing Symantec Workspace Virtualization

This chapter includes the following topics:

About Workspace Virtualization

Solving Problems with Workspace Virtualization

How Workspace Virtualization works

About file and registry redirection

About Virtual Software Layers

About Extensible Package Format (XPF) files

Virtual Software Layer architecture

About Workspace Virtualization

Symantec Workspace Virtualization (SWV) is a revolutionary approach to software management. By placing applications and data into managed units called Virtual Software Layers, Workspace Virtualization lets you instantly activate, deactivate or reset applications and to completely avoid conflicts between applications without altering the base Windows installation.

Rather than isolating applications to gain control, Symantec's application virtualization technologies seamlessly integrate virtualized applications to preserve the user experience. Virtualized applications act like normal applications, ensuring normal behavior and full functionality.

In addition to preserving the user experience, Workspace Virtualization lets you:

Instantly repair damaged applications by resetting them to a known state.

12

Introducing Symantec Workspace Virtualization Solving Problems with Workspace Virtualization

Run two version of the same program side by side.

Add and remove software with zero impact on the underlying operating system.

Turn applications on and off instantly.

The end result is a more managable desktop. Application conflicts are eliminated along with the problems associated with failed and corrupted software installations.

Workspace Virtualization is based on Symantec's patented core technology known as the SWV File System Filter driver.

Solving Problems with Workspace Virtualization

Workspace Virtualization solves the following common application management problems:

Provisioning and deprovisioning applications is disruptive to the user and time consuming

With Software Virtualization Solution, you can easily deploy virtualized applications without running an application install or uninstall on client computers. Application availability is instantaneous you can easily and immediately activate or deactivate your applications by sending a single command to the client computer. The user is not required to have system rights to run an installation, and you don t have to worry about restarting when you activate or deactivate an application. The solution can also register any services that the application installed with the Windows Service Control Manager, which then loads the service so that the application is fully functional.

Recovering a damaged application is time consuming

Rather than repairing or recovering a damaged application, you can simply reset it to the original deployed condition. Application resets can be performed instantly or on a schedule. An application can be reset whether the client computer is connected to the network or not. Resetting a virtual application does not damage other applications installed on the computer.

Conflicting applications are difficult or impossible to manage

Workspace Virtualization ensures applications use the correct files and registry settings without modifying the operating system and interfering with other applications. This provides numerous benefits, including improved reliability and

Introducing Symantec Workspace Virtualization 13 How Workspace Virtualization works

flexibility. Example: When installing new software or application updates, administrators might inadvertently replace newer .DLLs with older .DLLs, which can cause immediate problems between applications sharing those .DLLs, causing application failure or reintroducing security holes that previously were patched. With Workspace Virtualization, you can stop worrying about DLL hell.Other benefits include allowing different versions of the same application to co-exist on the same computer.

Migrating to new application versions requires significant testing and planning; takes a long time to execute and rollback is difficult

Rolling out new versions of an application requires significant time to test for conflicts and reprovisiong lab testing computers. Workspace Virtualization simplifies predeployment testing, accelerates the deployment cycle, and reduces post-deployment support costs. With Workspace Virtualization, you can host multiple versions of an application on the same system without conflicts between older and newer files. Even phased rollouts are greatly accelerated because rollback can occur immediately at any time. Once the transition from an older application to a newer application is complete, simply deactivate and remove the older version.

How Workspace Virtualization works

An application or set of data is virtualized by using a capture process that creates a Virtual Software Package (VSP). A VSP contains all the files and registry settings of the application or data. A VSP can be used on a client computer that has the Workspace Virtualization Agent. The VSP is installed to a special area on the hard drive. After the VSP is activated through the Workspace Virtualization Agent, the application becomes visible along with its files, folders, and settings. Even though it is a virtual application, it looks and behaves like any other application to the end user.

About file and registry redirection

Each Virtual Software Package (VSP) is managed by SWV as a distinct entity. When activated, VSPs are like layers over the base Windows operating system so the system appears to contain the aggregate contents of the base operating system plus the active VSPs.

When a VSP is imported onto a computer, the contents of the VSP (both files and registry settings) are placed in a folder in a special protected SWV area on the hard dive, referred to as the SWV redirection area.

14

Introducing Symantec Workspace Virtualization About file and registry redirection

When a VSP is imported on a client computer, the contents of the VSP are placed in the redirected folder, such as C:\fslrdr\1. When the VSP is activated on a client computer, the contents of the VSP are made available to the user. The files and settings appear to the user in the location they would be in if the application had been installed on the computer.

Example: You have a VSP for Mozilla Firefox. When the Firefox VSP is activated, all the contents of the VSP are layered over the base file system and registry to make it visible to the user. The user then sees its appropriate folders, files, registry settings, and shortcuts. When the contents are made visible, they are not displayed in the hidden area, but they are displayed in the locations that the user would see them had Firefox been installed on the computer. Example: Even though the Firefox application file may physically be located at

C:\fslrdr\1\PROGRAMFILES\Mozilla Firefox\firefox.exe

To the user, it is visible as

C:\Program Files\Mozilla Firefox\firefox.exe

Workspace Virtualization accomplishes this by using a filter that intercepts requests to the file system and registry, and when needed, redirects requests to the active VSPs. Workspace Virtualization uses the SWV File System Filter Driver to aggregate the real and virtual file systems into a single view for the end-user.

This process is displayed in the following figure:

the real and virtual file systems into a single view for the end-user. This process is

Introducing Symantec Workspace Virtualization 15 About Virtual Software Layers

The file system display in the lower left represents the baseenvironment Windows operating system files, data and applications installed conventionally.

The file system display in the lower right represents virtualized data that is stored in the isolated, hidden redirection area.

The file system display at the top represents what the system, applications and users see.

The SWV filter driver presents an aggregate view of the real file system and the layered virtual file system and registry. Gold represents data from the real file system. Blue represents data from a layer in the virtual file system. When an application or Windows requests a file, the request goes through the filter driver, which determines whether the request should be passed through to the real file system or redirected to a layer in the virtual file system.

If the file is in the real file system the request proceeds normally. If the filter driver determined that the file is in a layer in the virtual file system, the request is redirected to the layer files. In both cases, however, the application peforms a normal file open request and has no idea that the filter driver is even there or what it is doing.

With redirection, SWV can maintain discrete settings and file versions for different applications on a single system. By working with VSPs, a required version of a file will never be overwritten. This is particularly important when you are working with Dynamic Link Libraries (DLL). Incompatible .DLL files are known to cause application instability. By using applications within VSP, you can ensure that applications use its own set of .DLL files without interfering with the rest of the operating system or other applications running at the same time.

This extends not only to files that relate to applications, but also to registry settings and data files.

About Virtual Software Layers

When an application or set of data is captured into a Virtual Software Package, everything that is captured is contained in a layer. The layer represents all the files and registry settings that make up the virtualized application or data.

Typically, one layer is created for one application. However, one layer can contain multiple applications. Each layer is managed as a single entity.

The files and settings captured in a layer are stored in the SWV redirection area on the computers hard drive. However, when a layer is active, all files and settings appear in the system just as they would if the application or data was installed on the computer. This is accomplished through redirection using the SWV File System Filter Driver.

16

Introducing Symantec Workspace Virtualization About Extensible Package Format (XPF) files

About Extensible Package Format (XPF) files

If you want to make a layer portable so that it can be used on another computer, the contents of the layer are exported to a single XPF file.

XPF files can then be copied or deployed to other computers. To make the contents of the XPF usable on a computer, the XPF must be imported using the Workspace Virtualization Agent. When an XPF is imported on a computer, the layer (the files and registry settings in the XPF) are installed to the SWV redirection area on the client computers hard drive.

Symantec provides a dedicated application, called Wise Virtual Composer, to create XPF packages. See the Wise Virtual Composer User's Guide for additional details on XPF files and application packaging.

Virtual Software Layer architecture

There are two components or sublayers in a layer:

Read-only sublayer

Contains all captured files and settings. The XPF packages that contain applications provide the read-only sublayer.

Writeable sublayer

Contains any files or settings that are added or changed by a user of a layer.

For example, you create a layer for Firefox. As a person uses Firefox, they may make some changes to the program. They may select a unique home page, add bookmarks, or change the original security settings. They may also install a browser plug-in. Those user changes are stored in the Writeable sublayer. The original files and settings are maintained in the Read-only sublayer.

Having these distinct sublayers is useful in being able to reset a layer. When a layer is reset, any data added by a user is deleted, and the layer is returned to its original configuration. Example: If a user s Firefox application ever becomes damaged, you can simply reset the layer to restore it to the way it was first deployed. The application does not have to be uninstalled/reinstalled.

Resetting layers also maintains specific versions and configurations of applications across your network. You can control how the applications are installed and configured on client computers.

Chapter

2

Planning for the use of Virtual Software Packages

This chapter includes the following topics:

About working with virtual software packages

Virtual software package workflow

What you can virtualize using the Workspace Virtualization Agent

How to prevent the loss of application data

Where you can use Virtual Software Packages

How the Workspace Virtualization Agent affects security

About handling duplicate services

About multiple concurrent user support

About working with virtual software packages

The Symantec Workspace Virtualization Agent provides different interfaces for working with Virtual Software Packages (VSPs). The following table explains the differences between the interfaces:

Table 2-1

Workspace Virtualization interfaces

Interface

Description

SWV Admin tool

This tool lets you create, edit, and manage virtual software packages.

18

Planning for the use of Virtual Software Packages Virtual software package workflow

Table 2-1

Workspace Virtualization interfaces (continued)

Interface

Description

SVSCMD executable file

The SVSCMD executable file is installed with the Workspace Virtualization Agent. You can run it with its command-line parameters to work with VSPs.

See SVSCMD command-line parameters on page 72.

When you install the Workspace Virtualization Agent, you have the option to install the SWV Admin tool. You can also install it later by modifying the installation.

See Installing the Workspace Virtualization Agent on page 26.

See What you can virtualize using the Workspace Virtualization Agent on page 19.

See How to prevent the loss of application data on page 19.

See Where you can use Virtual Software Packages on page 21.

See Virtual software package workflow on page 18.

See How the Workspace Virtualization Agent affects securityon page 21.

See About handling duplicate services on page 23.

Virtual software package workflow

The following steps illustrate a typical workflow:

Capture an application into a virtual software layer. See About the creation of virtual software layers on page 33.

Export the layer to virtual software archive file. See Exporting a virtual software layer to an archive file on page 59.

Deploy the archive file to a client computer.

Import the archive file into a layer on the client computer.

Import the archive file into a layer on another computer. See Importing a virtual software archive file on page 60.

Activate the layer to access the application. See Activating and deactivating virtual software layers on page 61.

You can use the SWV Admin tool or the SVSCMD executable file to capture, export, import, and activate layers.

Planning for the use of Virtual Software Packages 19 What you can virtualize using the Workspace Virtualization Agent

See SVSCMD command-line parameters on page 72.

See SVSCMD command-line parameters on page 72.

After you capture a layer and before you export it, you can also edit it. You can use the SWV Admin tool to edit a layer.

See Editing the files in a virtual software layer on page 45.

What you can virtualize using the Workspace Virtualization Agent

Use the following guidelines to determine what you can and should not virtualize:

What you can virtualize

What you should not virtualize

Most applications can be virtualized. Typical applications include office suites, databases, Internet browsers, media, and spyware utilities. Applications function normally when virtualized by the Workspace Virtualization Agent. You can also create virtualized data layers.

Windows operating system components

Windows operating system patches

Most drivers

Applications that have dedicated drivers (example: Client firewalls)

All management agents including antivirus software, security scanners, encryption agents, or any Symantec Management Platform Agent

Data files that you plan to encrypt

Utilities that are designed to run only in safe mode (Workspace Virtualization does not run in safe mode)

See About working with virtual software packages on page 17.

How to prevent the loss of application data

When an application layer creates or modifies files they are stored in the writeable sublayer. If the layer is then reset, the files in the writeable sublayer are deleted. This behavior lets you reset an application to the default state if settings become corrupted. However, many applications create data files that you do not want to lose when a layer is reset. These files need to be stored on the base file system and not in the layer to prevent potential loss.

20

Planning for the use of Virtual Software Packages How to prevent the loss of application data

For example, you create and activate a Microsoft Word layer. You do not create any layer exclude entries, global exclude entries, or data layers to redirect .doc files from the layers writeable sublayer. You then activate the Microsoft Word layer and use it to create .doc files that you save on the computer s hard drive. If you then reset the Word layer, all of the .doc files you created are lost.

To prevent the loss of application data when a layer is reset, you must ensure that the data is not stored in the application layer.

The Workspace Virtualization Agent provides the following methods that you can use to prevent the loss of application data:

Table 2-2

Methods to prevent data loss

Method

Description

Data layer

You can create a data layer that captures the application data files that have specified extensions or that are in a specified directory. A data layer captures the application data so that it is not redirected to the writeable sublayer of the application layer.

Layer exclude entry

You can create layer exclude entries for an application layer.

A

layer exclude entry can be a file extension or a directory.

Application data that matches the layer exclude entry is saved in the base file system.

See Adding a layer exclude entry on page 48.

Global exclude entry

You can create global exclude entries for a computer. A global exclude entry can be a file extension or a directory.

A

global exclude entry applies to all layers on a computer.

Application data that matches the global exclude entry is saved in the base file system.

See Adding a global exclude entry on page 49.

Non-local storage

You can save the application data of a virtualized application

to

a non-local storage device, such as a network share. The

data is then not redirected to the application layer.

New reset point

You can copy the data from the writeable sublayer to the read-only sublayer using a new reset point.

See Resetting application layers on page 61.

See About working with virtual software packages on page 17.

Planning for the use of Virtual Software Packages 21 Where you can use Virtual Software Packages

Where you can use Virtual Software Packages

After you create virtual software packages (VSPs) with the Workspace Virtualization Agent, you can use them in the different environments. The following table indicates the environments in which VSPs can be used:

Table 2-3

VSP environments

Environment

Description

Symantec Workspace

Workspace Streaming provides native support for delivering Virtual Software Packages. See the Symantec Workspace Streaming Admin Guide .

Streaming

Altiris Notification

With Notification Server 7.0 and later, the Workspace Virtualization Agent lets you create tasks and policies to deliver and manage virtual software layers on client computers. See the Software Management Solution User's Guide .

With Notification Server 6.x, the Workspace Virtualization Agent lets you create tasks and policies to deliver and manage virtual software layers on client computers. See the Software Virtualization Solution 6.x Help .

Server

Altiris Deployment

Deployment Solution lets you create jobs to deploy and manage virtual software layers. See the Deployment Solution Admin Guide (6.x) or the Deployment Solution User's Guide (7.x).

Solution

Standard management

The Workspace Virtualization Agent works independently of the Altiris framework. Because API, WMI, and command-line interfaces are supported, you can manage client-side operations with any desktop management product. See the Altiris Software Developer Kit (SDK).

frameworks

Stand alone

You can use VSPs in a stand-alone environment. To use VSPs, install the SWV Admin tool on a computer and then create or import existing VSPs.

See About working with virtual software packages on page 17.

How the Workspace Virtualization Agent affects security

The Workspace Virtualization Agent uses the security systems that are built into the Windows NT family of operating systems. Access Control Lists (ACLs) in the registry and the file system control access to the Workspace Virtualization Agent.

22

Planning for the use of Virtual Software Packages How the Workspace Virtualization Agent affects security

The ability to protect files and directories through ACLs requires the use of the NTFS file system. ACLs on virtualized items (registry entries, files, and services) are persisted normally. The Workspace Virtualization Agent moves the ACLs when a Virtual Software Package (VSP) is exported and imported.

The following sections contain a description of how security works in several different areas for Virtual Software Packages (VSPs):

See Rights to modify a virtual software package on page 22.

See Rights to user-specific dataon page 22.

See Rights to start programs on page 23.

Rights to modify a virtual software package

To modify a Virtual Software Package (VSP), a user must generally be a member of the local administrators group. The following are exceptions to the general rule:

Users that have read access to the HKLM\System\CurrentControlSet\ Services\FSLX\Parameters\FSL\Rights\Activate key can activate VSPs.

Users with read access to the HKLM\System\CurrentControlSet\ Services\FSLX\Parameters\FSL\Rights\Deactivate key can deactivate VSPs.

A user has the same rights to the files and registry keys in the redirection areas as if the application had been installed normally. This accessibility is not a problem if an application properly creates ACLs for its files during installation.

Rights to user-specific data

Data layers and the writeable sublayer of application layers are user-specific. This means that the layer has a unique area for each user that holds the information that is unique to each user. These unique areas exist under a SID directory that is named with a string representation of the user's SID. This directory contains subdirectories like the user's profile directory and desktop directory. You can see the SID directories in the Edit Layer dialog box on the Files and Registry tabs.

See Editing the files in a virtual software layer on page 45.

The read-only sublayer of an application layer does not contain unique entries for each user. It contains only one copy of user data that is contained in a section that is named USER_TEMPLATE. During the capture process, any user-specific data goes into this area. When any user uses the layer outside of capture mode, a SID directory is created for the current user. The contents of the USER_TEMPLATE area are copied to this directory. The USER_TEMPLATE area in the read-only sublayer is not used during normal operation.

Planning for the use of Virtual Software Packages 23 About handling duplicate services

Files, directories, and registry keys are protected with the same rights that protect the corresponding objects in the base. For example, when the DESKTOP folder is created in the layer, the ACLs are copied from the user's base DESKTOP folder. This process ensures that only the proper users have rights to this folder.

When a layer is exported, the rights that are contained in the file system are represented in a file that is named ACLS in SDDL format. At import time, after the files and directories have been extracted, this information is used to re-apply the proper rights.

Rights to services are handled in a similar fashion. An SDDL string is generated and used to maintain the proper rights on the service

Rights to start programs

When a layer is activated, the Workspace Virtualization Agent typically starts all of the items in the layer that are configured to run at startup. These programs run as the user who activates the layer. For example, when a layer is activated remotely by Notification Server, it happens in the SYSTEM context by default. Therefore, the Workspace Virtualization Agent does not start an item unless the interactive user who is logged onto the system does the activation.

This control over the starting of programs does not apply to the OnEvent actions. OnEvent actions are run regardless of how the layer is activated. You must ensure that OnEvent actions are executed according to your security policies.

About handling duplicate services

The Workspace Virtualization Agent uses reference counts to properly control the creation, starting, stopping, and deletion of services with the Service Control Manager. The reference count information is stored under

HKLM\SYSTEM\CurrentControlSet\Services\FSLX\Parameters\FSL\Services.

For example, a service is run from the base and the same service is then started again through a layer. When you deactivate the layer, the first instance of the service continues to run.

See About working with virtual software packages on page 17.

About multiple concurrent user support

Workspace Virtualization supports multiple concurrent user environments. Multiple users can connect to a terminal server and run virtualized applications and not affect other users. Virtualized applications must natively support use in

24

Planning for the use of Virtual Software Packages About multiple concurrent user support

a terminal server environment. Support is provided for roaming profiles in multiple concurrent user environments.

Layers are activated on the server level, rather than the user level. Admin operations should be restricted to a single user to prevent conflicts. Exporting layers in multiple concurrent user environments is not recommended as the layer likely contains large amounts of user data.

Chapter

3

Installing the Symantec Workspace Virtualization Agent

This chapter includes the following topics:

Supported platforms for the Workspace Virtualization Agent

Installing the Workspace Virtualization Agent

Installing the Workspace Virtualization Agent silently

What the Workspace Virtualization Agent installs

Upgrading the Workspace Virtualization Agent

Uninstalling the Workspace Virtualization Agent

Troubleshooting Workspace Virtualization Agent installations

Cleaning up a failed Workspace Virtualization Agent installation

Removing the WMI Provider

Uninstalling the Agent in Runtime Mode

Supported platforms for the Workspace Virtualization Agent

Workspace Virtualization requires the Microsoft Visual C++ 2008 Runtime Libraries on all endpoints. If this runtime is not present during the installation, it is installed automatically.

26

Installing the Symantec Workspace Virtualization Agent Installing the Workspace Virtualization Agent

Workspace Virtualization supports 64-bit editions of the following operating systems:

Windows 7

Windows Vista SP1 or SP2

Windows Server 2008 and 2008 R2 when used as an endpoint

Workspace Virtualization supports 32-bit editions of the following operating systems:

Windows 7

Windows Vista SP1 or SP2

Windows XP Professional SP2 or SP3

Windows Server 2008 when used as an endpoint

Windows Server 2003 SP1 or later and 2003 R2 when used as an endpoint

Installing the Workspace Virtualization Agent

This section provides instructions for installing the Agent using the interactive installation program. You can download the Workspace Virtualization Agent installation setup files at the following URL:

Global exclude entries are added for the Desktop and My Documents folders by default.

See How to prevent the loss of application data on page 19.

See What the Workspace Virtualization Agent installs on page 28.

To install the Agent on a base computer

1 Run the 32- or 64-bit version of Symantec_Workspace_Virtualization.exe.

The version you select must match the endpoint architecture. The 32-bit version cannot be installed on a 64-bit operating system.

2 Enter the product key, and then click Next .

3 On the Select Features page, select any optional components you want to install:

Symantec Workspace Virtualization Admin Tool This option installs the SWV Admin tool. You can use this tool to create, edit, and manage virtual software layers on the endpoint.

Symantec Workspace Virtualization SDK

Installing the Symantec Workspace Virtualization Agent 27 Installing the Workspace Virtualization Agent silently

This option installs documentation and samples for the SDK. This should be installed if you are writing applications that use the SDK. It does not need to be installed to run applications that are written with the SDK.

Altiris Notification Server Support This option installs support for managing Workspace Virtualization on endpoints in a Notification Server environment.

4 Complete the setup wizard.

5 Restart the computer after the installation completes.

Installing the Workspace Virtualization Agent silently

You can run the Workspace Virtualization installation program from a command line to perform a silent installation.

For example, the following commands perform a silent install of the Agent:

Symantec_Workspace_Virtualization.exe /s SWV.PRODUCT_KEY=<product-key>

The product key is required. Additional options are listed in the following table. Options should be separated by a single space.

For example:

Symantec_Workspace_Virtualization.exe /s SWV.PRODUCT_KEY=<product-key> SWV.ADDLOCAL=SVS_Admin,SDK,Altiris_NS

Table 3-1

Windows Installer command-line properties and descriptions

Property

Description

SWV.DEFAULT_FILE_REDIR=D:\fslrdr

Changes the location of the file redirection area. The FSLRDR path cannot contain any non-ASCII characters. Unsupported characters include Hi ASCII, numeric digits, special characters, or any other character that cannot be upper or lower case. The file path must be at least three characters.

SWV.INSTALLDIR=C:\SVSAgent

Changes the default installation location.

SWV.PRODUCT_KEY=<product key>

Specifies the product key for the installation. You obtain this product key from Symantec when you purchase the product or download a key for free personal use of the product. This property is required.

28

Installing the Symantec Workspace Virtualization Agent What the Workspace Virtualization Agent installs

Table 3-1

Windows Installer command-line properties and descriptions (continued)

Property

Description

SWV.REBOOT=ReallySuppress

Suppresses the restart prompts. Without this switch, the installer automatically restarts the computer. Do not attempt to use Workspace Virtualization or to import or activate any layers until the computer is restarted.

SWV.ADDLOCAL=<value1>, <value2>

Add local adds the specified component to the local

REMOVE=<value1> , < value2>

installation. Remove removes the specified component.

Provide one or more of the following values that are separated by commas:

SVS_Admin

Changes the installation location of the command-line utility, WMI provider, and the SWV Admin tool.

SDK

Installs the Workspace Virtualization SDK.

Altiris_NS

Installs the components to integrate with the Symantec Management Platform.

What the Workspace Virtualization Agent installs

The installed components and the corresponding files are listed in the following table.

Table 3-2

Installed components

Component

Default path

Prerequisites

Microsoft Visual C++ 2008 Runtime Libraries (if not installed)

Command-line executable file

C:\Program Files\Symantec\Workspace Virtualization\SVSCmd.exe

C:\Program Files\Symantec\Workspace Virtualization\UIUtils.dll

Driver

C:\Windows\system32\drivers\fslx.sys

File redirection area

C:\fslrdr

Installing the Symantec Workspace Virtualization Agent 29 What the Workspace Virtualization Agent installs

Table 3-2

Installed components (continued)

Component

Default path

Libraries

C:\Windows\system32\fsllib32.dll

C:\Windows\system32\aszlib.dll

C:\Windows\system32\xerces-c_3_0.dll

C:\Windows\system32\XpaFormat.dll

C:\Windows\system32\XpfFormat.dll

C:\Windows\system32\XpfInstall.dll

SWV Admin tool

C:\Program Files\Symantec\Workspace Virtualization\svsadmin.exe

C:\Program Files\Symantec\Workspace Virtualization\fslui.dll

C:\Program Files\Symantec\Workspace Virtualization\<LCID>\FslUI_resources.dll

WMI provider

C:\Program Files\Symantec\Workspace Virtualization\SvsWmi.dll

C:\Program Files\Symantec\Workspace Virtualization\SvsWmi.mof

The file redirection area is where the files that are in a virtual software layer are stored.

The installation creates the following registry keys:

Table 3-3

Installed registry keys

Key

Registry path

Registry redirection area

HKEY_LOCAL_MACHINE\SOFTWARE\fslrdr

Workspace

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\

Virtualization Agent

Services\FSLX\Parameters\SVS

product settings

Virtual layer metadata

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\

Services\FSLX\Parameters\FSL

The registry redirection area is where the registry entries in a virtual software layer are stored. See the FSLRDR path limitations that are described in the command-line installation section before you change this value.

30

Installing the Symantec Workspace Virtualization Agent Upgrading the Workspace Virtualization Agent

The installation installs the driver similar to how a service is installed. The installation of the WMI provider uses the programmatic equivalent of mofcomp.exe.

The installation sets the security permissions on the file redirection area and the registry redirection area. Administrators and the System Account have full access to these redirection areas.

See Hiding the FSLRDR redirection areas on page 65.

Upgrading the Workspace Virtualization Agent

To upgrade the Workspace Virtualization Agent you can typically run the installation program for the new version without uninstalling. For supported upgrade paths and notes, see the release notes for the upgrade version.

Uninstalling the Workspace Virtualization Agent

You can uninstall the Workspace Virtualization Agent using the Add/Remove Programs applet in the Control Panel. You can also use the applet to add or remove optional components.

Uninstalling the Workspace Virtualization Agent does not remove any existing virtual software layers or remove your registry settings.

To remove layers manually after you uninstall the Agent

1 Delete the FSLRDR directory. It is located by default at c:\fslrdr.

2 Delete the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\FSLX\Parameters key.

Troubleshooting Workspace Virtualization Agent installations

You can complete most failed installations with a restart and a reinstallation. If that does not work, add the /l*v <logfile> command-line option to create a Windows Installer log for the installation. In the installation log, search for "return value 3". The lines preceding this value should contain an error message regarding the failure. If the error message identifies the problem (for example, an invalid product key), you should be able to resolve it. For more complex problems, you may need to contact Symantec support or do a manual cleanup of the installation.

Installing the Symantec Workspace Virtualization Agent 31 Cleaning up a failed Workspace Virtualization Agent installation

See Cleaning up a failed Workspace Virtualization Agent installationon page 31.

Cleaning up a failed Workspace Virtualization Agent installation

If the installation of the Workspace Virtualization Agent fails and the problem cannot be resolved, you can manually clean up the failed installation.

See Troubleshooting Workspace Virtualization Agent installations on page 30.

To clean up a failed installation of the Agent

1 Remove all the installed files and registry keys.

See What the Workspace Virtualization Agent installs on page 28.

2 To delete the FSLX driver, type the following command:

sc.exe delete FSLX

3 Remove the local group that was created for Agent security with the following command:

net.exe localgroup "Workspace Virtualization Administrators" /

delete

4 Remove the WMI Provider.

See Removing the WMI Provider on page 31.

5 To clean up the information that Windows Installer caches about the package, type the following command:

msizap.exe TW! {7D8DBB7C-1C55-4950-A107-043C164F379A}

The msizap.exe tool comes with the Windows Installer SDK.

Removing the WMI Provider

To clean a failed installation of the Workspace Virtualization Agent, the WMI Provider must be removed.

See Installing the Workspace Virtualization Agent silently on page 27.

See Cleaning up a failed Workspace Virtualization Agent installationon page 31.

To remove the WMI Provider

1 Launch wbemtest.exe.

2 Click Connect .

32

Installing the Symantec Workspace Virtualization Agent Uninstalling the Agent in Runtime Mode

3 Type root\default as the namespace, and then click Connect .

4 Click Delete Class .

5 Enter the class name AltirisVSProv, VirtualSoftwarePackage, and VirtualSoftwareSublayer and follow the prompts to delete the class.

6 Remove the following registry keys created by the WMI provider:

HKEY_CLASSES_ROOT\AppID\AltirisVSProvider.DLL

HKEY_CLASSES_ROOT\CLSID\{71D8DF9A-AD2D-44BF-A542-1412F68061D1}

HKEY_CLASSES_ROOT\TypeLib\{888967EF-E75C-4480-992D-93FDA658F21E}

Uninstalling the Agent in Runtime Mode

When a vendor distributes a vra file, it is wrapped in a WiseScript EXE that contains installation logic. This logic installs the Agent in runtime mode, if needed, and imports and activates the runtime layer.

If the Agent is installed in runtime mode, uninstall it before you install a licensed version of the Agent.

To uninstall the Agent in Runtime Mode

Because the Agent in runtime mode does not appear in Add/Remove Programs, do one of the following to uninstall it:

Msiexec.exe /x {7D8DBB7C-1C55-4950-A107-043C164F379A}

Chapter

4

Creating virtual software layers

This chapter includes the following topics:

About the creation of virtual software layers

Types of virtual software layers

Methods for capturing virtual software layers

Creating an application layer using single program capture

Creating an application layer using global capture

Adding an application to an existing layer

Creating a data layer

Creating an empty layer

About the creation of virtual software layers

Before you create layers, you should be familiar with the following:

What you can and should not virtualize. See What you can virtualize using the Workspace Virtualization Agent on page 19.

The types of virtual software layers. See Types of virtual software layers on page 34.

The methods for creating virtual software layers. See Methods for capturing virtual software layers on page 34.

How to set up the base computer that you use to create layers.

34

Creating virtual software layers Types of virtual software layers

See Installing the Workspace Virtualization Agent on page 26.

A best practice is to create application layers on a computer with the same operating system that is used in production. When you create an application layer, you capture the installation of the application. Some installations contain logic to install different files depending on the computer s operating system. This process is not required when an installation does not perform any operations that are specific to an operating system.

After you create a virtual software layer, you can edit it and then export it to create a portable virtual software archive file that you can use on other computers.

See Editing the files in a virtual software layer on page 45.

See Exporting a virtual software layer to an archive file on page 59.

Types of virtual software layers

You can create the following types of virtual software layers:

Application layer

An application layer is created by capturing the installation of an

application. It contains all the installed files and registry settings

of

the application. An application layer can contain one or more

applications.

See Creating an application layer using single program capture on page 35.

Data layer

A

data layer captures and stores data files that an application

creates. A data layer is one way to prevent the loss of application data when an application layer is reset.

See Creating a data layer on page 40.

See How to prevent the loss of application data on page 19.

Empty layer

An empty layer lets you manually add an application or capture an application. Empty layers let advanced users create custom layers.

See Creating an empty layer on page 41.

See Virtual software package workflow on page 18.

Methods for capturing virtual software layers

When you create a virtual software layer, you can use either of the following capture methods:

Creating virtual software layers 35 Creating an application layer using single program capture

Wise Virtual Composer

Wise Virtual Composer provides an advanced interface to create virtual software packages. See the Wise Virtual Composer User's Guide for details.

SWV Admin tool Single program capture

When you use this method, only changes that are made during the installation of a specified application are captured. Any other activity on the computer is ignored.

This method captures all the files, registry settings, and processes of an application. The capture includes child processes and process-induced changes. It also captures Microsoft Installer (MSI) and Service Control Manager changes.

You can use this method to capture both a single installation into a layer or multiple installations into a layer. You can also use this method to capture post-installation configurations.

See Creating an application layer using single program capture on page 35.

SWV Admin tool Global capture

This method captures all changes that are made to a computer during the capture process. Because it captures all changes, it also captures all background activity on the system. Use this method only when you can t use the single program capture.

See Creating an application layer using global capture on page 37.

Creating an application layer using single program capture

You can create an application layer by capturing the installation of an application. The single program capture method is the recommended capture method. You should use this method unless it does not let you properly capture the installation of an application.

See Methods for capturing virtual software layers on page 34.

With the single program capture method, you can capture an applications installation directly or from the command-line window. When you capture installations from the command-line window, you can capture multiple installations into a single layer and perform post-installation configurations of an application. When you capture an installation directly, you can only capture that installation.

You can also create a batch file that contains the command for starting each installation. You would then run the batch file instead of an installation program.

36

Creating virtual software layers Creating an application layer using single program capture

Before you create an application layer you must deactivate all layers on the computer.

To capture an application layer with single program capture

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, on the File menu, click New Layer .

4 On the first panel, click Install application , and then click Next .

5 On the second dialog box, type a name for the layer, and then click Next . Layer names are limited to 50 characters.

6 On the Capture dialog box, do the following tasks:

Click Single program capture .

Click Browse and select the setup file. This file can be an EXE or an MSI.

(Optional) Type parameters for running the setup file.

Click Next .

Click Finish. A rotating icon appears in the system tray.

7 To capture the installation, work through the installation dialog boxes to complete the capture.

You must exit all processes that the installation starts (for example, a system tray application) before the capture process is complete.

8 (Optional) If an installation has an option to launch the application at the end of the installation, do the following tasks:

Select the option to open the application.

When the application opens, make changes to the default settings of the application. Because the installer opens the application, you are still in capture mode and the changes are captured.

Close the application to complete the capture.

The layer now appears in the SWV Admin tool.

Creating virtual software layers 37 Creating an application layer using global capture

To capture an application installation from the command-line window

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, on the File menu, click New Layer .

4 On the first dialog box, click Install application , and then click Next.

5 On the second dialog box, type a name for the layer, and then click Next . Layer names are limited to 50 characters.

6 On the Capture dialog box, do the following tasks:

Click Single program capture.

Click Browse, and then locate and click cmd.exe. For example, C:\Windows\system32\cmd.exe.

Click Next .

Click Finish.

7 In the command-line window, do the following tasks:

Start and run the installations you want to capture.

(Optional) Start an application you captured and perform post-installation configuration.

8 Close the command-line window and any process the installation started.

You must exit all processes that the installation starts (example: a system tray application) before the capture process is complete.

The layer appears in the SWV Admin tool.

See About the creation of virtual software layers on page 33.

See Creating an application layer using global captureon page 37.

See Adding an application to an existing layer on page 38.

Creating an application layer using global capture

For most applications, we recommend that you use the single program capture method. Only use the global capture method if the single program capture method does not properly capture the installation of an application.

See Methods for capturing virtual software layers on page 34.

To create an application layer, all layers on the computer must be deactivated.

38

Creating virtual software layers Adding an application to an existing layer

To create an application layer with global capture

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, on the File menu, click Create New Layer .

4 On the first dialog box, click Install application , and then click Next.

5 On the second dialog box, type a name for the layer, and then click Next . Layer names are limited to 50 characters.

6 On the Capture dialog box, click Global capture , and then click Next.

7 Click Finish.

A rotating icon appears in the system tray.

8 Run the installation program of the application.

9 (Optional) After the installation is complete, open the application, configure its default settings, and then exit it.

For example, you might set a default home page or custom security settings.

10 (Optional) Run the installation program of one or more programs and open each application to set default settings.

11 Right-click the rotating icon in the system tray and click Stop Capture.

The layer appears in the SWV Admin tool.

See About the creation of virtual software layers on page 33.

See Creating an application layer using single program captureon page 35.

See Adding an application to an existing layer on page 38.

Adding an application to an existing layer

After you create a layer, you can add an application to the layer. You can add an application to an empty layer or a layer that contains one or more applications. You can repeat the following procedure to add any number of applications to a layer.

You can only add an application to an existing layer with the SWV Admin tool.

To add an application to an existing layer, all layers on the computer must be deactivated.

See Methods for capturing virtual software layers on page 34.

Creating virtual software layers 39 Adding an application to an existing layer

To add an application to an existing layer

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, right-click the layer to which you want to add an application, and then click Add to Layer .

4 On the Capture dialog box, do the following tasks:

Click Single program capture. Use global capture only if you cannot properly capture the update with single program capture. With global capture, you must manually run the installation of the application.

Click Browse, and then select the setup file. This file can be an EXE or an MSI.

Click Next .

Click Finish. A rotating icon appears in the system tray.

5 To capture the installation, work through the installation dialog boxes to complete the capture.

You must exit all processes that the installation starts (example: a system tray application) before the capture process is complete.

6 (Optional) If an installation has an option to launch the application at the end of the installation, do the following tasks:

Select the option to open the application.

When the application opens, make changes to the default settings of the application. Because the installer opens the application, you are still in capture mode and the changes are captured.

Close the application to complete the capture.

See About the creation of virtual software layers on page 33.

See Creating an application layer using single program captureon page 35.

See Creating an application layer using global captureon page 37.

40

Creating virtual software layers Creating a data layer

Creating a data layer

You create data layers to capture data files into a dedicated layer. Data layers can store the data that would otherwise be written to an application layer or the base file system.

You can create a data layer that captures all files with specified extensions (for example, all files with a .doc extension). Files with specified extensions are captured even if they are generated outside of the layer.

You can also create a data layer for a specific directory (for example, the My Documents folder). When you specify a directory, you can include its subdirectories. Any files that are saved into this directory are saved in the data layer.

When a data layer is activated on a computer, files that already exist on the computer are not automatically captured into the layer. However, any files that match the specifications of the data layer are redirected to the layer when they are modified.

To create a data layer

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, on the File menu, click New Layer .

4 On the Create new layer dialog box, click Data layer , and then click Next.

5 On the second dialog box, type a name for the layer. In the Data layer details section, click either the File extension(s) separated by semi-colon or Directory option, and then specify the extensions or directory. Layer names are limited to 50 characters.

To create a data layer that uses both file extensions and a directory, you must edit the layer after it is created.

See Editing a data layeron page 46.

6 Click Next , and then click Finish .

The layer appears in the SWV Admin tool.

See About the creation of virtual software layers on page 33.

See Creating an application layer using single program captureon page 35.

Creating an empty layer

Creating virtual software layers 41 Creating an empty layer

If a program does not have an installer, you could create an empty layer and then edit it to add files and registry settings. After you create an empty layer, you can also capture the installation of an application to add it to the layer.

See Editing the files in a virtual software layer on page 45.

See Adding an application to an existing layer on page 38.

To create an empty layer

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, on the File menu, click New Layer .

4 On the Create new layer dialog box, click Empty layer , and then click Next.

5 On the second dialog box, type a name for the layer, click Next , and then click Finish . Layer names are limited to 50 characters.

The layer appears in the SWV Admin tool.

See About the creation of virtual software layers on page 33.

42

Creating virtual software layers Creating an empty layer

Chapter

5

Editing virtual software layers

This chapter includes the following topics:

Configuring a virtual software layer to start automatically

Activating a virtual software layer using a desktop shortcut

Editing the files in a virtual software layer

Editing the registry settings of a virtual software layer

Editing a data layer

Adding exclude entries to virtual software layers

Adding a layer exclude entry

Adding a global exclude entry

Adding a global user profile exclude entry

Ignoring the global exclude list for a single layer

Transferring global excludes to another computer

Adding a delete entry to a virtual software layer

About updating a virtual software layer

Updating a virtual software layer

Creating a layer patch to update a virtual software layer

Renaming a virtual software layer

44

Editing virtual software layers Configuring a virtual software layer to start automatically

Configuring a virtual software layer to start automatically

You can configure a virtual software layer to start (activate) automatically when a client computer starts. You can also activate a layer from a desktop shortcut.

See Activating a virtual software layer using a desktop shortcut on page 44.

Note: If you don t configure a layer to start automatically and if the user cannot manually activate it, the user cannot access it.

You can also use the SVSCMD executable file with the AUTOACTIVATE parameter to set a layer to start automatically.

See SVSCMD command-line parameters on page 72.

To configure a layer to start automatically

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, right-click a layer, and then click Activate On System Startup .

If a check mark appears next to the option, it is enabled.

See Editing the files in a virtual software layer on page 45.

Activating a virtual software layer using a desktop shortcut

Layer activation using a shortcut is enabled by setting the layer to be partially activated. After a layer is partially activated shortcut icons and file associations are displayed as if the layer is activated. When a shortcut or a file association starts the application, the layer is fully activated. This feature is useful in environments where you want a large number of applications active when the computer starts.

Partially activating a layer can be done using SVSCMD. Deactivating and reactivating a partially activated layer fully activates it.

Partial activation does not work with virtualized applications that contain advertised shortcuts.

See SVSCMD command-line parameters on page 72.

Editing virtual software layers 45 Editing the files in a virtual software layer

To activate a virtual software layer using a desktop shortcut

1 At the command line, enter svscmd <layerGUID/layerName>

partialactivate -y.

2 At the command line, enter svscmd <layerGUID/LayerName> Auto[Activate]

-y to enable Activate on system startup.

3 When the computer restarts the layer is partially activated and can be activated using a desktop shortcut.

To disable partial activation for a layer

At the command line, enter svscmd <layerGUID/layerName>

partialactivate -n.

See Actions you can perform to manage layers on page 58.

Editing the files in a virtual software layer

You can make the following changes to the files in a layer:

Create new folders.

Rename and delete folders and files.

Copy or move files and folders within a layer, into a layer, or outside a layer.

You cannot overwrite files in a layer. To replace a file, delete or move the original and replace it with the updated file. To edit a file, move the original, update the file and then replace the original with the updated file.

To edit the files in a virtual software layer

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, double-click the layer.

4 In the Layer Properties dialog box, click the Files tab.

The Files tab has two nodes to separate the files in the read-only and writeable sublayers. When you edit the files in a layer, make sure that you make the changes in the correct node.

Most folders on the Files tab use a name that is a variable.

See Viewing variables used in a virtual software layer on page 66.

46

Editing virtual software layers Editing the registry settings of a virtual software layer

6 To edit a folder, right-click a folder, and then select an option.

7 To edit a file do the following:

Select the folder that contains the file. The file appears in the right pane.

In the right pane, right-click the file, and then select an option.

Editing the registry settings of a virtual software layer

After you create a virtual software layer, you can edit its registry settings. If you create an empty layer, you can add registry settings to the layer.

Note: The Workspace Virtualization Agent does not store data in the virtual HKEY_CLASSES_ROOT key. Instead it stores it in its real location under either HKEY_USERS\USER_TEMPLATE\Software\Classes or HKEY_LOCAL_MACHINE\ Software\Classes. At runtime, Windows reads the Workspace Virtualization data for activated layers from these locations and properly renders HKEY_CLASSES_ROOT.

To edit registry settings of a virtual software layer

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, double-click the layer.

4 In the Layer Properties dialog box, click the Registry tab.

The Registry tab has two nodes to separate registry settings in the read-only and writeable sublayers. When you edit a layer, make sure that you make the changes in the correct node.

5 To edit registry settings, use the same process as you would with regedit.

Editing a data layer

After you create a data layer, you can edit which files the data layer captures. For example, after you create a data layer that captures .doc files. You can edit it to also capture the files that are added to a specified directory.

To edit a data layer, the layer must be deactivated.

Editing virtual software layers 47 Adding exclude entries to virtual software layers

To edit a data layer

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, double-click the layer.

4 In the Layer Properties dialog box, click the Data Capture tab.

5 On the right-click menu, click New Data Capture Item .

6 On the Data Layer Capture Entry dialog box, click either the File extension or the Directory option, and then specify the extension or directory.

It doesn t matter if you include the period before the extension. Enter only one extension per entry. To include subdirectories, check Include Subdirectories .

7 Click OK .

The data capture entry appears in the list box.

See Creating a data layeron page 40.

Adding exclude entries to virtual software layers

Exclude entries let you prevent files from being saved in the redirect area of the layer. By default, when an application layer generates files,those files are saved to the applications writeable sublayer. If the layer is reset, the files in the writeable sublayer are lost. An exclude entry lets you specify file types or locations on the base system and not in the application's writeable sublayer.

Layer excludes affect a single layer. Global excludes affect all layers on the computer.

See How to prevent the loss of application data on page 19.

Note: Data layer includes take precedence over data layer excludes.

You can add the following types of exclude entries:

48

Editing virtual software layers Adding a layer exclude entry

Layer exclude entry

A

layer exclude entry redirects files from a specific layer to the

base file system. You add layer excludes on a layer by layer basis. For example, you can add excludes to a Microsoft Word layer for .doc, .rtf, and .txt file types. When Word saves any of these file types, they are saved in the base file system and not in the layer.

See Adding a layer exclude entry on page 48.

Global exclude entry

A

global exclude entry redirects files for every layer on a

computer to the base file system. For example, you can add a global exclude for PDF files. If any layer creates PDF files, the files are excluded from the layer and saved in the base file system.

When you install the Workspace Virtualization Agent, you have the option to add global excludes for the My Documents and the Desktop directories. You can edit these predefined global exclude entries and add your own.

Global excludes are not associated with a specific layer and are not exported when you export a layer. To export a global exclude list to another computer, create and export a registry file that contains the settings for the list.

See Adding a global exclude entry on page 49.

User profile exclude

A

user profile exclude entry redirects files that are stored in the

entry

user profile to the base file system. This exclude entry should be enabled in environments that use roaming profiles.

See Adding a global user profile exclude entry on page 50.

Adding a layer exclude entry

You add a layer exclude entry to exclude files from a specific layer. A layer can have any number of exclude entries.

See Adding exclude entries to virtual software layers on page 47.

To add a layer exclude entry

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, deactivate and then double-click the layer.

4 In the Layer Properties dialog box, click the Exclude Entries tab.

Editing virtual software layers 49 Adding a global exclude entry

6 On the Layer exclude entry dialog box, click either the File extension or the Directory option, and then specify the extension or directory.

It doesn t matter if you include the period before the extension. Enter only one extension per entry. To exclude subdirectories, check Exclude Subdirectories .

7 Click OK .

The exclude entry appears in the list box.

8 To edit or delete an exclude entry, on the entries right-click menu, click Modify Exclude Entry or Delete Exclude Entry .

Adding a global exclude entry

You add a global exclude entry to exclude files from all layers on the computer. A computer can have any number of global exclude entries.

See Adding exclude entries to virtual software layers on page 47.

Global excludes are set on each computer and are not exported when a virtual software layer is exported. To transfer global excludes you can export the global excludes from the registry and then import them on another computer.

See Transferring global excludes to another computer on page 50.

You can configure a layer to ignore the global excludes.

See Ignoring the global exclude list for a single layer on page 50.

To add a global exclude entry

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, on the File menu, click Global Excludes .

4 In the global excludes pane, on the right-click menu, click New Exclude Entry .

5 In the Global Excludes dialog box, on the right-click menu, click New Exclude Entry. On the Global exclude entry dialog box, click either the File extension or Directory option, and then specify the extension or directory.

It doesn t matter if you include the period before the extension. Enter only one extension per entry. To exclude subdirectories, check Exclude Subdirectories .

50

Editing virtual software layers Adding a global user profile exclude entry

6 Click OK .

The exclude entry appears in the list box.

7 To edit or delete a global exclude entry, right-click entries , and then click Modify Exclude Entry or Delete Exclude Entry .

Adding a global user profile exclude entry

You add a profile exclude entry to exclude all files that are stored in the user profile. This exclusion stores user profile data in the base and not in a layer. This exclusion allows profile data to roam in environments with roaming profiles.

To add a global profiles exclude

1 Use the SVSCMD command line EXCLUDEALLPROFILES -y. This command creates a DWORD value that is named ExcludeProfileData under

HKLM\System\CurrentControlSet\Services\FSLX\Parameters\FSL

2 Restart the computer.

See SVSCMD command-line parameters on page 72.

See Adding exclude entries to virtual software layers on page 47.

Ignoring the global exclude list for a single layer

Ignoring the global exclude list lets you specify that global excludes should not be used for a layer.

See Adding exclude entries to virtual software layers on page 47.

To ignore the global exclude list

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, double-click the layer.

4 In the Layer Properties dialog box, on the Exclude Entries tab, check Ignore Global Exclude List .

Transferring global excludes to another computer

Global excludes are set on each computer and are not exported when a virtual software layer is exported. To transfer global excludes you can export the global excludes from the registry and then import them on another computer.

Editing virtual software layers 51 Adding a delete entry to a virtual software layer

See Adding a global exclude entryon page 49.

To transfer global excludes to another computer

1 On the computer with the global excludes that you want to export, run regedit and browse to HKLM\SYSTEM\CurrentControlSet\Services\FSLX\Parameters\FSL\ExcludePath.

2 Right-click the ExcludePath folder and then click Export.

3 Copy the registry file to another computer and and then import the settings.

Warning: When you run this file, if the registry key already exists on a computer it is overwritten with the contents of the new registry key.

4 To reload the global exclude list without restarting the computer, run the SVSCMD executable file with the REL[LOAD] parameter.

Adding a delete entry to a virtual software layer

A delete entry hides a file on a computer when a virtual software layer is active.

The hidden file functions as if it were deleted. When the layer is deactivated or deleted, the file reappears.

You can use delete entries to hide any file on a computer when a layer is activated. For example, you can create a layer for Mozilla Firefox with delete the entries that hide the Internet Explorer shortcuts. When the Firefox layer is activated, the Internet Explorer shortcuts are hidden. If the Firefox layer is deactivated or deleted, the shortcuts are visible.

With the global capture method, you can add a delete entry when you create a

layer. Any file or registry setting that you delete when in capture mode becomes

a delete entry in the read-only sublayer.

You can also manually add one or more delete entries to a layer. You normally add a delete entry to the read-only sublayer. To add a delete entry for a layer, the layer must be deactivated.

Warning: Avoid adding delete entries to a layer unless you are sure that no other applications need the file.

A delete entry is also added whenever a user deletes a file or a registry entry from

the read-only sublayer. The files are not deleted, but they become delete entries

in the writeable sublayer. If the layer is reset, the file is restored to the read-only

52

Editing virtual software layers About updating a virtual software layer

sublayer. You can view a layers delete entries to see if files from the read-only layer have been deleted.

To add a delete entry to a virtual software layer

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, double-click the layer.

4 In the Layer Properties dialog box, click the Delete Entries tab.

5 In the left pane, select the folder for the delete entry.

The Delete Entries tab has a read-only and a writeable node for both files and registry entries. When you add a delete entry, make sure that you select the appropriate node. The writeable nodes have a System Delete List and a user-specific delete list. If you add a delete entry to the System Delete List, the delete entry is deleted for all users. If you add a delete entry to a specific user delete list, it is only deleted for that user. For example, if you specify a user delete entry for a desktop shortcut, it is only deleted for that user.

6 In the right pane, on the right-click menu, click New Delete Entry.

7 Edit the default entry, [SYSTEMDRIVE]\Filename.ext, to define the delete entry.

About updating a virtual software layer

After you create a virtual software layer, you can update the layer with an update or patch. Before you update an existing layer, you should first decide whether the update warrants creating a new layer. If you create a new layer, you must reapply any edits that you applied to the existing layer.

Before you update an existing layer, you must also decide whether to update its writeable or read-only sublayers. An applications writeable sublayer is updated when the update runs on a computer where the application layer is activated. The major disadvantage of updating the writeable sublayer is that the update is lost if the layer is reset. The major advantage of updating the writeable sublayer is that it preserves user-specific settings in the writeable sublayer.

To update a layers read-only, you must use the SWV Admin tool. You use this tool to capture the update into the existing layer. The major disadvantage of updating the read-only sublayer is that any user-specific settings in the writable sublayer are lost. The major advantage of updating the read-only sublayer is that you can ensure that all users have an identical version of the application.

Editing virtual software layers 53 Updating a virtual software layer

See Updating a virtual software layer on page 53.

Before you update the read-only sublayer of an application, you should change the layer s name and GUID. You can then import the updated layer on a computer without deleting the original layer. If the updated layer causes problems, you can then quickly deactivate it and activate the original layer. To change the GUID of a layer, use the SETGUID SVSCMD command-line parameter.

See SVSCMD command-line parameters on page 72.

See Editing the files in a virtual software layer on page 45.

Updating a virtual software layer

After you create a virtual software layer, you can update the layer with an update or patch. For example, if you have a layer for Microsoft Office, you can update it when an update or patch is released for Office.

See About updating a virtual software layer on page 52.

You can also use this option to update a layer to add an application to an existing layer.

See Adding an application to an existing layer on page 38.

After you update a layer, export the layer to create a new layer archive file.

See Exporting a virtual software layer to an archive file on page 59.

To update a virtual software layer

1 Start the SWV Admin tool.

2 In the SWV Admin tool, on the File menu, click Update Existing Layer .

3 On the first dialog box, select the layer and click Next.

4 On the second dialog box, do the following:

Click Single program capture. Use global capture only if you cannot properly capture the update with single program capture. With global capture, you must manually run the update.

Click Browse and select the update file.

Click Next .

54

Editing virtual software layers Creating a layer patch to update a virtual software layer

5 Click Finish.

A rotating icon appears in the system tray.

6 To capture the installation, work through the installation dialog boxes to complete the capture.

You must exit all processes that the installation starts (for example, a system tray application) before the capture process is complete.

Creating a layer patch to update a virtual software layer

Layer patches provide a mechanism to make small, incremental updates to an existing application layer. Layer patches reduce the need to create a new layer to provide an application update. A layer patch file contains the changes between two versions of an application. Layer patches let you update layers without distributing a completely new layer.

For example, an existing Firefox 3.01 virtual software layer can be updated to version 3.02 by applying a small patch file.

When applying a patch, you can select to keep the previous layer and create new layer with the updated versions. This feature can simplify application migration by providing access to both versions. You can also copy all of the data and the settings that are stored in the writeable sublayer to the new version.

Patch files must be applied incrementally. If you create multiple patches, they must be applied in the order they were created.

To create a layer patch file you need a layer that contains the existing version of an application. This layer must have the same GUID as the layer distributed in your environment. You also need a second layer that contains the updated version of the same application. For example, Firefox 3.01 in the first layer and Firefox 3.02 in the second.

For a detailed explanation of the patch creation process, see the following article on Symantec Connect:

Note: Due to significant path and other system changes in 64-bit, patches created for 64-bit operating systems should be created on the specific operating system where they will be deployed. For example, we recommend creating a separate patch file for 64-bit Windows 7 using a 64-bit Windows 7 operating system.

Editing virtual software layers 55 Renaming a virtual software layer

To create a layer patch file

1 Import the layer that contains the existing version.

2 Import the layer that contains the updated version of the application.

3 In the SWV Admin tool, click File > Create patch .

4 On the Create Layer Patch Archive File dialog box, do the following:

Select the original layer from the Original layer drop-down menu.

Select the updated layer from the Updated layer drop-down menu.

Click Browse , select the name and path for the layer patch file, and then click Open .

Click OK .

To apply a layer patch file

1 In the SWV Admin tool, click File > Apply Patch .

2 Click Browse, select the name and path for the layer patch file, and then click Open.

Click Patch existing layer to apply the patch to an existing layer. This option updates the existing layer.

Select Export before patching to create a backup of the layer before the patch is applied.

Select Create new layer to apply the patch to a new layer. This option leaves the original layer intact.

Select Copy writeable sublayer from existing layer to copy the data that is stored in the writeable sublayer. This option moves the changes that are stored in the existing layer to the new layer.

3 Click OK .

After a patch is applied, Windows Shortcut files (.LNK) that are contained in the writeable sublayer of the previous version are removed. Any new shortcuts in the new version are available. This process helps prevent unusable shortcuts from being left after an upgrade.

Renaming a virtual software layer

You can rename a virtual software layer. Before you update a layer, we recommend that you rename the layer and change its GUID to avoid confusion. To change the GUID of a layer, use the SETGUID SVSCMD command-line parameter. You can also use the SVSCMD executable file to rename a layer.

56

Editing virtual software layers Renaming a virtual software layer

See SVSCMD command-line parameters on page 72.

To rename a layer, you must first deactivate the layer.

To rename a virtual software layer

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, on a layer s right-click menu, click Rename.

4 Type the new name for the layer.

Chapter

6

Managing virtual software layers

This chapter includes the following topics:

About the management of virtual software layers

Actions you can perform to manage layers

Testing a virtual software layer

Interoperability with antivirus scanners

Hiding the FSLRDR redirection areas

Viewing the properties of a virtual software layer

Viewing variables used in a virtual software layer

About the management of virtual software layers

After you create and edit virtual software layers, you can manage them throughout their life cycle. You can manage layers locally and remotely. To manage layers locally, you use the SWV Admin tool.

To manage layers remotely, you can use the following methods:

Symantec Workspace Streaming

Symantec Workspace Streaming provides a platform to stream virtual software directly to virtual software layers. You can deliver virtualized applications on-the-fly and leverage advanced license tracking and reporting capabilities.

58

Managing virtual software layers Actions you can perform to manage layers

SVSCMD

Altiris Notification Server

Altiris Deployment Solution

WiseScript Package Editor

Standard management framework

The SVSCMD executable file has a set of command-line parameters that let you manage virtual software layers.

See SVSCMD command-line parameters on page 72.

Symantec Client Management Suite lets you create tasks and policies to deliver and manage virtual software layers on client computers. See the Software Management Solution User's Guide.

Altiris Notification Server 6.x has a plug-in that lets you create tasks and policies to deliver and manage virtual software layers on client computers. See the Symantec Workspace Virtualization Agent 6.x Help .

Symantec Deployment Solution lets you create jobs to deploy and manage virtual software layers. See the Deployment Solution Admin Guide (6.x) or the Deployment Solution User's Guide (7.x).

WiseScript Package Editor has a set of Workspace Virtualization-specific actions that let you create scripts to manage virtual software layers. See the WiseScript Package Editor Help .

Workspace Virtualization provides command-line, WMI, and API interfaces to manage Workspace Virtualization client-side operations with any desktop management product.

Actions you can perform to manage layers

Table 6-1 indicates the actions that you can perform on a layer.

Table 6-1

Actions to manage layers

Action

Description

Activate

Activates a layer that was imported on a computer. When a layer is activated, its contents become visible. An activated layer is fully functional. Activation is almost instantaneous.

See Activating and deactivating virtual software layers on page 61.

Managing virtual software layers 59 Actions you can perform to manage layers

Table 6-1

Actions to manage layers (continued)

Action

Description

Deactivate

Deactivates a layer that was imported on a computer. When a layer is deactivated, it is hidden from the user but is still on the computer. Deactivation is almost instantaneous. If a process is running in a layer, this action can only deactivate the layer if it includes the Force parameter. A layer cannot be deactivated if it contains a process running for another user, even by using the Force parameter. An administrator must end the process and then deactivate the layer.

See Activating and deactivating virtual software layers on page 61.

See SVSCMD command-line parameters on page 72.

Delete

Deletes a layer from a computer.

See Deleting virtual software layers on page 62.

Export

Exports a virtual software layer to create a portable archive file in Extensible Package Format (XPF).

See Exporting a virtual software layer to an archive file on page 59.

Import

Imports a virtual software layer in XPF or VSA format into the Workspace Virtualization redirection areas on a computer. The imported layer appears in the SWV Admin tool, if it is installed.

See Importing a virtual software archive file on page 60.

Reset

Resets an application layer to its original imported state. Any data in the writeable sublayer is deleted, including user profiles that were added or changed. Data layers cannot be reset. You can use the new reset point operation to create a new reset point.

See Resetting application layers on page 61.

Exporting a virtual software layer to an archive file

After you create a virtual software layer, you can export it to an Extensible Package Format (XPF) archive file. XPF replaced VSA as the export file format.

Layer archive files can be stored on a network share, e-mailed, or deployed to client computers on your network. After the archive file is copied to a client computer, you import it to create a new layer.

See Importing a virtual software archive file on page 60.

You can export a layer locally or remotely. To export a layer remotely, you can use the SVSCMD executable file.

60

Managing virtual software layers Actions you can perform to manage layers

See SVSCMD command-line parameters on page 72.

To export a layer, you must deactivate the layer.

Do not select the Export user information option if you plan to distribute this layer to other computers. If this option is selected, layer data that is stored in the user SID is also exported. Select this option only when you create a backup.

To export a virtual software layer to an archive file

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, on the layer s right-click menu, click Export .

4 Specify a name and location.

5 Click OK .

See About the management of virtual software layers on page 57.

See Actions you can perform to manage layers on page 58.

Importing a virtual software archive file

Virtual software is imported from Extensible Package Format (XPF) files. XPF replaced VSA as the import file format, though support for importing VSA files is still provided.

See Exporting a virtual software layer to an archive file on page 59.

You can import an archive file on a computer to create a new layer if the Workspace Virtualization Agent is installed. After you import an archive file, you activate the layer to complete the installation of the application.

See About the management of virtual software layers on page 57.

To import an archive file

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, on the File menu, click Import Layer .

4 In the Open dialog box, select the archive file to import and click Open .

5 After the import completes, click OK.

The layer appears in the SWV Admin tool.

See Actions you can perform to manage layers on page 58.

Managing virtual software layers 61 Actions you can perform to manage layers

Activating and deactivating virtual software layers

When a virtual software layer is activated, all the contents of the layer are visible. When a layer is deactivated, the contents of the layer are hidden. When you create an application layer, it is activated by default. When a layer is activated, its name is displayed in bold type.

You can activate and deactivate layers locally or remotely. To activate or deactivate a layer remotely, you can use any of the interfaces that manage virtual software layers.

See About the management of virtual software layers on page 57.

To activate or deactivate a layer

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, on a layer s right-click menu, click Activate or Deactivate .

You can select and activate or deactivate multiple layers by holding the Ctrl key.

4 If you try to deactivate a layer that has a process running, a message prompts you to stop the process. Click Yes to stop the process and deactivate the layer.

The message also displays a process ID (PID). You can use this PID to look up the process in Windows Task Manager. For information about PIDs, see the Windows Task Manager Help .

See Actions you can perform to manage layers on page 58.

Resetting application layers

You can reset a damaged application layer to restore it to its original imported state.

The ability to reset an application layer provides the following benefits:

It does not require an uninstallation and reinstallation of an application.

It cannot damage the other applications that are installed on the computer.

It lets you maintain standard versions and configurations of applications across your network.

When an application layer is created, the applications data is stored in a read-only sublayer. When a user runs the application, all of the data that is created by the application is saved in a writeable sublayer. When you reset the application layer,

62

Managing virtual software layers Actions you can perform to manage layers

the data in the writeable sublayer is deleted and the read-only sublayer is maintained.

Creating a new reset point merges the existing contents from the writable sublayer with the read-only sublayer. This option can help preserve customizations and prevent data loss when a reset occurs.

Caution: To prevent the loss of any data that is created by an application, redirect the data out of the writeable sublayer.

See How to prevent the loss of application data on page 19.

Before you reset a layer, you can access the Edit Layer dialog box to view the files and registry settings in the layer s writeable sublayer.

See Editing the files in a virtual software layer on page 45.

You can reset an application layer locally or remotely. To reset an application layer remotely, you can use any of the interfaces that manage virtual software layers.

See About the management of virtual software layers on page 57.

To reset an application layer

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, on a layer s right-click menu, click Reset .

4 Click Yes .

To create a new reset point

1 In the SWV Admin tool, right-click the deactivated layer for which you want to create a new reset point. Click New Reset Point .

2 The Export layer before creating new reset point option creates a backup version of the layer with its original reset point. The Copy current user's settings to default user's settings area option merges the contents of the writeable sublayer. This option restores these settings when the layer is reset.

See Actions you can perform to manage layers on page 58.

Deleting virtual software layers

To remove a virtual software layer from a computer, you delete it. When you delete a layer, all the data in the layer is deleted. We recomend creating a new reset point and then exporting a backup copy of layer before deletion. This backup

Managing virtual software layers 63 Testing a virtual software layer

copy lets you quickly reimport the application to the current state if you decide to install it again.

You can delete an application layer locally or remotely. To delete an application layer remotely, you can use any of the interfaces that manage virtual software layers.

See About the management of virtual software layers on page 57.

To delete a virtual software layer

1 Start the SWV Admin tool.

2 Click Start > All Programs > Symantec > Workspace > Virtualization > Symantec Workspace Virtualization Admin .

3 In the SWV Admin tool, on a layer s right-click menu, click Delete .

4 Click Yes .

See Actions you can perform to manage layers on page 58.

Testing a virtual software layer

After you create a virtual software layer, you should test it to verify that it functions properly. Because virtual software layers cannot conflict with other applications, you do not have to test for conflicts. If you create both application layers and data layers, you need to perform different tests on each.

To test an application layer

1 Activate the layer and run the captured application.

See Activating and deactivating virtual software layers on page 61.

2 Verify that the applications files appear in the file system when the layer is activated and the files are hidden when the layer is deactivated.

3 To test the layer s portability, do the following:

Export the layer to an archive file. See Exporting a virtual software layer to an archive file on page 59.

Import the layer archive file on another computer. See Importing a virtual software archive file on page 60.

Activate and run the application.

64

Managing virtual software layers Interoperability with antivirus scanners

To test a data layer

1

Activate the layer.

See Activating and deactivating virtual software layers on page 61.

2

Create one or more files that meet the specifications of the data layer.

You can create these files by using an application or by copying files to a directory that is specified in the data layer.

3

Verify that the data files appear in the file system when the data layer is active and are hidden when the data layer is deactivated.

4

If

you create data files with a virtualized application, reset the application

layer and verify that the data files remain intact.

Interoperability with antivirus scanners

Workspace Virtualization contains functionality to guarantee that antivirus scanners and other file utility applications can scan the native file system. These applications are added to an ignore list so they do not see virtualized data when they run. This guarantees that all files are properly scanned. You might also want to add other programs to the ignore list so that they view the file system data without any Virtualization. For example, if an inventory program sees a file twice (virtualized and unvirtualized), it might count the file twice.

We recommend that you use this feature for your