Symantec Workspace Virtualization 7.5 SP1 and Symantec Workspace Streaming 7.5 SP1 Release Notes

(1)

Symantec™ Workspace

Virtualization 7.5 SP1 and

Symantec™ Workspace

Streaming 7.5 SP1 Release

Notes

(2)

Symantec™ Workspace Virtualization 7.5 SP1 and

Symantec™ Workspace Streaming 7.5 SP1 Release

Notes

Legal Notice

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

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

(3)

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

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

(4)

■ 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

(5)

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:

[email protected] Asia-Pacific and Japan

[email protected] Europe, Middle-East, and Africa

[email protected] North America and Latin America

(6)

Workspace Virtualization

and Workspace Streaming

Release Notes

This document includes the following topics:

■ About Workspace Virtualization and Workspace Streaming

■ 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 Workspace Virtualization and Workspace

Streaming

This document contains release information of the following Workspace Virtualization and Workspace Streaming products:

(7)

■ Symantec™ Workspace Virtualization build number: 7.5.0.749

■ Symantec™ Virtual Composer build number: 7.5.0.749

■ Symantec™ Workspace Streaming Server build number: 7.5.0.749

What's new in this release

In this release, the following new features are introduced:

Table 1-1 List of new features of Workspace Streaming and Workspace Virtualization

Description Feature

Now, a new Refresh button is added in the main toolbar of Virtual Composer.

The Refresh button in the Templates tab and the Refresh option in the right-click menu in the Templates tab are removed.

New Refresh button in Symantec Virtual Composer to remove inconsistency in refresh feature.

Now, Symantec Virtual Composer home page consists only the following frequently used links:

■ Create a new Package using a Simple Wizard

■ Create a new Package using advanced Wizard

■ Edit a Package (XPF) and re-compile

■ Create an Upgrade Package from an existing Package

Simplified Symantec Virtual Composer home page.

In the Layer Properties page, now the Delete entries tab is renamed to Hidden entries tab.

Similarly, in the Layer menu, the modified options as follows:

■ The Not Seen By Other Layers option is renamed to

Hide From Other Layers option.

■ The Cannot See Other Layouts option is renamed to

Hide Other Layers From This Layer option.

■ The Not Seen By Operating System option is renamed to Hide From Operating System option.

Modified tab name and menu options in the Layer

Properties page and the Layer menu options of

Symantec Virtual Composer.

Driver load order and Filter group for FSLX.SYS and Appstream.SYSare modified for better interoperability with other filter drivers.

Modified SWV driver load order.

7 Workspace Virtualization and Workspace Streaming Release Notes

(8)

Table 1-1 List of new features of Workspace Streaming and Workspace Virtualization (continued)

Description Feature

Now, Streaming Server uses a special key code called ‘Access Key’ to securely communicate between all the components. You can set-up or modify the Access Key for each component.

Secured communication between components through Access Key.

Now, the tab layout is improved to display the tab names properly.

Improved Symantec Virtual Composer tabs.

Now, the Packaging Details page is modified to include the information displayed in the Streaming Details page. This includes the streaming server information such as vendor name, vendor version, and comments, etc.

Modified Packaging Details page in Symantec Virtual Composer.

A new feature has added to stream virtualized applications directly from a network file share with VHD support. This is an additional feature for existing users who has configured the Streaming Server and wanted to try application streaming from a network file share.

Ability to stream virtualized application from network file share with VHD support.

In the Streaming Console, the User Data Source page is modified to simplify the Active Directory configuration. In the new page, you can find all the configuration on a single page. You do not need to navigate to different tabs to perform the configuration.

Simplified User Data Source (UDS) configuration.

(9)

Description Feature

The new Workspace Streaming Console has a set of user-friendly toolbar icons to provide navigation shortcuts for frequently used pages of the console.

In the Streaming Console, the toolbar icons are available for the following items:

■ Packages ■ User Provision ■ Group Provisions ■ Active Users ■ Server Groups ■ Repository Locations ■ Console Settings ■ Collect Logs ■ Auto Refresh

You can enable or disable the refresh option through the

Auto Refresh icon. By default, the refresh frequency

value is set to 30 seconds. The refresh frequency is configurable and can be changed from Settings > System

Settings > Network Settings page.

In the Streaming Console, the Auto Refresh icon is available only on the following pages:

■ Component Status page

■ Available Packages page

■ Manage License page

■ Front End Servers page

■ Active Users page

