Hi, I have configured Expiration Workflow which deletes the Users which have left the Organization after 5 Days from their last date. (I have used two Custom attributes ("Employee_Updated_date" an "Employment_Status"based on which the User becomes part of a particular SET, and post transition In the SET the Expiration Workflow is triggered by an MPR which deletes the User from FIM Portal). All this was working fine till 7th June. I upgraded FIM from RTM to version 4.0.3606.2 first and then to the latest version 4.0.3617.2. Post this Upgrade I have observed that the users whose End Date is 2nd june 2012/prior these only get Deleted from FIM Portal. i.e. the FIM Portal Date is stuck at 7th June (i.e. the Date on which the Upgrade was done). I even restarted the FIM Servers post Upgrade. I have a similar Development Environment, wherin i replicated the issue with out of box attributes (i.e. Employee End Date and last Name The user deletion works fine here for Employee end date as 9th June i.e. 5 Days from today. Thus , I again tried to replicate samething with Outof Box attributes in Production Environment , but there the user entry is deleted only when the Employee End date becomes 2nd June 2012 or prior. i.e. I concluded the Issue is not with Custiom Attributes post Upgrade. Am i missing something in my configuration. as to why the Date assumed by FIM Portal is 7th June 2012 , even today. How to change this Date/overcome this Issue since it occurs with both out of box as well as custom attributes. Request your replies, Thanks in Advance, Regards, Kaushik B