Symantec Workspace Virtualization 7.5 and Symantec Workspace Streaming 7.

5 Release Notes

Legal Notice
Copyright 2013 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, the Checkmark Logo and Altiris, and any Altiris or Symantec trademarks used in the product 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. 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. Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com 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 Supports 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. Symantecs 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 Symantecs support offerings, you can visit our website at the following URL: www.symantec.com/business/support/ All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy.

Contacting Technical Support

Customers with a current support agreement may access Technical Support information at the following URL: www.symantec.com/business/support/ 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: www.symantec.com/business/support/

Customer service
Customer service information is available at the following URL: www.symantec.com/business/support/ 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, DVDs, 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 customercare_apac@symantec.com semea@symantec.com supportsolutions@symantec.com

Release Notes
This document includes the following topics:

About Symantec Workspace Virtualization What's new in this release Supported platforms System requirements Installation and upgrade information Known issues Other things to know Fixed issues Installation, User's, and Administrator's Guides Additional information

About Symantec Workspace Virtualization

This document contains release information for the release of following Symantec Workspace Virtualization products:

Symantec Workspace Virtualization Agent build number: 7.5.522 Symantec Virtual Composer build number: 7.5.0.493 Symantec Workspace Streaming Server build number: 7.5.0.493 Symantec Workspace Streaming Agent build number 7.5.0.493

Release Notes What's new in this release

What's new in this release

In the release, the following new features are introduced: Table 1-1 Feature
New installers

List of new features Description

This release includes a simplified install with the ability to easily scale in a large organization. Virtual Composer includes several improvements to the user interface, as well as a better workflow for packaging applications. Composer now includes an automatic exclude finder. Virtual Composer now includes the layer and package editing functionality that was previously available only in SWV Admin. This lets use one packaging utility for most of your packing needs. However; SWV Admin is still available in the release. The LDF tool is now integrated. There are single-click definitions for 40+ apps. You can now add registry exclude entries to your layers. This feature prohibits the registry keys that you specify, from being captured into the layer. This release includes support for Windows 8 Clients. Workspace Virtualization includes performance enhancements in the driver. The APIs provide a more consistent experience. Workspace Streaming includes performance enhancements through client cache provisioning. The new Workspace Streaming installer requires minimal user intervention during the server installation. Now, you do not need to depend on database availability as database configuration is separated from the installer. Once you are done with the server installation, you can proceed with the post-installation configuration without restarting your computer. The new installer does not prompt you to restart your computer after the server installation.

Updated Virtual Composer

Additional Packaging Functionalities

LDF Tool

Registry Excludes

Windows 8 support Virtualization Performance Enhancements Enhanced APIs Client Performance Improvements. New Workspace Streaming installer for quick and easy server installation.

Release Notes What's new in this release

Table 1-1 Feature

List of new features (continued) Description

The new Workspace Streaming Console is user-friendly and has a set of more organized navigation elements. The console provides you a consistent experience with different context-sensitive actions. In the new console the navigation elements are categorized into the following areas:

New and improved user-friendly Workspace Streaming Console for better usability and performance.

Home Monitor Manage Reports Settings

Enhanced Workspace Streaming component management.

Now, you can dynamically manage different Workspace Streaming components by using Streaming Console, command prompt, and through web access to the Streaming Console. Customizing components through the Modify install option in the Workspace Streaming wizard is no longer supported.

Support for a new Workspace Workspace Streaming supports a new silent mode server Streaming installation mode. installation using the command prompt. The silent mode installation is very quick and easy to use. This type of installation is useful in scenarios where you can use a tool or a logon script to complete a silent mode installation on multiple computers during maintenance. Support for a new command The new [setup.cmd] tool lets you configure the Workspace line tool [setup.cmd]. Streaming components during the silent mode server installation. The tool has several options to configure the components. You can execute following command to see all the help options to configure the required components: %systemdrive%\Symantec\Workspace Streaming\Server\installation\bin>setup.cmd -help

Release Notes What's new in this release

Table 1-1 Feature

List of new features (continued) Description

Support for modern browsers. The new Workspace Streaming Console supports following modern browser:

Chrome, IE 8, 9, 10 Works best in Firefox and IE 8, 9 Support for HTML5 CSS3

Support for Multi-Domain AD. Workspace Streaming support for a multiple AD domain within a single forest. Now AD configuration is simplified and you need to provide only the following details:

Root Domain User Principal Name and Password

Improved streaming performance.

Faster streaming performance through the virtual file system improvements in the following ways:

IOPS Reductions Eliminating extra writes for each block by delaying streamed file system creation on the physical disk. Client Cache Provisioning By reducing the number of requests, the client makes to the server for the large chunk of information. It uses two levels of caching through the User/Machine request cache and User package info cache.

Support for new modes of database configuration.

As the database configuration is separated from the Workspace Streaming installer, you can configure the database in following ways:

Interactive mode database configuration using the Streaming Console After installing the Back-End server component, you can configure the database using the Streaming Console. Silent mode database configuration You can configure the database through silent mode using the command prompt. The silent mode database configuration is very quick and easy. It requires minimal user intervention. Remote database configuration After installing the Back-End server component, you can Web access to the Streaming Console and configure the database remotely at any time.

Release Notes What's new in this release

10

Table 1-1 Feature

List of new features (continued) Description

