Recommendation: Backup pre-existing layers before upgrading

You can install Software Virtualization Solution 2.1 SP2 over an existing Software Virtualization Solution 2.0 installation. Before you do this, create a backup of pre-existing layers by exporting them. Software Virtualization Solution 2.1 uses a new layer format. When you upgrade from 2.0 to 2.1, existing layers are automatically converted to this new format. However, if you need to roll back to 2.0, you cannot revert layers back to the 2.0 format . Therefore, we recommend that you back up layers before you upgrade.

Issue: Upgrading the Symantec SVS applet

Following an upgrade, the Symantec SVS applet is not available.

Issues causing user variables to resolve incorrectly the first time a user logs on to a Windows Vista computer were fixed.

Transactions

Software Virtualization Solution 2.1 SP2 does not support applications using transactions during the installation on Vista. Office 2007 and Adobe 8 both run transactions during capture. The current work-around is to create the Virtual Software Package on a different operating system.

Creating a string value in a registry during capture

If you create a registry string value when you capture a layer, two values are created and the string data is put in the second registry value. The current work-around is to create the Virtual Software Package on a different operating system.

Elevation issue with dragging and dropping files into the Edit Layer dialog box

When logged onto a Windows Vista computer, as a limited user or a regular admin, dragging and dropping files in the Edit Layer dialog box fails.

This issue occurs only on Windows Vista computers when elevated rights are required. This problem does not occur when you run Symantec Software Virtualization Solution Admin on a Windows Vista computer as an elevated administrator.

SVSCMD requires the administrator token

You must run SVSCMD in a process that uses the Administrator token.

Office launches repair

When you launch Microsoft Office 2003 or 2007 for the first time as a limited user, Microsoft Word performs a repair. This repair does not effect operation.

User Account Control warning with Software Virtualization Solution installation

When you install Software Virtualization Solution on a Windows Vista computer, a User Account Control dialog box informs you that "An unidentified program wants access to your computer." To install Software Virtualization Solution, select Allow. I trust this program. I know where it's from or I've used it before.

Variables not valid on Windows Vista computers

The Variables COMMONFAVORITES and LOCALSETTINGS do not resolve on a Windows Vista computer.

 Fatal error occurs when you attempt to perform a repair of the Software Virtualization Agent installation

If you install the Software Virtualization Agent on a Windows Vista computer and then try to repair the installation under User Account Control, you encounter a fatal error. The workaround is to perform the repair as a domain administrator, the computer administrator, or from a command line as an elevated user. 

Layers Created with 2.1 SP2 are not backward compatible with 2.0

Layers created in Software Virtualization Solution 2.1 SP2 do not work with Software Virtualization Solution 2.0 because of a change of format.

Short file names do not resolve properly

Programs that store path information in the registry that use short file names (for example, C:\progr~1 instead of C:\Program Files) might not function correctly when virtualized. This is an issue only if the base or a program in another layer uses the same short name abbreviation for a similar but different path. To resolve this issue, install the program to a directory where the first six characters of the folder name are unique.

Files saved to a non-system drive may not be visible when a layer is exported

If a file is saved into a layer on a drive other than the system drive (the C drive on most computers), the file may not appear when the layer is exported and imported onto another computer.

Fonts in a layer are not available to the application

When using an application that is in a layer, some of the application's fonts may not display correctly. The work-around is to move the fonts to the base. A utility has been developed to move a layer's fonts to the base. See http://juice.altiris.com/tech-tip/270/problems-with-svs-and-fonts-try-this.

Altiris Recovery Solution cannot complete a full snapshot

Altiris Recovery Solution cannot complete a full snapshot on computers running Software Virtualization Solution.  To resolve this issue, add an exclusion to the ProgramIgnoreList value in the registry for the Recovery Solution agent.

Registry permissions not checked in priority order

When Software Virtualization Solution checks registry permissions, it does not do it in priority order. It checks the base first.

Intermittent crashes in wininet.dll

In some instances, a virtualized application has caused wininet.dll to crash.

Acrobat Reader 7.x update may not install correctly

Acrobat Reader 8 does not have this problem.

Shortcuts not saved in layers

If you create a shortcut that references an application in a layer after the creation of the layer, the shortcut is not saved in the layer. The shortcut still appears when the layer is deactivated.

A blue screen sometimes appears when a computer is restarted after the installation of the Software Virtualization Agent

On computers that use a non-English Windows operating system and that have Symantec AntiVirus for Windows installed, a blue screen may appear after the Software Virtualization Agent is installed and the computer is restarted. To resolve this problem, install the SAVCE9_KStackMinFree.reg file. This reg file creates a KStackMinFree registry value of 2200 that resolves the problem. You can download this registry file at http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2002071208532048

Delete Layer from Software Virtualization Solution does not report the event to Notification Server

When a layer is deleted on a client computer, the event is not reported to Notification Server. This issue causes the Notification Server database to be out of sync with what is actually on the client computer and causes errors when trying to perform other actions on the layer. 

SVScontrol.cpl does not work on a Windows 2000 computer

On a Windows 2000 computer, you cannot start the Symantec SVS applet with the svscontrol.cpl command line. You can start the Symantec SVS applet from the Control Panel.

Symantec SVS applet does not work on a Windows 2008 computer

On a Windows 2008 computer, you cannot start the Symantec SVS applet.

Broken links to SVS task icons

If you upgrade or repair Task Server on a Notification Server 6.x, any links to the icons of existing SVS Tasks are broken. The tasks are still functional but the icons do not appear. To repair the links to the icons, run a repair of Altiris SVS Task in Add Remove Programs.

SVS archives located on a drive other than the system drive fail to import in the Altiris Console

When adding a new SVS archive for distribution in the Altiris Console, the operation fails if the archive is located on a drive other than the system drive. As a workaround, copy the SVS archive to the system drive before adding in the Altiris Console.

Fortress filter driver and running Windows in Safe Mode

The SVS Fortress filter driver is not loaded when a computer is started in Windows Safe Mode. Therefore, any diagnostic or recovery utilities that run in safe mode should not be installed in a layer.

Restart required after the installation of the Software Virtualization Agent

After the Software Virtualization Agent is deployed and installed, the client computer must be restarted for the agent to become active.

Clean machine captures

We recommend that you build your virtual software archive files on a clean machine. This ensures that all required files and registry settings are captured in the package.

How Altiris Recovery Solution backs up Virtual Software Packages

Because Software Virtualization Solution redirects files in Virtual Software Packages, program and data files that are in layers are not backed up in the regular file system. Consequently, you cannot view them in the Recovery utilities. However, the redirect files in the C:\fslrdr directory are backed up.

For example, if you have Microsoft Office in an active layer, the C:\Program Files\Microsoft Office directory appears. These files are actually redirected to C:\fslrdr. When you do a snapshot or recovery, the C:\Program Files\Microsoft Office folder is not recognized.