Ardence

Ardence 4.1 SP2 Software-Streaming Platform Release Notes

P/N ARD-5RN-4.1.SP2-R02 Document Rev 03 September 2007

Copyright 2007 by Ardence, a Citrix company. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means, graphic, electronic, or mechanical, including photocopying, and recording or by any information storage or retrieval system without the prior written permission of Ardence, Inc., unless such copying is expressly permitted by federal copyright law.

Disclaimer
While every effort has been made to ensure the accuracy and completeness of all information in this document, Ardence, Inc. assumes no liability to any party for any loss or damage caused by errors or omissions or by statements of any kind in this document, its updates, supplements, or special editions, whether such errors, omissions, or statements result from negligence, accident, or any other cause. Ardence, Inc. further assumes no liability arising out of the application or use of any product or system described herein; nor any liability for incidental or consequential damages arising from the use of this document. Ardence, Inc. disclaims all warranties regarding the information contained herein, whether expressed, implied or statutory, including implied warranties of merchantability or fitness for a particular purpose. Ardence, Inc. reserves the right to make changes to this document or to the products described herein without further notice.

Trademarks
Ardence is a trademark of Ardence, Inc. Microsoft and Windows are registered trademarks of Microsoft Corporation. 3Com is a registered trademark of 3Com Corporation; Ardence PXE, Ardence BOOTP, and Ardence BOOTPTAB Editor were built using technology developed and owned by 3Com Corporation. All other companies and product names may be trademarks or registered trademarks of their respective holders.

Third Party Code

Copyright (c) 1998-2005 The OpenSSL Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)" 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org. 5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project. 6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http:// www.openssl.org/)" THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Version Information Ardence 4.1 SP2 Ardence Software-Streaming Platform Release Notes P/N ARD-5PD-4.1.SP2-R02 September 2007

About These Release Notes

Purpose
The purpose of these Release Notes is to identify new product features and enhancements, as well as any known or fixed issues. These Release Notes may also contain any last minute information that was not included in the product documentation.

Audience
This document is written for Ardence administrators who are responsible for installing and configuring Ardence software. It assumes users have network, system administration, Windows operating system, and previous Ardence product knowledge and other system level knowledge.

Organization
This Release Notes document includes the following sections: Additional References .................................................................................................... 4 If You Need Support........................................................................................................ 6 Ardence Editions............................................................................................................. 7 Fixes in Release 4.1 SP2 ................................................................................................ 7 Fixes in 4.1 SP1 ............................................................................................................. 12 Known Issues and Limitations .................................................................................... 15 New Features and Enhancements in 4.1 and SP1 ..................................................... 17 Supported 32 Bit Linux Distributions and Kernels .................................................... 27 Supported 64 Bit Linux Distributions and Kernels .................................................... 30

Additional References
This section lists and describes supporting documentation for this Ardence release. Ardence PDF documents become available from the Ardence product installation after the Ardence installation executable is run. After installing Ardence, these documents also become available from:
Start>All Programs>Ardence Software-Streaming Platform>Documentation

Note: Documentation can also be downloaded from within the Support Web site.

The Ardence Software-Streaming Platform product documentation includes:

Product Guide
The Product Guide includes information on planning, installing, configuring, and maintaining an Ardence implementation. This guide is intended to be read after the Ardence Release Notes. This document is also available from the Ardence Administrators Help drop-down menu.

Administrator Online Help (Professional/Corporate Editions or Secure Edition)

The Administrator Online Help provides information necessary to complete system configuration and management tasks using the Ardence Administrator. This help system is intended to be referenced while completing tasks using the interface. This help system is available from the Help menu on the Ardence Administrator. Context-sensitive dialog box help is available from the Help button or by pressing the F1 key when the dialog box is active.
Note: Not all dialog boxes have Help buttons. To view all help topics, open the Ardence Administrator Online Help from the Help menu.

Ardence Device Client User Guide

This guide provides the information necessary to install and configure Device Client.

Ardence Product Licensing for Professional Edition

This guide provides the information necessary to license Ardence Clients for Professional Edition users.

Ardence vDisk Status Tray Help

This Ardence help system is available from the Ardence Clients status tray. The online help defines status information associated with vDisks that are assigned to a client.

