1.1. New Features in Release 4.70

This section describes the features that are new in the SGD 4.70 release.

1.1.1. Secure Installation by Default

In previous releases of SGD, connections to SGD servers were secured as a post-installation task. In this release, connections to the SGD server can be made secure during installation. This is called installing in secure mode.

Secure mode installation uses the tarantella security enable command to configure and enable SGD security services automatically. During installation, users can choose to use their own Secure Sockets Layer (SSL) certificate to secure connections.

Secure mode installation also enables secure intra-array communication for the SGD server. This means that connections between the SGD servers in an array are encrypted.

When you install in secure mode, firewall forwarding is disabled. This means that the SGD server can be used with the SGD Gateway.

Installation of SGD without using secure connections is still available.

See Installing SGD for more details about installing in secure mode.

1.1.2. New X Server Implementation

This release incorporates a new X Protocol Engine implementation, based on the X.Org Foundation X Server release X11R7.6.

The new implementation provides enhanced support for multiple monitors and dynamic session resizing. These features are enabled through the use of the RANDR and XINERAMA X extensions.

New attributes have been introduced for configuring RANDR extension support. The RandR Extension (--array-xrandr-enabled) attribute enables RANDR support for the array. The Window Size: RandR Extension (--xrandr) enables RANDR support for an application object.

SGD now supports the X Keyboard (XKB) X extension. Using XKB enhances globalization support, by providing built-in support for more locales. Legacy keyboard maps and server-side configuration are no longer required to process keyboard input for X applications.

See the Using the RANDR X Extension for more details about configuring applications to use these new features.

1.1.3. Audio Recording for Windows Applications

This release provides support for audio recording in Windows applications displayed through SGD.

The Audio Input (--array-audioin) attribute has been introduced to enable audio input for an SGD array.

See the Enabling SGD Audio Services for more details of how to set up audio recording for Windows applications.

1.1.4. Network Level Authentication Support for Windows Applications

This release supports the use of Network Level Authentication (NLA) using CredSSP, for authenticating Windows application users. Using NLA enables users to authenticate themselves before establishing a session on the Windows application server.

The Enhanced Network Security (--enhancednetworksecurity) attribute has been introduced to configure NLA for Windows applications. This attribute is enabled by default.

1.1.5. New Virtual Server Broker for Oracle VDI

To provide closer integration with Oracle Virtual Desktop Infrastructure (Oracle VDI) deployments, a new virtual server broker has been introduced. The new broker can be used with Oracle VDI Release 3.3 and later.

The new broker uses the Oracle VDI web services API to authenticate the user, obtain a list of desktops, and to start and stop the desktop. With this broker, SGD and Oracle VDI can be installed on different hosts.

The new broker is called the VDI broker. The existing broker for legacy Oracle VDI installations was formerly called the VDI broker, and has been renamed in this release as the Legacy VDI broker.

The following table shows broker compatibility with Oracle VDI versions.

Table 1.1. Brokers Used With Oracle VDI

Broker Name

Oracle VDI Version

VDI broker

3.3.2 and 3.4.1

Legacy VDI broker

3.2


The VDI broker provides additional features, such as support for a dedicated certificate truststore, host load balancing, and timeouts.

See VDI Broker for details of how to configure and use the VDI broker.

See Section 3.3.1, “Legacy VDI Broker Documentation Issue” for important information about documentation issues concerning the Legacy VDI broker.