SVS Pro Streaming System 5.2.2 Release Notes

Article:DOC1537  |  Created: 2007-11-21  |  Updated: 2008-05-07  |  Article URL http://www.symantec.com/docs/DOC1537
Article Type
Documentation


Description



Question
What do I need to know about Altiris® Streaming System 5.2.2?

Answer

SVS Pro Streaming System 5.2.2

Release Notes

Installation and Upgrade

What's New in this Release

Fixes in this Release

Known Issues in this Release

Additional Documentation

Document History

Installation and Upgrade

This section lists items to be aware of before installing. For instructions on setting up and installing the Streaming System, see the Altiris® Streaming System 5.2.2 Administrator's Guide that accompanies the Streaming System product download.  

Upgrade paths to this version are not available in this release

This version of the Streaming System only supports clean installation scenarios. You cannot upgrade from previous versions of either Altiris Software Virtualization Solution Professional, or AppStream. If you have previous versions installed you must first uninstall them before installing SVS Pro Streaming System 5.2.2. Future versions of the Streaming System are expected to support upgrading from this version.

Streaming packages are backward compatible

Streaming System 5.2.2 is backward compatible with Streaming Packages created with Altiris Software Virtualization Solution Professional and AppStream 5.1 and higher versions.

Do not install the Streaming Server on the Notification Server computer  

At this time due to performance concerns, installing the Streaming Server or the Streaming Composer on a computer containing Altiris Notification Server is not recommended. 

Do not use the default port 80 when installing the Streaming Server on a computer running IIS

During installation of the Streaming Server you are prompted to specify the Launch Server Settings Port on which the Launch Server listens for connections from browsers. By default, this port number is set to Port 80. However if IIS is running on the same computer where you are installing the Streaming Server, you must configure the Streaming Server so that it does not use port 80. This is done by simply specifying a different port number during installation.

During the final step of installation all ports are then validated. If the port that you specify is in use and unavailable then installation will not complete until a different port is chosen.

External database must be configured for case sensitivity

If you plan to implement an external database instead of using the default database bundled with the Streaming System installation, then the database must be configured for case sensitivity. The Streaming System will not work with an external database that is configured as case-insensitive.

Prerequisites

Minimum Streaming Server requirements:

System Processor Minimum 1GHz of processor capability 
System Memory 2 GB memory minimum
Free Disk Space 2 GB of free disk space, plus three times space required by the applications to be uploaded on to the server
Operating System Windows 2000 Service Pack 2 or greater
Windows 2003
Networking IE 6.0 or later
 

Minimum Client computer requirements:

System Processor Pentium III, 500 MHz
System Memory 256 MB memory minimum
Free Disk Space 50 MB of free disk space, plus twice the size of the installed application(s) (NTFS recommended)
Operating System Windows XP SP1, Windows 2000 SP4, Win2003 SP1, Windows Vista
Networking 128 Kbps network connection (DSL, cable, or broadband recommended)
IE 6.0 or later or Fire Fox 1.0 or later

Minimum Streaming Composer computer requirements: 

System Processor Pentium III, 700 MHz
System Memory 256 MB memory minimum (512 MB recommended)
Free Disk Space 30 MB of free disk space, plus three times size of the package
Operating System Windows XP, Windows 2000, Windows 2003, Windows Vista
System Prerequisites System must be clean i.e. system should only be loaded with operating system and minimal utilities required to run applications. Alternatively, system can be a mirror image of the system where applications may ultimately run.
 

What's New in this Release

Improvements for this release include the following new features and enhancements:

  • Vista Support: The Streaming Agent installs on 32-bit Windows Vista
  • Intel AMT vPro System Support: Offline connectivity alerts and 3 PDS supported by Streaming Agent
  • WAN Optimization: Central application caching capabilities supported by the Streaming Server.
  • MSI command line packaging: The streaming composer supports the ability to create MSI packages using the command line.  
  • Improved agent install error detection: The Streaming Agent installer has improved error detection
  • LDAP Configuration Wizard Improvements: Usability improvements were made to the Streaming Server's LDAP Configuration Wizard
  • Java daylight savings time patch: Java DST patch has been incorporated into the Streaming Server.

Fixes in this Release

The following issues were resolved in this release.

Component Fix
Streaming Issues
  • Office 2004 streaming on Vista is slow
  • SVS, Photoshop package streams slowly
Client
  • Adding throttling to client
  • AutoDesk Map 3D does not work thru squid prox
  • Appmgr Cmdline does not fetch offline blocks 
  • Fix for blue screen issues with McAfee Antivirus. 
  • Unable to stream any package - in Build 5.2.0.89.
  • Several debug messages appear while installing or uninstalling the client, if c:\debug.txt exists
  • Does not support Squid proxy. Applications fail to stream. And there is a communication failure.
  • User-provision page functionality documented in the Admin Guide.
  • License is not getting removed for Conventionally installed applications.
  • Display of message “Entry point not found” while using AppMgrCmd command.
  • Prompts the user to launch application from the portal when application was installed on a different user account.
  • Problem while upgrading Adobe Reader SVS package.
  • Application Manager service and GUI not started automatically after client silent install.
  • Several pop ups and windows attack the user's desktop.
  • Windows XP SP2 crashes if Streaming client IE Add-On is disabled.
  • Client not installed in locale specific equivalent of Program Files.