The new database configuration is more flexible as it provides you following options to configure the database:

New database configuration options.

Create a completely new database. Attach an existing production database to the newly installed server. Skip the database configuration and configure it later manually based on your time and available resources.

New central configuration file The name of the new configuration file is Install.cfg file. to keep track of all the This file contains overall information about install or upgrade configuration details. such as server type, port used, install date, upgrade date, build number, upgraded build number, etc. The Install.cfg also provides the database configuration details such as database server IP, port, and instance details. New installation and configuration log file to keep track of all the logs. The name of the new log file is install.log file and the file is generated under the <home> folder. The install.log file logs all the installation and the database configuration information. You can also extract error messages from <home>\install.log file. Other logs can be found under the <home>\installation\logs folder. Enhanced package dependency management. Now, you can create, update or delete package dependencies through the Streaming Console. Dependencies that are defined in the Virtual Composer are imported when the package is uploaded on the Streaming Server. Dependencies can be multi-level so the Workspace Streaming supports following views to manage the package dependencies:

Flat View The Flat View provides a flattened list of the dependencies that will get installed or removed when a package is streamed. This view lets you handle the circular dependencies. Parent View The Parent View provides a list of packages that can be directly depend on a particular package. This package view displays the direct package dependency.

Release Notes What's new in this release

11

Table 1-1 Feature

List of new features (continued) Description

New features to diagnose the While provisioning a user, a new Check Dependencies package dependency issues action is introduced to view a list of dependencies, which are on the server. missing for the user based on its user and group provisions. The helps you to diagnose the package dependency issues on the server. Improved security features. Now, you can get the user groups details from their NTLM credentials; not from the LDAP queries. With the use of new AD security settings, the auto authentication work more effectively. Support for new databases. Workspace Streaming now supports Microsoft SQL Server 2008 R2 and Microsoft SQL Server 2012 database. Workspace Streaming and Virtualization Agents now support Windows 8 and Windows Server 2012 operating system. Now, you can easily reclaim licenses from the client computers. When a Windows user logs off, the client computer sends an empty Client Inventory message to the server. This message instructs the server to remove all the licenses on the server for that particular host. New user identifier is introduced. Provisions are now recorded against SIDs instead of user names. SIDs help you to handle the duplicate user names in different domains. Now, recovery information is not stored in the Temp folder or C:\Program Files folder. The new default location for RecoveryInfo is as follows: C:\_AC\RecoveryInfo Enhanced support for web services. New web services are supported to provide all the core functionality, that is performed through the Streaming Console. This functionality includes the configuration and management of different components, licenses, user identity, packages, provisions, reports, server groups, and version, etc.

Support for new operating systems. New feature for license reclamation.

New default location for recovery info on the Workspace Streaming client computer.

Release Notes Supported platforms

12

Supported platforms
Streaming endpoint operating systems
64-bit editions of the following:

Windows Server 2012 Windows 8 Windows 7 and 7 SP1 Windows Vista SP1 and Windows Vista SP2 Windows Server 2008 R2 when used as an endpoint

32-bit editions of the following operating systems:

Windows 8 Windows 7 and 7 SP1 Windows Vista SP2 Windows XP SP3 is recommended for English language versions and required for non-English language versions of XP Windows XP is supported with the additional components of Windows Installer 3.1: http://support.microsoft.com/kb/893803 and the Filter manager roll up hotfix: http://support.microsoft.com/kb/914882

Virtualization endpoint operating systems

64-bit editions of the following:

Windows Server 2012 Windows 8 Windows 7 and 7 SP1 Windows Vista SP1 and Windows Vista SP2 Windows Server 2008 SP2

32-bit editions of the following:

Windows 8 Windows 7 and 7 SP1 Windows Vista SP2 Windows Server 2008 SP2 Windows Server 2003 SP2

Release Notes System requirements

13

Windows XP SP3 is recommended for English language versions and required for non-English language versions of XP Windows XP is supported with the additional components of Windows Installer 3.1: http://support.microsoft.com/kb/893803 and the Filter manager roll up hotfix: http://support.microsoft.com/kb/914882

Streaming Server operating systems

32-bit and 64-bit editions of the following operating systems:

Windows Server 2008 and 2008 R2 Windows Server 2003 SP2 or later and Windows Server 2003 R2 Windows Server 2012 (64-bit)

Streaming Databases
Streaming supports the following databases:

Microsoft SQL Server 2005 SP4, Microsoft SQL Server 2008 R2 SP1, Microsoft SQL Server 2008 R2 Express, Microsoft SQL 2012 Oracle 10g, 11g, RAC

Virtual Composer
64-bit versions of the following operating systems:

Windows 8 Windows 7 and 7 SP1 Windows Vista SP2 or later

32-bit versions of the following operating systems:

Windows 8 Windows 7 and 7 SP1 Windows Vista SP1 or later Windows XP SP3

System requirements
The following tables contain system requirements for the endpoints, Streaming Server, and Virtual Composer:

Release Notes Installation and upgrade information

14

Table 1-2

Endpoints Requirement
Same as recommended by the operating system and installed applications. Same as recommended by the operating system and installed applications. 50 MB of free disk space plus additional space as required by installed applications.

System component
System Processor

System memory

Free disk space

Table 1-3

Streaming Server Requirement

