We are using a PowerShell script to update the filter criteria of dynamic distribution groups and are experiencing performance issues.
For each group, the script exports the filter from FIM, adds the following 2 clauses, and then imports the updated filter to FIM using the commandImport-FIMConfig:
(not(Column1 = 'X')) and (not(Column2 = 'X'))
The overall impact of the filter update is that the filter criteria is longer and the resulting member list is shorter.
We run 2 scripts. The scripts are virtually identical. The difference is that the first one adds the above clauses to the filter criteria, and the second script removes those same clauses. The second script runs 4 times faster than the first script. The performance impact appears to be FIM related and not a result of the PowerShell code itself in that the “import” step takes a long time.
It’s not clear to us why importing the filter is so much faster in one case than the other since the same workflows apply in both cases. Could this be an indexing issue with Column1 and Column2 given that the import takes longer when those are included in the filter? Any thoughts or suggestions on how to make our first script (the one that adds the clauses) at least as fast as the second script (the one that deletes those same clauses) would be appreciated.
Ramona Balke