3.12. About Global Oracle VDI Centers

3.12.1. Home and Foreign Oracle VDI Centers
3.12.2. Guest Pools
3.12.3. Global Oracle VDI Centers and Desktop Login
3.12.4. Preparing a User Directory for Global Oracle VDI Centers

The Global Oracle VDI Centers feature is useful for companies whose users travel from one site to another. It extends the basic hotdesking experience to multiple Oracle VDI environments so that, when they travel, users can access desktops in their home Oracle VDI Center or locally hosted desktops.

Global Oracle VDI Centers assume the existence of a global user directory infrastructure. Global Oracle VDI Centers are always enabled, but you cannot take advantage of this feature unless your user directory is properly prepared. For more information about how to prepare the user directory, refer to Section 3.12.4, “Preparing a User Directory for Global Oracle VDI Centers”.

When considering the user experience, you should decide whether to implement manual or automatic redirection for hotdesking and whether to make guest pools available.

Guest pools are described in Section 3.12.2, “Guest Pools”. For more information on hotdesking, see Hotdesking in the Sun Ray Software Administration Guide. Manual and automatic redirection are described below in Section 3.12.3.1, “Manual Redirection” and Section 3.12.3.2, “Automatic Redirection”.

3.12.1. Home and Foreign Oracle VDI Centers

An Oracle VDI Center is an individual Oracle VDI environment consisting of one or more Oracle VDI hosts. The Oracle VDI Center where a user normally works is that person's home Oracle VDI Center. Working in one's home Oracle VDI Center is no different, from the user point-of-view, than working in a standalone Oracle VDI Center. With Global Oracle VDI Centers, once the user directory has been properly prepared, a user can continue to access an existing desktop in the home Oracle VDI Center while traveling or use a desktop from a guest pool at the foreign Oracle VDI Centers.

3.12.2. Guest Pools

A Guest pool (a pool with the Guest flag turned on) provides desktops for users who have no assignments to desktops or other non-Guest pools in the Oracle VDI Center to which they are currently connecting. A Guest pool is displayed on the Desktop Selector screen only when a user meets this condition.

You can set a pool as a Guest pool with the Oracle VDI Manager or the command line. Although they are not mandatory, the following settings for Guest pools are recommended:

  • Flexible desktop assignment

  • Small Preferred Size, to conserve resources

  • Small number of Free Desktops, to conserve resources

  • Large Maximum Size, depending on how many guest users are expected to work at the same time in a worst-case scenario

3.12.3. Global Oracle VDI Centers and Desktop Login

When Global Oracle VDI Centers are configured, there are no changes to the Desktop Login screen. However, the process for logging in and selecting a desktop can change depending on configuration.

When the user provides a user name and password, Oracle VDI first determines whether to connect the user to their home Oracle VDI Center or to a foreign Oracle VDI Center. It does this by searching the user directory for the Global Oracle VDI Center data. If no such data can be found for the current user, the current Oracle VDI Center is considered to be the user's home Oracle VDI Center.

If a user connects to a foreign Oracle VDI Center, the Desktop Selector screen contains new entries, such as:

  1. One or more Guest pool entries. If you have configured the Guest pools correctly, the user can get a local desktop from a Guest pool in the foreign Oracle VDI Center, after which the Desktop Selector displays that desktop instead of the Guest pools.

  2. An entry to switch to the user's home Oracle VDI Center. This option redirects the current session to the user's home Oracle VDI Center. The Desktop Login screen is displayed with the user name pre-populated, and the user has to enter a password again. After successful authentication, the Desktop Selector screen displays the user's assigned desktops and pools.

3.12.3.1. Manual Redirection

Normally, the Desktop Login screen prompts for user name, domain, and password. If authentication succeeds, the Oracle VDI system determines the user's home Oracle VDI Center. If the Sun Ray Client is connected to the user's home Oracle VDI Center, then nothing changes in the screen's behavior, and the user is presented with the Desktop Selector screen. However, if the Sun Ray Client is not connected to the user's home Oracle VDI Center, then the Desktop Selector screen displays an Oracle VDI Center entry in addition to any other guest desktops that may be available for a visitor to that Oracle VDI Center. The user now has the choice of being redirected to the home Oracle VDI Center or of using one of the guest desktops available at the foreign Oracle VDI Center.

