Top Banner
SymantecWorkspace Virtualization 7.5 and SymantecWorkspace Streaming 7.5 Release Notes
36

Virtualization 7_5 and Workspace Streaming 7_5 Release Notes

Oct 19, 2015

Download

Documents

sebymi

Symantec Virtualization & Workspace Streaming VWS Release Notes
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
  • SymantecWorkspaceVirtualization 7.5 andSymantecWorkspaceStreaming 7.5 ReleaseNotes

  • Legal NoticeCopyright 2013 Symantec Corporation. All rights reserved.

    Symantec, the Symantec Logo, the Checkmark Logo and Altiris, and any Altiris or Symantectrademarks used in the product are trademarks or registered trademarks of SymantecCorporation or its affiliates in the U.S. and other countries. Other names may be trademarksof 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 bereproduced in any form by any means without prior written authorization of SymantecCorporation and its licensors, if any.

    THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIEDCONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIEDWARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ORNON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCHDISCLAIMERSAREHELD TOBE LEGALLY INVALID. SYMANTECCORPORATIONSHALLNOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTIONWITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THEINFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGEWITHOUT NOTICE.

    Symantec Corporation350 Ellis StreetMountain 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 SupportSymantec Technical Support maintains support centers globally. Technical Supportsprimary 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 areaswithin Symantec to answer your questions in a timely fashion. For example, theTechnical Support group works with Product Engineering and Symantec SecurityResponse 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 amountof service for any size organization

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

    Upgrade assurance that delivers software upgrades

    Global support purchased on a regional business hours or 24 hours a day, 7days a week basis

    Premium service offerings that include Account Management Services

    For information about Symantecs support offerings, you can visit our website atthe following URL:

    www.symantec.com/business/support/

    All support services will be delivered in accordance with your support agreementand the then-current enterprise technical support policy.

    Contacting Technical SupportCustomers with a current support agreement may access Technical Supportinformation at the following URL:

    www.symantec.com/business/support/

    Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should be atthe computer on which the problem occurred, in case it is necessary to replicatethe problem.

    When you contact Technical Support, please have the following informationavailable:

    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 registrationIf your Symantec product requires registration or a license key, access our technicalsupport Web page at the following URL:

    www.symantec.com/business/support/

    Customer serviceCustomer 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 thefollowing 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 resourcesIf you want to contact Symantec regarding an existing support agreement, pleasecontact the support agreement administration team for your region as follows:

    [email protected] and Japan

    [email protected], Middle-East, and Africa

    [email protected] America and Latin America

  • 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 VirtualizationThis document contains release information for the release of following SymantecWorkspace 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

  • What's new in this releaseIn the release, the following new features are introduced:

    Table 1-1 List of new features

    DescriptionFeature

    This release includes a simplified install with the ability toeasily scale in a large organization.

    New installers

    Virtual Composer includes several improvements to the userinterface, as well as a better workflow for packagingapplications.

    Updated Virtual Composer

    Composer now includes an automatic exclude finder.

    Virtual Composer now includes the layer and package editingfunctionality that was previously available only in SWVAdmin.This lets use one packaging utility for most of your packingneeds. However; SWV Admin is still available in the release.

    Additional PackagingFunctionalities

    The LDF tool is now integrated. There are single-clickdefinitions for 40+ apps.

    LDF Tool

    You can now add registry exclude entries to your layers. Thisfeature prohibits the registry keys that you specify, from beingcaptured into the layer.

    Registry Excludes

    This release includes support for Windows 8 Clients.Windows 8 support

    Workspace Virtualization includes performanceenhancements in the driver.

    Virtualization PerformanceEnhancements

    The APIs provide a more consistent experience.Enhanced APIs

    Workspace Streaming includes performance enhancementsthrough client cache provisioning.

    Client PerformanceImprovements.

    The new Workspace Streaming installer requires minimaluser intervention during the server installation. Now, you donot need to depend on database availability as databaseconfiguration is separated from the installer.

    Once you are done with the server installation, you canproceed with the post-installation configuration withoutrestarting your computer. The new installer does not promptyou to restart your computer after the server installation.

    New Workspace Streaminginstaller for quick and easyserver installation.

    7Release NotesWhat's new in this release

  • Table 1-1 List of new features (continued)

    DescriptionFeature

    The newWorkspace Streaming Console is user-friendly andhas a set of more organized navigation elements. The consoleprovides you a consistent experience with differentcontext-sensitive actions.

    In the new console the navigation elements are categorizedinto the following areas:

    Home

    Monitor

    Manage

    Reports

    Settings

    New and improveduser-friendly WorkspaceStreaming Console for betterusability and performance.

    Now, you can dynamically manage different WorkspaceStreaming components by using Streaming Console,command prompt, and through web access to the StreamingConsole.

    Customizing components through the Modify install optionin the Workspace Streaming wizard is no longer supported.

    Enhanced WorkspaceStreaming componentmanagement.

    Workspace Streaming supports a new silent mode serverinstallation using the command prompt. The silent modeinstallation is very quick and easy to use. This type ofinstallation is useful in scenarios where you can use a toolor a logon script to complete a silent mode installation onmultiple computers during maintenance.

    Support for a newWorkspaceStreaming installation mode.

    The new [setup.cmd] tool lets you configure the WorkspaceStreaming components during the silent mode serverinstallation. The tool has several options to configure thecomponents.

    You can execute following command to see all the helpoptions to configure the required components:

    %systemdrive%\Symantec\Workspace

    Streaming\Server\installation\bin>setup.cmd

    -help

    Support for a new commandline tool [setup.cmd].

    8Release NotesWhat's new in this release

  • Table 1-1 List of new features (continued)

    DescriptionFeature

    The new Workspace Streaming Console supports followingmodern browser:

    Chrome, IE 8, 9, 10

    Works best in Firefox and IE 8, 9

    Support for HTML5 CSS3

    Support for modern browsers.

    Workspace Streaming support for amultiple AD domain withina single forest.

    Now AD configuration is simplified and you need to provideonly the following details:

    Root Domain

    User Principal Name and Password

    Support for Multi-Domain AD.

    Faster streaming performance through the virtual file systemimprovements in the following ways:

    IOPS ReductionsEliminating extra writes for each block by delayingstreamed file system creation on the physical disk.

    Client Cache ProvisioningBy reducing the number of requests, the client makes tothe server for the large chunk of information. It uses twolevels of caching through the User/Machine request cacheand User package info cache.

    Improved streamingperformance.

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

    Interactive mode database configuration using theStreaming ConsoleAfter installing the Back-End server component, you canconfigure the database using the Streaming Console.

    Silent mode database configurationYou can configure the database through silent mode usingthe command prompt. The silent mode databaseconfiguration is very quick and easy. It requires minimaluser intervention.

    Remote database configurationAfter installing the Back-End server component, you canWeb access to the Streaming Console and configure thedatabase remotely at any time.

    Support for new modes ofdatabase configuration.

    9Release NotesWhat's new in this release

  • Table 1-1 List of new features (continued)

    DescriptionFeature

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

    Create a completely new database.

    Attach an existing production database to the newlyinstalled server.

    Skip the database configuration and configure it latermanually based on your time and available resources.

    New database configurationoptions.

    The name of the new configuration file is Install.cfg file.This file contains overall information about install or upgradesuch as server type, port used, install date, upgrade date,build number, upgraded build number, etc.

    The Install.cfg also provides the database configurationdetails such as database server IP, port, and instance details.

    New central configuration fileto keep track of all theconfiguration details.

    The name of the new log file is install.log file and thefile is generated under the folder.

    The install.log file logs all the installation and thedatabase configuration information. You can also extracterror messages from \install.log file.

    Other logs can be found under the\installation\logs folder.

    New installation andconfiguration log file to keeptrack of all the logs.

    Now, you can create, update or delete package dependenciesthrough the Streaming Console.

    Dependencies that are defined in the Virtual Composer areimported when the package is uploaded on the StreamingServer.

    Dependencies can bemulti-level so theWorkspace Streamingsupports following views to manage the packagedependencies:

    Flat ViewThe Flat View provides a flattened list of the dependenciesthat will get installed or removed when a package isstreamed. This view lets you handle the circulardependencies.

    Parent ViewThe Parent View provides a list of packages that can bedirectly depend on a particular package. This packageview displays the direct package dependency.

    Enhanced packagedependency management.

    10Release NotesWhat's new in this release

  • Table 1-1 List of new features (continued)

    DescriptionFeature

    While provisioning a user, a new Check Dependenciesaction is introduced to view a list of dependencies, which aremissing for the user based on its user and group provisions.The helps you to diagnose the package dependency issueson the server.

    New features to diagnose thepackage dependency issueson the server.

    Now, you can get the user groups details from their NTLMcredentials; not from the LDAP queries.

    With the use of new AD security settings, the autoauthentication work more effectively.

    Improved security features.

    Workspace Streaming now supports Microsoft SQL Server2008 R2 and Microsoft SQL Server 2012 database.

    Support for new databases.

    Workspace Streaming and Virtualization Agents now supportWindows 8 and Windows Server 2012 operating system.

    Support for new operatingsystems.

    Now, you can easily reclaim licenses from the clientcomputers.

    When a Windows user logs off, the client computer sendsan empty Client Inventory message to the server. Thismessage instructs the server to remove all the licenses onthe server for that particular host.

    New feature for licensereclamation.

    Provisions are now recorded against SIDs instead of usernames. SIDs help you to handle the duplicate user namesin different domains.

    New user identifier isintroduced.

    Now, recovery information is not stored in the Temp folder orC:\Program Files folder.

    The new default location for RecoveryInfo is as follows:

    C:\_AC\RecoveryInfo

    New default location forrecovery info on theWorkspace Streaming clientcomputer.

    New web services are supported to provide all the corefunctionality, that is performed through the StreamingConsole.

    This functionality includes the configuration andmanagementof different components, licenses, user identity, packages,provisions, reports, server groups, and version, etc.

    Enhanced support for webservices.

    11Release NotesWhat's new in this release

  • Supported platformsStreaming endpoint operating systems64-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 requiredfor non-English language versions of XPWindows XP is supported with the additional components of Windows Installer3.1: http://support.microsoft.com/kb/893803 and the Filter manager roll up hotfix:http://support.microsoft.com/kb/914882

    Virtualization endpoint operating systems64-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

    12Release NotesSupported platforms

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

    Streaming Server operating systems32-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 DatabasesStreaming supports the following databases:

    Microsoft SQL Server 2005 SP4, Microsoft SQL Server 2008 R2 SP1, MicrosoftSQL Server 2008 R2 Express, Microsoft SQL 2012

    Oracle 10g, 11g, RAC

    Virtual Composer64-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 requirementsThe following tables contain system requirements for the endpoints, StreamingServer, and Virtual Composer:

    13Release NotesSystem requirements

  • Table 1-2 Endpoints

    RequirementSystem component

    Same as recommended by the operating system and installedapplications.

    System Processor

    Same as recommended by the operating system and installedapplications.

    System memory

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

    Free disk space

    Table 1-3 Streaming Server

    RequirementSystem 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 isrequired by the applications to be uploaded on to the server.

    Free disk space

    Table 1-4 Virtual Composer

    RequirementSystem component

    Same as recommended by the operating system.System Processor

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

    System memory

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

    Free disk space

    Installation and upgrade informationStreaming, Virtualization, and Composer Installation instructions are included inthe User's and Administrator's guides.

    The following table contains instructions to upgrade to this version:

    14Release NotesInstallation and upgrade information

  • Table 1-5 Upgrade instructions

    Upgrade instructionsProduct

    Upgrade instructions for Workspace Streaming are at thefollowing link:

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

    Workspace Streaming

    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 thepackager.ini file, sample scripts, and default templates. Afterthe new version is installed you can copy these files back tothe installation folder.

    Virtual Composer

    After you upgrade the server from 6.1 SP8 to 7.5, ensure that you do not reconfigurethe Active directory on the server. If you reconfigure the Active directory then theconfiguration that you have set for the user and the user groups are lost.

    You can use current version with previous version. Backward compatibility issupported between 7.5 and SP8 (and above versions) where Back-End must be in7.5 and all the Front-End can be in SP8 and above version. You can run 7.5 agentsagainst SP8 Back-End servers and vice versa. In this case, SP8 client can streamfrom 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-Endserver alone to 7.5 then your standalone DA works properly. But, if you try to adda SP8 standalone DA to a Back-End computer, which is running 7.5 version thenthe DA is not supported.

    You cannot upgrade SWS client in the terminal server mode. The SWS clientupgrade is completed through the silent mode only in the terminal servicesenvironment. The SWS agent upgrade fails if you initiate the upgrade process usingthe Streaming Portal or the setup.exe file.

    Before upgrading to the Parent STE in a Parent STE-Child STE setup you mustfollow 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'sconsole.

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

    15Release NotesInstallation and upgrade information

  • 4 Upgrade the Child STE separately that was removed from the Parent STEpreviously. Verify that the upgrade is successful..

    5 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 bothSTEs are have the same build version installed.

    Known issuesThe following are known issues for this release:

    Table 1-6 Workspace Virtualization Known issues

    DescriptionIssue

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

    Launch theMicrosoft Office Customizationtool using Setup.exe /admin.

    Note: The customization tool is onlyavailable for the volume license editions.

    Add SETUP_REBOOT in theModify SetupProperties page, and then add the valueIfneeded.

    Additional steps are required to packageMicrosoft Office 2010 in a Windows 8environment.

    To avoid this issue, it is best practice to installthe fonts into the base, and not into the layer.

    To work around this issue, you mustdeactivate and reactivate the layer to makethe fonts display properly.

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

    The Error code 1009 is displayed when youattempt to create an upgrade package fromOffice 2007 to Office 2010. This error occursbecause to upgrade from Office 2007 toOffice 2010 is not considered best practice.This upgrade path is not supported byMicrosoft. Various issues cause the XPF fileto not save properly and the upgrade packageis not created. To upgrade to Microsoft Office2010, you must create and stream acompletely new package.

    You cannot create an upgrade package fromOffice 2007 to Office 2010

    16Release NotesKnown issues

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

    DescriptionIssue

    This issue occurs because when the Office2010 layer is activated it starts the processBCSSync.exe. After the BCSSynch processcompletes it exits. This exit triggers thedeactivate on last process exit command. Toworkaround this issue youmust usemsconfigto disable BCSSync.exe.

    If you flag an Office 2010 layer to deactivateon last process exit, the layer deactivatesafter activation.

    The use of non-ASCII characters (includingHi ASCII), numeric digits, or specialcharacters (e.g. any character that cannot becased are not supported in the root path forthe fslrdr redirect area. You must either usethe default path "FSLDR", or use ASCIIcharacters.

    Symantec recommends the length be aminimum of 3 ASCII characters.

    You cannot use non-ASCII or Hi ASCIIcharacters in the root path of the fsldr redirectarea. For example, You cannot use Japanesecharacters instead of the root file path:"C:\FSLDR\".

    LDFs that were created on a 32-bit operatingsystem do not function properly when youuse them with a 64-bit Symantec VirtualComposer.

    To workaround, you must use the 32-bitversion of Symantec Virtual Composer.

    Most of the predefined LDF's were createdon a 32-bit operating system. These LDF'sdo not function properly when you use themwith a 64-bit Symantec Virtual Composer.

    If AppV is in layer format then Office2010Service Pack installation will fail and it is notpossible to create Office2010 SP1 upgradepackage.

    To create upgrade package for Office2010you must install OSPP in the base. You needto install "AppV Deployment Kit forOffice2010" in the base and then create theOffice2010 SP1 upgrade package.

    You must install AppV in the base whenCapturing an Office 2010 upgrade package.

    This issue occurs with Virtual Composer onlyafter clicking the tabs like Files, Registry andExclude Entries in the layer properties screen.

    Exclude Entries were not displayed properlyin the composer when clicking the tabs in thelayer properties screen.

    When you migrate an Office 2013 packageonWindows 8, Office will run an Office Repairutility when you import and activate the layer.

    Compatibility issues with Windows 8.

    17Release NotesKnown issues

  • Table 1-7 Workspace Streaming Known issues

    DescriptionIssue

    You cannot add a standalone Data Access Component if you upgradeonly the Front-End Server. You must first install the Front-End Severand a standalone Data Access Component together, and thenupgrade the Front-End Sever.

    Cannot add thestandalone DataAccess Componentafter upgrading theupgraded Front-EndServer only.

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

    The Additional Detailsmenu of a packagedoes not display thePackage Versionvalue separately.

    To work around this issue, youmust manually install the VC runtime9.0.30729.6161 version.

    For Windows 2003R2 BE server, the FEand DA componentsthat are installed donot upgrade.

    Only the IP-based rules work for an external package repository.For an externalpackage repository,the user-based ruleand the group-basedrules do not work.

    To work around this issue, you must manually change the passwordby copying the password from the STE's da.conf file to theda.conf file in all DA machine's or remove DA component(s) andadd it again.

    In the StreamingConsole > Settings> System Settings >DB Configurationpage, changing thepassword doesn'treflect in DAmachine's da.conffile.

    To work around this issue you run the install as an administrator.Non admin usercannot installStreaming Agentusing MSI file.

    18Release NotesKnown issues

  • Table 1-7 Workspace Streaming Known issues (continued)

    DescriptionIssue

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

    The package uploadwill fail when packagewith the same nameis already in server.

    Themessage to download jnlp client file is displayed every time whenyou click on the Manage > Add package option in the StreamingConsole that is configured with SSL.

    The message todownload jnlp file isdisplayed when youclick on the addpackage option fromthe SWS console thatis configured withSSL .

    You must not upload XPF packages created under SWV Admin toolto SWS streaming server as the packages created from SWV Admintool is not streaming compatible.

    SWS console doesnot restrict thepackages, which arecreated using SWVadmin from uploadprocess.

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

    Error on launchingMicrosoft LegacySnapshot packages,when office isremoved withproject/visio in cache.

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

    Pre-pop icons are notdisplayed in the newtiled start screen inWindows 8.

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

    When connecting tothe Streaming Portalfrom a Windows 8computer, you cannotinstall the streamingagent when usingInternet Explore inMetro Apps.

    19Release NotesKnown issues

  • Table 1-7 Workspace Streaming Known issues (continued)

    DescriptionIssue

    When you are installing the Workspace Streaming, if you use theDBCS or HI-ASCII characters in the Host name, the StreamingConsole fails to open and displays an error message.

    To work around this issue, you must not use DBCS or HI-ASCIIcharacters in the Host name for the Streaming Server.

    The WorkspaceStreaming installationfails in scenarioswhere the Host namecontains Non-ASCIIcharacters.

    The Front End and Data Access components services aredynamically added or removed depending on whether the componentis added or removed from the Back End server. Once the componentis removed from the server, the service is de-registered and thesettings are not retained for future uses.

    To work around this issue, every time a component is removed andadded again to the server, you must manually reconfigure all thechanges that are made to the removed Portal or STS services.

    In scenarios where anexternal repository isconfigured and theFront End componentis set to use theshared repositorythen once thecomponent isremoved from theserver, thecomponent servicessettings are alsoremoved.

    If you are using JapaneseOS and used DBCS or HI-ASCII charactersin the Host name then the characters are corrupted while you openthe Streaming Console in Internet Explorer.

    To work around this issue, you must not use DBCS or HI-ASCIIcharacters in the Host name for the Streaming Server.

    While using JapaneseOS, the DBCScharacters in the Hostname are corruptedafter opening theStreaming Console inInternet Explorer.

    To workaround, turn off the Training option for the packages, whichare over 2 GB to avoid constantly increasing memory use whilestreaming the package.

    In the Streaming Console, you can do this while configuring thepackage version settings. In the Package Version settings page,deselect the Training check box under the Options section of thepage.

    Training option is used to describe the process that determines thedata that should be initially streamed to an endpoint.

    You must turn offtraining for packagesover 2 GB

    20Release NotesKnown issues

  • Table 1-7 Workspace Streaming Known issues (continued)

    DescriptionIssue

    If you use the DBCS or HI-ASCII characters in the host name toinstall theWorkspace Streaming, the Streaming Console fails to openand displays an error message.

    To work around this issue, you must not use DBCS or HI-ASCIIcharacters in the host name for the streaming server.

    When you install theWorkspaceStreaming server inHi-ASCII location, anerror is displayedafter you configurethe User Data Sourceusing the ActiveDirectory.

    If you use the DBCS or HI-ASCII characters in the Host name, theStreaming Console fails to open and displays an error message.

    To work around this issue, you must not use DBCS or HI-ASCIIcharacters in the Host name for the Streaming Server.

    While using JapaneseOS, an error isdisplayed after youinstall the WorkspaceStreaming server inDBCS location andthe StreamingConsole fails to open.

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

    Package corruptionwarning fornon-provisionedapplications in theStreaming Consolehome page.

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

    If you attempt to finda very large amountof users (10,000)from an ActiveDirectory query, youmay receive an errormessage. The errorinforms you that youneed to configureActiveDirectorysettings to allow youto fetch so manyusers.

    21Release NotesKnown issues

  • Table 1-7 Workspace Streaming Known issues (continued)

    DescriptionIssue

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

    When the BrowserSelector Manager isset up to accept aremote configurationfile, you must useAccess Control tosecure access to theremote configurationfile's location.

    If you want to upload a package with same name which is alreadyuploaded then OS list should be different else package upload willfail. If you have package with same name/ but a different GUID thenyou should not be changing the supported Available on OS optionin the server, it will cause various problems.

    If you want to uploada package with samename which isalready uploadedthen OS list should bedifferent else packageupload will fail. If youhave package withsame name/ but adifferent GUID thenyou should not bechanging thesupported Availableon OS option in theserver, it will causevarious problems.

    If you click the cancel button when exporting a package, the packageis exported anyway.

    You cannot cancelthe export process ofa package from theManage > Packagespage.

    Other things to knowThe following are things to know about SymantecWorkspace Virtualization ReleasePreview release:

    22Release NotesOther things to know

  • Table 1-8 Other things to know

    DescriptionThing to know

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

    A downgrade isnot a supportedconfiguration.

    Old package types are no longer supported.Old packagetypes are nolongersupported.

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

    Internet Explorerpackages thatwere created forWindows 7 donot run onWindows 8.

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

    PostgreSQL isno longersupported as adatabase option.

    You must create Internet Explorer 6 packages on a Windows XP Basecomputer. Microsoft has removed some of the packages required to buildIE6. 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 createInternet Explorer6 packages on aWindows XPBase computer.

    Locations to store an ojdbc6.jar file are as follows:

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

    \Agent\lib

    \common\apache-tomcat\shared\lib

    \common\jboss\server\appstream\deploy\ste\ste.jar\

    While installing a single node with a Front End or Data Access servercomponents or with both Front End and Data Access servercomponents, you must store the ojdbc6.jar file in the followingplaces: \Agent\lib

    \common\apache-tomcat\shared\lib

    Location to storean Oracleojdbc6.jar filewhile connectingto an oracledatabase.

    23Release NotesOther things to know

  • Table 1-8 Other things to know (continued)

    DescriptionThing to know

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

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

    You must runComposer'sVCCMD.exe asan administrator.

    Symantec recommends that you use the Single Program Capture optioninstead of the Global Capture options when you capture Microsoft Officeproducts into a layer.

    SymantecRecommends tocaptureMicrosoftOffice productsby using theSingle ProgramCapture option.

    When configuring the Workspace Virtualization BSO, if you choose touse a remote XML file location, Symantec recommends that you use httpsto connect to it.

    Whenconfiguring theWorkspaceVirtualizationBSO, if youchoose to use aremote XML filelocation,Symantecrecommendsthat you usehttps to connectto it.

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

    In VirtualComposer, whenyou attempt torecompile apackage into ahigher version,youmust providethe previousversion of thepackage.

    24Release NotesOther things to know

  • Table 1-8 Other things to know (continued)

    DescriptionThing to know

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

    Other directoryservices are nolonger supportedfor the User DataSourceconfiguration -

    If you want to terminate a running session, you must use the TerminateUser option given on theMonitor > Active Users page of the StreamingConsole.

    Applications arenot terminatedon stopping theFE servercomponents.

    Fixed issuesThe following are issues that were fixed in this release

    Workspace Virtualization fixed issuesThe following Workspace Virtualization issues are fixed in this release:

    Table 1-9 Workspace Virtualization fixed issues

    Article IDAbstract of the Fixed Issue

    NASWV path expansion breaks windows firewall

    NAWhen SVS is checking registry permissions, it is not doing it in priorityorder, it checks the base first.

    NAItems under Run key executed as user who activates layer

    NAEnvironment variables in base take priority even when process run fromlayer.

    NALookup option causes winword.exe to consume 50% CPU on a dualcore processor and 90% + in single processor

    NASystem performance slow with 64-bit Trend Micro

    NASWV does not properly handle the presence of bogus user profiles.This causes performance problems

    25Release NotesFixed issues

  • Table 1-9 Workspace Virtualization fixed issues (continued)

    Article IDAbstract of the Fixed Issue

    NAWhen layer active, SEP client communication to server causesWmiPrvSE.exe to peg CPU on Windows 7

    NAQuickBooks Enterprise 10: cannot capture via global nor single programcapture

    NAUninstalling and reinstalling SWV with different accounts loses themetadata information.

    NAIf process icon pinned to task bar was launched from an advertisedshortcut, the pinned shortcut points directly to redirect area.

    NAIf process or shortcut in layer is "pinned" to taskbar, the taskbar remainsafter deactivating layer

    NAResearchMachines: A CC4 RM component fails to assign (install) whenan Open office layer is active.

    NAGoogle Chrome XPF does not work when imported in Win7 64bit OS.

    NAOSPP.VBS /dstatus will only return license status on machine Office2010 was captured. returns error on all others

    NAThe machine freezes when deactivating a layer or when importing alayer, and it has to be forcefully powered off in order to use it again

    NASWV_6_1_SP6_MP1_HF1 + Citrix PS 4.5 + Windows Server 2003 R2TS causes BSOD

    NASWV is making Microsoft Webmatrix unstable. Usually causing theapplication to hang within a minute

    NAUpgrading to SP6.x causes our Java based Expense Reporting productto freeze when trying to synch with its server.

    NA32-bit registry key App Paths getting deleted on x64 system when layerset to activate on system startup.

    NABlack Screen-Instability

    NAIf only the RW sublayer conflicts with a layer on the machine. Layersget out of sync on import.

    NAExplorer Hangs in the middle of activating bunch of layers at once onDEV Build (6.4.1286)

    26Release NotesFixed issues

  • Table 1-9 Workspace Virtualization fixed issues (continued)

    Article IDAbstract of the Fixed Issue

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

    NAThe exec command (to run an external process from the layer) doesn'tseem to work properly in SP7.

    NAWhen using ExcludeAllProfiles copy the user specific area to the basefor proper functioning of the application.

    NATestRegCreateKey0022 fails when running from a layer or in capturemode. This test is trying to create a registry link.

    NALatent Zero Minerva application performance issues

    NADWORD values in SVS Admin are limited to a maximum value of7FFFFFFF(Dec:2147483647) instead of FFFFFFFF(Dec:4294967295).Larger values are reduced to 7FFFFFFF. The same issue still occurswith SWV 6.1 SP7.

    NAInstructions to obtain license for personal use need to be updated oninstaller dialog.

    NAFonts not registering when streaming application

    NAVS 2010 projects pop up exceptions when MS Office / Project 2010layers are deactivated.

    NAError : Font '?' cannot be found while trying to open SQL Server MGMTStudio

    NAOnPostActivate fails to find "wscript.exe" when the full path is notspecified; this is different from the behavior in 2.1.3078.

    NAUsers have to open outlook twice to detect the Enterprise Vault plug-in.

    NASystem handle count creep whilst using layered applications

    NASWV_6_1_SP7_MP1_HF1_6.4.1354 + VMWare vSphere 5.0Windows7 x86 Enterprise SP1 VM + VMWare Host Profiles = BSOD at boot

    NAPath Settings Captured During Layering Result in Corrupt Path Entries

    NAVzNotifications don't properly work when event is triggered via WMI

    NADLL errors while trying to virtualize Apple Bonjour Service(customizedMSI)

    27Release NotesFixed issues

  • Table 1-9 Workspace Virtualization fixed issues (continued)

    Article IDAbstract of the Fixed Issue

    NAIssue when upgrading Acrobat Reader patches

    NAFonts do not appear in the Fonts folder until a log-off/log-on is performedwhen fonts are streamed

    NAIE Zone group policies and digital certificates stored under IE8 32-biton a Windows 7 x64 machine are lost when shared registry keys aremodified on the base and layer contains those shared registry keys aswell

    NAInstall and WDE shows 25% CPU usage on pgptray.exe. If they openpgpdesk.exe it also utilizes 25%

    NAAdding additional toolbar icons to Adobe Reader 10.x layer are notretained when the application is closed and then reopened.

    NAUSER_TEMPLATE file objects are not showing after layer is activatedon system startup for the user that added the objects during capturemode.

    NANew Reset Point Does not work

    NASWV "SVSCMD SENDINVENTORY" command fails to run with error"Registry operation on layer information failed. This is caused bymissingor in correct registry keys or values. Error: 1040 SVSCMD failed:SENDINVENTORY"

    NACom+ addin for MSword 2003 is being captured outside the layer evenin Global capture.

    NARegistry modifications done via "Run application from layer" affects thebase registry and are not isolated.

    NASWV uninstall does not remove fslrdr folder

    NAIsolation rules are not applied to keys/values in the RW sublayer

    NACreating a key blocked by isolation rules thinks key already exists

    NARestarting machine with WsApps component installed/configured shutdown the machine

    NAWorkspace Virtualization Admin shows strange characters in GUI withGerman locale settings.

    NAClick on Start - All programs it takes about 4 seconds to open. Ithappens only for the first time.

    28Release NotesFixed issues

  • Table 1-9 Workspace Virtualization fixed issues (continued)

    Article IDAbstract of the Fixed Issue

    NARO & RW folders of streamed packages under C:\flsrdr\1 or \2 are stillpersists even after the same package was mounted & stored underc:\fslrdr\Xaaa-1111\RW or RO folders.

    NAProblem with the streamed Adobe Acrobat Pro 10.1.4 software(Impacting the system functionality - causes system fonts to disappear).Deactivating the app fixes the problem temporarily

    NAValues larger than ~8K are not copied from the USER_TEMPLATEarea.

    NAWindows 8 Assessment and Deployment Kit fails to install on a machinerunning SWV.

    NARegistry conflict between OS and Layer causes CREDANT not to workproperly

    NAPPT table column input action has a delay of around 5-6 seconds beforedata is displayed when Office 2010 is in a layer

    NAIssues with streaming applications reorganizing USB devices

    NAIssue with security permissions on users profiles when we use theUSER_TEMPLATE

    NAMachine does not reboot properly when layer are set to "Activate OnSystem Startup"

    NALayer Properties: Import process is not working with Layer registrysettings

    NABSOD on XP SP2when user opens a file streamwith write permissionsand layer is active

    NADriver: Laptops randomly crash with BSOD

    NABSOD: Stop error: IRQL_NOT_LESS_OR_EQUAL on Windows 8Enterprise x64 after installing

    NABSOD on XP SP2when user opens a file streamwith write permissionsand layer is active

    NASWV - local kernel mode privilege escalation exploit.

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

    29Release NotesFixed issues

  • Article IDAbstract of the Fixed Issue

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

    NAQuicktime package is installing a new c++ runtime and a policy to forceall application to load the newer version. This is breaking SEP

    NAFile Type Associations not working for a virtualized app when app setto pre-cache Icons + File Associations

    NAWise Virtual Composer not keeping updated vendor version numberafter compiling UPGRADE packages of all Mozilla products fromprevious versions to 10.0 and above

    NAComposer takes over 10 to 15 minutes to load.

    NAIs it a normal behavior that first we need to compile a package beforebeginning to create package streamlets?

    NALayer Creation Tool: IE6 or IE7 for Windows 7 does not create workingIE layer

    NAcreating upgrade package from only .xpf file is stripping out all the preand post scripts from the package

    NAWhen clicking Second shortcut link in a streamed package shows themenu instead of opening the shortcut, when trying through SWS portal

    NAExpandable String and QWORD value is missing while trying to add"Registry Value" using the composer.

    Workspace Streaming fixed issuesThe following Workspace Streaming issues are fixed in this release:

    Table 1-10 Workspace Streaming fixed issues

    Article IDAbstract of the Fixed Issue

    NACannot get roles per group

    NAGetPackageUsageReport gives an "os Cannot be Null!!" exception

    NA"Bad Inputs" error is returned when retrieving reports(getLicenseUsedReportByName & getUsageDataReportByName)information

    NA"No package to process" error is returned when retrieving reports(getPackageUsageReport) information

    30Release NotesFixed issues

  • Table 1-10 Workspace Streaming fixed issues (continued)

    Article IDAbstract of the Fixed Issue

    NAInstallation there is an option to install launch server and streamingserver separately

    NAPortal button when clicked displays two launch server links when failover is configured.

    NAInstalling DA through installer (install Streaming server) removes theexisting STS & LS services if previously installed.

    NAConsoleConfig.xml is rewritten when STE is restarted.

    NAOffline package report from streaming agent takes long time to openLDAP connection, because for each session in the report we are doinga full LDAP user lookup

    NALicense descriptor saving "Maximum Concurrent Licenses:" changeswithout clicking "Save".

    NAOn component details page the memory always shows 0 for someSTSs.

    NAOn console CPU usage and other machine details are not correct

    NASupport LDAP connectivity in multiple forests environment.

    NAWarning message pops up, blocking navigation from advance tab toexternal address tab in server group configuration page

    NAServer installer should detect the exact existing build and present amessage on the GUI if upgrade is compatible from version x to versiony.

    NAWarning message in User Data Source configuration wizard, if theserver is not in that same domain.

    NAThe client upgrade process adds an icon to the sys-tray with a tool tipof "-100%"

    NA[DependentProducts] and [ProductName] are missing in the clientupgrade log file.

    NACreate DB schema not checking if enforce password requirements isenabled on DB.

    NAAdd the white listing and blacklisting parameters to the config file.

    31Release NotesFixed issues

  • Table 1-10 Workspace Streaming fixed issues (continued)

    Article IDAbstract of the Fixed Issue

    NAGrammar on db connectivity error page - change "may not be exist" to"may exist"

    NAAdd toggle for default upload option for caching type

    NACPU Spikes to 100%when opening AD related items in a ManagementConsole

    NAServer uninstall does not allow uninstall of a single component whencustom install was used.

    NADomain users and groups are not showing up when using root DN assearch base and LDAP Connectivity is set to AUTO

    NAAvailable package view "All" filter does not show "All". It showspagination w/100 entries per page.

    NAShow group provision info when viewing user provisions.

    NARemoving user from user group is only functioning if you remove fromindividual user properties.

    NAInactive Agents Search lists all the agents data whenDaysOfInactivity=0. This needs to be changed. Display a messagesomething like 0 will display all the agents that streamed.

    NASort By function is not working for Application Usage Report.

    NAIncorrect message is displayed after server group->external addressis applied and updated in an multinode + LB environment

    NABackend fail-over issues

    NAAdd an option to expire a package and remove it from client immediately

    NABrowsing is cancelled and application is not launched using IE9. LaunchServer is SSL enabled.

    NABSOD on the machine where SWS & Hibun AE encryption software isinstalled.

    NAFEs are down after applying the MS patches on Server.

    NAAppstreamservice.exe client error: connection could not be established

    NAx64 clientversion.txt file is ignored in favor of x86 one on an x64 platform

    32Release NotesFixed issues

  • Table 1-10 Workspace Streaming fixed issues (continued)

    Article IDAbstract of the Fixed Issue

    NAError "Failed to get user when trying to look up for userwith Swedish characters".

    NALDAP and performance issues with streaming console

    NAComponent details not populated when server is left running for around2 weeks or more

    NAApplication Launch Performance SWS Vs SWV Standalone

    NALDAP + SSL does not fetch multi domain users when LDAPs configuredwith GC

    NAStreamed applications will run if sync proc request times out

    NAAdd java version to dci/agent logs upon service restart.

    NAProvide more accurate info about STE status on console page/ logs

    NACan't add the STE to the console with the fully qualified name b/c ofcharacters space limitation

    NAFeature request: option to disable the SEV agent from prompting theuser to upgrade to latest version.

    NAAttachmate ReflectionWorkspace crashes after upgrade from v1 to v2.Requires layer reset to make the application stop crashing.

    NALDAP Timeouts - DA losing connectivity to LDAP servers.

    NAConsole shows wrong info about the NAS space availability. Since,Customer was unable to upload packagemore than the specified spacein Console.

    NAdb.PSexception 33 database error in STS log

    NANew Server Installer: New installer does not allow for a single nodeinstall in attended mode

    NAPre-cached Icons not working.

    NAWhen user data source = local SQL (PG/MS SQL)check box is inunchecked state for the provisioned packages in user provision pageif the user name has "@" in it

    NAAfter SP8 Upgrades, Some AppsWon't StreamUnless Run from PortalFirst

    33Release NotesFixed issues

  • Table 1-10 Workspace Streaming fixed issues (continued)

    Article IDAbstract of the Fixed Issue

    NARecurring client errors in logs ("created outside the AppStream filesystem" and "oli checksum")

    NACan't login to console with network ID

    NAFE in Amber state and STE showing database and null pointerexceptions

    NANeed to remove OpenSSL.exe from the server install.

    NATwo distiller process running in task manager while streaming acrobat10, Getting an error "another instance of distiller is starting up; thisinstance can not continue"

    NASEP 12.1 RU1 MP1 Fail to install on Win7 32 and 64 bit VM, installrolls back. SEP Dev traced to SEV drivers

    NADA Name Field on Create DA Component Screen Truncates at 32Characters

    NAAfter FE server installation, the SWS Launch & Streaming serverservices are not started automatically.

    NAInstallation: Just tried to install the 7.5 FE setup on the machine wheresame version is already installed; installer shows a upgrade notification& installs successfully instead of warningmessage that the same versionis already installed.

    NANEWCONSOLE-Unable to change the component description fromSWS Console.

    NASingle Node server console shows exception errors very often.

    NAServer Console shows Exception error after adding the FE component& also, Streaming Server Services is not listed.

    NA"Authentication failure 8003" warnings were flooded in the launch serverlogs

    NAUnable to provision any package to a AD user. Receiving an errormessage " Failed to get user"

    NAAll pre-populated apps after client installation show as 0% cached andcan't be launched

    NAAmbiguity in "To set up the user data source for the back-end server"

    34Release NotesFixed issues

  • Table 1-10 Workspace Streaming fixed issues (continued)

    Article IDAbstract of the Fixed Issue

    NA2 Packages with same name but different GUID are allowed to beupload using web client but display as single entry on console and has2 DB entries

    NAappmgr service crashes Intermittently and appstream dump files arecreating on each crash.

    NABasingstoke Packaging Server - Console Slowness

    NAConsole: Results not shown when User Data Source Connectivity testis success.

    NAWhen selecting portal from Agent GUI both FQDN and short name ofstreaming server is shown

    NACONSOLE: The Management console administration account is notaccepting a certain password even though its with valid characters andsymbols.

    NAWhen my end user create an application package for some newsoftware and stream it down to clients, some ini file with in the packagegets corrupted.

    NAAfter restarting the client machine, it throws an Authentication error10057 when we try to launch the streamed application.

    NAChange the time zone in DB as a UTC time rather than localized timezone

    NAUsers intermittently encounter Error Code 10037 when launchingapplications from the streaming portal.

    NAWhen domain membership changes, LDAP should not bemarked downinstead should report NoSuchObject and continue its routine

    NAAdding FE to Server Group without External Address set createsincomplete Component in DB

    NAMissing Package version from the streaming agent

    NASearching for local groups only using local or local\ in front of groupname

    NASWS Console supports one Active Directory user source

    NAIssue with Clear Route application and streaming agent

    35Release NotesFixed issues

  • Installation, User's, and Administrator's GuidesTable 1-11 Product documentation

    LocationDocument

    http://www.symantec.com/docs/DOC6666Symantec Workspace Virtualization 7.5User's Guide

    http://www.symantec.com/docs/DOC6667Symantec Workspace Streaming 7.5Installation and Implementation Guide

    http://www.symantec.com/docs/DOC6548Symantec Workspace Streaming 7.5Administration Guide

    Additional informationThe following sections contain additional information about this release:

    Workspace Streaming SDKSymantec Workspace Streaming SDK is made up of several web services that areaccessed using Simple Object Access Protocol (SOAP). The interface is exposedthrough a web services description language (WSDL) document. The WSDLdocument provides details on the publishedmethods and objects. Most programminglanguages provide support for SOAPweb services including C#, Visual Basic, C++,Java, Python, and others. Most languages provide the ability to automaticallygenerate proxy classes using the WSDL document.

    Third Party Legal NoticesThis Symantec product may contain third party software for which Symantec isrequired to provide attribution to the third party (Third Party Programs). Some ofthe Third Party Programs are available under open source or free software licenses.The License Agreement accompanying the Licensed Software does not alter anyrights or obligations you may have under those open source or free softwarelicenses. For more information on the Third Party Programs, please see the ThirdParty Notice document for this Symantec product that may be available athttp://www.symantec.com/about/profile/policies/eulas/, the Third Party Legal NoticeAppendix that may be included with this Documentation and/or Third Party LegalNotice readme File that may accompany this Symantec product.

    36Release NotesInstallation, User's, and Administrator's Guides

    Symantec Workspace Virtualization 7.5 and Symantec Workspace Streaming 7.5 Release NotesTechnical SupportRelease NotesAbout Symantec Workspace VirtualizationWhat's new in this releaseSupported platformsSystem requirementsInstallation and upgrade informationKnown issuesOther things to knowFixed issuesInstallation, User's, and Administrator's GuidesAdditional informationWorkspace Streaming SDKThird Party Legal Notices