User manual REDHAT DIRECTORY SERVER 7.1 SP7 RELEASE NOTES

[. . . ] Obtaining Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Directory Server 7. 1 SP7 on Red Hat Enterprise Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Directory Server 7. 1 SP7 on HP-UX and Sun Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Synchronization Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [. . . ] Open the new directory. cd ds71sp7 4. Download the Directory Server product binaries file to this directory. Unpack the product binaries. gzip -dc filename. tar. gz | tar -xvof filename is the product binaries file; the exact name depends on your platform. Make sure that the Configuration Directory Server instance on the machine is running and that the Administration Server instance is stopped. 6 Installing Synchronization Services # cd serverRoot. /stop-admin # cd serverRoot/slapd-instance. /restart-slapd 7. Open the new ds71sp7 directory, and extract the binary files for the new service pack setup program by running the setup command with the -b option. # cd /path/to/ds71sp7 # . /setup -b serverRoot 8. Run the setup program again to install the service pack. NOTE When upgrading from an Directory Server instance version 7. 1SP4 or older, you must run the setup script to resolve security issues addressed in 7. 1SP5. If you are upgrading from version 7. 1SP5, then this is not necessary. 9. Supply the configuration information as prompted by the installer. An upgrade usually requires this information: · Agreeing to the setup and licensing terms. · The full path to the server root directory (the installation directory) where Directory Server 7. 1 is located; by default, this is /opt/redhat-ds/servers. · The Configuration Administrator's password for the Directory Server 7. 1 instance. The upgrade process beings after all of the 7. 1 instance information is given. 2. 4. Installing Synchronization Services If Windows synchronization will be used on a Windows server in conjunction with a Red Hat Directory Server 7. 1 server, then install the 7. 1 SP7 Windows Sync services on the Windows machine: 1. If the Windows sync peer is an NT server, then also uninstall the User Sync service. This is described in the Directory Server 7. 1 Administrator's Guide, available at http://1www. redhat. com/1docs/1manuals/1dir-server/1ag/17. 1/1sync. html#2878810. 7 Release Notes NOTE The SSL databases or keystore are preserved and can be re-used after upgrade is complete. 2. Copy the the updated msi files from /opt/redhat-ds/winsync/ to the Windows system. Double-click the new msi files to install them. Reboot the Windows system after re-installing the Password Sync and, on NT, User Sync services. Perform a full resynchronization between the Directory Server and Windows sync servers. In the Directory Server Console, click the Configuration tab. Expand the Replication folder in the left navigation window. Click the name of the Directory Server database which is synchronized with the Windows directory, and select the sync agreement. [. . . ] Known Issues The following are some of the most important known issues in Directory Server 7. 1 SP7. When possible, supported workarounds are also described. Bug Number 171140 Description Upgrading the Windows Sync service on the Windows server from version 7. 1 to version 7. 1 SP1 or higher (including 7. 1 SP7) requires two things: · Rebooting the Windows machine. Workaround 11 Release Notes Bug Number Description · Performing a full manual resynchronization. To manually synchronize Active Directory and Directory Server, open the Directory Server Console, and, in the Configuration tab, click the Replication folder, select the database, and the right-click on the synchronization agreement. Workaround 311851 SASL mapping entries are dynamically created Manually create SASL mapand stored in the configuration file at the inping entries that are associstance generation. The mapping entries are ated with the second suffix. [. . . ]