Microsoft KB Archive/255797

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 17:17, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


Article ID: 255797

Article Last Modified on 10/2/2003



APPLIES TO

  • Microsoft Metadirectory Services 2.1



This article was previously published under Q255797

SYMPTOMS

In Microsoft Metadirectory Services (MMS), the discovery of a connected directory may result in either:

  • Fewer users than expected being discovered.
  • No users being discovered.

This behavior can occur in any Lightweight Directory Access Protocol-based (LDAP-based) Management Agent (MA) discovery process. Currently, this includes the Microsoft Exchange (LDAP), Netscape, and Novell NDS MAs.

CAUSE

Causes for this type of problem include access privileges to the connected directory, and the type of users involved.

The current MMS design treats foreign users (or custom recipients in Exchange) differently from regular users. The foreign users must be placed in a separate organizational unit. This helps to distinguish between foreign users and native users within the connected directory.

By default, the discovery programs (for example, Cdir_ldp.exe) explicitly ignore these organizational units for performance and simplicity purposes.

You can enable the processing of foreign users under the Operate MA action. For example, when you are working with the Exchange MA, on the When Running the Management Agent tab, click to select the Process Custom Recipients check box in the Types of Objects to Process area.

RESOLUTION

Verify the access rights and privileges of the MMS server and the MA that you are using. If the permissions granted to the MA are sufficient, verify the name of the Foreign Users container. The name of this container must differ from the context prefix. To view or set the context prefix, click Configure, click Connected Directory Specifics, click Discovery, and then click Context Prefix.

MORE INFORMATION

The current design requires that foreign users be isolated in their own separate organizational unit, typically below the context prefix and in a descriptively named container such as Foreign Users. There is no workaround for this requirement.


Additional query words: Zoomit Via MA

Keywords: kbenv kbprb KB255797