Disconnection Flow Script Is Not Processed with the $Disconnect_Specific() Function (295675)
The information in this article applies to:
- Microsoft Metadirectory Services 2.2 SP1
This article was previously published under Q295675 SYMPTOMS
When the $DISCONNECT_SPECIFIC($MA()) function is called to remove users based on certain criteria, these users are disconnected, but the attribute flow rules, which you define in the disconnection flow script, do not run. Therefore, the attributes, which should have been added, deleted or modified on the associated metaverse object, remain unchanged. This result may cause difficulties when you try to reconnect the objects with new join operations.
CAUSE
This behavior occurs because the disconnection flow script is not called when you run $DISCONNECT_SPECIFIC() function.
STATUS
This behavior is by design.
MORE INFORMATION
With the $DISCONNECT_SPECIFIC() function, you can run this function from one management agent (MA) while you are disconnecting objects from another MA.
| Modification Type: | Minor | Last Reviewed: | 1/25/2006 |
|---|
| Keywords: | kbprb KB295675 |
|---|
|