Minimum 1 GHz of processor capability. 2-GB memory minimum. 2 GB of free disk space, plus three times the space that is required by the applications to be uploaded on to the server.

System component
System Processor System memory Free disk space

Table 1-4

Virtual Composer Requirement

Same as recommended by the operating system. 1-GB memory minimum. Additional as recommended by the applications you want to package. 30 MB of free disk space, plus three times the size of the package.

System component
System Processor System memory

Free disk space

Installation and upgrade information

Streaming, Virtualization, and Composer Installation instructions are included in the User's and Administrator's guides. The following table contains instructions to upgrade to this version:

Release Notes Installation and upgrade information

15

Table 1-5 Product

Upgrade instructions Upgrade instructions

Upgrade instructions for Workspace Streaming are at the following link: http://www.symantec.com/docs/DOC6667

Workspace Streaming

Virtual Composer

There is no upgrade path for Symantec Virtual Composer. First uninstall the previous version and then install the new. Any changes you've made to the installation folder (C:\Program Files\Symantec\Symantec Virtual Composer) should be backed up. This includes changes to the packager.ini file, sample scripts, and default templates. After the new version is installed you can copy these files back to the installation folder.

After you upgrade the server from 6.1 SP8 to 7.5, ensure that you do not reconfigure the Active directory on the server. If you reconfigure the Active directory then the configuration that you have set for the user and the user groups are lost. You can use current version with previous version. Backward compatibility is supported between 7.5 and SP8 (and above versions) where Back-End must be in 7.5 and all the Front-End can be in SP8 and above version. You can run 7.5 agents against SP8 Back-End servers and vice versa. In this case, SP8 client can stream from 7.5 server and 7.5 client can stream from SP8 Front-End servers. If you already added a SP8 DA to your computer and then upgraded to the Back-End server alone to 7.5 then your standalone DA works properly. But, if you try to add a SP8 standalone DA to a Back-End computer, which is running 7.5 version then the DA is not supported. You cannot upgrade SWS client in the terminal server mode. The SWS client upgrade is completed through the silent mode only in the terminal services environment. The SWS agent upgrade fails if you initiate the upgrade process using the Streaming Portal or the setup.exe file. Before upgrading to the Parent STE in a Parent STE-Child STE setup you must follow the below procedure. To upgrade the server when you have added a child STE in your network

1 2 3

Launch the Streaming Console. Remove the associated Child STE from the Parent STE using the Parent STE's console. Upgrade the Parent STE first, and verify that the upgrade is successful.

Release Notes Known issues

16

4 5

Upgrade the Child STE separately that was removed from the Parent STE previously. Verify that the upgrade is successful.. Add the child STE back to the Parent STE using the parent STE's console.

Note: The Parent STE-Child STE backward compatibility works only when both STEs are have the same build version installed.

Known issues
The following are known issues for this release: Table 1-6 Issue
Additional steps are required to package Microsoft Office 2010 in a Windows 8 environment.

Workspace Virtualization Known issues Description

To work around this issue, you must suppress the restart while you are capturing the image. To do this do the following:

Launch the Microsoft Office Customization tool using Setup.exe /admin.

Note: The customization tool is only

available for the volume license editions.

Add SETUP_REBOOT in the Modify Setup Properties page, and then add the value Ifneeded.

On Windows XP endpoints, when you use To avoid this issue, it is best practice to install the Activate on System Startup option, the fonts into the base, and not into the layer. True-type and open type fonts do not display. To work around this issue, you must deactivate and reactivate the layer to make the fonts display properly. You cannot create an upgrade package from The Error code 1009 is displayed when you Office 2007 to Office 2010 attempt to create an upgrade package from Office 2007 to Office 2010. This error occurs because to upgrade from Office 2007 to Office 2010 is not considered best practice. This upgrade path is not supported by Microsoft. Various issues cause the XPF file to not save properly and the upgrade package is not created. To upgrade to Microsoft Office 2010, you must create and stream a completely new package.

Release Notes Known issues

17

Table 1-6 Issue

Workspace Virtualization Known issues (continued) Description

If you flag an Office 2010 layer to deactivate This issue occurs because when the Office on last process exit, the layer deactivates 2010 layer is activated it starts the process after activation. BCSSync.exe. After the BCSSynch process completes it exits. This exit triggers the deactivate on last process exit command. To workaround this issue you must use msconfig to disable BCSSync.exe. You cannot use non-ASCII or Hi ASCII characters in the root path of the fsldr redirect area. For example, You cannot use Japanese characters instead of the root file path: "C:\FSLDR\". The use of non-ASCII characters (including Hi ASCII), numeric digits, or special characters (e.g. any character that cannot be cased are not supported in the root path for the fslrdr redirect area. You must either use the default path "FSLDR", or use ASCII characters. Symantec recommends the length be a minimum of 3 ASCII characters. Most of the predefined LDF's were created on a 32-bit operating system. These LDF's do not function properly when you use them with a 64-bit Symantec Virtual Composer. LDFs that were created on a 32-bit operating system do not function properly when you use them with a 64-bit Symantec Virtual Composer. To workaround, you must use the 32-bit version of Symantec Virtual Composer. You must install AppV in the base when If AppV is in layer format then Office2010 Capturing an Office 2010 upgrade package. Service Pack installation will fail and it is not possible to create Office2010 SP1 upgrade package. To create upgrade package for Office2010 you must install OSPP in the base. You need to install "AppV Deployment Kit for Office2010" in the base and then create the Office2010 SP1 upgrade package. Exclude Entries were not displayed properly This issue occurs with Virtual Composer only in the composer when clicking the tabs in the after clicking the tabs like Files, Registry and layer properties screen. Exclude Entries in the layer properties screen. Compatibility issues with Windows 8. When you migrate an Office 2013 package on Windows 8, Office will run an Office Repair utility when you import and activate the layer.

