Home Remote Support (Formerly Control Center)
We appreciate you taking the time to vote and add your suggestions to make our products awesome! Your request will be submitted to the community for review and inclusion into the backlog.

We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.

For more information around feature requests in the Cireson Community click here.

Account Lockout Location for AD Users.

Brett_MoffettBrett_Moffett Cireson PACE Super IT Monkey ✭✭✭✭✭
On the user management tools it currently shows the current status of the users account in AD as being either locked or unlock.

A good feature would be to have a button that triggers a PowerShell command to show where the account got locked out from like is described here: http://woshub.com/troubleshooting-identify-source-of-active-directory-account-lockouts/
or here: https://silentcrash.com/2018/06/using-powershell-to-trace-the-source-of-account-lockouts-in-active-directory/

This would allow analysts to track the machine that is having the issue due to a service or automation script being used that is locking out the account.

User Stories:
  1. As an analyst within the user management controls, I want to be able to click a button and get a text report on where potential lockout locations for the selected user are happening.
  2. As an analyst within the user management controls, I want to be able to select and copy the results of the returned lock out data for use in a ITSM platform.
6 votes

Submitted · Last Updated


  • Tom_HendricksTom_Hendricks Customer Super IT Monkey ✭✭✭✭✭
    We had to write a lot of custom code for this, and a few sync jobs.  It would be great if we could retire all that and it "just worked" in the portal.
  • Adam_DzyackyAdam_Dzyacky Product Owner Contributor Monkey ✭✭✭✭✭
    Currently just using PowerShell and/or SCOM to achieve this. It wouldn't be a significant improvement for us, but an improvement none the less.
  • Michael_AidinovichMichael_Aidinovich Cireson Solution Architect Advanced IT Monkey ✭✭✭
    Good idea and would be useful troubleshooting tool but suggest an invoke button for the Analyst to use only when needed.
  • Brett_MoffettBrett_Moffett Cireson PACE Super IT Monkey ✭✭✭✭✭
    I agree @Michael_Aidinovich
    Having it auto load every time could be a delay that is not needed 90% of the time.
    A button to check the status and lock out location would be best.
Sign In or Register to comment.