Ardence Management Interface Guide

This guide provides the information necessary to configure and manage the Ardence Software-Streaming platform using an application programming interface (API).

If You Need Support

If you have trouble with your Ardence network, refer to the Product Guide or Help system. If additional help is necessary, contact Ardence Technical Support or your local Ardence distributor. Based on your support agreement, Technical Support may be accessed through the following:

Web Site Support

To use the Ardence Support Web site, go to https:\\support.ardence.com. With a valid login ID, access the online problem report database to submit new issues, or to obtain the status of previously reported issues. From this site, you can also access Technical Notes and product downloads.

Telephone Support
Within the United States

Call technical support at 1 (800) 334-8649 between 8:30 a.m. and 5:30 p.m. Eastern time (excluding weekends and holidays).
Outside the United States

Call technical support at 1 (781) 647-3000 between 8:30 a.m. and 5:30 p.m. Eastern Time (excluding weekends and holidays).

Ardence Editions
This section lists the Ardence Editions that are supported in this release as well as valid platforms. For hardware and software requirements, refer to Module 2: Installing and Configuring Ardence in the Ardence Software-Streaming Platform Guide.

Supported Ardence Editions

This release supports the following Ardence Editions: Corporate Edition Professional Edition Secure Edition

Notes:
High Availability is a licensed option. For hardware and software requirements, refer to Module 2 in the Product Guide. 4.1 SP2 includes all relevant hot fixes issued against previous releases.

Fixes in Release 4.1 SP2

Administrator
5683 - Secure client cannot boot to separate network segment, when Boot Device is configured from Management Console. 5814 Display message on client feature for Vista Client, now displays the message. 5819 - GetClientInfo does not write the client personality data to the registry correctly. After issuing the GetClientInfo FieldName /r=RegistryKeyPath command, only one half of the Client personality data is written to the client registry. 5830 Streaming service crashes when the database is on a share and looses connection for approximately 40 seconds or longer.

5851 Clients with 15 or more characters cannot login to the Active Directory domain. 5856 Command "AutoUpdate info deltafile" displays distorted data. 5884 - Mapping/unmapping a vdisk would sometimes cause BSOD on server

Client
5540 Client-side cache with Intel AMT fails to boot on some machines. 5717 - NEC AMT Machine boots slowly. 5781 Unreadable message in client shutdown dialog box on x64 systems. 5806 - Cannot boot Linux client using 1G or more RAM side cache. What was addressed in the code is that when excessive amounts of RAM are requested, the actual amount gets reset to the maximum value, somewhere around 780MB. The system is fully operational albeit with the smaller amount of RAM cache than requested. Please see the list of known limitations for more information on this subject. 5830 - When the cable of the server hosting the Ardence database is unplugged, the next client to boot will crash the login server. 5848 - While in boot process some clients would halt with the following message displayed: Connecting to the Ardence services. Please wait..... It is unpredictable which clients will hang. This issue is more reproducible as the number of Ardence clients increases on the network. 5990 When booting Vista the following message appears in the system event log; Driver detect controller error in \Device\Hardisk1\DR1 6122 Random characters seen with client TCPIP property when using static IP. 6258 HP Blade with multi-function NIC #NC373m fails to connect to vDisk. (using NIC driver; 3.4.10.0 or 3.0.7.0) 5896 Client system tray displays red X if logged in with non-Administrator account however the client functions normally.

Image Builder
3846 During Linux vdisk build process when user tries to build a vdisk using a vdisk in shared mode, the client does not give an error message. 5704 vDisk image corrupted do to lack of disk space.

5862 Reverse imaging on Vista is now supported. 5946 - During Linux vdisk build process the following diagnostic would be displayed: "Ardence imager: could not find virtual disk! Check setting in the Ardence Administrator." The build process would be unsuccessful. 5991 - Customer asked to support multi-homed NICs. 6000 Issue building vDisk of Fedora 4 6085 - Fix for the Linux experimental 'Fedora Core 6' distribution. On certain Pentium 4 HT systems there is a problem building a virtual disk image. 6126 - Creating a Vista virtual disk image takes a very long time. Only occurs on certain systems in certain networks.

