Again, this is what we do now. We have a Role called "Disabled" which has no permissions.

This works, but causes continuous password popups if the disabled user logs in.

We also have to record which roles each employee had when they were disabled, so they can be reactivated correctly.

Ideally, there would be an option, as requested, for an account disabled checkbox.

If that person tried to login, they would get a message saying their account is disabled.

It would be easy to see all the disabled accounts in the list - they could be a different colour, or have a checkbox beside them in the list. They could be reactivated easily, with the correct permissions.

But then we cannot see in the list who is disabled and who is not.

The user could also request a password reset, and if their mailbox is active, then they would be back in again. Many of our seasonal staff return year after year, and their mailbox would be active so they can coordinate with managers.

Hence the request for a disabled state that is functional.

This sure would be nice. I wonder if any progress could be made after 5 years in the queue?

We have seasonal staff that only need to login for 3-6 months of the year, and constantly adding and removing their accounts is a bit annoying.

We've kind of been able to work around this by creating a Disabled security role with absolutely nothing enabled. This kind of works but causes the login box to constantly reappear, so we get helpdesk calls. Also, we have to record somewhere which role a person had when they were deactivated so they can have that added back again at the start of the season.

There has to be a better way!

Any progress on this?

It's a real pain to send a script to a bunch of remote machines and have the whole thing fail because I forgot #!ps at the top.