Download Release Notes 5.0.13 - Print me

Lotus Notes, Domino, and Domino Designer 5.0.13 Release Notes
Chapter 3 - Troubleshooting
Client, Server
Running the Directory Cataloger
Lotus recommends that you build or update a source directory catalog by running the Directory Cataloger on a
schedule enabled in the Domino Directory 'Server' document. You can also immediately build or update the source
directory catalog using the console command:
tell dircat quit
...and then issuing the command:
load dircat filename
...where 'filename' is the name of the source directory catalog. Do not choose Task->Start->Directory Cataloger from
the Server Status tab of the Domino Administrator to immediately build or update a source directory catalog; this tool
does not allow you to specify the file name for the directory catalog.
Server
Create full-text indexes manually on directory catalog copies
Full-text indexes are created automatically only on replicas of a directory catalog. A copy of a directory catalog is not
automatically full-text indexed; you must manually create the full-text index on a copy.
Server
Signer of a cross-domain "Delete in Address Book" request
If your domain receives "Delete Person in Address Book" or "Delete Server in Address Book" requests and the
Administrators in the source domain typically perform immediate deletions, the Administration Server of the Domino
Directory of the source domain must be in the "List of approved signers" field of your Inbound Request Configuration
document for the source domain.
Server
Do not use "container" or "domainComponent" for object classes
Do not use container or domainComponent as the name for a new object class. These object classes are reserved for
future use.
Server
Web client authentication using Microsoft Exchange Server directory
Authenticating Web users registered in a Microsoft Exchange Server directory fails if the Exchange Server the Domino
Web server connects to is not a Primary Domain controller or a Backup Domain controller and the users belong to a
different Windows NT domain than the Exchange Server. Authentication fails because in this situation the Exchange
Server requires clients to bind using cn=NTAccount,cn=NTDomain while directory assistance requires that users'
distinguished names -- the industry standard convention -- be used for binds. A workaround for this problem is
making sure that the users and the Exchange Server reside in the same NT domain.
111