Useful Hints

• Non-English locales: For non-English locales, the server on which the Desktop Manager console is installed should have a locale setting that supports UTF-8 encoding. To enable UTF-8 encoding, add the following line to the /etc/TIMEZONE file:

  LANG=en_US.UTF-8

• Using a global host profile with a file-based back end:

  To obtain host-specific data for a host running the Configuration Agent from the configuration repository, that host is uniquely identified by the host identifier. That identifier can denote the host in two different ways:

  - by the host name that represents the host by its name, e.g. calzone. This is the default setting.

  - by the IP address that represents the host by its IP address, e.g. 10.16.67.132. This address is preferably retrieved from the hosts file. If there is no hosts file available, the IP is determined by the interfaces of the host. If there is more than one interface, the first non-local interface is selected.

  If you are using a file-based back end, be sure that the selection of host identifier matches the contents of the entities.txt files (IPs or hostnames).

• Installing the correct Java™ Web Console version:

  Java Web Console 2.2.2 is the default version found in the Solaris^TM 10 operating system, however the Desktop Manager requires version 2.2.5 or higher. A copy of version 2.2.5 is provided in the Desktop Manager archive in the server/console directory. It can be installed by running ./setup in that directory.