The schema is generated based on the dynamic discovery of the
data source by the management agent. When you refresh the schema
for this management agent, the connected data source schema is
rediscovered, the current management agent schema is updated, and
then Management Agent Designer starts. In Management Agent
Designer, you can correct any inconsistencies that were introduced
by the updated schema, such as deleted object types or deleted
To synchronize multiple sites within the organization with a
single management agent, define a partition in the management agent
for each site.
You must provide a server name, user account, password, and
logon domain to log on to Exchange Server 5.5. The user
name that you specify must have at least read/write access for the
Exchange Server 5.5 global address list (GAL). Each time
you run the management agent, it uses this information to log on to
Exchange Server 5.5 to read or write to the directory
that you specify.
To associate the domain\username of a Windows NT 4.0
user account with an Exchange Server 5.5 mailbox, follow
Join, or project, the Exchange Server 5.5 mailboxes
to the metaverse, flowing the assoc-nt-account attribute to
a user-created metaverse attribute named SID. For more
information about creating metaverse attributes, see Add an
attribute. For faster join searches, it is recommended that the
SID attribute be indexed.
Join the Windows NT 4.0 objects to the metaverse,
matching the Windows NT 4.0 objectSID attribute to
the metaverse SID attribute. For more information about
creating join rules, see Join rules.
Configure the import attribute flow for the management agent
for Windows NT 4.0 to flow the domain\username
value to the metaverse.
The RulesRecipient object type in Exchange Server 5.5 is
the same as the Contact object type in Active Directory.
This management agent does not support password management.