Users Are Created As Disconnectors in Reflector Mode (291302)

SYMPTOMS

If you use either of the following methods to import users from multiple Organizational Units (OUs) or containers in a connected directory and place them into one OU in the metaverse, neither action results in the correct behavior.

Method 1

Run the management agent (MA) in Association mode to bring in the structure of the connected directory so that the MA disconnects it. To import the users, run the MA in Reflector mode by changing the MA mode. This results in the creation of users as "disconnectors" in the previously-discovered organizational structure, rather than as connectors, even though you ran the MA in Reflector mode.

Method 1

Run the discovery of the connected directory structure in Reflector mode. This results in the addition of all users to the metaverse in the correct location, with the exception of the first user. For additional information about the issue related to the first user, click the article number below to view the article in the Microsoft Knowledge Base:

291303 The First User Created in a Metaverse Container is Placed in the Wrong

CAUSE

This behavior occurs because Microsoft Metadirectory Services (MMS) either projects parents for connectors, or creates disconnectors if the parents are disconnectors. Even if you switch the MA to Reflector mode for users, the users are still created as disconnectors. This behavior is by design.

RESOLUTION

To work around this behavior:

Configure the MA in Reflector mode.
On the Action panel, click Attribute Flow.
On the Advanced Flow Script tab, add the following lines to Advanced Attribute Flow:
```
if $mv.structuralObjectClass = person
then
  $set_reflection("On")
endif
						
```
With this code, the synchronization engine projects users (makes the user objects connectors), but leaves the connected directory organization structure hierarchy objects as disconnectors.
Run the MA to sychronize users.