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
On desktops for which the audio adapter type is specified as Intel HD, the following commands do not work:
vda desktop-show
vda desktop-getprops
vda desktop-setprops
The workaround is to use Oracle VDI Manager instead.
On Oracle Linux platforms, the update from Oracle VDI Release 3.3 to Release 3.3.1 might fail in some circumstances, and this results in an unresponsive Sun Ray Software service and user interface.
The workaround is as follows:
Stop Cacao on all hosts in the Oracle VDI Center.
Run the following command as root:
# /opt/sun/cacao2/bin/cacaoadm stop -f -i vda
Follow the steps for updating to Oracle VDI release 3.3.1.
See Section 3.8, “Updating Oracle VDI to Release 3.3.1” for details.
Check that the Sun Ray Software service and user interface is available.
If they are not available, run the following command as root on each host in the Oracle VDI Center:
# /opt/SUNWut/sbin/utrestart
On Oracle Solaris platforms, the existing Sun Ray Authentication Manager configuration (utpolicy) is not preserved when you update from Oracle VDI Release 3.2.2 to Release 3.3.1. As a result, the Kiosk session is no longer enabled and users cannot log in to Oracle VDI.
The workaround is as follows:
Before you update, make a note of your existing Sun Ray Authentication Manager configuration.
To check your existing configuration, run the following command as root:
# /opt/SUNWut/sbin/utpolicy
After the update, verify the configuration.
Run the following command as root:
# /opt/SUNWut/sbin/utpolicy
If the configuration is not correct, run the following command as root to correct it:
# /opt/SUNWut/sbin/utpolicy <policy>
For example:
# /opt/SUNWut/sbin/utpolicy -a -g -m -z both -k both -u both
Alternatively, log in to the Sun Ray Admin tool and go to the Advanced tab and correct the System Policy setting.
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.