Management Agent for Lotus Notes

Applies To: Windows Server 2003 with SP1

Use the management agent for Lotus Notes to synchronize data from ILM 2007 FP1 with Lotus Notes Release 4.6, 5.0, 6.0, 6.5, or 7.0.


Available in Identity Integration Feature Pack for Microsoft® Windows Server™ Active Directory® (IIFP)


Management agent type


Supported connected data source versions

  • Lotus Notes Release 4.6

  • Lotus Notes Release 5.0

  • Lotus Notes Release 6.0

  • Lotus Notes Release 6.5

  • Lotus Notes Release 7.0

MIIS 2003 features supported

  • Password management

  • Full import

  • Delta import

  • Export

Schema Information

The schema is generated based on a fixed schema that models the database structure. Refresh schema is not available for this management agent, because it uses a static schema that cannot be changed.


The schema for the management agent for Lotus Notes has been updated for ILM 2007 FP1. The FullName attribute is now read-write, and supports exporting single and multiple values.


  • Before creating a management agent for Lotus Notes, the Lotus Notes client must be installed on the server that is running ILM 2007 FP1, and any users that either create or run the management agent must have permissions for the Notes.ini file.


The Lotus Notes client must be installed using the Single User Install option. ILM 2007 FP1 does not support Lotus Notes client installed using the Multi-User Install option.

  • The version of the Lotus Notes client that you use should match the version of the Domino server with which you are synchronizing. If you use different versions (for example, a Lotus Notes client release 4.6 and a Domino server release 5.0), you might experience import and export failures.


If you are connecting to a Domino server release 6.0 or 6.5, you should use the Lotus Notes client release 5.0.

  • The Microsoft Identity Integration Server service account needs permission to write to the Lotus Notes client installation folder. When you create a management agent for Lotus Notes, the file Mmslnext.dll is copied to the Lotus Notes client installation folder, if it is not already there. To ensure that the management agent runs properly, the Mmslnext.dll file should be secured by setting access permissions to the file or to the folder that contains the file. In addition, the first parameter of the ExtMgr_AddIns settings in the Notes.ini file must be Mmslnext.dll.

  • ILM 2007 FP1 is aware of the default Lotus Notes schema only. If you extend the Lotus Notes schema, Microsoft Identity Integration Server 2003 cannot recognize any of the new items.

  • ILM 2007 FP1 cannot run more than one management agent for Lotus Notes at a time.

  • When provisioning users into a Lotus Notes secondary address book, you can create Person documents and groups.

  • The Lotus Notes management agent requires that you use the hierarchical name that appears in the Lotus Notes server configuration document when populating the Hierarchical server name field in the Connect to Notes Server wizard page. The Lotus Notes hierarchical server name can also be found in the Domino directory and appears as Myserver/Myorg.

  • Transient objects in Notes are likely to be replication conflicts. In most cases, this is caused where there are replication conflicts, such as updates on two different servers that caused the existence of two objects with the same Fullname. These objects can be identified by using a view on the NAB where all objects having the field Conflict was listed. The existence of this field indicates a replication collision.

  • When attempting to export a certifier using the Lotus Notes 7.0 client, you may receive the error "You specified an illegal certifier name." This is a known issue with the Lotus Notes 7.0 client.

See Also


Management Agents in MIIS 2003