Upgrading to Symantec Workspace Streaming 6.1 SP7

Article:DOC3729  |  Created: 2011-03-07  |  Updated: 2011-03-28  |  Article URL http://www.symantec.com/docs/DOC3729
Article Type
Documentation


Description



This document contains instructions for upgrading to Symantec Workspace Streaming 6.1 SP7. To upgrade to Symantec Workspace Streaming 6.1 SP7, you must first upgrade to either  6.1 SP4, 6.1 SP4 MP1, 6.1 SP6 MP1, or 6.1 SP6 MP1 HF1.

 

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\conf

agent.lcf
maaccess.key
MAConfig.xml

\common\jdk1.6.0_03\lib\security

cacerts
jssecacerts
mgmtcerts
stscerts

\console\conf

ConsoleConfig.xml
ConsoleLogConfig.lcf
server.xml

\console\lib\security

UserRepository.txt

\launchserv\conf

launchserv.lcf
launchserv.properties
server.xml

\launchserv\webapps\launchserv\old

AppstreamCfg.txt
setupcfg.txt

\server\bin

AppStreamServerCfg.txt

\streamletEngine\da\conf

AppstreamSASL.conf
da.conf
provision.xml

\streamletEngine\conf

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.


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 SP7 directly from Workspace Streaming 6.1 SP4, 6.1 SP4 MP1, or 6.1 SP6. 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 SP7 directly from Workspace Streaming 6.1 SP4, 6.1 SP4 MP1, or 6.1 SP6.

 

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.

 

Post-upgrade instructions

If you are performing an upgrade from 6.1 SP6 MP1 to 6.1 SP7 and the Front End Server is already HTTPS(SSL) enabled, you must re-configure the Front End server components after upgrade to allow HTTPS(SSL) on the Streaming Portal to work.

Configuring Front End server components

  1. In the Streaming Console under Configuration, click Launch Server.
  2. In the Launch Server Configuration screen, select the portal then click Basic.
  3. Check Enable Secure Socket Connection between End User and Launch Server.
  4. Click Save and then click OK on the Message from webpage window.
  5. In the Streaming Console under Status and Control, click Component Status.
  6. Select the portal and click Restart.

 



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


Terms of use for this information are found in Legal Notices