|
|
http://www.redhat.com/docs/manuals/dir-server/release-notes/ds71sp3relnotes.html
Red Hat Directory Server 7.1 SP3 Release Notes
Copyright © 2006 Red Hat, Inc.
Table of Contents
Summary
Platform Requirements
Server Support
Client Support
Installing Red Hat Directory Server 7.1 SP3
Obtaining Packages
Installing Red Hat Directory Server 7.1 SP3 on Red Hat Enterprise Linux
Installing Red Hat Directory Server 7.1 SP3 on Solaris and HP-UX
Installing Windows Sync for Red Hat Directory Server 7.1 SP3
Known Issues
Bug Fixes
Summary
This service pack for the 7.1 release fixes a number of bugs. There are no new features.
Platform Requirements
Platform requirements for this release are identical to those for 7.1.
Server Support
*
HP-UX 11i (PA-RISC, 64-bit)
*
Solaris 9 (SPARC, 32-bit)
*
Solaris 9 (SPARC, 64-bit)
*
Red Hat Enterprise Linux 3 Update 4 (x86, 32-bit)
*
Red Hat Enterprise Linux 4 (x86, 32-bit)
In addition, the Windows Sync module runs on these Windows platforms:
*
Windows 2003 Server
*
Windows 2000 Server
*
Windows NT SAM Registry
Client Support
This release supports the following browsers for Admin Express, a web interface for administrators, and online Help, which is for administrators only:
*
Firefox 1.0 (RHEL 3 & 4, Solaris 9)
*
Mozilla 1.4 (HP-UX)
*
Mozilla 1.4.3 (RHEL 3, Solaris 9)
*
Mozilla 1.7.3 (RHEL 4)
This release supports the following browsers for end user access to the Org Tool and Phonebook applications:
*
Firefox 1.0 (RHEL 3 & 4, Solaris 9)
*
Mozilla 1.4 (HP-UX)
*
Mozilla 1.4.3 (RHEL 3, Solaris 9)
*
Mozilla 1.7.3 (RHEL 4)
*
Microsoft Internet Explorer 6.0 (Windows XP only)
Installing Red Hat Directory Server 7.1 SP3
To install Red Hat Directory Server 7.1 SP3 on Solaris and HP-UX, Red Hat Directory Server 7.1 must already be installed. To install Red Hat Directory Server 7.1 SP3 on Red Hat Enterprise Linux, either upgrade the existing installation (refer to the section called “Installing Red Hat Directory Server 7.1 SP3 on Red Hat Enterprise Linux”) or install a new server using the RPM package. For instructions on installation of Red Hat Directory Server 7.1 SP3, refer to the Red Hat Directory Server Installation Guide at the following URL:
http://www.redhat.com/docs/manua ... tall/7.1/index.html
Obtaining Packages
Red Hat Network (RHN) (http://rhn.redhat.com) is the software distribution mechanism for most Red Hat customers. Customers will have received account login information for RHN, including entitlements for the Red Hat Directory Server 7.1 SP3 release. If so, use the RHN website to obtain the software. After logging into RHN, go to Channels (view complete list if needed) and, in the Red Hat Directory Server 7.1 channel, go to the Downloads tab. The Solaris 9 32-bit and 64-bit packages can be found there under the ISOs list as well as the tarball (.tar.gz file) archive for the source code.
NOTE
The files are tarball (.tar.gz) archive files, not ISO images.
Customers looking for RPMs for Red Hat Enterprise Linux can access these files from the RHN website or via up2date, using an account with entitlements for the Red Hat Directory Server 7.1 release. There are also ISO images containing both RPM and SRPM package files available as downloads on the Red Hat Directory Server 7.1 channel. The RPM packages can be downloaded and installed as normal. The ISO images can be downloaded and burned onto CD-recordable media using the appropriate software.
For Red Hat Enterprise Linux 4, if a CD was created from an ISO image and the install CD should run automatically when inserted into the CD-ROM drive, the appropriate settings will have to be set in Applications > Preferences > Removable storage.
Red Hat Enterprise Linux installed from the CD will use the Package Management Tool. Run /opt/redhat-ds/setup/setup to configure the new Red Hat Directory Server once the package is installed.
Installing Red Hat Directory Server 7.1 SP3 on Red Hat Enterprise Linux
After installing Red Hat Directory Server 7.1 on Red Hat Enterprise Linux 3 or 4 system, upgrade to Red Hat Directory Server 7.1 SP3.
1.
Log in as root
2.
Upgrade the Directory Server using the package appropriate for the version of Red Hat Enterprise Linux installed.
*
For Red Hat Enterprise Linux 3:
rpm -U redhat-ds-7.1SP3-3.RHEL3.i386.opt.rpm
*
For Red Hat Enterprise Linux 4:
rpm -U redhat-ds-7.1SP3-3.RHEL4.i386.opt.rpm
Installing Red Hat Directory Server 7.1 SP3 on Solaris and HP-UX
After installing Red Hat Directory Server 7.1, upgrade to Red Hat Directory Server 7.1 SP3.
1.
On the 7.1 host machine, log in as root or superuser (su).
2.
Create a new directory for the new Directory Server
mkdir ds71sp3
Open the new directory.
cd ds71sp3
3.
Download the Directory Server product binaries file to this directory.
4.
Unpack the product binaries.
gzip -dc filename.tar.gz | tar -xvof -
where filename corresponds to the product binaries file.
5.
Locate the setup program in the list of files.
6.
Run the setup program from the installation directory and follow the prompts.
./setup
7.
The setup will prompt to proceed with setup. Press Y to continue.
8.
The setup program will prompt agree to the license terms. Press Y to agree with the license terms.
9.
Enter the full path to the server root directory (or the installation directory) location where Directory Server 7.1 is installed. By default, the setup program provides the following path:
/opt/redhat-ds/servers
If the Directory Server is installed in a different path, enter that path. Once the path is correct, press Enter.
10.
Last, the setup program will prompt for the administration server password. Enter the password for the Configuration Administrator. Upgrade will then begin.
Installing Windows Sync for Red Hat Directory Server 7.1 SP3
If Red Hat Directory Server is running in conjunction with Windows Active Directory services, refer to the following instructions to install Windows Sync for Red Hat Directory Server 7.1 SP3.
1.
Follow the uninstall section of Red Hat Directory Server Administration Guide to uninstall the Password and User Synchronization (NT only) services on the Windows system. Refer to the WIndows Sync chapter for more information:
http://www.redhat.com/docs/manua ... 1/sync.html#2878810
NOTE
The SSL dbs or keystore will be preserved and can be re-used after upgrade is complete.
2.
Copy and install the updated msi files from /opt/redhat-ds/winsync/ to the Windows system.
3.
Reboot the Windows system after re-installing the Password and User (NT only) Synchronization services.
Known Issues
The following bugs or situations are known issues; when possible, a work-around is provided.
Table 1. Known Issues
Issue Description Work-Around
Bug 200799 The Console allows the internal user SIE to authenticate to login. It should be prohibited. Log into the Console only as the proper admin user, not the SIE user.
Bug Fixes
Table 2, “Bugs Addressed in Red Hat Directory Server 7.1 SP3” lists the bugs addressed in Red Hat Directory Server 7.1 SP3, either via bug fixes or available supported workarounds.
Table 2. Bugs Addressed in Red Hat Directory Server 7.1 SP3
Bug Number Description
189264 This bug was only triggered by an in-place upgrade, when a database version was changed between the version being migrated from and the version being migrated to. In this event, transaction logs may not be removed. This problem has been fixed.
191240 The initial Admin Server password could be used to log into the Admin Server even after the password was updated. This problem has been fixed.
192901 When the given base DN had no children in a subtree search, even if the filter did not match the base DN entry, the entry was returned. This problem was introduced in the Red Hat Directory Server 7.1 SP2. This bug has been fixed.
197757 After updating the admin user password, an attempt to log into the Console with the previous password issued a wrong error message. This problem has been fixed.
197831 When an attempt to update the Admin Server password through the Console failed, the error message was not helpful in determining the cause of the failure. This problem has been fixed.
200146 When updating the admin user password on the Console, if the new password contained characters which were escaped over HTTP, the escaped password was submitted. This problem has been fixed. |
|