■ Logs Monitoring page

You can enable all the toolbar icons by selecting the Console

Tool Bar option on the Settings > System Settings > Network settings page.

New toolbar icons in the

Streaming Console for

better usability and performance.

In the Streaming Console, a new pagination feature is added on the Settings > General Settings > Repository

Information > Repository Location page to specify the

number of packages, which you want to see on a single page. This feature also helps you to jump to different pages through the First, Previous, Next, and Last buttons.

New pagination feature is added in SWS Repository

Location page.

(10)

Description Feature

While configuring a new Workspace Streaming database, a new alert has been added, which will prompt you to confirm whether you want to overwrite your existing AppStream database.

A new alert box is added in the Database Configuration page.

Virtual Composer now supports Microsoft Windows 8.1 64 bit and 32 bit operating systems.

New operating systems support for Virtual Composer

Symantec Workspace Streaming and Symantec Workspace Virtualization agents now support Microsoft Windows 8.1 and Windows Server 2012 R2 operating system.

New operating systems support for SWS and SWV Agents.

Streaming Server now supports Microsoft Windows Server 2012 R2 operating system.

New operating systems support for Streaming Server.

In the Streaming Console, now you can generate different reports in the HTML graphical report format.

Support for new HTML graphical report format.

On the new Launch Page Settings page, the OS type for

Win8 is changed to Win8.x. Now, the packages, which are

created in Win8 will work in both Win8 and Win 8.1 operating systems.

Enhanced Launch Page

Settings page to support

Win8.x operating systems.

Supported platforms

Streaming endpoint operating systems

64-bit editions of the following:

■ Windows Server 2012 R2

■ Windows 8.1

■ Windows 8

■ Windows 7 and 7 SP1

■ Windows Vista SP1 and Windows Vista SP2

■ Windows Server 2008 R2 SP1 when used as an endpoint

32-bit editions of the following operating systems:

■ Windows 8.1

■ Windows 8

(11)

■ 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/893803and the Filter manager roll up hotfix:

http://support.microsoft.com/kb/914882

Virtualization endpoint operating systems

■ Windows 8.1

■ Windows 8

■ Windows Vista SP1 and Windows Vista SP2

■ Windows Server 2008 SP2 32-bit editions of the following:

■ Windows 8.1 ■ Windows 8 ■ Windows 7 and 7 SP1 ■ Windows Vista SP2 ■ Windows Server 2008 SP2 ■ Windows Server 2003 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/893803and the Filter manager roll up hotfix:

http://support.microsoft.com/kb/914882

Streaming Server operating systems

■ Windows Server 2008 SP2 and 2008 R2 SP1 32-bit editions of the following:

(12)

■ Windows Server 2008 SP2

■ Windows Server 2003 SP2 or later

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.1

■ Windows 8

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

32-bit versions of the following operating systems:

■ Windows 8.1

■ 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:

Table 1-2 Endpoints

Requirement System component

Same as recommended by the operating system and installed applications.

System Processor

Same as recommended by the operating system and installed applications.

System memory

(13)

Table 1-2 Endpoints (continued) Requirement System component

50 MB of free disk space plus additional space as required by installed applications.

Free disk space

Table 1-3 Streaming Server Requirement System component

Minimum 1 GHz of processor capability. System Processor

2-GB memory minimum. System memory

2 GB of free disk space, plus three times the space that is required by the applications to be uploaded on to the server. Free disk space

Table 1-4 Virtual Composer Requirement System component

Same as recommended by the operating system. System Processor

1-GB memory minimum. Additional as recommended by the applications you want to package.

System memory

30 MB of free disk space, plus three times the size of the package.

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: Table 1-5 Upgrade instructions

Upgrade instructions Product

Upgrade instructions for Workspace Streaming are at the following link:

http://www.symantec.com/docs/HOWTO95653 http://www.symantec.com/docs/DOC7391 Workspace Streaming

(14)

Table 1-5 Upgrade instructions (continued) Upgrade instructions Product

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.

Virtual Composer

Symantec Workspace Streaming installer supports upgrade from Symantec Workspace Streaming server or client 7.5 or above version to 7.5 SP1. In this process, the installer updates all the files except the configuration files or customized files. You can also upgrade database in case any change in the database schema. Due to upgraded Jboss version, STE service running in named account must be set again after the server upgrade.

