There is blcli to disable the acct – you could also just change the passwd.
I know the blcli, but what I am trying to establish is if I run the disable command on the user account, will that in turn error any scheduled jobs that the user has set up. Or do we need to go in and manually reassign the jobs to other users.
They have somewhere around 600 users here and some users have a number of scheduled jobs set against their account so I am trying to prevent any users accessing Bladelogic after they have left the team/company, but want to maintain their job capability until the support team get around to deleting their account.
Using the password change is a great idea except that their will be no "flags" identifying dead accounts for when a clean up operation can be scheduled.
i don't know about the job behaviour off the top of my head - so it's probably best to just try it. if disabling does indeed disable the job schedules as well the passwd plus setting a property on the acct, or disabling all the auth mechanisms - something like that you could query for.
Is it too late to suggest running the jobs under service accounts?