C H A P T E R 2 |
The following table lists the end-of-support dates for SGD products.
Software and Version | End of Full Support | End of Limited Support | End of Service Life |
---|---|---|---|
Sun Secure Global Desktop Software 4.40 | February 3, 2010 | February 3, 2014 | February 3, 2014 |
Sun Secure Global Desktop Software 4.31 | May 19, 2009 | May 19, 2013 | May 19, 2013 |
Sun Secure Global Desktop Software 4.3 | April 29, 2009 | April 29, 2013 | April 29, 2013 |
Sun Secure Global Desktop Software 4.2 | November 8, 2008 | November 8, 2012 | November 8, 2012 |
Secure Global Desktop Enterprise Edition 4.1 | March 31, 2007 | ||
Secure Global Desktop Enterprise Edition 4.0 | March 31, 2007 | ||
Secure Global Desktop Software Appliance 4.0 | March 31, 2007 | ||
Secure Global Desktop Enterprise Edition 3.44[1] | December 31, 2007 | ||
Secure Global Desktop Enterprise Edition 3.42 | March 31, 2007 | ||
Tarantella Enterprise 3 (including TASP) | March 31, 2007 |
For details of the Sun End of Service Life (EOSL) Policy, see http://www.sun.com/service/eosl/.
Customers with a valid support agreement can upgrade to the latest version of SGD free of charge.
Changes to the supported platforms for the release following SGD version 4.41 are as follows:
SGD servers. OpenSolaris is supported as an SGD server installation platform in this release. Solaris OS 8, Solaris OS 9, Red Hat Enterprise Linux 4, Fedora Linux 8, and SUSE Linux Enterprise Server 9 are not supported.
The following table lists the supported installation platforms for the next release.
Operating System | Supported Versions |
---|---|
Solaris![]() |
10, 10 Trusted Extensions |
Solaris OS on x86 platforms | 10, 10 Trusted Extensions |
OpenSolaris on x86 platforms | Latest version |
Red Hat Enterprise Linux (Intel x86 32-bit) | 5 |
SUSE Linux Enterprise Server (Intel x86 32‐bit) | 10 |
SGD Enhancement Module. OpenSolaris is supported as an installation platform for the SGD Enhancement Module in this release. Windows 2000 Server, Red Hat Enterprise Linux 4, Fedora Linux 8, SUSE Linux Enterprise Server 9, and SUSE Linux Enterprise Server 10 are not supported.
The following table lists the supported installation platforms for the SGD Enhancement Module in the next release.
Client platforms. OpenSolaris is a supported client platform for this release. Solaris 8 OS, Solaris 9 OS, Microsoft Windows 2000 Professional, Fedora Linux 8, and SUSE Linux Enterprise Desktop 10 are not supported in this release. The Internet Explorer 6.0 browser is not supported.
The following table lists the supported client platforms for the SGD Client in the next release. Also included are the supported browsers.
Supported Client Platform | Supported Browsers |
---|---|
Microsoft Windows Vista | Internet Explorer 7.0+ |
Microsoft Windows XP Professional | Internet Explorer 7.0+ |
OpenSolaris on x86 platforms (latest version) | Mozilla Firefox 2.0+ |
Solaris 10 OS on SPARC platforms | Mozilla Firefox 2.0+ |
Solaris 10 OS on x86 platforms | Mozilla Firefox 2.0+ |
Solaris 10 OS Trusted Extensions on x86 platforms | Mozilla Firefox 2.0+ |
Mac OS X 10.4+, 10.5+ | Safari 2.0+ |
Red Hat Desktop (latest version) | Mozilla Firefox 2.0+ |
Ubuntu (latest version) | Mozilla Firefox 2.0+ |
This section lists the known bugs and issues with SGD version 4.41.
Problem: SGD X and character emulators cannot distinguish between the Return key and the keypad Enter key on the user’s client keyboard.
Solution: By default, the SGD Client maps the keypad Enter key to Return in both X and character application sessions. With additional configuration, this behavior can be changed.
To change the behavior of the keypad Enter key in a character application session, you need to set up a keymap for your character application object (--keymap) and add a mapping for KPENTER, for example:
To change the behavior of the keypad Enter key in a Windows or X application session, you need to modify your X keymap, for example xuniversal.txt, and add a mapping for the KP_Enter key, for example:
92 KP_Enter KP_Enter NoSymbol NoSymbol 0x801c
Problem: Proxy server automatic configuration scripts can specify a list of proxy servers to try. If the first proxy server in the list is unavailable, the browser tries the other proxy servers in turn until it finds one that is available.
If you are using Microsoft Internet Explorer with Sun Java Plug-in tool version 1.5.0, only the first proxy server in the list is used. If that proxy server is not available, the connection fails.
Problem: On Solaris 10 x86 platforms, enabling Integrated mode when you are logged in as the root user does not add applications to the Solaris 10 Launch menu. You might also see the following warning:
gnome-vfs-modules-WARNING **: Error writing vfolder configuration file "//.gnome2/vfolders/applications.vfolder-info": File not found.
Cause: A known issue with the Gnome Virtual File System (VFS).
Problem: On client devices running SUSE Linux Enterprise Server 10, the Gnome Main Menu crashes when using the SGD Client in Integrated mode. The crash usually occurs on login or logout.
Cause: A known problem with the Gnome Main Menu applet on SUSE Linux Enterprise Server 10 (Novell bug reference 186555).
Solution: Install the latest version of the gnome-main-menu.rpm package for SUSE Linux Enterprise Server 10.
Alternatively, disabling the Recently Used Applications functionality improves the stability of the Gnome Main Menu. Run the following commands on the client device:
$ gconftool-2 --set --type=list --list-type=int \ /desktop/gnome/applications/main-menu/lock‐down/showable_file_types [0,2] $ pkill main-menu $ pkill application-browser |
Problem: After enabling Automatic Client Login or Integrated mode, the SGD Client does not start automatically when you log in to the Gnome Desktop and the Start menu is not updated with webtop content when you log in to SGD. This problem affects SUSE Linux Enterprise Server 9 and Red Hat Enterprise Linux 4.
Cause: The directories containing the .menu files are not monitored and so changes to the Start menu are not detected.
Solution: The workaround is run the pkill gnome-panel command to restart the gnome-panel and pick up new menu information.
Note - You must run the pkill gnome-panel command to update the menu each time the menu changes. |
Problem: Shortcuts for the SGD Client do not display on the KDE Desktop Menu on SUSE Linux Enterprise Server 10.
Cause: SUSE-specific configuration of the KDE menu system means that if a menu contains only one application entry, then that single application is used in the main menu instead of the menu. If menu entry is a sub-menu, the sub-menu does not display at all. This causes the Login menu for the SGD Client in Integrated mode not to display.
Solution: The workaround is to add the following line to the [menus] section of the $HOME/.kde/share/config/kickerrc file:
ReduceMenuDepth=false
Then run the following command for the KDE panel to immediately pick up the changes:
# dcop kicker kicker restart |
Problem: After upgrading to version 4.40, a server that was configured to accept only secure connections now accepts standard and secure connections.
Solution: Reconfigure the server to accept only secure connections. In the Administration Console, display the Secure Global Desktop Servers -> Security tab for the SGD server and deselect the Standard check box in the Connection Types field. Alternatively, run the following command:
$ tarantella config edit --security-connectiontypes ssl |
Problem: Using Internet Explorer 7 on Microsoft Windows Vista platforms, the SGD Client cannot be downloaded and installed automatically. The SGD Client can be installed manually and can be installed automatically using another browser, such as Firefox.
Cause: Internet Explorer has a Protected Mode that prevents the SGD Client from downloading and installing automatically.
Solution: Add the SGD server to the list of Trusted Sites in Internet Explorer's Security Settings.
Problem: Users in Simplified Chinese and Traditional Chinese locales cannot display non-ASCII characters in the candidate and status windows of the input method when running applications on a Solaris OS application server. This affects Solaris 8 OS, 9 OS, 10 OS, and 10 OS update 1 platforms.
Cause: Missing font path configuration on the SGD server.
Solution: If the application server is running on Solaris 10 OS or Solaris 10 OS update 1, do one of the following:
For SPARC platforms, install patches 120410, 120412, and 120414.
For x86 platforms, install patches 120411, 120413, and 12041.
If the application server is running on Solaris 8 OS or Solaris 9 OS, do one of the following:
Problem: On Sun Java Desktop Systems (JDS), users might find that Launch menu entries are not created for SGD when they enable Integrated mode. The Launch menu entries are added when they log out of their desktop and log in again.
Cause: A known issue with the Gnome panel.
Solution: The solution is to install the following patches:
These patches are included in the Solaris 10 OS update 5 release.
The workaround is to log out of the desktop and log in again.
Problem: If Java technology is enabled in your web browser settings, but a Sun Java Plug-in tool is not installed on the client device, the SGD webtop does not display. The login process halts at the splash screen.
Cause: SGD uses the web browser settings to determine whether to use Java technology.
Solution: Install the Sun Java Plug-in tool and create a symbolic link from the web browser plug-ins directory to the location of the JVM. Refer to your web browser documentation for more information.
Problem: The online help for the Administration Console is disabled when HTTPS connections to the SGD Web Server are enabled.
Cause: The Administration
Console uses the JavaHelp software
to display the online help. Additional configuration is required
to run JavaHelp over an HTTPS connection.
Solution: Import the CA certificate
used to sign the certificate for the SGD Web Server into the JDK software keystore. Use the Java
software keytool application as follows:
$ keytool -import \ -keystore /opt/tarantella/bin/jdk‐version/jre/lib/security/cacerts \ -storepass changeit -file /opt/tarantella/var/tsp/ca.pem |
Where changeit is the password for the keystore and jdk-version is the version of the JDK installed on the SGD server.
If you have more than one certificate in your ca.pem file, separate each certificate and add them individually.
Problem: When using a Canadian French (legacy) keyboard layout with Windows applications, some French characters are printed incorrectly.
Cause: A known issue with Canadian French (legacy) keyboard layouts.
Solution: No known solution. A compatible keymap file is not supplied with SGD at present.
Problem: You cannot add a new secondary server to an SGD array when the Administration Console is running on an existing secondary server.
Cause: In this release, it is not possible to supply credentials for more than one secondary server.
Solution: Run the Administration Console on the primary server, or on the server that is to be joined into the array.
Problem: Custom PDF printer settings are not applied when printing from Windows applications.
For example, if you enable the SGD Universal PDF Printer and Universal PDF Viewer printers for an organizational unit (OU) object. Then, you override the parent objects setting and disable the Universal PDF Printer and Universal PDF Viewer printers for a user in the OU. The custom printer settings are not inherited by the user.
Cause: A known issue when inheriting PDF printer settings.
Solution: No known solution. Configure PDF printer settings at OU or organization level wherever possible, rather than at user level.
Problem: Creating or modifying objects when running the Administration Console on a secondary SGD server returns the following error message: “Object could not be created”.
Cause: The creation or modification of the object is successful, but the Administration Console proceeds before the replicated data has come back from the primary server.
Solution: Wait for a couple of seconds and then repeat the operation.
Problem: Integrated mode does not work correctly for arrays where the SGD load-balancing JSP is being used. The SGD load-balancing JSP, swcd.jsp, is used for load balancing of user sessions.
Solution: No known solution at present. Do not run the SGD Client in Integrated mode when using the load-balancing JSP.
Problem: Users who log in using the LDAP authentication mechanism see a blank webtop.
Cause: LDAP assignment of applications fails if the user object does not match the following LDAP search filter:
(|(objectclass=user)(objectclass=person)(uid=*))
For example, LDAP assignment of applications fails if an LDAP object is of inetOrgPerson object class and does not have a uid attribute.
Solution: In the LDAP directory, ensure that SGD users are of person or user object class. Alternatively, assign a uid attribute to the LDAP object describing the SGD user.
Problem: High CPU usage can be reported when using the SGD Enhancement Module on a Microsoft Windows application server. Processes with high CPU usage can include ttaswm.exe and ttatdm.exe.
Problem: For full-screen Microsoft Windows Vista desktop sessions, the display color depth on the client device is limited to 16-bit.
Cause: A known issue when using SGD to display Microsoft Windows Vista desktop sessions.
Problem: Log in to SGD can be slow when using the Active Directory (AD) authentication mechanism in large AD domains.
Cause: A known issue. The SGD Active Directory authentication mechanism does not always use the nearest domain controller when looking up users.
Problem: On Solaris 10 OS, font errors are reported and there are display problems when starting the VirtualBox software from a JDS desktop session that is displayed using MyDesktop. The problem is seen when using Xsession.jds as the Application Command for the MyDesktop application object.
Cause: Unavailable fonts on the SGD X server.
Solution: When starting the VirtualBox software from the JDS desktop session, use the -fn option to specify valid fonts. Alternatively, install the missing fonts on the SGD server. See the Sun Secure Global Desktop 4.41 Administration Guide for more details about using fonts with SGD.
Problem: If an SGD server is stopped, error messages are returned when starting security services using the tarantella security start command.
Cause: The tarantella security start command is unavailable if the SGD server is not running.
Solution: Start the SGD server first, before using the tarantella security start command.
Problem: SGD audio is not available when using a Linux platform client device.
Cause: The Enlightened Sound Daemon (ESD) is not running on the client device. ESD is usually started when the client device desktop session is started. Otherwise, the daemon must be autospawned by the ESD library on request.
Solution: Ensure that autospawning is enabled in the ESD configuration file. On most Linux platform client devices, this file is at /etc/esd.conf. For Ubuntu client devices, this file is at /etc/esound/esd.conf. The correct setting to make is auto_spawn=1.
Problem: SGD server will not start.
Cause: No available disk space on the SGD server.
Solution: Before starting the SGD server, ensure that sufficient disk space is available. The minimum disk space requirements are listed in the Sun Secure Global Desktop 4.41 Installation Guide.
Problem: The password expiry dialog used for Active Directory authentication does not work correctly. Users are unable to change their password. Additionally, log in to SGD can fail if the user does not enter a domain name.
Cause: A default-_realm entry is not present in the Kerberos configuration file used by the SGD server. The default_realm setting is used by the Kerberos password expiry mechanism. Additionally, for users who log in without typing a domain name, SGD uses the default_realm in cases where the Active Directory Default Domain (--login-ad-default-domain) attribute is not set.
Solution: Edit the Kerberos configuration file used by the SGD server, ensuring a valid entry is present for default_realm. See the Sun Secure Global Desktop 4.41 Administration Guide for more information about the Kerberos configuration file.
Problem: When printing from applications hosted on a Windows 2008 Server application server to a UNIX, Linux, or Mac OS X platform client device, a default client printer is not shown in the Windows application print dialog.
Cause: The default printer driver used by SGD is QMS 1060 Print System. This printer driver is not included with Windows 2008 Server.
Solution: Do either of the following:
Install the QMS 1060 Print System printer driver on the Windows 2008 Server application server.
Edit the global printer configuration file on the SGD server, and specify a different default printer driver. The global printer configuration file is /opt/tarantella/etc/data/default.printerinfo.txt.
Edit the user-specific printer configuration file on the client device, and specify a different default printer driver. The user-specific printer configuration file is $HOME/.tarantella/printerinfo.txt.
See the Sun Secure Global Desktop 4.41 Administration Guide for more details about configuring printer drivers for UNIX, Linux, and Mac OS X platform client devices.
Problem: When using Active Directory authentication, users cannot log in to SGD if SGD is configured to use Secure Sockets Layer (SSL) connections without client certificates to Microsoft Windows Server 2008.
Solution: The workaround is either to use client certificates with SSL connections, or to use the Kerberos protocol, to secure the connection to Microsoft Windows Server 2008.
Problem: The error log for the Apache component of the SGD Web Server contains multiple “Network is unreachable” warning messages. The error log is at /opt/tarantella/webserver/apache/2.2.8_openssl‑0.9.8g_jk1.2.25/logs/error_log.
Although this issue results in large log files, it does not affect the operation of SGD.
Solution: The workaround is to set the LogLevel directive to error in the main Apache configuration file at /opt/tarantella/webserver/apache/2.2.8_openssl‑0.9.8g_jk1.2.25/conf/httpd.conf.
Problem: Installation of SGD version 4.41 can take much longer than expected. The installation procedure halts at the following line:
... Configuring and starting Secure Global Desktop web server... |
Installation eventually completes with no adverse affects.
Cause: A known issue when installing SGD version 4.41. The installation program attempts to access a location on /net/telford.
Problem: Resuming of Windows Terminal Services sessions is not handled correctly when using Session Directory with routing token redirection.
Solution: Use IP address redirection for Session Directory. This is the default setting for Windows Terminal Services.
Problem: Users cannot start applications when using a secure SSL connection to SGD.
Cause: The SGD server is not forwarding connections from the external network interface of the SGD server to the localhost loopback network interface on the SGD server.
Solution: Ensure that the external bind address entry in the /opt/tarantella/var/serverconfig/local/nic.properties file on the SGD server contains a *. For example:
tarantella.config.edit.bindaddresses.external=*,www.example.com
where www.example.com is the external DNS name of the SGD server.
By default, the external bind address entry for an SGD server contains a *.
Problem: Users with Sun Type 7 Japanese keyboards cannot input characters correctly using SGD.
Cause: Missing Solaris OS keytable on the client device.
Solution: Install the appropriate patch to install the keytable on the client device.
Platform | Patch |
---|---|
Solaris 10 OS on SPARC platforms | 121868 |
Solaris 9 OS on SPARC platforms | 113764 |
Solaris 8 OS on SPARC platforms | 111075 |
Solaris 10 OS on x86 platforms | 121869 |
Solaris 9 OS on x86 platforms | 113765 |
Solaris 8 OS on x86 platforms | 114539 |
Problem: When using the SGD Client in Integrated mode on Microsoft Windows client devices, users might notice that the Start menu entries are not sorted alphabetically.
Cause: This is caused by a Windows feature that adds new items to end of a menu rather than preserving the alphabetical sorting.
Solution: See Microsoft KB article 177482 for details.
Problem: For Microsoft Windows Server 2003 applications, the display color depth on the client device is limited to 8-bit for large screen resolutions. The issue is seen when screen resolutions are higher than 1600 x 1200 pixels.
Cause: A known issue with Windows Server 2003 terminal services sessions.
Solution: See Microsoft Hotfix 942610 for details of how to increase the color depth to 16-bit.
The following table lists the significant bugs that are fixed in the 4.41 release.
Reference | Description |
---|---|
6489154 | Window focus issue when applications run in seamless window mode. |
6498460 | Text is not displayed properly after resizing of screen. Characters overlap or are too far apart. |
6506571 | SGD Enhancement Module upgrade on Solaris fails to merge client.prf file. |
6508202 | Em-size/normal-width change in Japanese. |
6524429 | Windows XP Home client takes a built-in license, instead of a Windows 2000 client access license (CAL). |
6531922 | Seamless windows are not launched after clicking the Close button on the remote application. |
6532001 | Active Directory: PKI expired password fails to prompt for new password. |
6536434 | Korean keyboard does not work correctly with SGD. |
6557536 | Initial post-launch focus misleading in SGD application window. |
6557568 | Unexpected focus change with loss of input focus. |
6568484 | Name of application using seamless windows is not displayed in Japanese, but displays correctly using a full screen. |
6570049 | Blank webtop when user DN contains “/”. |
6572217 | Webtop hints attribute is missing from Administration Console. |
6589194 | CPU load based load balancing algorithm providing skewed results. |
6591022 | Num Lock state unstable with SGD 4.31.905 patch for Num Lock and Caps Lock state issues. |
6591516 | Page transitions not working in Internet Explorer. |
6592699 | Accent characters, tonos and dialytika, do not work correctly using Greek keyboard. |
6594537 | Improved user experience and warning messages for firewall traversal mode. |
6600335 | “Hangul” and “Hanja” keys fail on WinXP client with Korean USB keyboard when running Windows terminal services applications. |
6609001 | Cannot detach a stopped secondary server using the Administration Console. |
6612935 | SGD Client shows blank logout menu items on Gnome panel. |
6615864 | Secure and non-secure content on Add Assignment page. |
6615864 | Internet Explorer Warning Messages When Accessing the Administration Console Over HTTPS. |
6616296 | Copy and paste from X-based 5250 or 3270 application to local Windows Notepad does not work. |
6617987 | Erratic behavior seen on creating a user object with inverted commas. |
6618516 | ttaauxserv reports fatal error and exits when file descriptor limit is reached. |
6620254 | Num Lock and accent acute characters on Portuguese keyboard do not work as expected. |
6620268 | Classic webtop attributes still available. |
6621456 | Enabling “Establish proxy settings on session start” in profile does not work. |
6621911 | Accented characters not properly emulated on Sun Ray![]() |
6623775 | Need to secure Active Directory queries without using client certificates from the Active Directory server. |
6624044 | The server/webtop/* logging filter is incorrect. |
6624122 | Copy and paste does not work with Windows application as non-root user in Trusted Extensions environment. |
6624795 | Title on minimized Internet Explorer incorrect when using seamless windows. |
6625786 | Session is cut off when accessing specific URL through a Windows desktop. |
6629782 | Ambiguous login and SecurID dialogs are not localized. |
6630832 | PDF printing fails on Solaris OS 8. |
6632864 | Errors in 4.40 datastore reorganization on upgrade. |
6633342 | Access Denied errors when accessing mapped drive with SWIFT application. |
6633363 | Third tier authorization dialog does not accept keyboard input in Mac OS X 10.5.1. |
6633389 | Cyclic links for application groups not upgraded correctly. |
6634373 | Log Active Directory errors more concisely. |
6634689 | 4.40 datastore reorganization does not handle dc trees very well. |
6635919 | -no-browser option required for ttatcc command. |
6636787 | Documentation for securing SOAP is unclear. |
6638874 | SGD Client crashes due to partial packet receipt. |
6639470 | Creation of new object not possible when Security Warning alert notifications enabled. |
6639655 | X server security vulnerabilities. |
6640141 | Exception caused by LDAP search on Assigned User Profiles tab for an OU in the Applications organization. |
6641356 | Extensible LDAP search filters are not validated correctly. |
6641475 | LDAP user attribute isMemberOf should be in the reverseAttributes list by default. |
6641538 | Documentation on cache --flush krb5config should include information about what it affects. |
6643772 | Unable to resume My Desktop session. |
6646817 | The printertypes.txt file needs to be updated. |
6649163 | SGD leaves “white screen” when Windows session is grabbed by Sun Ray client. |
6650200 | “Potentially unsafe connection” warning dialog presented repeatedly to users in an unsecure environment. |
6650334 | Difficulties in “mirroring” LDAP in ENS, based on groups, with LDAP profiles on OU. |
6651582 | -n option displayed on output during certificate request. |
6653001 | SGD Client crash when cancelling paste action in Trusted Extensions Sun Ray client. |
6653019 | Suspended Windows session causes ttatsc to consume 100% of CPU resources. |
6653024 | Authentication token information does not get updated in profile when changed a second time. |
6654565 | JDK change has changed keytool commands. |
6655852 | SGD Client fails on Ubuntu when Extra Visual Effects are enabled. |
6658738 | Application session load balancing is not firewall friendly. |
6659812 | Escape key and window close button are not working in View Certificate Details message box. |
6661505 | Active Directory Global Catalog and Domain Controller hostname sorting is incorrect. |
6661507 | “Failed to Find Site Objects” Active Directory error should be downgraded. |
6663148 | SGD server stability issues. |
6663754 | My Desktop feature fails if second webtop entry My Desktop2 exists. |
6664301 | New primary server detached unexpectedly when old primary server becomes available. |
6667259 | SGD Client by default is paused when printing. |
6668963 | Array join issues for two servers with different configurations for secure intra-array communications. |
6670774 | Array join on secure intra-array communications-enabled servers fails in certain scenarios. |
6670843 | Array make_primary option is not working in the Administration Console. |
6671528 | Absence of Java not detected on Windows client using Internet Explorer 6. |
6673906 | Licenses replication issues after array remaster. |
6678939 | Network printers are not appearing in Windows sessions. |
6679810 | Documentation for CommandExecutionFailed or Error 7 should also mention permissions on the /tmp folder on the application server. |
6679845 | Sun Ray DTU ID required for Windows terminal services sessions. |
6680413 | ttatsc core dumps with Solaris patch 119060-38. |
6682124 | Flushing a cached LDAP configuration using tarantella cache --flush does not work. |
6685521 | Login to SGD webtop fails after upgrade from 4.31. |
6686727 | Administration Console: New Object pop up needs scroll bars. |
6689236 | How to use load balancing JSP for My Desktop functionality. |
6689502 | Entering application command line arguments in the Administration Console. |
6690301 | SGD Client crashes when using OpenOffice from SGD webtop. |
6692376 | SGD Client pegged at 100% CPU, fails on authorization of Windows application running OS X Leopard as a client device. |
6692620 | Unable to interrupt Active Directory discovery timeouts when using default Kerberos credentials. |
6693487 | Unable to write to CDM drives using Office 2007. |
6693489 | Invalid session cookie causes JSP error with French locale. |
6693496 | Browsing to Info->Detailed Diagnostics immediately after login fails. |
6693498 | SGD Client Motif dialog has large icons on Solaris 10u4. |
6693505 | Microsoft Word 2007 does not maximize correctly on Solaris 10u4 desktop. |
6693508 | Microsoft Word 2007 claims to start in German locale on Solaris 10u4 desktop. |
6693516 | Window close operation not handled correctly in GIMP on Solaris 10u4. |
6693972 | Internet Explorer browser hangs on connection with obsolete JRE 1.3. |
6694481 | Restricting the LDAP search when the ou= has multibyte characters fails to authenticate user via LDAP authorization to Active Directory. |
6695371 | Copy and paste between two protocol engines crashes ttaxpe. |
6695876 | Misleading load balancing error message in log. |
6697034 | Create button remains inactive for localized characters input. |
6698552 | X application launch failure seen in certain scenarios with “Unknown Terminal” error. |
6698730 | No errors displayed to user when the SGD application shortcut is no longer valid. |
6699329 | tarantella security fingerprint command shows wrong fingerprint. |
6699873 | Certain keys do not work with Turkish keyboard in Windows sessions. |
6700449 | Protocol argument (-dir) for Windows applications does not work with cmd.exe. |
6701438 | 2X load balancer does not work with SGD. |
6702069 | Seamless display method does not work correctly for applications on Windows 2008. |
6702822 | Solaris Trusted Extensions: kiosk mode area should be below the Trusted Extensions stripe area. |
6703066 | Solaris Trusted Extensions: Xerror in call to XSelectInput via copy and paste incremental selections. |
6704749 | Print job size does not match in webtop and command line. |
6704925 | Problems with portuguesebrazilian_abnt2 keyboard. |
6705544 | Terminal services CALs for users with parentheses in their CN are not reused by SGD. |
6707001 | Missing apostrophes in French translations. |
6709037 | Mouse over tooltips in an seamless windows session causes the SGD Client to crash. |
6710067 | Unicode to keysym table maps the Unicode for EuroSign to the keysym for EuroSign. |
6710510 | Solaris array operations take a long time to respond when other array members are down. |
6710580 | Printing status: potential null pointer exception in opt.jsp. |
6710927 | Log in menu item not completely seen on Sun Ray client start menu. |
6712258 | Missing information for InvalidSessionCookie error string in localized versions. |
6712649 | Integrated client login fails with StringIndexOutOfBounds exception. |
6712721 | Garbled characters are displayed in localized authentication error message for all languages. |
6714996 | Active Directory authentication does not fail over to the next Global Catalog. |
The following table lists the additional bugs that are fixed in the 4.40.917 release.
Reference | Description |
---|---|
6499184 | Support for Windows 2003 Session Directory required. |
6613733 | SGD printing causes core dumps, for Solaris OS on SPARC platforms. |
6624122 | Copy and paste issues with Windows applications for SGD on Solaris 10 OS Trusted Extensions. |
6632816 | Mac OS X client platform issues. |
6632864, | Datastore issues following upgrade to SGD version 4.40.907. |
6638874 | SGD Client exits unexpectedly due to network packet fragmentation. |
6639655 | SGD X server security vulnerabilities. |
6641522 | Administration Console errors when specifying an application server DNS name that begins with a number. |
6642603 | Upgrade of SGD Enhancement Module fails. |
6644678, | Upgrade issues when using a nonstandard installation directory. |
The following table lists the significant bugs that are fixed in the 4.40.907 release.
Reference | Description |
---|---|
2144612 | Active Directory authentication does not failover to the next global catalog. |
2147536 | ttaxpe command does not exit if an incorrect password is entered. |
2148699 | CDM fails with multiple external DNS names. |
2148700 | SGD Client fails when an X application opens a specific window. |
2148811 | Printer preferences on Terminal Services not set permanently with Zebra bar code printer. |
2149630 | Korean keyboard does not work correctly with SSGD 4.30.915. |
2150849 | Intermittent problems with serial COM port redirection. |
2151274 | Accented characters fail in French locale windows. |
6469935 | SGD Client should be able to match hostname to DNS item in certificate subjectAltName extension. |
6478585 | Java virtual machine SSL key and certificate store destroyed on upgrade. |
6520742 | The tarantella security peerca --show command fails on primary SGD server. |
6525004 | Extend client device access logging in the SGD Client. |
6527507 | Better error reporting for web service failures. |
6532425 | UNIX CDM fails if tta_tem is installed in non-standard directory. |
6532764 | LDAP failover is not seamless when multiple LDAP servers are configured. |
6537643 | SGD Client crashes if application exited while dialog displayed. |
6541478 | SGD session hangs if audio played from SGD while local audio is playing on Sun Ray Client. |
6541914 | CDM does not work in Windows Vista in certain scenarios. |
6542533 | Webtop does not update to display launched applications in Safari on MacOS X 10.4.9. |
6544350 | Webtop print controls are unstable in an array. |
6546840 | Integrated mode is not enabled on SUSE Linux Enterprise Server 9. |
6547337 | Using -preferredlanguage option for ttatcc command does not open page in appropriate locale. |
6550172 | Launch fails if offline server selected in a load balanced group. |
6552038 | Improvements to ttaxpe debug logging. |
6553252 | SGD Client exits with segmentation faults and is terminated by Electric Fence application. |
6558691 | Secondary licenses are removed when primary stopped or array breaks apart. |
6561306 | Check ssh version before updating ssh arguments. |
6563481 | Improve error messages in execpe log files. |
6571826 | Command line for creating 3270 and 5250 objects does not accept all arguments correctly. |
6574469 | Update Java Platform, Standard Edition to 1.6.0_01 or later (third party) for Solaris and Linux platforms. |
6583316 | CDM cannot be disabled on a per-client basis for SGD clients. |
6583333 | ssh launch failure when sshhelper is setuid, and SGD user has no home directory. |
6597576 | SGD Enhancement Module for Linux platforms does not get installed in non‐default path. |
6598686 | Application title is garbaged on locales. |
6601084 | In Integrated mode, the folder specified in the “Start In” box is invalid. |
The following table lists the significant bugs that are fixed in the 4.31 release.
Reference | Description |
---|---|
2140625 | Time zone redirection is fixed for clients on UNIX platforms. |
2145026 | Licensing information is not copied to all the secondaries until after a restart. |
2145602 | X application launch is slow or times out. Possible error in the Input Method handling in the procs.exp script. |
2145932 | Windows key functionality is being held when returning to SGD session. |
2146043 | Using client drive mapping, you cannot overwrite a larger file. |
2146285 | Tomcat fails and icons do not appear on the webtop. |
6440254 | The proxy server authentication dialog does not display realm information. |
6443192 | Upgrading using the pkgadd command on Solaris OS reports hundreds of file conflicts. |
6443840 | The SGD Client does not understand proxy failover from proxy server configuration (PAC) files. |
6474180 | The HARD_SERVER_LIMIT of the SGD Web Server is increased to 1024. |
6480225 | In Integrated mode, applications fail to resume on UNIX client platforms. |
6494450 | Client drive mapping cannot handle files larger than 2 gigabytes. |
6499639 | A recursive directory request causes a segmentation fault when using client drive mapping on UNIX and Linux platforms. |
6503627 | The xfrbelgian.txt keyboard map file contains a mistake. |
6518152 | Start menu is not updated using Integrated mode on Microsoft Windows Vista client devices. |
6518638 | The tarantella print cancel command deletes all print jobs instead of just the selected job. |
6525384 | XRDP does not work with SGD. |
6528037 | Page Not Found displays on the webtop when a group containing hosts is deployed by mistake to a webtop. |
6506222 | A user’s .Xdefaults file is not used when launching an application. |
This section lists the known documentation issues for the 4.41 release.
In the “Selecting a Cipher Suite for Secure Intra-Array Communication” section on page 55 of the Sun Secure Global Desktop 4.41 Administration Guide, the following sentence is incorrect:
“By default, the SGD uses the RSA_WITH_AES_256_CBC_SHA cipher suite.”
The corrected sentence is as follows:
“By default, SGD uses the TLS_RSA_WITH_AES_128_CBC_SHA cipher suite.”
The “Keep Alive Configuration for Windows Terminal Servers” section on page 166 of the Sun Secure Global Desktop 4.41 Administration Guide contains an invalid link to Microsoft Knowledge Base Article 216783.
The “How to Configure SSL Connections to Active Directory” section on page 83 of the Sun Secure Global Desktop 4.41 Administration Guide contains incorrect port number information.
The port number information in step 4 of the procedure should read as follows:
“The ports required depends on the SSL configuration used for Active Directory authentication, as follows:
SSL connections without client certificates – TCP port 636 for the secure LDAP connection to an Active Directory server, and TCP port 3269 for the secure connection to the global catalog server
SSL connections with client certificates – TCP port 389 for the secure LDAP connection to an Active Directory server, and TCP port 3268 for the secure connection to the global catalog server”
Copyright © 2008, Sun Microsystems, Inc. All rights reserved.