Server Management - Systems Insight Manager
1820592 Members
1873 Online
109626 Solutions
New Discussion юеВ

Invalid WMI Mapper account, causing domain account to lock

 
Ron Shih
Occasional Contributor

Invalid WMI Mapper account, causing domain account to lock

We are running SIM5.0 sp4. I had speicified my own domain user account as the WBEM account under Options\Global Protocol Settings. I have changed this to a different service account, however, it is still trying to use this everytime the polling interval comes around. I see that under the \WMI Mapper\Logs directory, the PegasusStandard.log file shows that it's still trying to use the old account to authenticate against domain multiples. In the process, locking out that account. I have updated the WBEM settings to use global settings for every single device, but this is not stopping the invalid credential from being used.

please help.
4 REPLIES 4
Rob Buxton
Honored Contributor

Re: Invalid WMI Mapper account, causing domain account to lock

Check that individual servers are not using System specific WBEM credentials that might be the old ones.
Ron Shih
Occasional Contributor

Re: Invalid WMI Mapper account, causing domain account to lock

Please direct me on how to proceed with checking that?

thank you
dospavlos
Frequent Advisor

Re: Invalid WMI Mapper account, causing domain account to lock

I also had this problem. Somehow SIM cached the account and disregards the credentials in the Global Protocol Settings. Try running this command which should show you a server list with the creds it's using.
mxnodesecurity -l -p wbem. There's some switches on the command to remove creds. I've found that the command didn't work trying a remove creds from multiple servers but would work if I tried to remove one server at a time. This was an issue for me in 4.2 but went away when I upgraded to 5.0. Doesn't sound like the issue is SIM version specific though.
Ron Shih
Occasional Contributor

Re: Invalid WMI Mapper account, causing domain account to lock

I just used that command and reset the ones that weren't reset to the new credential. It's odd why it doesn't update the protocol setting when you check it to under each system. thanks a bunch!