Installer
5793 - "Cancel" button is not disabled while installing the Server package. - Starting with the 4.0 release, on Windows 2000 and Windows XP platforms, the following dialog message appears on systems that do not contain Microsoft MSI installer version 3.1 or later:

10

To proceed with installation without the reboot, click OK. This Microsoft issue can be avoided by installing a Windows update file, Windows Installer 3.1 version 2 (3.1.4000.2435) with the name WindowsInstaller-KB893803-x86.exe. For more information about this Microsoft fix, go to:

http://support.microsoft.com/?kbid=893803
For the fix itself, go to:

http://www.microsoft.com/downloads/details.aspx?FamilyID=889482FC-5F56-4A38B838-DE776FD4138C&displaylang=en

Upgrade Wizard
5799 - When upgrading a client that has multiple NICs and only one of the NICs is bound to the Ardence Services, then attempting to modify the other NIC settings would result in a BSOD 5844 Added functionality to force upgrade in the Upgrade Wizard using a vdisk from the current or prior release. 6215 Automatic vDisk update does not preserve the state of software management attribute settings.

Utilities
5874 - Ardence Configuration wizard displays incorrect geometry for Japanese fonts. This symptom does not occur on English version of Windows. 6238 On the Configuration Wizard Define the location of the Ardence database is misleading.

Documentation
5289 Software Tab help link from the Client Status Tray does not work.

11

Fixes in 4.1 SP1

Product Licensing for Professional Edition
5345 When product license counts were updated (registering, installing, or returning licenses) the updates did not always appear in the counts without requiring that the Streaming Service be restarted. Licensing information is now managed dynamically without needing to restart the Streaming Service. 5449 When the Show Licenses right-click menu option is selected on the Ardence License Manager, the Linux client licenses did not display. The Linux client licenses now display correctly. 5286 Input Fields in Product License Manager unclear. The input field in focus is now highlighted.

Administrator
4927 A vDisk can no longer be deleted from the database when the .lok file is still active. 5543 A user can no longer unassign a vDisk from active clients. 5665 The Rebalance Clients feature appeared enabled for non-HA deployments. This feature now appears disabled for non-HA deployments. Also, in HA deployments, if there is more than one server and it is selected, a check is done to see if there are any disks with the same name on active servers that have LICENSE_OPTION_HA set. If none are found, the following message appears: No HA disks found that exist on more than one active server. Rebalance is only used with HA. 5727 When the vDisk cache is set to client RAM cache, the Altiris SVS applications did not appear dynamically on the client

5736 When run from an RDP session, the Administrator incorrectly indicates that the server status as off, when it is on. Now, the server status appears correctly. Also, in the RDP session, remote Ardence servers cannot add/create vdisks. Resolved now.

Documentation

12

4894 In Ardence Administrator Help->Managing VDisks->Configuring VDisk Access modes->Configuring a VDisk for Shared, "Shared image mode with encrypted client cache" link has been fixed. 5530 The 4.1 product documentation does not include the different versions of Vista that is supported by Ardence. 5755 The Upgrade Wizard inaccurately stated that the Ardence Database for 4.X versions must be upgraded. For 4.X, the upgrade wizard only needs to be run to upgrade vDisks to the current version. 5756 The link to product documentation on the Support Web site was removed from documentation. Users must first enter the Support Web site using a valid user name and password before they can navigate to Ardence Product documentation.

Image Builder
5209 Image Builder does not work in reverse. Sometimes, after clicking OK to transfer an image from a vDisk to a local hard drive, the following error message appeared: The client image build process has been canceled. The selected destination path may contain files copied during the build, but the path does not include a complete system image. In addition, after a successful transfer of a Common Image from a vDisk to a local hard drive, when the client starts to boot off the local hard drive, the following message might appear: Windows could not start because the following file is missing or corrupt: Windows\System32\Hal.dll Both issues are now resolved. 5050 After booting from a vDisk, and then adding a new domain user, the account profile would be created but the shortcut images did not display. The images now display appropriately. 4925 Sometimes, the original file attributes of the vDisk were not captured correctly during the vDisk was built. Those attributes are now captured correctly. 5324 Windows command GPRESULT.EXE does not work in an Ardence Image.

13

