Juniper STRM LOG MANAGEMENT 2008.2 - RELEASE NOTES 6-2008 Release Note page 5

Resolved Issues 5
Resolved Issues
This section describes the resolved issues in STRM Log Management 2008.2:
Changing Network Settings No Longer Causes System Failure
Previously, if you changed your network settings (for more information, see the
Changing Network Settings Technical Note), a failure occurred when you
attempted to access the system. This no longer occurs.
During Installation Process, Error No Longer Occurs When Root Password is
Not Changed
During the installation process, a message appears indicating that you are able to
use the default root password. However, if you attempted to use the default
password, a message appeared indicating that you must enter a new password.
This no longer occurs.
Hostname that Includes Underscores and Special Characters No Longer
Causes Error
Previously, if the hostname of your STRM Log Management system included
underscores and/or special characters (except dashes), the Host Context
component failed to start. Once this occurred, STRM Log Management failed to
collect data. This no longer occurs.
Now Able to Deploy License Key Once Current Key Expires
Previously, if your license key expired and you uploaded a new license key, STRM
Log Management did not provide the option to deploy the new license key.
Changing the Authentication to STRM Log Management Authentication No
Longer Requires Edits to Passwords
Previously, if you changed your authentication from TACACS, RADIUS, or LDAP/
Active Directory to STRM Log Management Authentication, you were required
configure access for users on the system before they are able to login to STRM
Log Management. No message appeared in STRM Log Management stating this
requirements. In STRM Log Management 2008.2, you must define passwords for
all users that do not have a password defined.
Updating License Key When Using Internet Explorer 6 No Longer Causes
Error
Previously, when you updated your license key using an Internet Explorer 6
browser, a window appeared stating "The page cannot be displayed" when you
click Save. This no longer occurs.
New Administrative User Now Able to Access Deployment Editor
A STRM Log Management administrative (admin) user can create multiple admin
accounts for a STRM Log Management system. A administrative user should have
unrestricted access to all components of your deployment. Previously, when a new
administrative user attempted to access the deployment editor, an error message
appeared and access was denied.
530-025628-01