If you are using 6.x version then you cannot directly upgrade to 7.5 SP1 version. In these scenarios, you must first upgrade your environment to 7.5.0.493 version, and then upgrade to 7.5 SP1 version. Backward compatibility between 7.5 SP1 Parent STE and 7.5 Child STE is not supported. So, both the STEs must be in 7.5 SP1 version for communication to work. Backward compatibilities for FE components are supported between versions 7.5x and 6.x.

Backward compatibility for STE and DA is supported only between 7.5x version. In case of upgrading from Symantec Workspace Streaming 6.1 SP8 MP2, you must configure the User Data Source to take advantage of the latest Active Directory features. If you are performing this upgrade operation on a Windows 2003 R2 Enterprise Edition, you must copy the disk1 folder on your local computer and then start with the upgrade operation. Before proceeding with the upgrade, ensure that you have a taken a backup of all the configuration files. To take the backup, you must copy the entire folder from%systemdrive%\symantec\workspace streaming \serverto some other location.

Note:If you have stored all the packages on your local computer then you can ignore all the .xpa files and copy the remaining files. In this way, you can reduce a large amount of data, which need to be copied.

After you upgrade the Streamlet Engine (STE) from 6.x to 7.5 SP1, ensure that you do not reconfigure the user data source. If you want to reconfigure the user data source then you must first take a backup of theprovision.xmlfile, and then

(15)

reconfigure your UDS so that you can take advantage of the latest Active Directory features such as multi domain, cyclic group, nested group provisions, auto discovery etc.

If you want to reconfigure to ADSI and keep your provisions as it was, you can go for Case 2. Case 1 is for SID based provision.

Case 1: LoginRepositoryType=AD, LdapProvisionType=SID AdRootDomain =SAMPLE.COM

■ This is the default configuration for either newly installed SWS 7.5 SP1 or reconfiguring UDS after upgrade to SWS 7.5 SP1.

■ New AD features and functionalities are supported

■ In an upgraded server, reconfiguring UDS will lost existing provisions because new provisions are based on SID instead of NAME.

Case 2: LoginRepositoryType=AD, LdapProvisionType=NAME AdRootDomain=SAMPLE.COM

■ This is the default configuration for either newly installed SWS 7.5 SP1 or

reconfiguring UDS after upgrade to SWS 7.5 SP1.

■ New AD features and functionalities are supported.

■ In an upgraded server, reconfiguring UDS will not lost existing provisions as in theprovision.xmlfile, now the value of the LdapProvisionType is used as

NAME; not SID.

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 thesetup.exefile.

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

Launch the Streaming Console.

2

Remove the associated Child STE from the Parent STE using the Parent STE's console.

3

Upgrade the Parent STE first, and verify that the upgrade is successful.

4

Upgrade the Child STE separately that was removed from the Parent STE previously. Verify that the upgrade is successful..

5

Add the child STE back to the Parent STE using the parent STE's console.

(16)

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 Workspace Virtualization Known issues

Description Issue

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. Additional steps are required to package

Microsoft Office 2010 in a Windows 8 environment.

To avoid this issue, it is best practice to install the fonts into the base, and not into the layer. To work around this issue, you must deactivate and reactivate the layer to make the fonts display properly.

On Windows XP endpoints, when you use the Activate on System Startup option, True-type and open type fonts do not display.

The Error code 1009 is displayed when you 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.

You cannot create an upgrade package from Office 2007 to Office 2010

(17)

Table 1-6 Workspace Virtualization Known issues (continued) Description

Issue

This issue occurs because when the Office 2010 layer is activated it starts the process 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.

If you flag an Office 2010 layer to deactivate on last process exit, the layer deactivates after activation.

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. 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\".

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. 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.

If AppV is in layer format then Office2010 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. You must install AppV in the base when

Capturing an Office 2010 upgrade package.

When you migrate an Office 2013 package on Windows 8, Office will run an Office Repair utility when you import and activate the layer. Compatibility issues with Windows 8.

(18)

Table 1-7 Symantec Virtual Composer Known issues Description Issue

After freshly installing Windows 8.1 32-bit OS, computer gets unresponsive while performing capturing process in the Global capture mode. The Global capture works fine after the restart.

Computer gets unresponsive while stopping the capturing process in Global capture mode.

Table 1-8 Workspace Streaming Known issues Description

Issue

To work around this issue, run the setup.cmd again to update the access key.

Error message is displayed while changing the access key in the upgraded server.

