Installation guide

Chapter 3. Known Issues, Bug Fixes, and Documentation Issues

This chapter contains information about known issues, bug fixes, and documentation issues for Oracle

Secure Global Desktop (SGD). Details on providing feedback and reporting bugs are also included.

3.1. Known Bugs and Issues

This section lists the known bugs and issues for the SGD 4.70 release.

3.1.1. 2205237 – Seamless Windows Display Problems When Restarting a

Disconnected Session

Problem: Issues with seamless windows might be encountered when the user restarts a Windows

application after closing it down. The problem is seen when the application is hosted on a Windows Server

2008 R2 server.

Cause: A known problem with some versions of the SGD Enhancement Module.

Solution: Ensure that the version of the SGD Enhancement Module running on the Windows application

server is the same as the SGD server version.

3.1.2. 6555834 – Java Technology is Enabled For Browser But Is Not Installed

On Client Device

Problem: If Java technology is enabled in your browser settings, but Java Plug-in software 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 browser settings to determine whether to use Java technology.

Solution: Install the Java Plug-in software and create a symbolic link from the browser plug-ins directory

to the location of the Java Virtual Machine (JVM) software. Refer to your browser documentation for more

information.

3.1.3. 6831480 – Backup Primaries List Command Returns an Error

Problem: Using the tarantella array list_backup_primaries command on an SGD server that

has been stopped and then detached from an array returns a "Failed to connect" error.

Cause: A known issue.

Solution: Restart the detached SGD server before using the tarantella array

list_backup_primaries command.

3.1.4. 6863153 – HyperTerminal Application Hangs in a Relocated Windows

Desktop Session

Problem: Users running the HyperTerminal application in a Windows desktop session experience

problems when they try to resume the desktop session from another client device. The HyperTerminal

application is unresponsive and cannot be closed down.

Cause: A known issue with HyperTerminal when resuming Windows desktop sessions from another client

device (also called “session grabbing”).

Solution: Close down the HyperTerminal application before you resume the Windows desktop session

from another client device.