Chapter 1 Release Notes

These release notes contain information about the Sun Java^TM Desktop System Configuration Manager, Release 1. The notes contain important information available at the time of Release 1, including information about known issues and workarounds, technical notes, and pointers to additional resources. Be sure you read this document before you begin using the Sun Java Desktop System Configuration Manager (also known in this document as the Configuration Manager).

System Requirements

For information about system requirements, see the Sun Java^TM Desktop System Configuration Manager Installation Guide, which can be found at http://docs.sun.com.

Installation Notes

If you need to reinstall the Sun Java Desktop System Configuration Manager, you must first uninstall the Configuration Manager that is already on your system.

Known Issues

This list covers some of the known problems with the Sun Java Desktop System Configuration Manager. Read the list before reporting any new bugs.

bash: /root/.bashrc: Permission denied error

Troubleshooting

If exceptions are displayed in your HTML pages directly after entering the Configuration Manager from the Sun^TM Web Console, try the following:

• Clear the cache directory (/usr/share/webconsole/work/Standalone/localhost/apoc/jsp/) where tomcat stores its compiled JSPs.

• Verify that the file policymgr.cfg exists (/usr/share/webconsole/apoc/WEB-INF/).

• Verify that the file policymgr.cfg has correct user rights (read access for noaccess:noaccess).

• Verify that the LDAP data stored in the file policymgr.cfg corresponds to your LDAP server, such as host, port, baseDN, and so on.

Sun Java System Directory Server 5.2 Hotfix 1

This patch should be applied to avail of the fix for bug 4903368. Without this fix, if a user chooses to remove five or more policy groups assigned to an entity, then the Configuration Manager will remove all the assigned policy groups from that entity. More importantly, if a user chooses to remove five or more policy groups assigned to the root entity, then not only will all assigned policy groups be removed from that entity, but the Configuration Manager LDAP metaconfiguration data will also be deleted from the Directory Server. The Directory Server cannot then be used by the Configuration Manager until the createServiceTree installation script is run again.

Issues with the Java^TM Desktop System Release 2 for the Solaris^TM Operating System

Users who want to use the Configuration Manager to manage the Java^TM Desktop System Release 2 for the Solaris operating platform will need to use the Configuration Manager Release 1 that was delivered with the Java^TM Desktop System Release 2 for Linux. In so doing, users should note that the following managed configuration options of the Configuration Manager are currently not applicable:

• Policies – Gnome 2.2 – Advanced – Panels

• Policies – Gnome 2.2 – Lockdown (except for Terminal Settings)

Documentation

Sun Java Desktop System Configuration Manager documentation is available on the accompanying Documentation CD and at http://docs.sun.com. The docs.sun.com^SM Web site enables you to access Sun technical documentation online. You can browse the docs.sun.com archive or search for a specific book title or subject.

The following table lists the tasks and concepts described in each manual:

Reporting Problems and Providing Feedback

If you would like to provide general feedback, or if you find a bug in the software, send an email to jdsconfig-feedback@sun.com.

If you are reporting a bug, provide the following information, where applicable:

• Description of the problem, including the situation where the problem occurs and its impact on your operation.

• Machine type, operating system version, browser type and version, product Web page language (locale), and product version, including any patches and other software that might be affecting the problem.

• Detailed steps on the methods you have used to reproduce the problem.

• Any error logs or core dumps.