In client AppMgrGUI when you open the Additional Details menu of a package, the Package Version value is not displayed separately. The Package version is appended to the package identifier. The Additional Details

menu of a package does not display the Package Version value separately.

To work around this issue, you must manually install the VC runtime 9.0.30729.6161version.

For Windows 2003 R2 BE server, the FE and DA components that are installed do not upgrade.

Only the IP-based rules work for an external package repository. For an external

package repository, the user-based rule and the group-based rules do not work.

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

cannot install Streaming Agent using MSI file.

To work around this issue, use different package name or supporting OS of the package should be different.

The package upload will fail when package with the same name is already in server.

(19)

Table 1-8 Workspace Streaming Known issues (continued) Description

Issue

The message to download jnlp client file is displayed every time when you click on the Manage > Add package option in the Streaming Console that is configured with SSL

The message to download jnlp file is displayed when you click on the add package option from the SWS console that is configured with SSL .

Streaming no more supports all of the old package types so recommendation is not to use old package type.

Error on launching Microsoft Legacy Snapshot packages, when office is removed with project/visio in cache.

To workaround this issue, pin the application icon to start screen from the All Application page.

Pre-pop icons are not displayed in the new tiled start screen in Windows 8.

Currently, this issue is under investigation and there is no workaround for now.

When connecting to the Streaming Portal from a Windows 8 computer, you cannot install the streaming agent when using Internet Explore in Metro Apps.

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.

(20)

Issue

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. 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

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. While using Japanese

OS, the DBCS characters in the Host name are corrupted after opening the Streaming Console in Internet Explorer.

To workaround, turn off the Training option for the packages, which are over 2 GB to avoid constantly increasing memory use while 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.

You must turn off training for packages over 2 GB

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.

(21)

Issue

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. 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.

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.

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.

When the Browser Selector Manager is set up to accept a remote configuration file, you must use Access Control to secure access to the remote configuration file's location

(22)

Issue

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 click the cancel button when exporting a package, the package is exported anyway.

You cannot cancel the export process of a package from the

Manage > Packages

page.

Other things to know

The following are things to know about Symantec Workspace Virtualization 7.5 SP1 and Symantec Workspace Streaming 7.5 SP1 release:

Table 1-9 Other things to know Description

Thing to know

In Symantec Workspace Streaming (SWS) 7.5 SP1, all the references to struts libraries used in SWS product is removed and addressed the security vulnerability reported in Apache Struts 1 PST14-064 3rd Party Security Alert More Apache Struts enjoyment but for the EOL Struts 1 this time CVE-2014-0114.

Struts libraries used in SWS product is removed.

Disable SLAM feature while using Network Apps to avoid any unexpected behavior. You can deactivate a package from Network Apps without using SLAM.

Do not enable SLAM feature for Network Apps.

(23)

Table 1-9 Other things to know (continued) Description

Thing to know

The layers get updated and cannot be used on old drivers, and the settings get updated and are invalid on old versions.

A downgrade is not a supported configuration.

Old package types are no longer supported. Old package

types are no longer supported.

Internet Explorer packages that were created for Windows 7 do not run on Windows 8.

PostgreSQL is no longer supported as a database therefore upgrading a server which has PostgreSQL as a database is also not supported. PostgreSQL is

no longer supported as a database option.

You must create Internet Explorer 6 packages on a Windows XP Base computer. Microsoft has removed some of the packages that are 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 You must create

Internet Explorer 6 packages on a Windows XP Base computer.

(24)

Thing to know

Locations to store anojdbc6.jarfile are as follows:

■ While installing a single node with a Back End and Front End server components or with only a Back End component then you must store the ojdbc6.jar file in the following places:

■ <home>\Agent\lib

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

■ <home>\common\jboss\modules\appstream\lib\main Additionally, you must add an entry <resource-root path="ojdbc6.jar"/>in the module.xml file at the following location:

<home>\common\jboss\modules\appstream\lib\main

■ 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 Location to store an Oracle ojdbc6.jarfile while connecting to an oracle database.

VCCmd needs to read and write to the disk. It needs the proper privileges to run. In 6.1 SP8 composer, VCCMD.exe displays the commands in the user privileged command prompt.

In this release, if you want to read the commands you need to run as an administrator user.

You must run Composer's VCCMD.exe as an administrator.

Symantec recommends that you use the Single Program Capture option instead of the Global Capture options when you capture Microsoft Office products into a layer.

