Red Hat LINUX VIRTUAL SERVER 4.7 - ADMINISTRATION Installation Guide Page 37

  • Download
  • Add to my manuals
  • Print
  • Page
    / 52
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 36
13971245 – Package Removal Issues on Oracle Solaris 11
31
Cause: A known issue with how SGD caches user credentials for certain configurations of Oracle VDI.
Solution: On the SGD server, edit the application launch script at /opt/tarantella/webserver/
tomcat/tomcat-version/webapps/sgd/applicationLaunch/appLaunch.jsp.
Locate the following statement, at line 484 in appLaunch.jsp:
if (chosenCandidate.getUsername() == null)
Edit the statement, to read as follows:
if (chosenCandidate.getUsername() == null || chosenCandidate.getPassword() == null)
3.1.16. 13971245 – Package Removal Issues on Oracle Solaris 11
Problem: SGD might not uninstall cleanly on Oracle Solaris 11 platforms. After uninstalling SGD, entries
for SGD packages are still present in the Solaris package database.
Cause: A known issue when you are using the Image Packaging System (IPS) included with Oracle
Solaris 11 and you remove SGD.
Solution: The workaround is to use the SGD package database repair script pkgdbfix.sh after
uninstalling SGD. This script is included in the /opt/tarantella/etc/data directory on an SGD
server.
Log in as superuser (root) and do the following:
Uninstall SGD and check for SGD package entries in the Solaris package database.
# pkgchk -l tta
# pkgchk -l tta.2
If any package entries are reported using either of the previous commands, repair the package
database.
# sh pkgdbfix.sh package-instance
where package-instance is the reported package instance, either tta or tta.2.
3.1.17. 14026511 – VDI Broker Connections Fail After an Oracle VDI Upgrade
Problem: After an Oracle VDI host has been upgraded or reconfigured, users might not be able to connect
to their Oracle VDI desktops using the VDI broker.
Cause: When using the VDI broker, connections to the Oracle VDI host are secured using a self-signed
SSL certificate for the web services API.
Whenever you reconfigure or upgrade Oracle VDI on a host, the web services self-signed certificate is
regenerated and the existing SSL certificate is not preserved. In addition, when you upgrade, the host
name (subject) used in the web services SSL certificate might change.
Solution: Use one of the following workarounds:
Back up the web services certificate keystore on the Oracle VDI host before upgrading or reconfiguring.
Restore the keystore from backup after you have made changes to the Oracle VDI installation.
This process is described in the Oracle VDI documentation.
Reconfigure the VDI broker as follows:
Page view 36
1 2 ... 32 33 34 35 36 37 38 39 40 41 42 ... 51 52

Comments to this Manuals

No comments