5505 For Ardence 4.1 clients running on Windows 2003 SP1 or R2, Image Builder fails when a terminal server is installed. In this release, Image Builder no longer fails when a terminal server is installed.

SetComputerAccount Utility
5427 Occasionally, when running SetComputerAccount.exe, internal debug messages that should not appear would appear. These messages were suppressed. 5746 SetComputerAccount utility not adding client machine account into Active Directory correctly.

Upgrade Wizard
4954 The Upgrade Wizard could not upgrade a vDisk with a space in its name. Similarly, the BNMAPCL command-line tool cannot map a vDisk with a space in its name. This issue has been resolved to support spaces within names. 5320 Upgrade Wizard corrupts database and Vdisks in HA environment. 5326 The Upgrade process for 4.0 to 4.1 is not available. The 4.1 Upgrade Wizard would not locate the vDisk created in the 4.0 release during the upgrade process. In this release, the Upgrade Wizard works appropriately. 5731 If the database contains multiple vDisks with the same name for different servers, and the Upgrade Wizard is run on a server other than the one matching the first vDisk record in the database, the vDisk upgrade fails. This also occurs if running the Upgrade Wizard stand-alone with just the vDisk name (no server name). In either case, the following message appears:

Error:

request to lock disk failed - (status = -32712)

This issue is resolved and no longer causes the upgrade to fail.

Utilities
5366 In the Ardence 3.5.2, 4.0, and 4.1 releases, the Configuration Wizard does not add Option 60 to a Microsoft DHCP server, when Ardence PXE is chosen. In this release, Option 60 is added for a Microsoft DHCP server if the Ardence PXE is chosen. 5543 The BootpTab editor utility does not work in Ardence 4.1, but does work in this release.

14

Known Issues and Limitations

This section lists and describes known issues and limitations that apply to this Ardence release.
Note: Refer to the release notes for a prior Ardence release, to view known issues and limitations specific to that release.

Administrator
5335 Secure Boot Devices, other than SDOM, can not be programmed on Windows 2000. 5517 - Vista Issue: Locks and Client Status Not Accurate When Ardence Booted Vista Client Shutdown 6303 - 64 bit Ardence client may freeze while booting with ram side cache (works with other cache mode). Enabling PAE in the bootstrap makes it work.

Installation
4935 The first screen that appears after running the Ardence install package is an Error 1603 message that indicates that some files required by the installer may be in use by other applications. Clicking OK allows the user to proceed and complete the installation. This issue is a tradeoff made in release 4.0 for the requirement to minimize reboots. The alternative is to allow the Ardence installer prerequisite (Windows Installer Engine 3.1) to install, reboot, and then proceed with the Ardence Server or Client Setup. 5487 Unable to install the Ardence Software for use by a specific user.

Licensing
5678 When the License Manager is offline, the License History numbers may not display accurately. For example, attempting to install licenses that appear available will fail because the information cannot be retrieved from, or updated by, Ardence Corporation. Some users confuse the concept of available licenses with licenses that are installed. The number of available licenses represents the number of licenses that have been registered with Ardence Corporation and are available (not yet installed) from Ardence. After installing a number of licenses from the pool of available licenses at Ardence, those

15

licenses become usable within that particular server farm, and the number of licenses that were available are decreased by that amount. 6357 Cannot enter the Ardence License Manager after importing a .vlf file when the 25th character of the username or password is a .

Upgrade Wizard
6288 Vista Issue: The Vista OS Security Model prevents the Upgrade Wizard from upgrading the system level device drivers. If attempted, the Access Denied message is generated in the UpgradeWizard.log file. 6289 Upgrade Wizard does not currently support upgrading an x64 vDisk. 6424 Upgrading multiple Vdisks from 4.1 to 4.1 SP2 using the UpgradeWizard fails after the first 2 upgrades.

Linux Client
5806 - Cannot boot Linux client using 1G or more RAM side cache. This is Linux kernel size limitation. Please see section Physical memory zone in the http://www128.ibm.com/developerworks/linux/library/l-memmod/ Linux Memory Model description.

Disk Imaging
The disk imaging process aborts while attempting to generate a vDisk for the Vista SP1 Beta OS.

16

New Features and Enhancements in 4.1 and SP1

This section lists major features and enhancements that are included in this release. Features or enhancements are applicable to all Ardence editions, unless otherwise noted.