Symantec Recommends to capture Microsoft Office products by using the Single Program Capture option. 24 Workspace Virtualization and Workspace Streaming Release Notes

(25)

Thing to know

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

You must provide the previous version's package in order to recompile a package to a higher version.

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

Other LDAP directory services like OpenLDAP and Novell eDirectory are no more supported for the User Data Source configuration.

Other directory services are no longer supported for the User Data Source configuration

-If you want to terminate a running session, you must use the Terminate

User option given on the Monitor > Active Users page of the Streaming

Console. Applications are not terminated on stopping the FE server components.

Fixed issues

The following are issues that were fixed in this release

(26)

Workspace Virtualization fixed issues

The following Workspace Virtualization issues are fixed in this release: Table 1-10 Workspace Virtualization fixed issues

Article ID Abstract of the Fixed Issue

NA Windows Search stops with an error, when you like to rebuild the index.

NA SWS_SWV_API was crashing when running the test suite.

NA SWV - local kernel mode privilege escalation exploit.

NA SVSCmd.exe Visual C++ Runtime Error on Dell latitude D630 during layer import.

NA Certain user variables were ocasionally missing in a SWV and

XenDesktop e2856777nvironment. This issue is addressed in this release.

NA Windows 8.1 x64 metro applications fail to launch with SWV 7.5.529 installed. This issue is addressed in this release.

NA Unable to remotely access the files and folders in C:\Users directory when a data layer is active.

NA Uninitialized variable gets freed causing a BSOD on Windows 7.

NA Missing File Error "Unable to find locale data files. Please reinstall" while launching virtual Google Chrome 31.0.1650.59.

NA Null pointer exception found in fslxRealVariableLoadSingleVariable.

NA Multiple error and warnings while trying to launch virtual Visual Studio 2010 Ultimate.

NA Error 1063 when using the SVSCMD command line utility to 'exec from layer' when the path contains a space.

Symantec Virtual Composer fixed issues

The following Symantec Virtual Composer issues are fixed in this release: Table 1-11 Symantec Virtual Composer fixed issues

NA Exclude Entries were not displayed properly in the composer when clicking the tabs like Files, Registry and Exclude Entries in the layer properties screen of Virtual Composer.

(27)

Table 1-11 Symantec Virtual Composer fixed issues (continued) Article ID Abstract of the Fixed Issue

NA While editing existing layer and switching (ALT+TAB) to other windows the Modify layer - Properties screen moves to top most layer. This issue is addressed in this release.

NA Help button and Help icon was not working.

NA Updated IE6,7,8 and 9 LDF's needed with Microsoft Security Bulletin MS14-012.

Workspace Streaming fixed issues

The following Workspace Streaming issues are fixed in this release: Table 1-12 Workspace Streaming fixed issues

NA SWS console was not restricting the packages, which were created using SWV admin from upload process.

NA In the Streaming Console > Settings > System Settings > DB

Configuration page, changing the password doesn't reflect in DA

machine's da.conf file.

NA Could not add the standalone Data Access Component after upgrading the upgraded Front-End Server only.

NA Environment variables are not resolved when an application is launched from the portal.

NA No warning message displayed while configuring 7.5 db in which

AppStream database already exists. The existing SP8 MP2 database is overwritten or recreated without warning.

NA Package Provisioning - Add packages in the console, which does not have java installed, do not redirect current window.

NA Alternate ways to upload or enable packages to specific server groups via runClient.cmd.

NA Unable to set a package as default on SWS Console. This issue is addressed in this release.

NA JMS Exception is thrown and error is displayed on console during package upload.

(28)

Table 1-12 Workspace Streaming fixed issues (continued)

NA Access denied with UNC share to remote computer.

NA Lync 2010 4x v6 Fails to Launch - "Unable to locate shortcut information for this package. Please make sure the virtualised package is active."

NA Unable to upload package to the streaming server console.

NA STS Service crashed abruptly causing downtime.

NA Unable to access the streaming console after upgrading tfrom 7.5 to 7.5 HF1.

Installation, User's, and Administrator's Guides

Table 1-13 Product documentation

Location Document

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

Symantec™ Workspace Virtualization 7.5 SP1 User's Guide

Symantec™ Workspace Streaming 7.5 SP1 Installation and Implementation Guide

Symantec™ Workspace Streaming 7.5 SP1 Administration Guide

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

Symantec™ Workspace Streaming 7.5 SP1 Server Upgrade Quick Start Guide

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++,

(29)

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.