Server

• The Domino Administrator can administer an environment that includes Notes/Domino 4.6 or Notes/Domino 5 and Domino 6. However, because the Domino Administrator takes advantage of new Domino 6 features, there are some limitations in a mixed environment.
  • Server bookmarks
  
  If the Directory server (set in the Administration Preferences by choosing File - Preferences - Administration Preferences) is not a Lotus Domino 6 or 5 server, the Domino Administrator can retrieve only 64K of server names for the server bookmarks. To avoid this limitation, designate a Domino 6 server as the Directory server.
  • User registration
  
  User registration with the Domino Administrator does not function properly if the registration server does not use the new Domino Directory template.
  • Server monitoring
  
  When monitoring Domino 4.6 servers, the Domino Administrator cannot report the status of individual tasks, such as the router. The Domino Administrator reports only whether or not the server is responding.
  • Replication schedule
  
  The replication schedule display does not work with Domino 4.6 servers.
  • ACL management tools
  
  The ACL management tools on the Files tab of the Domino Administrator do not work with databases on Domino 4.6 servers.
• In previous releases of Lotus Notes/Domino, you configured Setup Profiles to set workstation defaults. In Lotus Notes/Domino 6, you use policies to configure the workstation defaults. Implementing policies is optional. Lotus Notes/Domino 6 continues to support Setup Profiles. However, if you choose to implement policies, be aware of the following:
  • Archive and registration settings documents have limited support on Lotus Notes 5 and earlier clients, while the setup, desktop, and security settings documents are supported only by Lotus Notes 6 clients.
  • Setup Profiles in a Person document override policies.
  • Setup Profiles continue to work in Lotus Notes/Domino 6, but are not easily located in the Domino Directory.

• The Domino 6 Web administrator template can be used to administer only Lotus Domino 6 servers. Earlier releases of the Web administrator template cannot administer a Lotus Domino 6 server.
• Domino 6 supports a new IP standard, IPv6. To connect Domino 4.6 or Domino 5 servers to an IPv6-enabled Domino server, create an old A-type record in the Lotus Domino 6 server's DNS.

• In a Domino 6 environment, you can implement either Internet site documents or Server documents, but not both. If you select the "Loads Internet configuration from Server/Internet Sites documents" on the Basics tab of the Server document, then Internet site documents will take precedence over your Server documents. If you implement Internet site documents for one protocol, you must implement the documents for each protocol that you use. Implementing Internet Site documents for the POP3, IMAP, and SMTP protocols overrides any server document settings that you have set for those protocols.

  In the mixed-release environment, you can use both Internet site documents and Server documents to manage your environment. You cannot use Internet site documents to configure your Domino 5 or earlier servers.

• If you plan to create a cluster that includes some Domino 6 servers and some Domino Release 5 or Release 4.6 servers, keep the following in mind:
  • Because the Cluster Replicator always replicates the template design between replicas, a user's mail replicas should all use the same mail template -- the Domino 6 mail template, the Domino Release 5 mail template, or the Domino Release 4.6 mail template.
  • If you move a user's mail file from a Domino 6 or a Domino Release 5 server to a Domino 4.6 server, free time information for the user is not removed from CLUBUSY.NSF. Remove this information from CLUBUSY.NSF so that cluster servers do not have the wrong information for the user.
  • If you are using an extended ACL in a database on a Domino 6 server in a cluster, it is best to include only Domino 6 servers in the cluster. Otherwise, the replicas of the database can become unsynchronized. When you use an extended ACL in a database, changes you make to a replica on a Domino Release 5 or Release 4.6 server do not replicate to Domino 6 servers. In addition, Domino 6 servers replicate to Domino 5 or Release 4.6 servers only those changes allowed by the extended ACL.
  • The Internet Cluster Manager (ICM) directs client requests to any Domino Web server in the cluster. However, only Domino 6 and Domino Release 5 Web servers generate URLs that include references to the ICM. When a user selects one of these URLs, the ICM balances the workload by redirecting the user to the most available server. If the ICM redirects a user to a Domino Release 4.6 Web server, the server will not generate URLs that reference the ICM. As the user moves between Web pages, the user continues to access Web pages on the Domino Release 4.6 server only. To take advantage of the ICM at that point, the user must select or enter a URL that contains a reference to the ICM.

