A customer is going to reorganize its departmental structure. This will affect every employee there (approx 5000 users).
There are now over 500 *new* AD groups and group membership depends directly and indirectly on the departmentNumber. The indirect method is handled by a PostProcess workflow activity. Direct membership is handled by a FIM Portal Criteria-based security group.
I am not so concerned with normal AD attributes, it is the sheer volume of group membership changes + post processes that I am concerned about. I have no idea how many concurrent operations an AD DC can handle before it gets swamped. I believe our clients
are written so that any error including "directory service busy" aborts the update.
Potentially there suddenly could be 5000 requests sent to FIMService via export of 5000 updates to FIMMA .
What is the smartest way to configure this FIMMA to limit the number of exports to FIMMA based on some crieteria e.g. "lastname starts with Ba" or "EmployeeID starts with 12"
