Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Ah ha. ERROR: Can not have both a user password and a user secret. We were in the wrong. Our configuration was set up with an existing username XXXXX password XXXXX rather than secret XXXXX. I've updated our switches with the correct password type, and retested the script. Everything is working perfectly now, and more secure! Double bonus. Thank you so much for your help!
  2. 1. Pasted into the script side of ISE 2. Updated to the PasswordState bin folder path. Note - We put our installation in a non-default location, so our path on 58 was D:\PasswordState\bin 3. Updated 95 with default { Write-Output $results.ToString() } 4. Input our relevant information Failed to reset password for account 'XXXXX' on Host 'XXXXXX'. Error = Cannot bind parameter 'Seconds'. Cannot convert value "[OpenTimeout]" to type "System.Int32". Error: "Input string was not in a correct format." We are running password state on a Win 2012r2 box (Powershell 4.0 native) with a .NET Framework 4.6.1.
  3. Hello! I've set up our Cisco Catalyst 3560G switches as hosts in Password state. I've also set up a password list that allows for password resets and heartbeats. I'm able to get the validation to work with our current network credentials, and the green marker appears next to the password list that is tied to the host. I can remote session launcher in with the credentials used for the positive heartbeat, and access the switch I set up the Cisco - Privilege 15 Script to run, and then expired the password to have the system automatically reset the password. It successfully ran, updated the password state, and then showed green in the two boxes for both heartbeat and reset status. However. When I attempt to run a remote session launcher or manually putty in to the device with the new credentials, I can't log in. When I attempt to log in with the old credentials that were used before the password reset, I can still log in. And after the next scheduled heartbeat, I now have a red circle in that column. I've gone into the switch and checked the running configuration, compared them side by side, and as far as I can tell everything is exactly the same as before the script was run. But the audit history in the process seems to have completed without error The Passwordstate Windows Service successfully processed the Password Reset Script 'Reset Cisco Host Password - Priv 15' against Host 'XXXXXX' for the account 'XXXXX' (\XXXXXXXX\Network Equipment) The Passwordstate Windows Service removed the account 'XXXXXXX' (Password List = \XXXXXXX\Network Equipment, UserName = XXXXXX, Description = Catalyst 3560G - School) from the Queue as the Process Reset Task is now complete. This account relates to the Host XXXXXXXX. What am I missing here?
  4. Ah, interesting. That did it, thank you for your help!
  5. As an added layer of redundancy, we would like to export our passwords to a CSV file to print and keep in a locked vault in case of disaster. Unfortunately, when we export the CSV we get an error message I've checked the lists and they are all set to allow for export. This occurs with an administrator level account, and on the server that is hosting the instance of Password State. The error code is 0x80004005 but that seems to be a generic error message. We are using Windows Server 2012r2 and Windows 10 to attempt to unzip.
  • Create New...