2.4 Application Requirements and Support

This section describes the supported platforms and requirements for displaying applications through SGD.

2.4.1 Supported Applications

You can use SGD to access the following types of applications:

  • Microsoft Windows

  • X applications running on Oracle Solaris, Linux, HP-UX, and AIX application servers

  • Character applications running on Oracle Solaris, Linux, HP-UX, and AIX application servers

  • Applications running on IBM mainframe and AS/400 systems

  • Web applications, using HTML and Java technology

SGD supports the following protocols:

  • Microsoft Remote Desktop Protocol (RDP)

  • X11

  • HTTP

  • HTTPS

  • SSH at least version 2

  • Telnet VT, American National Standards Institute (ANSI)

  • TN3270E

  • TN5250

2.4.2 Network Requirements

IPv6 network addresses are not supported for application servers used by SGD. See the Oracle Secure Global Desktop Installation Guide for details of network requirements for SGD.

2.4.3 Supported Installation Platforms for the SGD Enhancement Module

The SGD Enhancement Module is a software component that can be installed on an application server to provide the following additional functionality when using applications displayed through SGD:

  • Advanced load balancing

  • Client drive mapping (UNIX or Linux platforms only)

  • Seamless windows (Windows platforms only)

  • Audio (UNIX or Linux platforms only) [1]

Table 2.7, “Supported Installation Platforms for the SGD Enhancement Module” lists the supported installation platforms for the SGD Enhancement Module.

Table 2.7 Supported Installation Platforms for the SGD Enhancement Module

Operating System

Supported Versions

Microsoft Windows (64-bit)

Windows Server 2016, 2012 R2, 2008 R2

Oracle Solaris on SPARC platforms

Solaris 10 8/11 (update 10) or later

Solaris 11

Trusted Extensions versions of the above

Oracle Solaris on x86 platforms

Solaris 10 8/11 (update 10) or later

Solaris 11

Trusted Extensions versions of the above

Oracle Linux (32-bit and 64-bit)

5 (at least version 5.5)

6 (at least version 6.2)

7 (at least version 7.0)


Oracle products certified on Oracle Linux are also certified and supported on Red Hat Enterprise Linux due to implicit compatibility between both distributions. Oracle does not run any additional testing on Red Hat Enterprise Linux products.

On Oracle Solaris Trusted Extensions platforms, only advanced load balancing is supported. Audio and CDM are not supported.

For best results, ensure that the version of the Enhancement Module is the same as the SGD server version.

Application servers that are not supported platforms for the SGD Enhancement Module can be used with SGD to access a supported application type using any of the supported protocols.

2.4.3.1 Virtualization Support

The SGD Enhancement Module is supported and can be installed in an Oracle virtualized environment. If you encounter a problem when using an unsupported virtualization environment, you may be asked to demonstrate the issue on a non-virtualized operating system to ensure the problem is not related to the virtualization product.

Installation in zones is supported for Oracle Solaris platforms. The Enhancement Module can be installed in the global zone, or in one or more non-global zones. Installation in both the global zone and a non-global zone is not supported.

On Oracle Solaris Trusted Extensions platforms, you must install the Enhancement Module in a labeled zone. Do not install in the global zone.

2.4.4 Microsoft Windows Remote Desktop Services

SGD does not include licenses for Microsoft Windows Remote Desktop Services. If you access Remote Desktop Services functionality provided by Microsoft operating system products, you need to purchase additional licenses to use such products. Consult the license agreements for the Microsoft operating system products you are using to determine which licenses you must acquire.

Note

Before Microsoft Windows Server 2008 R2, Remote Desktop Services was called Terminal Services.

SGD supports RDP connections to the following versions of Microsoft Windows:

  • Windows Server 2016

  • Windows Server 2012, 2012 R2

  • Windows Server 2008, 2008 R2

  • Windows 7 SP1

  • Windows 8, 8.1

  • Windows 10

On Windows 7, Windows 8, and Windows 10 platforms, only full Windows desktop sessions are supported. Running individual applications is not supported. Seamless windows are also not supported.

SGD supports RDP connections to virtual machines (VMs) running on Oracle VM VirtualBox and Microsoft Hyper-V.

The features supported by SGD depend on whether you connect using RDP or Oracle VM VirtualBox RDP (VRDP), as shown in the following table.

Table 2.8 Comparison of Features Supported by SGD When Using RDP and VRDP

Feature

RDP

VRDP

Audio recording (input audio)

Audio redirection

Clipboard redirection

COM port mapping

Compression

Drive redirection (client drive mapping)

Multi-monitor

Network security (encryption level)

Session directory

Smart card device redirection

Time zone redirection

Windows printer mapping (client printing)


