The Advanced Management Console is a commercial product available for Java users who have license for Java Standard Edition (SE) Advanced or Java SE Suite.
For an overview of the Advanced Management Console, see the Advanced Management Console product page.
This release adds the following features to Advanced Management Console 2.4:
Support added for the following:
- Agent support on Mac OS X for usage tracking and Deployment Rule Sets
- MySQL 5.7
- WebLogic 12.2.1
- JREs can be installed and removed on managed desktops.
- Self-signed certificates for
DeploymentRuleSet.jar files are supported.
- Advanced Management Console agents can be unregistered from the Advanced Management Console server.
- Deployment rule sets management is a part of the Advanced Management Console user interface (UI) and not a separate application.
- Status tab shows all the Java Usage Tracker records which are rejected by the Advanced Management Console.
When the Advanced Management Console agents are unregistered, make sure that the Advanced Management Console server is accessible. If the server cannot be reached from the managed desktop, then the unregistration may fail in a number of ways:
- The desktop is not unregistered on the server, but the agent server is removed locally from the desktop; this desktop is first shown in the Desktops tab as offline and then retired.
- The desktop is unregistered on the server, but the agent service is still running; the agent cannot connect to the server, and the server doesn't manage the desktop.
- Currently, registered agents do not connect to the server after the SSL certificate is changed.
- The Advanced Management Console agent fails on a few localized directories, for example, Chinese, Japanese, or Korean.
- If changes are made on an endpoint system through the Java Control Panel (JCP), then those changes might not be reflected in the Advanced Management Console user interface until the Advanced Management Console agent on the endpoint system is restarted.
- Some Desktops can face an installation fail issue with MSI error code 1603. In detailed MSI error log, you can find the following line: CustomAction installexe returned actual error code 61016.
Workaround: Create an empty file, such as
C:\ProgramData\Oracle\Java\java.settings.cfg on those desktops and run the installation process again.
- The Status tab contains a Desktop sub-tab that displays Failed and Retired desktops. In some cases the button set that allows you to switch between table and properties views is disabled and is not accessible.
Workaround: To switch from the table to the properties view, double click a non-empty table row. To switch back just reload the page.
JREs listed in the web-enabled JREs table may not exactly match what is shown in the JCP for the following reasons:
- You may occasionally see a JRE used by the agent in the web-enabled JREs table.
- If the agent runs using a 32-bit JRE, then only 32-bit web-enabled JREs (as shown in JCP) are listed in the table, and similarly 64-bit JREs are listed when the agent runs using a 64-bit JRE.