Release Notes Known issues

18

Table 1-7 Issue

Workspace Streaming Known issues Description

You cannot add a standalone Data Access Component if you upgrade only the Front-End Server. You must first install the Front-End Sever and a standalone Data Access Component together, and then upgrade the Front-End Sever.

Cannot add the standalone Data Access Component after upgrading the upgraded Front-End Server only.

The Additional Details In client AppMgrGUI when you open the Additional Details menu of menu of a package a package, the Package Version value is not displayed separately. does not display the The Package version is appended to the package identifier. Package Version value separately. For Windows 2003 To work around this issue, you must manually install the VC runtime R2 BE server, the FE 9.0.30729.6161 version. and DA components that are installed do not upgrade. For an external Only the IP-based rules work for an external package repository. package repository, the user-based rule and the group-based rules do not work. In the Streaming Console > Settings > System Settings > DB Configuration page, changing the password doesn't reflect in DA machine's da.conf file. Non admin user cannot install Streaming Agent using MSI file. To work around this issue, you must manually change the password by copying the password from the STE's da.conf file to the da.conf file in all DA machine's or remove DA component(s) and add it again.

To work around this issue you run the install as an administrator.

Release Notes Known issues

19

Table 1-7 Issue

Workspace Streaming Known issues (continued) Description

The package upload To work around this issue, use different package name or supporting will fail when package OS of the package should be different. with the same name is already in server. The message to The message to download jnlp client file is displayed every time when download jnlp file is you click on the Manage > Add package option in the Streaming displayed when you Console that is configured with SSL. click on the add package option from the SWS console that is configured with SSL . SWS console does not restrict the packages, which are created using SWV admin from upload process. You must not upload XPF packages created under SWV Admin tool to SWS streaming server as the packages created from SWV Admin tool is not streaming compatible.

Error on launching Streaming no more supports all of the old package types so Microsoft Legacy recommendation is not to use old package type. Snapshot packages, when office is removed with project/visio in cache. Pre-pop icons are not To workaround this issue, pin the application icon to start screen displayed in the new from the All Application page. tiled start screen in Windows 8. When connecting to Currently, this issue is under investigation and there is no workaround the Streaming Portal for now. from a Windows 8 computer, you cannot install the streaming agent when using Internet Explore in Metro Apps.

Release Notes Known issues

20

Table 1-7 Issue

Workspace Streaming Known issues (continued) Description

When you are installing the Workspace Streaming, if you use the DBCS or HI-ASCII characters in the Host name, the Streaming Console fails to open and displays an error message. To work around this issue, you must not use DBCS or HI-ASCII characters in the Host name for the Streaming Server.

The Workspace Streaming installation fails in scenarios where the Host name contains Non-ASCII characters. In scenarios where an external repository is configured and the Front End component is set to use the shared repository then once the component is removed from the server, the component services settings are also removed. While using Japanese OS, the DBCS characters in the Host name are corrupted after opening the Streaming Console in Internet Explorer.

The Front End and Data Access components services are dynamically added or removed depending on whether the component is added or removed from the Back End server. Once the component is removed from the server, the service is de-registered and the settings are not retained for future uses. To work around this issue, every time a component is removed and added again to the server, you must manually reconfigure all the changes that are made to the removed Portal or STS services.

If you are using Japanese OS and used DBCS or HI-ASCII characters in the Host name then the characters are corrupted while you open the Streaming Console in Internet Explorer. To work around this issue, you must not use DBCS or HI-ASCII characters in the Host name for the Streaming Server.

You must turn off To workaround, turn off the Training option for the packages, which training for packages are over 2 GB to avoid constantly increasing memory use while over 2 GB streaming the package. In the Streaming Console, you can do this while configuring the package version settings. In the Package Version settings page, deselect the Training check box under the Options section of the page. Training option is used to describe the process that determines the data that should be initially streamed to an endpoint.

Release Notes Known issues

21

Table 1-7 Issue

Workspace Streaming Known issues (continued) Description

If you use the DBCS or HI-ASCII characters in the host name to install the Workspace Streaming, the Streaming Console fails to open and displays an error message. To work around this issue, you must not use DBCS or HI-ASCII characters in the host name for the streaming server.

When you install the Workspace Streaming server in Hi-ASCII location, an error is displayed after you configure the User Data Source using the Active Directory. While using Japanese OS, an error is displayed after you install the Workspace Streaming server in DBCS location and the Streaming Console fails to open. Package corruption warning for non-provisioned applications in the Streaming Console home page. If you attempt to find a very large amount of users (10,000) from an Active Directory query, you may receive an error message. The error informs you that you need to configure ActiveDirectory settings to allow you to fetch so many users.

If you use the DBCS or HI-ASCII characters in the Host name, the Streaming Console fails to open and displays an error message. To work around this issue, you must not use DBCS or HI-ASCII characters in the Host name for the Streaming Server.

