topic Re: Insight Manager username change in Server Management - Systems Insight Manager

Insight Manager username change

richivey — Mon, 28 Jan 2008 22:18:15 GMT

The Active Directory account that I was using for Insight Manager authentication was deleted by another admin in my company. The person who created the account is no longer with the company, so I don't know the password and was forced to create a new account.

I've changed the account/password of all services that used the old account. I've also changed the database.props & database.admin files to show the new username, and I ran the mxpassword command to change the password.

Still, mxpassword is running (using a lot of CPU), and giving me security log errors on the old username. Where else is the username referenced? I want to make the change anywhere that the username might be referenced. I really don't want to re-install this software, since it's currently been monitoring over 100 servers for several years.

Any suggestions will be greatly appreciated.

Re: Insight Manager username change

Rob Buxton — Tue, 29 Jan 2008 23:55:28 GMT

Have a look at;

http://h10018.www1.hp.com/wwsolutions/misc/hpsim-helpfiles/hpsim_5_changing_the_SystemName.pdf

Re: Insight Manager username change

richivey — Wed, 30 Jan 2008 14:40:18 GMT

Wasn't exactly what I was looking for, but it got me to the right place. After seeing reference to the globalsettings.props, I went back in (I had changed the username in here in one place, but had missed another). Apparently, that's the reference that wasn't authenticating.

Files that must be checked:

database.props
database.admin
globalsettings.props

Also must run mxpassword command to change password:

mxpassword -m -x MxDBUserPassword="newpassword"

Hope this helps anyone else who experiences this issue in the future.

Re: Insight Manager username change

richivey — Wed, 30 Jan 2008 17:00:11 GMT

Actually, I was wrong. It is still doing the same thing. The services were not running, so I wasn't seeing the mxpassword process trying to authenticate.

Still eating up various amounts of CPU. Also of note - the PID changes, so that means it is ending and starting a new process every few seconds.