Upgrading to Workspace Streaming 6.1 SP4

Article:DOC2159  |  Created: 2010-05-28  |  Updated: 2010-10-01  |  Article URL http://www.symantec.com/docs/DOC2159
Article Type


This document contains instructions for upgrading to Symantec Workspace Streaming 6.1 SP4 from Symantec Workspace Streaming 6.1 SP1 (build or later.

If you are using a previous version you must first upgrade to Workspace Streaming 6.1 SP1. For instructions on upgrading to 6.1 SP1, see KB #48168.

Before you upgrade

Database backup

We recommend performing a full database backup before upgrading. The upgrade process uses scripts to update your database schema to the latest version.

Configuration backup

The following paths contain custom files or files with custom settings. We recommend that you backup any changes you make to these files for review after upgrade.

After the upgrade, you should review any customizations and compare them with the default settings installed with this release. We do not recommend simply overwriting any existing settings with previous settings. Some of the previous values apply only to legacy package types (SVS, MSI, snapshot, and tracking packages), and several default values have been updated.

Please contact Symantec customer support if you are unsure if a specific change should be merged into the new configuration file.

Before upgrade, any portal customizations as well as any changes in the following files should be backed up:


  • agent.lcf
  • maaccess.key
  • MAConfig.xml


  • cacerts
  •  jssecacerts
  •  mgmtcerts
  • stscerts


  • ConsoleConfig.xml
  • ConsoleLogConfig.lcf
  • server.xml


  • UserRepository.txt
  • \launchserv\conf
  • launchserv.lcf
  • launchserv.properties
  • server.xml


  • AppstreamCfg.txt
  • setupcfg.txt


  • AppStreamServerCfg.txt


  • AppstreamSASL.conf
  • da.conf
  • provision.xml


  • maxSeats.properties
  • maxSessions.properties
  • ste.conf

Custom reports

Any custom reports should be backed up before upgrading. These reports can be recopied when the upgrade completes.

Server Group Configurations – new default keep alive intervals

The default values for Minimum Keep-Alive and Maximum Keep-Alive intervals have changed in 6.1 SP4 as follows:

Value Previous default New default (6.1SP4)
Min. Keep-Alive Interval 60 secs 20 secs
Max.Keep-Alive Interval 14400 Secs 600 secs

To prevent losing the current default values for the Minimum Keep-Alive and Maximum Keep-Alive intervals for your server groups, you must save them manually. This procedure saves the values to the database so they are available after upgrade.

1. In the Streaming Console, click Configuration > Server Group > Default Server Group > Configure > Advanced.
2. Update the values as required and click Save.

You can also change these values to the previous defaults after upgrade.

Addition of Kerberos Authentication

After upgrade, you can enable kerberos authentication by reconfiguring the User Data Source in the Streaming Console. See the Workspace Streaming Admin Guide for details.

Upgrade known issues

Review the following known issues before upgrading:

Issue Workaround, if any
If you are using LDAP with SSL, the STSCERTS certificate is not copied to the data access server automatically.

If LDAP+SSL was configured in 6.1 Sp1 and upgraded server to 6.2. Now if you add
new 6.2 DA Component to single node, still STSCERTS certificate will not be copied
to DA. machine to DA machine.

Manually copy the STSCerts file from the Streamlet Engine to the Data Access server.

The certificate file is located at

<installDir>\Server\common\jdk1.6.0_03\lib\security on the back end server (hosting the streamlet engine).

Copy this file to all servers hosting the data access component to

C:\Program Files\Symantec\Endpoint

Virtualization\Workspace Streaming\Server\common\jre\lib\security

JRE 1.6u18 should be manually uninstalled before upgrading to 1.6u20 Uninstall JRE 1.6u18 and then install JRE 1.6u20. See the Sun JRE documentation for details.
CLI packages created in older versions of Workspace Composer return an error when uploaded. Workspace Streaming 6.1 SP4 supports CLI packages created in 6.x and later.
File in use error when upgrading the Streaming Agent If this occurs you are prompted to Exit, Ignore, or retry the operation. You can safely click Ignore and the upgrade completes successfully.
Non-admin users are unable to complete Agent upgrade if initiated from a shortcut or from the Application Manager GUI. If this occurs open the Streaming Portal to perform the upgrade.

Performing the Upgrade

Server upgrade

Servers hosting back-end server components should be upgraded before any other servers.

Starting with your back-end server, run the Workspace Streaming server installation on each server that is hosting a streaming component (back-end, front-end, backup, data access, and so on). The installer detects the existing installation and upgrades the necessary components.

After upgrading front end servers, the Streamlet Engine service (named ATWE STE in the Services applet) on your back end server should be restarted. This restart is required to display the correct software version of front end servers and data access components in the Streaming Console.

Agent upgrade

We recommend using a software distribution application, such as Symantec Client Management Suite, to upgrade the Agent.

Agent upgrade using the client installation executable

The Streaming Agent can be upgraded to 6.1 SP4 directly from Workspace Streaming 6.1 SP1. The installation can be performed by a user with admin privileges or silently through a software distribution application.

Agent upgrade from the Streaming Portal

The Streaming Agent can be upgraded to 6.1 SP4 directly from Workspace Streaming 6.1 SP1.

Non-admin users on Windows Vista

Non-admin users on Windows Vista are unable to initiate an Agent upgrade from the Agent GUI or from a shortcut. These users should open the Streaming Portal to initiate the upgrade process.

Legacy ID


Article URL http://www.symantec.com/docs/DOC2159

Terms of use for this information are found in Legal Notices