If the user selects the home Oracle VDI Center entry, the Sun Ray Client is redirected to one of the Sun Ray servers in the user's home Oracle VDI Center, and the Desktop Login screen displays the user name and current domain. Upon re-entering the correct password, the user is presented with the normal Desktop Selector screen. Since the Sun Ray Client is now connected to the user's home Oracle VDI Center, the assigned desktops in the home Oracle VDI Center are now accessible. At this point, the user cannot revert to the new local Center.

If you want to enable redirection back to the previous home Oracle VDI Center, see Section 3.12.3.3, “Automatic Redirection to Initial Server”.

3.12.3.2. Automatic Redirection

The default redirection logic requires the user to enter a password twice, first on the initial login screen and then after redirection. To avoid this inconvenience, you can configure the Desktop Login screen to perform multi-step authentication. Setting the client.autoredirection.homeserver=Enabled property instructs the screen to ask only for user name and domain information (see Section 6.2.6, “Global Settings for the Oracle VDI Kiosk Session”). This information is sufficient to determine the user's home Oracle VDI Center.

Users already connected to their home Oracle VDI Center get a password prompt in a second step. For users not already connected, the Sun Ray Client is automatically redirected to any server in the user's home Oracle VDI Center. After redirection, the password prompt is presented (user name and domain are preset). After successful authentication, the user gets the Desktop Selector screen.

Automatic redirection does not offer the capability to stay at the foreign Oracle VDI Center and to use or select a guest desktop. Instead, the user must work with desktops hosted in the user's home Oracle VDI Center.

3.12.3.3. Automatic Redirection to Initial Server

After a Sun Ray Client has been redirected to a different server, it usually remains there when the user disconnects. This can cause some confusion for the next user, who might be surprised to be offered an Oracle VDI Center link and a list of guest desktops instead of the expected list of assigned desktops. Under automatic redirection, however, the client is automatically redirected to the current user's home Oracle VDI Center during the login sequence.

You can use the client.autoredirect.firstserver setting to configure the Oracle VDI kiosk session to redirect the Sun Ray Client to return to its initial server automatically when the user logs off, disconnects, or quits the session. It is enabled by default (see Section 6.2.6, “Global Settings for the Oracle VDI Kiosk Session”).

3.12.4. Preparing a User Directory for Global Oracle VDI Centers

Global Oracle VDI Centers do not require any additional configuration in Oracle VDI. However, the user directory needs to populated with the data needed according to the schema used by Oracle VDI, see Section 3.12.4.1, “Oracle VDI Center Data Schema”.

If you want to use different attribute names and object types than the defaults, you may do so. You will then need to customize the LDAP filters and attributes used for Global Oracle VDI Centers to reflect the attributes and objects used in your schema.

See Section C.1, “Editing LDAP Filters and Attributes” for the necessary steps and the default LDAP filters and attributes for Global Oracle VDI Centers.

3.12.4.1. Oracle VDI Center Data Schema

Oracle VDI is configured to use the following schema for storing Oracle VDI Center data. This schema uses classes and attributes that already exist in LDAP v3 directories.

  • Oracle VDI Center: an Oracle VDI Center is an Organization Unit (ou) object. It may be located in any place in the user directory. The name used to represent an Oracle VDI Center in the Desktop Selector screen is taken from the displayName attribute if this attribute is specified. Otherwise, the value of the ou attribute is used. An Oracle VDI Center ou contains (directly or through a hierarchy) several Oracle VDI Host objects, which are the Oracle VDI hosts composing the Oracle VDI Center.

  • Oracle VDI Host: an Oracle VDI Host is a computer object (on Active Directory) or a device object (on other LDAP directories). The host name/IP address of the Oracle VDI Host is taken from the dNSHostName attribute (on Active Directory) or the ipHostNumber attribute (on other LDAP directories). If none of there attributes are defined, the value of the cn attribute of the host object is used.

  • Associating an Oracle VDI Center with a User: the Oracle VDI Center to which a user belongs is defined on the user object, in the seeAlso attribute. This value of this attribute needs to be the full DN of the Oracle VDI Center object for that user.

Figure 3.1 shows an example global Oracle VDI Center in Active Directory.

Figure 3.1. Active Directory Example

The image shows an Active Directory tree for a global Oracle VDI Center, with OUs for different countries and users with seeAlso attributes that reference the country OUs.