• The Domino Directory database templates are backward compatible, and you can replicate the Domino 6 design to your Domino 4.6 and Domino 5 servers. However, note the following precautions:
  • Before you upgrade the Domino 4.6 Name and Address Book (NAB) or Domino 5 Domino Directory to the Domino 6 design, create a backup of the NAB or Domino Directory.
  • To administer the Domino 6 Domino Directory, use a Domino 6 Administrator client.
  • The Domino 6 Domino Directory template includes a number of new field names that increased the size of the UniqueNameKey (UNK) table. Domino 4.6 databases are limited to 64K, which the Domino 6 Domino Directory template exceeds. Upgrade your Domino 4.6 servers to Domino 4.6.7a to avoid problems with the Domino Directory database size.

• If a Domino 5 server and a Domino 6 server in the same domain both run the LDAP service, LDAP users connecting to the Domino 5 server can search for an LDAP entry created on the Domino 6 server that is not defined by the Domino 5 schema.
• If you implement Extended ACLs (xACLs), note the following:
  • You must use a Notes 6 client to set Extended ACLs, and you must set the Extended ACLs on a directory database on a Domino 6 server.
  • You can use Extended ACLs in a mixed-release environment. To replicate changes from a Domino 5 server to a Domino 6 server, the Domino 6 server must pull the changes from the Domino 5 server.
  • During Domino 6 to Domino 5 replication, the Domino 6 server only replicates to the Domino 5 server the database contents that the Extended ACLs allows the Domino 5 server to access.
  • Lotus Domino 5 and earlier releases do not enforce Extended ACL rules.
• After you upgrade your Domino 4.6 Public Address Book to the Domino 6 Domino Directory design, you must upgrade your Domino servers running LDAP to at least Domino 4.6.3 so they can properly handle LDAP queries and return correct information. The Domino Directory uses the Internet Address field to answer LDAP queries. Lotus Notes/Domino 4.6 releases earlier than 4.6.3 do not handle this change.
• You can implement the new Central Directory feature in a mixed-release environment. Domino 6 servers can host either the central or configuration directories. Domino 4.6 and Domino 5 servers can host the central directory, but not the configuration directories.
• To implement cross-domain configuration documents in a mixed-release environment, you must specify a Domino 5 or later server as the administration server. Cross-domain requests are processed only by Domino 5 or later servers.

• When you include a Domino 4.6 server in a Domain search, the Catalog task spiders the Domino 4.6 server rather than using pull-replication as the task does with the database catalogs on Domino 5 or Domino 6 servers. As a result, creating or updating the Domain Catalog is time-consuming.

• In a mixed-release cluster, users cannot have a Notes/Domino 6 mail file on Domino 4.6 or Domino 5 servers -- the Notes/Domino 6 mail template does not work properly on these releases. If you have a mixed-release cluster with mail files, use the Notes/Domino 4.6 or Notes/Domino 5 design for mail files or place users' mail files only on Domino 4.6 servers (with Domino 4.6 design), on Domino 5 servers only (with Domino 5 design), or on Domino 6 servers only with the Domino 6 design. Do not mix mail file templates. Because cluster replication ignores selective replication formulas, you cannot prevent the mail file design from replicating to other clustered servers.
• Message tracking for administrators (using the Tracking Center in the Domino Administrator) can only track messages across Domino 6 servers that have message tracking enabled. If a message was transferred to an earlier Domino or third-party server, you can no longer track that message using the Tracking Center.

  Users with a Notes/Domino 6 mail file can track messages that are routed through earlier Domino and third-party servers as long as these servers maintain the fidelity of the Notes fields in the message tracking request. Lotus Domino 6 only returns message tracking information from Domino 6 servers that have message tracking enabled. If the third-party servers do not maintain these fields, messages cannot be tracked beyond these servers.

• Lotus Notes 4.6 clients and servers cannot read native MIME messages. To route a MIME message to a Lotus Domino 4.6 server, Lotus Domino 6 has to convert a native MIME message to a Notes document with a MIME attachment. Domino cannot convert an encrypted MIME (S/MIME) message. When an S/MIME message is transferred to a Domino 4.6 server, Lotus Domino converts the message to an attachment containing the S/MIME and a Notes format message stating that the Notes 4.6 client cannot display the message because the Domino 4.6 server cannot decrypt it. This conversion allows IMAP, POP, and Domino 6 users to receive encrypted MIME mail and for encrypted MIME mail to be transferred from a Domino 6 server to a Domino 4.6 server to another Domino 6 server without loss of fidelity or breaking the encrypted signature.
• Lotus Domino 6 introduces server mail rules, a feature that earlier releases of Lotus Domino do not support. When you implement mail rules, Lotus Domino 6 adds new entries to the Configuration Settings document in the Domino Directory. This increases the size of the UniqueNameKey (UNK) table. If your environment includes Domino 4.6 servers, those servers must accommodate the increased UNK table size even though the servers do not support the new feature. Domino 4.6 servers, prior to Domino 4.6.7a, have a maximum UNK table size of 64K.