If you log in into the Streaming Console as a package admin, the Streaming Console home page displays a warning about package corruption for all the non-provisioned applications.

If you attempt to find a very large amount of users (10,000) from an Active Directory query, you may receive an error message. The error informs you that you need to configure ActiveDirectory settings to allow you to fetch so many users.

Release Notes Other things to know

22

Table 1-7 Issue

Workspace Streaming Known issues (continued) Description

When the Browser When the Browser Selector Manager is set up to accept a remote Selector Manager is configuration file, you must use Access Control to secure access to set up to accept a the remote configuration file's location. remote configuration file, you must use Access Control to secure access to the remote configuration file's location. If you want to upload a package with same name which is already uploaded then OS list should be different else package upload will fail. If you have package with same name/ but a different GUID then you should not be changing the supported Available on OS option in the server, it will cause various problems. If you want to upload a package with same name which is already uploaded then OS list should be different else package upload will fail. If you have package with same name/ but a different GUID then you should not be changing the supported Available on OS option in the server, it will cause various problems.

You cannot cancel If you click the cancel button when exporting a package, the package the export process of is exported anyway. a package from the Manage > Packages page.

Other things to know

The following are things to know about Symantec Workspace Virtualization Release Preview release:

Release Notes Other things to know

23

Table 1-8

Other things to know

Thing to know Description

A downgrade is not a supported configuration. Old package types are no longer supported. The layers get updated and cannot be used on old drivers, and the settings get updated and are invalid on old versions.

Old package types are no longer supported.

Internet Explorer Internet Explorer packages that were created for Windows 7 do not run packages that on Windows 8. were created for Windows 7 do not run on Windows 8. PostgreSQL is PostgreSQL is no longer supported as a database therefore upgrading no longer a server which has PostgreSQL as a database is also not supported. supported as a database option. You must create Internet Explorer 6 packages on a Windows XP Base computer. You must create Internet Explorer 6 packages on a Windows XP Base computer. Microsoft has removed some of the packages required to build IE6. You must build the layer on Windows XP. For more information see the following: http://www.symantec.com/connect/downloads/internet-explorer-6-windows-XP-layer-definition-file http://www.symantec.com/connect/endpoint-virtualization/downloads Location to store Locations to store an ojdbc6.jar file are as follows: an Oracle While installing a single node with a Back End and Front End server ojdbc6.jar file components or with only a Back End component then you must store while connecting the ojdbc6.jar file in the following places: to an oracle <home>\Agent\lib database. <home>\common\apache-tomcat\shared\lib

<home>\common\jboss\server\appstream\deploy\ste\ste.jar\

While installing a single node with a Front End or Data Access server components or with both Front End and Data Access server components, you must store the ojdbc6.jar file in the following places: <home>\Agent\lib

<home>\common\apache-tomcat\shared\lib

Release Notes Other things to know

24

Table 1-8

Other things to know (continued)

Thing to know Description

You must run VCCmd needs to read and write to the disk. It needs the proper privileges Composer's to run. In 6.1 SP8 composer, VCCMD.exe displays the commands in the VCCMD.exe as user privileged command prompt. an administrator. In this release, if you want to read the commands you need to run as an administrator user. Symantec Symantec recommends that you use the Single Program Capture option Recommends to instead of the Global Capture options when you capture Microsoft Office capture Microsoft products into a layer. Office products by using the Single Program Capture option. When configuring the Workspace Virtualization BSO, if you choose to use a remote XML file location, Symantec recommends that you use https to connect to it. When configuring the Workspace Virtualization BSO, if you choose to use a remote XML file location, Symantec recommends that you use https to connect to it.

In Virtual You must provide the previous version's package in order to recompile Composer, when a package to a higher version. you attempt to recompile a package into a higher version, you must provide the previous version of the package.

Release Notes Fixed issues

25

Table 1-8

Other things to know (continued)

Thing to know Description

Other directory Other LDAP directory services like OpenLDAP and Novell eDirectory are services are no no more supported for the User Data Source configuration. longer supported for the User Data Source configuration Applications are If you want to terminate a running session, you must use the Terminate not terminated User option given on the Monitor > Active Users page of the Streaming on stopping the Console. FE server components.

Fixed issues
The following are issues that were fixed in this release

Workspace Virtualization fixed issues

The following Workspace Virtualization issues are fixed in this release: Table 1-9 Workspace Virtualization fixed issues Article ID
NA

Abstract of the Fixed Issue

SWV path expansion breaks windows firewall

When SVS is checking registry permissions, it is not doing it in priority NA order, it checks the base first. Items under Run key executed as user who activates layer NA

Environment variables in base take priority even when process run from NA layer. Lookup option causes winword.exe to consume 50% CPU on a dual core processor and 90% + in single processor System performance slow with 64-bit Trend Micro SWV does not properly handle the presence of bogus user profiles. This causes performance problems NA

NA NA

Release Notes Fixed issues

26

Table 1-9

Workspace Virtualization fixed issues (continued) Article ID

NA

Abstract of the Fixed Issue

When layer active, SEP client communication to server causes WmiPrvSE.exe to peg CPU on Windows 7

QuickBooks Enterprise 10: cannot capture via global nor single program NA capture Uninstalling and reinstalling SWV with different accounts loses the metadata information. If process icon pinned to task bar was launched from an advertised shortcut, the pinned shortcut points directly to redirect area. NA

