Symantec Endpoint Virtualization Suite 6.1 SP3 MP3 Release Notes
|Article:DOC2126|||||Created: 2010-03-31|||||Updated: 2011-08-01|||||Article URL http://www.symantec.com/docs/DOC2126|
Note: This is not the current version of Symantec Endpoint Virtualization.
Workspace Streaming build number: 184.108.40.206
Workspace Virtualization build number: 220.127.116.1126
Symantec Endpoint Virtualization Suite 6.1 SP3 MP3 is a cumulative release containing all previous service packs, maintenence packs, and hotfixes for Workspace Streaming 6.1 and Workspace Virtualization 6.1.
This article contains a list of new fixes in this maintenence pack. For details on previous fixes see the release notes links in the following sections:
For supported platforms, product installation instructions, and additional known issues, see KB #48193, Symantec Workspace Streaming 6.1 SP1 Release Notes.
|Fixed an issue that caused some applications to launch correctly from the portal but not from a desktop shortcut. This was due to the command line environment variables being resolved to incorrect paths.|
|Fixed an issue that caused environment variables to be lost after a user logs off and then back on again if SLAM is enabled. An ENVIRONMENT_REFRESH_DELAY value was added to appstream.cfg to perform an environment refresh after releasing the userinit or shell process. If you experience this issue set this value to 1 for a 1 second delay.|
|Fixed an issue that prevented RUN registry entries in a virtual layers from executing when SLAM was enabled and the user was a limited user.|
|Fixed an issue that was preventing front end server fail over in load balancing environments for new application launches when other applications are already running.|
|Fixed an issue that was reverting the priority of data access components to default if certain configuration changes were made after the priority was set manually. Manual priority changes are now maintained when configuration changes are made.|
|Fixed an issue that was causing Front End servers to crash due to a lack of temporary storage and in in rare circumstances when client reports were being cached on disk..|
|Fixed an issue that was causing the active users list to load slowly when there is a large number of active sessions.|
|Changed the total users field in the Streaming Console to total running sessions. This field now contains only running sessions (both user initiated and system initiated) and does not include suspended sessions.|
|Fixed an issue that prevented the user from installing the database on systems that do not support long path to short path conversion.|
|Added enhancements to validate several attributes on the Streaming Server before processing. The Agent also received enhancements to avoid sending bad data. These changes resolve assorted issues encountered when corrupted data is exchanged.|
|Fixed an issue that was preventing the package installation process from recognizing if a package is already installed when using the system account. This caused the package installation process to attempt to install the package until a user session was started on the computer. After this fix, the version is now correctly recognized when using the system account and no attempt is made to stream the package if it is already installed.|
|Added indexes to the database tables used when generating reports. This change speeds up the reporting queries and potentially avoids issues caused by excess system load.|
|Increased the default JVM memory to avoid issues encountered when generating large reports in PDF format.|
For supported platforms, product installation instructions, and additional known issues, see KB #48658, Workspace Virtualization 6.1 SP1 Release Notes.
|Enhanced layer import to allow two or more import operations to happen concurrently.|
|Fixed an access violation (BSOD) caused by certain application behavior. This appears to happen more frequently when the “Hide From Operating System” setting is used.|
|Fixed an issue that caused the system to hang on startup.|
|Fixed an issue that gave limited operating system users delete access to some specific registry keys that they should not be able to access.|
|Fixed an interoperability issue that was causing deadlocks with the Microsoft UPHClean tool.|
Article URL http://www.symantec.com/docs/DOC2126