• With the relaxation of US government regulations on the export of cryptography, the Domino server and the Domino Administrator, Domino Designer, and Lotus Notes client have consolidated all previous encryption strengths - North American, International, and France - into one strong encryption level resulting in a single "Global" release of the products. The Global release adopts the encryption characteristics previously known as North American. Strong encryption in Global products can be used worldwide, except in countries whose import laws prohibit it, or except in those countries to which the export of goods and services is prohibited by the U.S. government. Customers are no longer required to order Notes software according to cryptographic strength.

• User and Server IDs contain a flag bit that indicates that the ID is North American. Global editions of Lotus Notes/Domino 5.0.3 and later ignore this flag. However, earlier international editions of Lotus Notes/Domino (Notes/Domino 5.0.2 and earlier) recognize this flag and refuse an ID marked North American. If you require an ID that works with earlier international editions of Lotus Notes/Domino, create an ID with an earlier international edition of Lotus Notes. For earlier North American editions of Lotus Notes, use a North American ID. You can use an international ID; however, those IDs have a weaker cryptography than the North American IDs.

• For Domino 4.6 administrators who want to implement transaction logging, convert Domino 4.6 databases to the Domino 6 database format. Transaction logging does not support database formats earlier than Domino 5.
• The Domino 6 Events Log includes a Search Results view in LOG.NSF. In Lotus Domino 5, you had the option to create a database, RESULTS.NSF, to display search results, an option which no longer exists in Lotus Domino 6. If you have a Lotus Domino 6 Administrator and a Lotus Domino 5 server, the log analysis is based on the Lotus Domino 5 Log Analysis functionality, and the results are saved in the Results database (RESULTS.NSF).

  If you are using a Lotus Domino 6 server, you can still create a Results database and save your results to this database. To save a Domino 6 log file to the Results database, open the document from the Search Results view in LOG.NSF, then use the File - Save As menu to save it to the desired location.

Clients

• Upgrade Lotus Notes clients to Notes 6 before upgrading mail file databases to the Notes 6 mail file template.

• When you access the Archive Settings dialog box of a database on a Domino 5 server with your Notes 6 client, you see the Domino 5 Archive Settings dialog box rather than the enhanced Domino 6 dialog box.

• When you compact a database on a Domino 6 server, the server upgrades the database to the Domino 6 format. To retain a database in Domino 4.6 or Domino 5 format, create a replica of the database and name the replica with an NS4 or NS5 extension (instead of NSF). After a database is upgraded to Domino 6 format, you can roll back to Domino 5 format (ODS41) by using the -R option or by creating a new replica or copy of the database in Domino 5 format. Note that the -R option will not roll back a database to Domino 4.6 format (ODS21). You can continue to replicate between a Domino 6 replica and a Domino 4.6 or Domino 5 replica -- the database format does not replicate.

• In Lotus Domino 6, LZ1 compression for file attachments replaces Huffman compression in Lotus Notes/Domino 5. If the LZ1 compression option is set on a Domino 6 database, a Notes 5 client will be unable to read the compression. The Lotus Domino 6 server converts LZ1 to Huffman compression for the Notes 5 client. This affects server performance. Implement LZ1 compression in an exclusively Lotus Notes/Domino 6 environment.
• Document locking can be used with a database on Lotus Notes/Domino 6. A Lotus Notes 6 client cannot lock a document on a Lotus Domino 5 or earlier server.
• View structures, including collection, btree, and container page, have changed in Notes/Domino 6. When switching between a previously released client and a Notes 6 client, Lotus Notes rebuilds the views, despite the database format. For instance, if you have a local copy of a mail database in Domino 5 database format and have installed both Lotus Notes 5 and Lotus Notes 6 on the same computer, Lotus Notes 6 rebuilds the view when the database is opened in that client release. When you open the database in Lotus Notes 5, that client also rebuilds the view even though the database format has not changed. View rebuilds occur every time you open the database in a client with a different version from the previous client that opened the same database. View rebuilds do not occur when opening a database on a server.
• The "Replicate or copy documents" option in Access Control List dialog box enables replication or copying of documents for a database. Lotus Notes 5 and 4.6 clients ignore the "Replicate or copy documents" option. By default, this option is selected. If you deselect this option with a Lotus Notes 6 client to prevent replication or copying of documents, Lotus Notes 5 and 4.6 clients can continue to replicate and copy documents from the database.