NA

If process or shortcut in layer is "pinned" to taskbar, the taskbar remains NA after deactivating layer Research Machines: A CC4 RM component fails to assign (install) when NA an Open office layer is active. Google Chrome XPF does not work when imported in Win7 64bit OS. NA OSPP.VBS /dstatus will only return license status on machine Office 2010 was captured. returns error on all others The machine freezes when deactivating a layer or when importing a layer, and it has to be forcefully powered off in order to use it again NA

NA

SWV_6_1_SP6_MP1_HF1 + Citrix PS 4.5 + Windows Server 2003 R2 NA TS causes BSOD SWV is making Microsoft Webmatrix unstable. Usually causing the application to hang within a minute NA

Upgrading to SP6.x causes our Java based Expense Reporting product NA to freeze when trying to synch with its server. 32-bit registry key App Paths getting deleted on x64 system when layer NA set to activate on system startup. Black Screen-Instability If only the RW sublayer conflicts with a layer on the machine. Layers get out of sync on import. Explorer Hangs in the middle of activating bunch of layers at once on DEV Build (6.4.1286) NA NA

NA

Release Notes Fixed issues

27

Table 1-9

Workspace Virtualization fixed issues (continued) Article ID

NA

Abstract of the Fixed Issue

Upgrading to SWV 6.4.1266 causes the video driver to revert back to 800 x 600 instead of maintaining its configured screen resolution.

The exec command (to run an external process from the layer) doesn't NA seem to work properly in SP7. When using ExcludeAllProfiles copy the user specific area to the base NA for proper functioning of the application. TestRegCreateKey0022 fails when running from a layer or in capture mode. This test is trying to create a registry link. Latent Zero Minerva application performance issues NA

NA

DWORD values in SVS Admin are limited to a maximum value of NA 7FFFFFFF(Dec:2147483647) instead of FFFFFFFF(Dec:4294967295). Larger values are reduced to 7FFFFFFF. The same issue still occurs with SWV 6.1 SP7. Instructions to obtain license for personal use need to be updated on installer dialog. Fonts not registering when streaming application VS 2010 projects pop up exceptions when MS Office / Project 2010 layers are deactivated. NA

NA NA

Error : Font '?' cannot be found while trying to open SQL Server MGMT NA Studio OnPostActivate fails to find "wscript.exe" when the full path is not specified; this is different from the behavior in 2.1.3078. NA

Users have to open outlook twice to detect the Enterprise Vault plug-in. NA System handle count creep whilst using layered applications NA

SWV_6_1_SP7_MP1_HF1_6.4.1354 + VMWare vSphere 5.0 Windows NA 7 x86 Enterprise SP1 VM + VMWare Host Profiles = BSOD at boot Path Settings Captured During Layering Result in Corrupt Path Entries NA VzNotifications don't properly work when event is triggered via WMI NA

DLL errors while trying to virtualize Apple Bonjour Service(customized NA MSI)

Release Notes Fixed issues

28

Table 1-9

Workspace Virtualization fixed issues (continued) Article ID

NA

Abstract of the Fixed Issue

Issue when upgrading Acrobat Reader patches

Fonts do not appear in the Fonts folder until a log-off/log-on is performed NA when fonts are streamed IE Zone group policies and digital certificates stored under IE8 32-bit NA on a Windows 7 x64 machine are lost when shared registry keys are modified on the base and layer contains those shared registry keys as well Install and WDE shows 25% CPU usage on pgptray.exe. If they open NA pgpdesk.exe it also utilizes 25% Adding additional toolbar icons to Adobe Reader 10.x layer are not retained when the application is closed and then reopened. NA

USER_TEMPLATE file objects are not showing after layer is activated NA on system startup for the user that added the objects during capture mode. New Reset Point Does not work NA

SWV "SVSCMD SENDINVENTORY" command fails to run with error NA "Registry operation on layer information failed. This is caused by missing or in correct registry keys or values. Error: 1040 SVSCMD failed: SENDINVENTORY" Com+ addin for MSword 2003 is being captured outside the layer even NA in Global capture. Registry modifications done via "Run application from layer" affects the NA base registry and are not isolated. SWV uninstall does not remove fslrdr folder Isolation rules are not applied to keys/values in the RW sublayer Creating a key blocked by isolation rules thinks key already exists NA NA NA

Restarting machine with WsApps component installed/configured shut NA down the machine Workspace Virtualization Admin shows strange characters in GUI with NA German locale settings. Click on Start - All programs it takes about 4 seconds to open. It happens only for the first time. NA

Release Notes Fixed issues

29

Table 1-9

Workspace Virtualization fixed issues (continued) Article ID

Abstract of the Fixed Issue

RO & RW folders of streamed packages under C:\flsrdr\1 or \2 are still NA persists even after the same package was mounted & stored under c:\fslrdr\Xaaa-1111\RW or RO folders. Problem with the streamed Adobe Acrobat Pro 10.1.4 software NA (Impacting the system functionality - causes system fonts to disappear). Deactivating the app fixes the problem temporarily Values larger than ~8K are not copied from the USER_TEMPLATE area. NA

