This chapter includes the following topics: User's and Administrator's Guides. Symantec Workspace Virtualization build:

Transcription

1 Chapter 1 Symantec Endpoint Virtualization 6.1 SP8 MP1 Release Notes This chapter includes the following topics: About Symantec Endpoint Virtualization 6.1 SP8 MP1 What's new in 6.1 SP8 MP1 Supported Platforms System requirements Known Issues User's and Administrator's Guides About Symantec Endpoint Virtualization 6.1 SP8 MP1 This document contains release information about the release of Symantec Endpoint Virtualization. This release includes information about the following products: Symantec Workspace Streaming build: Symantec Workspace Virtualization build: Symantec Virtual Composer build:

2 2 Symantec Endpoint Virtualization 6.1 SP8 MP1 Release Notes What's new in 6.1 SP8 MP1 What's new in 6.1 SP8 MP1 Readdressing the primary server in SWS Client The SWS client now supports readdressing the primary server. This feature allows clients to pin packages to an external server address instead of the primary server. To activate this feature you must add the following entry to the AppStreamCfg.txt client configuration file: ALLOW_SERVER_READDRESSING=true This change causes the SWS client to pay attention to how the server is configured for its external address. Any Future attempts to contact the server through the re-mapped address, have the client use the external address until the AppMgrService is restarted. Pinning an address to the returned external address by the server is only valid for the lifetime of the AppMgrService.exe instance. It is not persistent across restarts of the service. A different external address can be used for the primary the next time the AppMgrService is started if necessary. Use this functionality only if the primary server address for the client represents a load balancer address and there is no server for its external address. Note: The backup server list for the external server group should contain the global (primary) address for failover using the global load balancer. Supported Platforms Streaming and Virtualization endpoint operating systems Table 1-1 Edition 64-bit 32-bit Streaming and Virtualization endpoint operating systems Operating systems Microsoft Windows 7 Microsoft Windows Server 2008 Microsoft Windows Vista SP2 Microsoft Windows 7 Microsoft Windows Vista SP2 Microsoft Windows XP SP3

3 Symantec Endpoint Virtualization 6.1 SP8 MP1 Release Notes System requirements 3 Streaming Server operating systems Table 1-2 Edition 64-bit Streaming Server operating systems Operating systems Microsoft Windows Server 2008 Microsoft Windows Server 2008 R2 Microsoft Windows Server 2003 R2 SP2 or later 32-bit Microsoft Windows Server 2008 SP1 or later Microsoft Windows Server 2003 R2 SP2 or later Streaming databases Table 1-3 Streaming databases Editions SQL Express SQL 2008 SP1 64-bit Microsoft SQL Server 2005 SP4 or later Oracle 10g and 11g, RAC Symantec Virtual Composer Table 1-4 Edition 64-bit 32-bit Symantec Virtual Composer Operating systems Windows 7 Windows Vista SP2 Windows 7 Windows XP SP3 Windows Vista SP2 System requirements The following tables contain system requirements for the endpoints, Streaming Server, and Virtual Composer:

4 4 Symantec Endpoint Virtualization 6.1 SP8 MP1 Release Notes Table 1-5 Endpoint requirements System component System Processor System memory Free disk space Requirement Same as recommended by the operating system and installed applications. Same as recommended by the operating system and installed applications. 50 MB of free disk space plus additional space as required by installed applications. Table 1-6 Streaming Server requirements System component System Processor System memory Free disk space Requirement Minimum 1 GHz of processor capability. 2-GB memory minimum. 2 GB of free disk space. In addition, the applications to be uploaded on the server require three times their space. Table 1-7 Virtual Composer requirements System component System Processor System memory Free disk space Requirement Same as recommended by the operating system. 1-GB memory minimum. Additional space is required according to the recommendations of the applications that you want to package. 30 MB of free disk space, plus three times the size of the package. The following are fixed issues in this release: Table 1-8 Symantec Workspace Virtualization Fixed Issues Resolved a high CPU usage and performance issue after an IE8 layer is activated.