Streaming Server
  • Tomcat Thread Leak Issue
  • Upgrading the server which has patch will result in STE init error
  • Server upgrade from 4.6 patch 7 to 5.1, failed when server is installed in non-root drive.
  • Prepopulation of icons for SVS packages are now enabled.
  • Host Machine name not displayed in Unique Client Install report for Upgraded packages.
  • Backward compatibility with AppStream 5.0 is now enabled in AppStream 5.2.
  • STS fails to start after clean single-node installation with MySQL.
  • JRE installation is not carried out.
  • Unable to Upgrade server with Read only files.
  • Version enabling failed in Child STE
Streaming Composer
  • Packaging Studio not deleting entries from INI files on upgrades  
  • Streaming Composer cannot handle Office 2007 advertised shortcuts or make all components local
Application Manager
  • Unable to retrieve offline blocks when offline is enabled after reboot and applications in the package (which integrates with Explorer) have never been launched on systems with an Anti-virus
  • Blue Screen while upgrading the client in win2k.
  • Provision enters a bad state when synchronize is canceled.
  • "Cancel Offline Streaming" menu option does not work properly. 
  • Cannot run process from the cache when using post-installation script.
Server - Control & Management
  • Report on Licenses consumed by user, displays the same username.
  • Unable to upload any package when SSL feature for C&M is enabled.
  • Shortcuts to paths & files that contain a single quote are not handled correctly when launched from the portal page.
  • Punch Software: Able to upload punch software only using Command line and not from GUI.
  • Failure to launch package upload window using DNS name on dual nic server with single nic install.
  • Package Upload Client does not remember last folder.
  • Package upload limit resets after server upgrade.
Streamlet Engine
  • Pre-population of icons does not work for exported package.
Database
  • MSSQL should be installed in NTFS mode to overcome memory issue. 
Launch Server
  • Portal login with full URL fails when cookies enabled.
Drivers
  • Blue Screen while running RegMon and AppStream driver(s) stop.
  • New drivers for build 5.0.1.30 have version set to 5.0.1.19.

Known Issues in this Release

The following are unresolved issues in this release.

Known Issues
Incorrect error message when attempting to connect to an off-box SQL server

If you install Altiris Streaming Server on a computer that does not have a SQL agent or SQL server installed and you try to connect to an off-box SQL server, you get an error message similar to the following:

sqlcmd.exe is not available in the MSSSQL 2005 server installed path

The error message should state that the sqlcmd.exe must be installed on the same computer as the Altiris Streaming Server.

To resolve this problem, do one of the following:

  • Install the sqlnative client on the computer where you install Altiris Streaming Server.
  • Copy sqlcmd.exe from the MSSQL server to the local machine and put it in a directory that is accessible from %PATH%.
Upload could fail while uploading multiple packages with default PostgreSQL database
To work around this issue, perform the following steps on the Streaming Server computer:
  1. From the Start menu open pgAdminIII > PostgreSQL Database Server 8.2.
  2. Type the password specified during server installation (the default password may be postgres#123 or "change on install").
  3. Expand Databases. Click Appstream. Go to Tools > Server Status.
  4. On the Status tab, check if there are any queries running – this can be identified by looking in the Query column and checking whether a query is listed as <IDLE> or not. If a query is not listed as <IDLE>, it could be one of the queries still running. Take note of the smallest PID (typically in the first column) of all running queries.
  5. Click on the Locks tab and take note of the list of transactions running and being locked.
  6. Select the first transaction with a previously identified PID. Click Cancel in the lower left corner.
  7. The lock should disappear. If it does not, repeat the above steps until all locks disappear.
  8. Go to the Windows Services panel and restart the "AWE Streamlet Engine" service.

Additional Documentation

Altiris Information Resources

Source What Information it Includes Location
Altiris Documentation Information about new features, update instructions, and known issues for each release. Includes Altiris formal documentation such as release notes, help, reference guides, best practice articles, and technical reference articles. http://www.altiris.com/support/documentation
Altiris Knowledgebase Comprehensive collection of articles, incidents, and issues for Altiris solutions. http://kb.altiris.com/
Altiris Juice:
an online magazine for Altiris users
Best practices, tips and tricks, and articles for users of Altiris solutions. http://www.altiris.com/juice
Online Forums Forums for Altiris solutions and suites. http://forums.altiris.com/

Document History

Date Changes
02/21/2008 Finalized for the 5.2.2 release.

Legacy ID



39314


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


Terms of use for this information are found in Legal Notices