Administrator
5443 The Copy client properties feature in the Ardence Administrator now includes the option to copy Port Blocker settings. 5627 Provided a mechanism to set the vDisk name and mode. They could not be entered in the client personality string. The following new reserve values have been included in the [StringData] section of the ClientPersonality.ini file to allow that information to be entered: $DiskName=<xx> $DiskMode=<Private or Shared> The xx is the name of the disk. A vDisk name cannot start with a $. This symbol is used for reserved values such as $DiskName and $DiskMode. The following message displays if a name that starts with $ is entered: A name cannot start with a $. This is used for reserve values like $DiskName and $DiskMode. The $DiskName and $DiskMode values can be retrieved on the client using GetClientInfo. 5400 The Ardence Streaming-Service and License Manager no longer require disabling of the Microsoft Data Execution Protection (DEP) feature.

17

Manage Client Domain Members from the Administrator

In the SetComputerAccount utility, the ability to add/remove clients from/to a domain has been integrated into the Administrator as menu options. The tasks that follow describe how to use this new feature.

Add Clients to a Domain

To add clients to a domain: 1. Right-click on one or more clients in the Administrator window, then select the Add Client to Domain menu option. The Add to Domain dialog appears:

2. Enter the Domain Controller that the clients should be added to, or leave the text box blank and the first Domain Controller found is used. 3. Click OK to add the selected clients to the domain. A status message appears to indicate if each client was successfully added or not.

18

Remove Clients from a Domain

To remove clients from a Domain: 1. Right-click on one or more clients in the Administrator window, then select the Remove Client from Domain menu option. The Remove from Domain dialog appears:

2. Enter the Domain Controller that the clients should be removed from, or leave the text box blank and the first Domain Controller found is used. 3. Click OK to remove the selected clients from the domain. A status message appears to indicate if each client was successfully added or not.

19

Client Groups
The new Client Group feature provides a method to quickly manage multiple clients at a group level. Groups are typically created according to business needs. For example, a group can represent a physical location, such as a building, or user type, such as a customer service representative. After the feature is enabled, groups are created, and clients are assigned as members to one or more of those groups. Group information appears in the Administrator Tree as illustrated below.

Using this feature, a single task can quickly be applied to all members of a group. For example, a vDisk can be assigned to all members within a group simply by dragging that vDisk and dropping it onto a Group. Each time a new client is added to the Ardence network, it is automatically placed in the default group labeled Clients Not Assigned. If a client becomes a member of a Group, the client no longer appears in the Clients Not Assigned group.
Note: Currently, the Group feature does not support sub-grouping.

20

Using the Client Groups Feature

This section describes how to use Group features using the Ardence Administrator. The Group feature is not enabled by default. To begin using Group features, enable the feature:
Note: Group settings are saved when selected, and will reappear if the Administrator restarts.

Enabling the Group Feature To enable Groups:

1. Open the Ardence Administrator, then right-click in the Details View.

2. Press Ctrl-G. The Technology Preview window appears:

21

3. Read the End User License Agreement, and then select Yes to continue (the Yes button is enabled after scrolling to the end of the agreement). Groups are now enabled and the Groups icon displays in the Administrator toolbar:

Disabling the Group Feature To disable the feature, open the Ardence Administrator, right-click in the Details View, and then press Ctrl-G. The Group feature is now disabled. Group information does not appear in the Administrator, toolbar, or menus.
Note: If the Group feature is re-enabled, Group (and clients assigned to those groups), which existed prior to disabling the feature, reappear in the Administrator. To temporarily disable the feature (disables menu options and the tool bar group icon, removes group information from the Tree and Details Views), refer to the Viewing Groups.

Group Tasks After the Group feature is enabled, the following tasks can be performed using the Ardence Administrator: Creating a New Group Viewing Groups Displaying Group Properties Deleting Groups Removing Clients From a Group Booting or Rebooting a Group of Clients Shutting Down Groups Marking Groups as Down Displaying Messages to a Group of Clients

Note: With the exception of the Remove task, any task that can be performed on a Client can also be performed on a client that is a member of a Group.

22

Creating a New Group of Clients To create a new Group: 1. Verify that Groups are enabled on the Administrator. 2. From the File>New menu, select the Groups menu option. The Group Properties dialog displays:

