Environment
PowerRecon 3.1 and above
Situation
This article discusses an issue which may occur when monitoring Windows bases systems with PowerRecon 3.1 and above. When monitoring Windows based systems with PowerRecon the account specified may become locked out and may require that and administrator reset the account. This issue can occur if the credentials attached to a set of servers fail to authenticate to any one of the servers in question.
When monitoring a windows based system with PowerRecon 3.1 and above the credentials attached to a specific server or group of servers may become locked out based on the account lockout policies implemented in the environment. When PowerRecon attempts to connect to a remote system for monitoring purposes it may make multiple attempts to collect the performance metrics. If the server which PowerRecon is trying to monitor is denying the remote connection requests it may cause the account to become locked out as PowerRecon will attempt to connect multiple times.