2.4.4.1 Audio Recording Redirection

To record audio in a Windows Remote Desktop Services session, audio recording redirection must be enabled on the application server. By default, audio recording redirection is disabled.

To enable audio recording for Microsoft Windows 7 Enterprise application servers, you also need to set the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\fDisableAudioCapture registry subkey to 0.

2.4.4.2 Color Depth

SGD supports 8-bit, 16-bit, 24-bit, and 32-bit color depths in a Windows Remote Desktop Services session.

To display 32-bit color, the client device must be capable of displaying 32-bit color.

15-bit color depths are not supported. If this color depth is specified on the Remote Desktop Session Host, SGD automatically adjusts the color depth to 8-bit.

2.4.4.3 Encryption Level

You can only use the Low, Client-compatible, or High encryption levels with SGD. SGD does not support the Federal Information Processing Standards (FIPS) encryption level.

2.4.4.4 Transport Layer Security

With Microsoft Windows Server, you can use Transport Layer Security (TLS) for server authentication, and to encrypt Remote Desktop Session Host communications.

2.4.4.5 Network Level Authentication

If the Remote Desktop Session Host supports Network Level Authentication (NLA) using CredSSP, you can use NLA for server authentication.

2.4.5 X and Character Applications

To run X and character applications, SGD must be able to connect to the application server that hosts the application. SGD supports SSH and Telnet as connection methods. SSH is the most secure connection method.

SGD works with SSH version 2 or later. Because of SSH version compatibility problems, use the same major version of SSH, either version 2 or version 3, on all SGD hosts and application servers.

If you are using SSH to connect to X applications, you must enable X11 forwarding. You can do this either in your SSH configuration or by configuring the application in SGD. The Oracle Secure Global Desktop Administration Guide has details on using SSH with SGD.

SGD supports the X Security extension. The X Security extension only works with versions of SSH that support the -Y option. For OpenSSH, this is version 3.8 or later.

To print from a UNIX or Linux system application server using CUPS, the version of CUPS must be at least 1.4.2.

2.4.5.1 X11 Software

SGD includes an X protocol engine (XPE) implementation based on the X.Org Foundation X Server release X11R7.7.

2.4.5.2 Supported X Extensions

SGD supports the following X extensions for X applications:

  • BIG-REQUESTS

  • Composite

  • DAMAGE

  • DOUBLE-BUFFER

  • GLX

  • Generic Event Extension

  • MIT-SCREEN-SAVER

  • MIT-SHM

  • RANDR

  • RECORD

  • RENDER

  • SGI-GLX

  • SHAPE

  • SYNC

  • X-Resource

  • XC-MISC

  • XFIXES

  • XINERAMA

  • XInputExtension

  • XKEYBOARD

  • XTEST

The following X extension is not supported:

  • XVIDEO

2.4.5.3 Character Applications

SGD supports VT420, Wyse 60, or SCO Console character applications

2.4.6 Virtual Desktop Infrastructure

SGD uses a type of object called a dynamic application server to represent a virtual server broker (VSB). SGD uses the VSB to obtain a list of application servers that can run an application.

SGD includes a broker that enables you to give users access to desktops provided by an Oracle Virtual Desktop Infrastructure (Oracle VDI) server.

Integration with Oracle VDI is also supported by configuring a Windows application object, as described in the Oracle Secure Global Desktop Administration Guide.

This release of SGD has been tested with version 3.5.1 of Oracle VDI.

Note

Premier Support for the Oracle VDI product transitions to Sustaining Support level after March 2017. For more information, see the following knowledge documents on My Oracle Support:

2.4.7 Oracle Hypervisor Hosts

SGD includes the following application server objects, which can be used to represent an Oracle hypervisor host.

  • Oracle VM hypervisor: Used to integrate with an Oracle VM hypervisor host.

    This release of SGD has been tested with version 3.3 and 3.4 of Oracle VM.

  • VirtualBox hypervisor: Used to integrate with an Oracle VM VirtualBox hypervisor host.

    This release of SGD has been tested with version 5.0 of Oracle VM VirtualBox.

Integration with Oracle VM and Oracle VM VirtualBox is described in the Oracle Secure Global Desktop Administration Guide.

2.4.8 Microsoft Hyper-V

This release of SGD supports connections to a Microsoft Hyper-V guest running on a Windows Server 2016 or Windows Server 2012 R2 host.

Integration with Microsoft Hyper-V is supported by configuring a Windows application object, as described in the Oracle Secure Global Desktop Administration Guide.

The enhanced session mode feature of Hyper-V can be used with supported virtual machines.



[1] PulseAudio audio module is supported on Oracle Linux 6 and Oracle Solaris 11 platforms only.