3. Enter a name for the new group in the Name text box. 4. Select the Member checkbox next to each client that belongs in this new group, or right-click in the client area, and then select the All Members menu option to include all clients in this group. Tasks that are performed on this group will now apply to all clients in that group.
Note: Members of the group can alternatively be assigned to a different group by dragging copies of one or more clients selected in the Tree or Details View, onto the appropriate Group in the Tree.

23

Viewing Groups The Groups feature can be temporarily disabled on the Administrator so that group information does not display in the Tree or Details view. However, unlike the Disabling Groups option, group menu options and the group toolbar icon display, are disabled. To view group information in the Administrator, select the disabled Groups menu option from the View menu or the disabled Groups icon in the toolbar. To hide group information in the Administrator, select the enabled Groups menu option from the View menu, or the enabled Groups icon in the toolbar. Displaying Group Properties To view the properties of an existing group, right-click on that group in the Administrator Tree view, then select the Properties menu option. The Group Properties dialog appears. Properties include the name of the Group and the Members (clients) that belong to that group. Deleting an Existing Group To delete a Group: 1. Right-click a group in the Administrator Tree view, then select the Delete menu option. The delete confirmation message appears. 2. Deleting the group removes the clients from the group and then deletes the group. Click Yes to verify the delete action.

Removing Clients from a Group To remove a client: In the Administrator Tree View, right-click on the client, then select the Remove menu option.
Note: Deleting a client from the Ardence network automatically removes that client from any group that client was a member of.

24

Booting or Rebooting a Group of Clients To boot or reboot a group of clients, right-click on the group in the Tree View, then select either the Boot group or Reboot group menu option. Shutting Down a Group of Clients To shut down a group of clients, right-click on the group in the Tree View, then select the Shutdown group menu option. Marking a Group of Clients as Down If a group of clients are down and they are not displaying in the Administrator as down, right-click on the Group, then select the Mark Group as down menu option. All clients within that group now appear with black screens. As each client reboots, the client screen in the Administrator turns green. The number of seconds this takes to occur may depend on the Refresh options dialog settings.
Note: To view Refresh option settings, select the Refresh options menu item from the View menu.

Displaying a Message to a Group of Clients To display a message to all client members within a group: 1. Right-click on the group in the Tree View, then select the Display message on group menu option. The Display message dialog appears. 2. Enter the message in the Message text box. 3. Click Send to send the message to all clients in this group, or highlight only those clients that should get this message, then click Send. The status column next to each client reports if the message is successfully sent or if it failed to be sent. 4. To exit the dialog, click Close.

25

Documentation
Enhancements have been made to the Ardence Software-Streaming Product Guide. Enhancements include: Reorganizing the order of each module to improve the flow of information. Updating the content to include product enhancements previously noted in the 4.1 Release Notes. Improving the product upgrade information. Vista version information.

The Release Notes and Product Guide are the only product documents revised for this service-pack release.

26

Supported 32 Bit Linux Distributions and Kernels

Fedora Core 2

2.6.10-1.771_FC2 2.6.10-1.771_FC2smp 2.6.5-1.358 2.6.5-1.358smp

Fedora Core 3

2.6.9-1.667 2.6.9-1.667smp 2.6.12-1.1372_FC3 2.6.12-1.1372_FC3smp

Fedora Core 4

2.6.11-1.1369_FC4 2.6.11-1.1369_FC4smp 2.6.13-1.1532_FC4 2.6.13-1.1532_FC4smp 2.6.14-1.1637_FC4 2.6.14-1.1637_FC4smp 2.6.16-1.2115_FC4 2.6.16.1.2115_FC4smp 2.6.17-1.2142_FC4 2.6.17-1.2142_FCsmp
Fedora Core 5

2.6.17-1.2139_FC5 2.6.17-1.2139_FC5smp 2.6.17-1.2145_FC5 2.6.17-1.2145_FC5smp 2.6.17-1.2157_FC5 2.6.17-1.2157_FC5smp 2.6.18-1.2200_FC5 2.6.18-1.2220_FC5smp 2.6.18-1.2239_FC5 2.6.18-1.2239_FC5smp
Fedora Core 6