Windows 8 Assessment and Deployment Kit fails to install on a machine NA running SWV. Registry conflict between OS and Layer causes CREDANT not to work NA properly PPT table column input action has a delay of around 5-6 seconds before NA data is displayed when Office 2010 is in a layer Issues with streaming applications reorganizing USB devices Issue with security permissions on users profiles when we use the USER_TEMPLATE Machine does not reboot properly when layer are set to "Activate On System Startup" Layer Properties: Import process is not working with Layer registry settings NA NA

NA

NA

BSOD on XP SP2 when user opens a file stream with write permissions NA and layer is active Driver: Laptops randomly crash with BSOD BSOD: Stop error: IRQL_NOT_LESS_OR_EQUAL on Windows 8 Enterprise x64 after installing NA NA

BSOD on XP SP2 when user opens a file stream with write permissions NA and layer is active SWV - local kernel mode privilege escalation exploit. NA

Symantec Virtual Composer fixed issues

The following Symantec Virtual Composer issues are fixed in this release:

Release Notes Fixed issues

30

Abstract of the Fixed Issue

Composer doesn't detect one of the application's icons

Article ID
NA

Quicktime package is installing a new c++ runtime and a policy to force NA all application to load the newer version. This is breaking SEP File Type Associations not working for a virtualized app when app set NA to pre-cache Icons + File Associations Wise Virtual Composer not keeping updated vendor version number after compiling UPGRADE packages of all Mozilla products from previous versions to 10.0 and above Composer takes over 10 to 15 minutes to load. NA

NA

Is it a normal behavior that first we need to compile a package before NA beginning to create package streamlets? Layer Creation Tool: IE6 or IE7 for Windows 7 does not create working NA IE layer creating upgrade package from only .xpf file is stripping out all the pre NA and post scripts from the package When clicking Second shortcut link in a streamed package shows the NA menu instead of opening the shortcut, when trying through SWS portal Expandable String and QWORD value is missing while trying to add "Registry Value" using the composer. NA

Workspace Streaming fixed issues

The following Workspace Streaming issues are fixed in this release: Table 1-10 Workspace Streaming fixed issues Article ID
NA NA NA

Abstract of the Fixed Issue

Cannot get roles per group GetPackageUsageReport gives an "os Cannot be Null!!" exception "Bad Inputs" error is returned when retrieving reports (getLicenseUsedReportByName & getUsageDataReportByName) information "No package to process" error is returned when retrieving reports (getPackageUsageReport) information

NA

Release Notes Fixed issues

31

Table 1-10

Workspace Streaming fixed issues (continued) Article ID

NA

Abstract of the Fixed Issue

Installation there is an option to install launch server and streaming server separately Portal button when clicked displays two launch server links when fail over is configured. Installing DA through installer (install Streaming server) removes the existing STS & LS services if previously installed. ConsoleConfig.xml is rewritten when STE is restarted.

NA

NA

NA

Offline package report from streaming agent takes long time to open NA LDAP connection, because for each session in the report we are doing a full LDAP user lookup License descriptor saving "Maximum Concurrent Licenses:" changes without clicking "Save". On component details page the memory always shows 0 for some STSs. On console CPU usage and other machine details are not correct Support LDAP connectivity in multiple forests environment. Warning message pops up, blocking navigation from advance tab to external address tab in server group configuration page NA

NA

NA NA NA

Server installer should detect the exact existing build and present a NA message on the GUI if upgrade is compatible from version x to version y. Warning message in User Data Source configuration wizard, if the server is not in that same domain. NA

The client upgrade process adds an icon to the sys-tray with a tool tip NA of "-100%" [DependentProducts] and [ProductName] are missing in the client upgrade log file. Create DB schema not checking if enforce password requirements is enabled on DB. Add the white listing and blacklisting parameters to the config file. NA

NA

NA

Release Notes Fixed issues

32

Table 1-10

Workspace Streaming fixed issues (continued) Article ID

Abstract of the Fixed Issue

Grammar on db connectivity error page - change "may not be exist" to NA "may exist" Add toggle for default upload option for caching type NA

CPU Spikes to 100% when opening AD related items in a Management NA Console Server uninstall does not allow uninstall of a single component when custom install was used. NA

Domain users and groups are not showing up when using root DN as NA search base and LDAP Connectivity is set to AUTO Available package view "All" filter does not show "All". It shows pagination w/100 entries per page. Show group provision info when viewing user provisions. NA

NA

Removing user from user group is only functioning if you remove from NA individual user properties. Inactive Agents Search lists all the agents data when DaysOfInactivity=0. This needs to be changed. Display a message something like 0 will display all the agents that streamed. Sort By function is not working for Application Usage Report. Incorrect message is displayed after server group->external address is applied and updated in an multinode + LB environment Backend fail-over issues NA

NA NA

NA

Add an option to expire a package and remove it from client immediately NA Browsing is cancelled and application is not launched using IE9. Launch NA Server is SSL enabled. BSOD on the machine where SWS & Hibun AE encryption software is NA installed. FEs are down after applying the MS patches on Server. NA

Appstreamservice.exe client error: connection could not be established NA x64 clientversion.txt file is ignored in favor of x86 one on an x64 platform NA

Release Notes Fixed issues

33

Table 1-10

Workspace Streaming fixed issues (continued) Article ID

NA

Abstract of the Fixed Issue

Error "Failed to get user <Username> when trying to look up for user with Swedish characters". LDAP and performance issues with streaming console

