Article ID: 40553 Symantec Software Virtualization Solution 2.1 SP2 Release Notes Applies To • Workspace Virtualization (formerly SVS) Question What do I need to know about Symantec Software Virtualization Solution™ 2.1 SP2? Answer Symantec Software Virtualization Solution™ 2.1 SP2 Build number 2.1.3062 Release Notes Introduction Installation and Upgrade What's New in this Release Fixes in this Release Known Issues in this Release Additional Documentation Document History Introduction Symantec Software Virtualization Solution is a revolutionary approach to software management. It lets you put applications and data into managed units called Virtual Software Packages (VSPs). When you put an application into a VSP, you completely avoid conflicts between the application and other applications installed on a computer. You can also instantly activate, deactivate, or reset the application. If an application is broken, you can reset it to return it to its original state. Software Virtualization Solution is available in two versions: The commercial version lets you create and distribute Virtual Software Packages. The free version for personal use lets you create and use your own virtual layers on your home or personal computer. For more information, see http://juice.altiris.com/svs. This document provides information about installation, upgrade, new features, fixes, known issues, and documentation for Software Virtualization Solution. Installation and Upgrade Prerequisites Prerequisites for Software Virtualization Solution Agent: Access to the application setup files that you intend to virtualize. One of the following client operating systems: Microsoft Windows Vista SP1 32-bit Microsoft Windows 2000 Professional SP4 or later Microsoft Windows 2000 Advanced Server SP4 or later when used as a client Microsoft Windows XP Professional SP2 or Home Edition SP2 or later Microsoft Windows Server 2003 or later when used as a client Microsoft Windows Server 2008 when used as a client Prerequisites for Software Virtualization Solution with the Notification Server Platform: Altiris Notification Server 6.0 SP3 R4 or later with the Altiris Agent 6.0 or later installed on client computers. Prerequisites for Software Virtualization Solution with the Deployment Server Platform: Altiris Deployment Solution 6.8 or later with the Deployment Agent installed on client computers. Where to Download You can download released versions of Altiris products from http://www.altiris.com/Download.aspx. You can also download released versions of Software Virtualization Solution from http://www.getsvs.com. New Installation For new installation information, please see the installation topics in the Symantec Software Virtualization Solution User's Guide. Upgrade Issues Article Issue ID 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 35363 Following an upgrade, the Symantec SVS applet is not available. Upgrade Steps Upgrading Software Virtualization Solution You can upgrade the solution over an existing 2.0 installation. If you uninstall Software Virtualization Solution 2.0 or earlier, existing Virtual Software Packages (layers) on that computer are deleted. To preserve the existing layers, you should use one of the following methods to upgrade the solution. In a Notification Server 7.0 environment In the Software Catalog, for the Software Virtualization Agent, create and use the following command msiexec.exe /qb /i Software_Virtualization_Agent.msi REINSTALL=ALL REINSTALLMODE=vomus PRODUCT_KEY='PRODUCTKEY' This requires a client computer restart. In a Notification Server 6.x environment Use the Software Virtualization Agent Upgrade policy. This requires a client computer restart. In a network environment not using Notification Server Run Software_Virtualization_Agent.exe. This requires a computer restart. You can also use the following command line: msiexec.exe /qb /i Software_Virtualization_Agent.msi REINSTALL=ALL REINSTALLMODE=vomus PRODUCT_KEY='PRODUCTKEY' This requires a client computer restart. For Software Virtualization Solution for Personal Use Run Software_Virtualization_Agent.exe. This requires a computer restart. What's New in this Release Improvements for this release include the following new features: Integration with Notification Server 7.0 With Notification Server 7.0, Software Virtualization Solution is no longer a solution that plugs into the Notification Server platform. The ability to deliver and manage Virtual Software Packages is now part of the Software Management Solution. Software Virtualization Solution is now a stand-alone product that lets you create Virtual Software Packages that you can deliver and manage with Software Management Solution. Support for Microsoft Windows Vista SP1 You can run this version of the Software Virtualization Solution Agent on computers using Microsoft Windows Vista SP1 32 bit. Note: 64-bit operating systems are not supported at this time. Support for Microsoft Windows Server 2008 You can run this version of the Software Virtualization Solution Agent on computers using Microsoft Windows Server 2008. Multiple file import in Symantec Software Virtualization Solution Admin (SVS Admin) You can now import multiple .vsa files at the same time into the SVS Admin. Fixes in this Release The following issues were resolved in this release. For additional information regarding a fixed issue click the Article ID link. Article Fix ID On a Windows Vista operating system, if one user logged off and another user logged, the SVS user variables were not loaded and specific sub-folders were not created 39225 for the second user. This has been fixed. The SVSCMD executable can now reference a GUID when exporting a layer. The Symantec SVS applet now supports the SVS runtime mode. 37870 Multiple internationalization problems were fixed. Multiple issues that caused blue screens were fixed. Issues causing user variables to resolve incorrectly the first time a user logs on to a Windows Vista computer were fixed. An issue causing Microsoft's User Profile Hive Cleanup service (UPHClean) to freeze at "Saving your settings ..." was fixed. Blue screen issues on computers running McAfee Antivirus were fixed. Known Issues and Things to Know The following are unresolved issues in this release. For additional information regarding a known issue, click the Article ID link. Known issues specific to Software Virtualization Solution and Microsoft Vista Article Compatibility ID Transactions Software Virtualization Solution 2.1 SP2 does not support applications using transactions 33508 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 34123 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. 34118 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 34119 You must run SVSCMD in a process that uses the Administrator token. Office launches repair 33510 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 35349 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. Article Additional Known Issues ID Layers Created with 2.1 SP2 are not backward compatible with 2.0 34120 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 30877 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 33511 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 20884 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 20863 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 21394 In some instances, a virtualized application has caused wininet.dll to crash. Acrobat Reader 7.x update may not install correctly 21361 Acrobat Reader 8 does not have this problem. Shortcuts not saved in layers 32716 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 34125 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. Things To Know 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. Additional Documentation Product documentation is posted on the Beta portal as a PDF document. The name of the file is softwarevirtualization_2.1_sp2_user_guide.pdf.