Hi, Just looking at a user object in the Metaverse, and in the ExpectedRulesList I see a few of the Sync rules that no longer exist in the FIM Portal. why would they still be here even though they have been deleted from the Portal? How do we clean these up, as they may be causing a lot of our problems. Thanks

Hi, When you remove a user who has one or more ExpectedRulesList entries those objects will nog be removes automaticly, they become orphaned. However because the parent object of those ERE's is removes is removed they easy to recognize. There is a Microsoft Wiki page that explains how to remove these orphaned ERE's. You can find it here: http://social.technet.microsoft.com/wiki/contents/articles/a-method-to-remove-orphaned-expectedruleentry-objects-from-your-environment.aspx Basicly you have to run a Powershell script that is able to identity the orphaned ERE's and will remove them. After they are removed, perform a Full Import and Full Sync on the FIM MA to remove them from the MV as well. Kind regards, Freek Berson http://microsoftplatform.blogspot.com/

Hi, When you remove a user who has one or more ExpectedRulesList entries those objects will nog be removes automaticly, they become orphaned. However because the parent object of those ERE's is removes is removed they easy to recognize. There is a Microsoft Wiki page that explains how to remove these orphaned ERE's. You can find it here: http://social.technet.microsoft.com/wiki/contents/articles/a-method-to-remove-orphaned-expectedruleentry-objects-from-your-environment.aspx Basicly you have to run a Powershell script that is able to identity the orphaned ERE's and will remove them. After they are removed, perform a Full Import and Full Sync on the FIM MA to remove them from the MV as well. Kind regards, Freek Berson http://microsoftplatform.blogspot.com/

Hi, Is it a huge problem if these EREs are still around? The reason I ask is that if I try run that powershell script on the page u posted I get the same error as on your page (http://social.technet.microsoft.com/wiki/contents/articles/a-method-to-remove-orphaned-expectedruleentry-objects-from-your-environment.aspx) "error: failure when making web service call' thanks

Hi, Is it a huge problem if these EREs are still around? The reason I ask is that if I try run that powershell script on the page u posted I get the same error as on your page (http://social.technet.microsoft.com/wiki/contents/articles/a-method-to-remove-orphaned-expectedruleentry-objects-from-your-environment.aspx) "error: failure when making web service call' thanks

Hi, Wether its a Huge problem...well as for all IT questions the answer is: "It depends". :-) It's not really an issue as long as the amount of orphaned ERE's doesn't reach sky-high. Especially in test-environments where you do a lot of add and removes of users for testing purpases with users that each have mutiple ERE's you could run into high numbers of orphaned ERE's which could lead in SQL storage issues or performance issues. About the error, not 100% sure what that is. The script assumes that the following URL is available on the machine that you run the script: http://localhost:5725 is that the case in your environment? Kind regards, Freek Berson http://microsoftplatform.blogspot.com/

thanks, yes that is the correct URL and port number. Not to worry about it then, this is a small test environment I am running - so it wont affect anything. thank you

And this is a good way to handle multiple FIM Scenario's in a test-environment: http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/d2d575a1-35b8-4ce0-b40a-a060115da961

just as an after-thought...is there a way to clean these manually...or only programmaticly?

Sure, Manually is also possible. Open de the FIM Portal, go to all resources, select Expected Rules List and remove the ERE is question. You can recognize an orhpaned ERE by the fast that it doesnt have a resourceparent.

Sure, Manually is also possible. Open de the FIM Portal, go to all resources, select Expected Rules List and remove the ERE is question. You can recognize an orhpaned ERE by the fast that it doesnt have a resourceparent.