I'm using FIM for password reset only. I'm using AD as the only data source and running a Full Import and a Full Synchronization on the ADMA the script then runs an Export, Full Import, Full Synchronization on the FIM MA this script runs nightly.. would this be a recommended run profile scenario for my configuration?

It depends on how fast you want user to appear in the portal. If your admins create a user on day x, it will take till day x + 1 before the user can use the password reset feature. If you are using the password reset client addin, this might be an issue as I've noticed that in the latest build users will be presented with an error if they log on to their desktop while their AD account is unknown in the portal. This behavior was not present in earlier builds. I've heard it's a known issue and is fixed in FIM 2010 R2... So to conclude if you want faster propagation times you could also do some run profiles at regular intervals. I would definately advise to start using delta profiles for that. They're faster and produce less overhead. Running full import/syncs is only required if you alter the synchronization configuration or if you have specific attribute flows with requirements. In your scenario I think you'll do fine with delta profiles. In my situation FIM is used to tie HR to AD. We run delta's every two hours during the day, once a night we do the switch with the updated CSV and once in the weekend we run full profiles. Just to give you an example. http://setspn.blogspot.com

so the run profiles im running in that order are just fine you're saying? not sure i understand why it would take day x + 1..? and no i can't forsee at this time any changes in the sync rule so i'll change my full's to delta's.. thanks for that..

Yes the order seems fine. You might want to check if after running the sync on the FIM MA any changes are ready to be exported to the FIM MA again. if there are, add another export/delta import step. I say day x + 1 because if someone adds a user to your AD at 9:15 in the morning, that user will only be added to FIM with the nightly run. Resulting in the user not being available in FIM the first day it's created in AD.http://setspn.blogspot.com

in order for your new users to use the PasswordReset feature in FIM, they must be members of the SET "Password Reset Users set" in portal, and in your case you synchronize your users to the portal once per day on night, so your users need to wait for the next day to use this feature. I think you need to run your synchronization more than one time per day, or you can notify new users that they cannot use the PasswordReset until next day. if you run delta profiles as thomas pointed out, your synchronization process duration will be decreased since only changes ( new users) will be in the cycle; thus you can run the process multiple times per day seamlessly.

thanks for the responses, much appreciated.. I've made some changes to my config as per your recommendations..!