WCS expiring guest accounts early

Question

Hi Folks, We've had a number of reports from our Service Desk (who create the guest accounts for us) that they've been getting users who have long-term accounts (90days) expire early.
I've taken a look at the settings and sure enough, today there are accounts on WCS that are showing as expired but have a long life time.
Example:
User(x) created on 13th July with an expiry of the 15th Sept
User(y) created on 12th July with an expiry of the 12th Oct
This is only a couple listed here but the problem seems to be widespread accross long-life accounts. I've checked the clocks and they're all synced between WCS and the WLC's, when accounts are created they are done through WCS and pushed down to the single mobility anchor (our topology is 6 WLC's split over 2 sites, with a 7th WLC for MA with a toe in the internet DMZ)
We're running 7.0.172.0 of WCS and 7.0.116.0 on all the WLC's I think the problem has started to occur as it's really only now that we're using longer life-time accounts in anger. 
Originally the accounts were being deleted by the cleaner process, so it just looked like the accounts were disappearing - we've stopped this and now it just shows that they expire.
Any suggestions that you can give as to why this might be occuring would be great!  Unfortunaly we can't create 'unlimited' accounts as our policy is that they should have a lifetime of no more than 3 months, so the overhead on monitoring would be too big - so there has to be an automated process.
Thanks in advance!
Kev

Answer 1

I upgraded to WLC 7.0.235.0 and WCS 7.0.230.0 and am still getting users complaining about their accounts expiring early.  Someone please correct me if I have misread something but the WCS is suppose to check the account every so often and re-provision the account based on the expire date set?  We setup our users with 90day accounts that is pushed to two 5508 controllers running the code above, the process works well but the expiration of accounts has become a issue.  Anyone know if the bug was truly fixed in 7.0.235 code or do I need to set the lifetime of the account lower.