Hi all, I have created a password expiration reminder with all the steps outlined by Brad Turner in this article (http://social.technet.microsoft.com/wiki/contents/articles/understanding-password-expiration-notifications-in-fim-2010.aspx?wa=wsignin1.0) Everything seems to work fine when I use a test set with just a simple filter with my name in it and some other options. When I try to use a filter that checks for multiple things that include date/time things, I can see users enter the set, but the email never goes out. Filter below: <Filter xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" Dialect="http://schemas.microsoft.com/2006/11/XPathFilterDialect" xmlns="http://schemas.xmlsoap.org/ws/2004/09/enumeration">/Person[(ADPasswordExpires &lt; op:add-dayTimeDuration-to-dateTime(fn:current-dateTime(), xs:dayTimeDuration('P14D'))) and (PasswordNeverExpires = False) and (EmployeeStatus = 'Active') and (PWremind14 = True) and (ADPasswordExpires &gt; fn:current-dateTime())]</Filter> Basically checking that the password expires after today, password expires prior to 14 days from today, password never expires is false and I added an option for user to opt in or out of the notification(PWRemind14). Like I said, i can see the filter works because the users i expect to see enter the set, but no email gets sent. Test set works fine with the same workflow, so i think the template is ok. Thanks, Rich

Rich- Time based sets aren't evaluted in real-time for this type of thing. You should see the workflow fire at 1AM every night (by default) when the SQL job runs to re-evaluate the set.My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com

Thanks for the reply Brian. It has bween several days and I have not seen the workflow fire yet.

Have you checked that the SQL agent is executing the FIM-related jobs? I've seen them stop for various reasons, which keeps the time based calculations from working.Frank C. Drewes III - Senior Consultant: Oxford Computer Group

I just checked and i do not see any jobs at all except for syspolicy_purge_history . I am thinking that is the problem. Anyone know how to quickly re add them?

Yep - thats definitely the problem.. good question.. Never had them missing before. Is this a production system or can you do some playing around?Frank C. Drewes III - Senior Consultant: Oxford Computer Group

It's production. I am willing to do some tentative playing around. No pain no gain I say.

This is normally set up during install. Not sure how you got through setup without it erroring and rolling back. I am guessing you probably installed some updates and possibly hotfixes too, which will update those. I'm wondering if a repair install would go back and fix that. I might also try setting up a test fim instance at the same patch level and copying the jobs over to the real systm. I'm concerned that if this didn't happen, perhaps something else is wrong too. The other thing to be concerned about is that those jobs also remove old request objects past 30 days, so depending on how long you've had FIM running, this could end up being a lot of stuff hanging around in SQL. I'll ask around my team if anyone else has run into this and fixed it. Hopefully some other people will jump in here with a known good repair. If nobody has a good answer, Microsoft PSS can probably get this fixed up pretty quick.Frank C. Drewes III - Senior Consultant: Oxford Computer Group

I think I will call PSS just to be safe. Thanks for the help. I did find this article http://setspn.blogspot.com/2010/11/recovering-or-installing-additional-fim.html that talks about the jobs getting messed up if you do a DB restore, which i did at one point. I will post what i learn for the MS call in case it helps others.