NA

Component details not populated when server is left running for around NA 2 weeks or more Application Launch Performance SWS Vs SWV Standalone NA

LDAP + SSL does not fetch multi domain users when LDAPs configured NA with GC Streamed applications will run if sync proc request times out Add java version to dci/agent logs upon service restart. Provide more accurate info about STE status on console page/ logs Can't add the STE to the console with the fully qualified name b/c of characters space limitation Feature request: option to disable the SEV agent from prompting the user to upgrade to latest version. NA NA NA NA

NA

Attachmate Reflection Workspace crashes after upgrade from v1 to v2. NA Requires layer reset to make the application stop crashing. LDAP Timeouts - DA losing connectivity to LDAP servers. NA

Console shows wrong info about the NAS space availability. Since, NA Customer was unable to upload package more than the specified space in Console. db.PSexception 33 database error in STS log New Server Installer: New installer does not allow for a single node install in attended mode Pre-cached Icons not working. When user data source = local SQL (PG/MS SQL)check box is in unchecked state for the provisioned packages in user provision page if the user name has "@" in it NA NA

NA NA

After SP8 Upgrades, Some Apps Won't Stream Unless Run from Portal NA First

Release Notes Fixed issues

34

Table 1-10

Workspace Streaming fixed issues (continued) Article ID

NA

Abstract of the Fixed Issue

Recurring client errors in logs ("created outside the AppStream file system" and "oli checksum") Can't login to console with network ID FE in Amber state and STE showing database and null pointer exceptions Need to remove OpenSSL.exe from the server install.

NA NA

NA

Two distiller process running in task manager while streaming acrobat NA 10, Getting an error "another instance of distiller is starting up; this instance can not continue" SEP 12.1 RU1 MP1 Fail to install on Win7 32 and 64 bit VM, install rolls back. SEP Dev traced to SEV drivers DA Name Field on Create DA Component Screen Truncates at 32 Characters After FE server installation, the SWS Launch & Streaming server services are not started automatically. NA

NA

NA

Installation: Just tried to install the 7.5 FE setup on the machine where NA same version is already installed; installer shows a upgrade notification & installs successfully instead of warning message that the same version is already installed. NEWCONSOLE-Unable to change the component description from SWS Console. Single Node server console shows exception errors very often. NA

NA

Server Console shows Exception error after adding the FE component NA & also, Streaming Server Services is not listed. "Authentication failure 8003" warnings were flooded in the launch server NA logs Unable to provision any package to a AD user. Receiving an error message " Failed to get user" NA

All pre-populated apps after client installation show as 0% cached and NA can't be launched Ambiguity in "To set up the user data source for the back-end server" NA

Release Notes Fixed issues

35

Table 1-10

Workspace Streaming fixed issues (continued) Article ID

Abstract of the Fixed Issue

2 Packages with same name but different GUID are allowed to be NA upload using web client but display as single entry on console and has 2 DB entries appmgr service crashes Intermittently and appstream dump files are creating on each crash. Basingstoke Packaging Server - Console Slowness NA

NA

Console: Results not shown when User Data Source Connectivity test NA is success. When selecting portal from Agent GUI both FQDN and short name of streaming server is shown NA

CONSOLE: The Management console administration account is not NA accepting a certain password even though its with valid characters and symbols. When my end user create an application package for some new NA software and stream it down to clients, some ini file with in the package gets corrupted. After restarting the client machine, it throws an Authentication error 10057 when we try to launch the streamed application. NA

Change the time zone in DB as a UTC time rather than localized time NA zone Users intermittently encounter Error Code 10037 when launching applications from the streaming portal. NA

When domain membership changes, LDAP should not be marked down NA instead should report NoSuchObject and continue its routine Adding FE to Server Group without External Address set creates incomplete Component in DB Missing Package version from the streaming agent Searching for local groups only using local or local\ in front of group name SWS Console supports one Active Directory user source Issue with Clear Route application and streaming agent NA

NA NA

NA NA

Release Notes Installation, User's, and Administrator's Guides

36

Installation, User's, and Administrator's Guides

Table 1-11 Document
Symantec Workspace Virtualization 7.5 User's Guide Symantec Workspace Streaming 7.5 Installation and Implementation Guide Symantec Workspace Streaming 7.5 Administration Guide

Product documentation Location

http://www.symantec.com/docs/DOC6666

http://www.symantec.com/docs/DOC6667

http://www.symantec.com/docs/DOC6548

Additional information
The following sections contain additional information about this release:

Workspace Streaming SDK

Symantec Workspace Streaming SDK is made up of several web services that are accessed using Simple Object Access Protocol (SOAP). The interface is exposed through a web services description language (WSDL) document. The WSDL document provides details on the published methods and objects. Most programming languages provide support for SOAP web services including C#, Visual Basic, C++, Java, Python, and others. Most languages provide the ability to automatically generate proxy classes using the WSDL document.

Third Party Legal Notices

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 Licensed Software does not alter any rights or obligations you may have under those open source or free software licenses. For more information on the Third Party Programs, please see the Third Party Notice document for this Symantec product that may be available at http://www.symantec.com/about/profile/policies/eulas/, the Third Party Legal Notice Appendix that may be included with this Documentation and/or Third Party Legal Notice readme File that may accompany this Symantec product.