2.6.18-1.2798_FC6 2.6.18-1.2849_FC6 2.6.20-1.2062.fc6

27

RedHat Enterprise 4 Workstation, AS and ES

2.6.9-5.EL 2.6.9-5.ELsmp 2.6.9-11.EL 2.6.9-11.ELsmp 2.6.9-22.ELsmp 2.6.9-22.EL 2.6.9-22.0.1.EL 2.6.9-22.0.1.ELsmp 2.6.9-34.EL 2.6.9-34.ELsmp 2.6.9-34.0.1.EL 2.6.9-34.0.1.ELsmp 2.6.9-34.0.2.EL 2.6.9-34.0.2.ELsmp 2.6.9-42.EL 2.6.9-42.ELsmp 2.6.9-42.0.2.EL 2.6.9-42.0.2.ELsmp 2.6.9-42.0.3.EL 2.6.9-42.0.3.ELsmp 2.6.9-55.EL 2.6.9-55.EL-smp 2.6.9-55.0.2.EL 2.6.9-55.0.2.EL-smp 2.6.9-55.0.6.EL 2.6.9-55.0.6.EL-smp
Novel Linux Desktop 9/SuSE Linux Enterprise Server 9

2.6.5-7.97-default 2.6.5-7.97-smp 2.6.5-7.111-default 2.6.5-7.111-smp 2.6.5-7.145-default 2.6.5-7.145-smp 2.6.5-7.191-default 2.6.5-7.191-smp 2.6.5-7.244-default 2.6.5-7.244-smp 2.6.5-7.276-default 2.6.5-7.276-smp 2.6.5-7.282-default 2.6.5-7.282-smp

28

SuSE Linux Enterprise Desktop 10/SuSE Linux Enterprise Server 10

2.6.16.21-0.8-default 2.6.16.21-0.8-smp 2.6.16.21-0.25-default 2.6.16.21-0.25-smp 2.6.16.27-0.9-default 2.6.16.27-0.9-smp 2.6.16.46-0.12-default 2.6.16.46-0.12-smp 2.6.16.46-0.14-default 2.6.16.46-0.14-smp
SuSE Professional 9.3

2.6.11.4-20a-default 2.6.11.4-20a-smp
SuSE Linux 10.0

2.6.13-15-default 2.6.13-15-smp 2.6.13-15.12-default 2.6.13-15.12-smp

SuSE Linux 10.1

2.6.16.13-4-default 2.6.16.13-4-smp
Turbo Linux FUJI 11

2.6.13-3 2.6.13-3smp 2.6.13-7 2.6.13-7smp 2.6.13-15 2.6.13-15smp 2.6.13-19 2.6.13-19smp

29

Supported 64 Bit Linux Distributions and Kernels

RedHat Enterprise 4 Workstation, AS, and ES

2.6.9-5.EL 2.6.9-5.ELsmp 2.6.9-11.EL 2.6.9-11.ELsmp 2.6.9-22.ELsmp 2.6.9-22.EL 2.6.9-22.0.1.EL 2.6.9-22.0.1.ELsmp 2.6.9-34.EL 2.6.9-34.ELsmp 2.6.9-34.0.1.EL 2.6.9-34.0.1.ELsmp 2.6.9-34.0.2.EL 2.6.9-34.0.2.ELsmp 2.6.9-42.EL 2.6.9-42.ELsmp 2.6.9-42.0.2.EL 2.6.9-42.0.2.ELsmp 2.6.9-42.0.3.EL 2.6.9-42.0.3.ELsmp 2.6.9-55.EL 2.6.9-55.EL-smp 2.6.9-55.0.2.EL 2.6.9-55.0.2.EL-smp 2.6.9-55.0.6.EL 2.6.9-55.0.6.EL-smp
SuSE Linux Enterprise Desktop 10/SuSE Linux Enterprise Server 10

2.6.16.21-0.8-default 2.6.16.21-0.8-smp 2.6.16.21-0.25-default 2.6.16.21-0.25-smp 2.6.16.27-0.9-default 2.6.16.27-0.9-smp 2.6.16.46-0.12-default 2.6.16.46-0.12-smp 2.6.16.46-0.14-default 2.6.16.46-0.14-smp 30