5 Symantec Endpoint Virtualization 6.1 SP8 MP1 Release Notes 5 Table 1-8 Symantec Workspace Virtualization Fixed Issues (continued) Resolved issue where Windows Search (SearchIndexer.exe) terminated unexpectedly due to the SWV driver. Resolved issue where OnPostImport failed to find cmd.exe or regedit.exe when the full path is not specified. This behavior is different from the behavior in SWV 6.1 SP4. Resolved issue where after an update to SWV , removing a user profile caused errors. Resolved issue with duplicate audio mixer keys getting created. Table 1-9 Symantec Workspace Streaming Fixed Issues Resolved issue where 100% blocks got collected in the desktop machine when "Offline enabled if Laptop" is set in the C&M. Resolved issue with LDAP Timeouts. The DA lost connectivity to the LDAP servers. The 5000ms hard coded timeout was removed. Resolved issue where the LDAP status showed down after AD changes were applied, and LDAP was configured with SSL. Console shows wrong info about the file space availability is resolved. Resolved and issue where "Received WinHTTP error: 12002" and then a fatal error message appears in the log "Could not get ProvisionInfoRPMsg Reply". Resolved issue where the GetPackageID method fails when the package name contains either a leading or a trailing space character. Resolved an issue where you needed to patch vulnerabilities in Apache Tomcat Web Server before going into production. Resolved an issue where after SP8 Upgrades, some Apps would not stream unless they were run from the portal first.

6 6 Symantec Endpoint Virtualization 6.1 SP8 MP1 Release Notes Table 1-9 Symantec Workspace Streaming Fixed Issues (continued) Resolved an issue where not all offline packages showing up in SWS agent GUI Resolved provisioning issues user names contained the character.wsapi:when passing a list of apps to be unprovisioned (method removeprovisions) for a user with username containing "@", it seems that the user loses all his provisioned apps instead of removing all the passed in the list. Resolved issue where Windows 7 agents got stuck at a "please wait"screen after restart from upgrade from SP7 and HIPS was installed. Resolved and issue when the SDK web method changenameandusercontact is used to modify the user data, the user provisioning data is not visible. Resolved issue where your received the message "Console errors managing packages NullPointerException." Resolved issue where you could not login to console with a network ID Resolved issue where the application failed to launch with errors "10048, 10043, client errors - Oracle Unique Constraint error." Resolved issue to avoid "Error Code : Insufficient disk space to stream application." Resolved issue where pre-populated apps after the client installation showed as 0% cached. They could not be launched Resolved issue with the following recurring client error in the logs: "created outside the AppStream file system" and "oli checksum". Resolved issue where the AppMgrService memory usage kept growing until the computer was restarted. Resolved issue with javax.jms.jmssecurityexception:jmssecurityexception in GetPackage WSAPI method.

7 Symantec Endpoint Virtualization 6.1 SP8 MP1 Release Notes Known Issues 7 Table 1-9 Symantec Workspace Streaming Fixed Issues (continued) Resolved issue where users in multiple domains got a blue screen in RegHook.sys when logging off and back on again. Resolved issue where the DA name field on the create DA component screen truncated at 32 characters. Known Issues The following are known issues in this Release: Table 1-10 Known issues Issue Due to a update of a data protocol there is a incompatibility between servers where a server running SP8 cannot correctly communicate with another server running SP7. When migrating to SP8 all servers in the group need to be upgraded to SP8. It is also recommended that clients hitting a SP8 server also be upgraded to the SP8 version. Article ID User's and Administrator's Guides The following table contains links to the latest documentation PDFs on the Web: Table 1-11 Product User's and Administrator's Guides Guide Symantec Workspace Streaming Admin Guide Symantec Workspace Virtualization User's Guide Symantec Virtual Composer User's Guide

8 8 Symantec Endpoint Virtualization 6.1 SP8 MP1 Release Notes User's and Administrator's Guides