For Oracle VDI on Oracle Linux
platforms, the iscsi-initiator-utils
package
is a required package. This package is used to create the iSCSI
initiator file
/etc/iscsi/initiatorname.iscsi
. If this
file is missing, or it is empty, it results in a database entry
with an empty value in a non-empty constrained field and this
causes a NullPointerException
when importing
a template for Hyper-V desktop providers.
The workaround is as follows:
Check that the iSCSI initiator file exists and that it is not empty.
Use the cat command to check the contents of the file. The following is an example of a correctly configure file.
# cat /etc/iscsi/initiatorname.iscsi InitiatorName=iqn.1994-05.com.redhat:bd25643d1f24
Create the iSCSI initiator file.
You can create the iSCSI initiator file by installing or
re-installing the iscsi-initiator-utils
package, or it can be generated on the command line.
If you install the iscsi-initiator-utils
package from a separately-provided .rpm
file, do not use the --noscript
option when
you install it, as this prevents some required files from
being installed. Install the package by running the
following command as root:
# rpm -ivh --nosignature iscsi-initiator-utils-<version>.rpm
To generate the file on the command line, run the following command as root:
# printf "InitiatorName=`iscsi-iname`\n" > /etc/iscsi/initiatorname.iscsi
Restart the iSCSI daemon.
Run the following commands as root:
# /etc/init.d/iscsi stop # /etc/init.d/iscsi start
This behavior can be prevented by editing the Greeter key in the GDM configuration file.
Edit file /etc/gdm/custom.conf
file.
Locate the [daemon]
section and replace
the Greeter key.
Change the line:
Greeter=/usr/libexec/gdmgreeter
to:
Greeter=/opt/SUNWkio/lib/gdm/kioskgreeter /usr/libexec/gdmgreeter
For Windows XP Professional virtual desktops, the hotdesking re-direct to the original VDI Center does not work if Windows RDP (MS-RDP) is selected as the desktop protocol for the pool.
The workaround is to use Oracle VDI RDP (VRDP) instead.
The user directory setting
ldap.group.short.attributes
is a
comma-separated list of LDAP attributes on a group object that
stores the information for primary group membership. If this
setting contains multiple values, the test for whether a user is
a member of a group fails.
The workaround is to configure only one value for
ldap.group.short.attributes
. See
Section C.1, “How to Edit LDAP Filters and Attributes” for details of how to
edit LDAP attributes.