From Case : 871361 - Ignite Password Change Procedure
We are required to change our passwords every 60 days. For the local ignite
accounts used by DPA, we've been following the below manual process, which is
very tedious when we have dozens of instances to update. Do you happen to have,
or can you suggest code for automating this effort across multiple selected
instances, or at least comment on if all the below manual steps are really
necessary (e.g. do we actually need to stop/start monitoring?)
1. Turn off monitoring for an instance.
2. Change the instance password for ingnite account
3. Go to options -> monitor setup -> Update connection Info and enter the new password.
4. Turn monitoring back on for the instance.
Response below from SolarWinds Support. While very helpful, the process could be made much easier and they suggested I submit this as a new requested feature.
Update for Case #871361 - "Ignite Password Change Procedure"
Peter,
I think we can speed you along with a combination of some GUI work and some code.
So the issue with all code for this item is that the password for monitored servers is stored in a table however it is hashed. So we need the hash value of that password.
If you are changing the password to the same password for all monitored connections then you should be able to just update in the GUI as you have been and then pull that hash value and update all the others to that in the table. If however you are changing to unique passwords for each monitor then you're stuck with the current setup you have listed here.
for the scripting if you are using the same password do the following.
Connect to the repository database either via SSMS or SQL Plus (not sure if your repository is SQL server or Oracle) or through the DPA query tool.
found under options -> support tab -> "database query tool" -> make sure the drop down for execute against says repository.
run the following.
select id,name,username,password,COMMAND,status from cond
find the ID of an instance you are going to go change in the GUI..
then replacing your steps some we can do
1. update COND set COMMAND='STOP' status = 'STOPPED'
2. GO update one server that we know the id for in the GUI via update connection info. in the GUI.
3. return to the query or query tool and run
select id,name,username,password,COMMAND,status from cond where id = <id from server you changed>
then update COND set PASSWORD='<value server you changed>'
4. set update COND set COMMAND='START' status = 'STARTED'
hope this helps.
Thanks,
Jamin Walters | DPA Support Technician
SolarWinds - Unexpected Simplicity
