So I have searched in here and also on the web but have found nothing that looks relevant, so I am hoping one of you FIM gurus has seen something similar and can point me in the right direction. I am in the process of rolling a Self Service Password Reset solution to our customer and have been deploying the solution to one domain at a time so as to manage user communications, registration loads, client updates etc. I have a password reset users set that grants access to SSPR for users in a deploy set. The membership for the deploy set is determined based on a user being a member of the appropriate domain, so the heirarchy looks like: SSPR users - based on being in the SSPR Deploy set SSPR Deploy set - based on being in "Domain A Set" or "Domain B Set" or "Domain C Set" So far, so good, but tonight I am deploying the solution to domains D, E, F and G. When I added "resourceID in Domain D Set" as a condition for membership of the SSPR Deploy set the request is sitting their with a status of Validating and has been like that for about 50 minutes. When I did this to the previous domain, I had about 5 mins of validating followed by 35 mins of post-processing as it managed the necessary changes to the users. This domain is really small (less than 40,000) so I was expecting it to be faster than the last one. I would be gratefule for any ideas as to why it would hang in this state or what I might be able to do to give it a kick in the guts. I have a feeling this could be a long night. Cheers, Eddie

To update, I kicked the request off again and this time it got to the post-processing stage before the hour was up so it looks like it was a "simple" timeout issue. I will be increasing my timeout to 4 hours for the next domains as I assume that the bigger my set gets the longer it will take to manage it. I would still be interested to hear if anyone has any suggestions - I have another 6 domains to roll out in the next few weeks. I have a feeling we might be pushing FIM to its limits :) Cheers Eddie