You are an AIX environment, right? I would check your users and users.local files to make sure that the map= is correct. I see this quite a bit when someone has something like this on a Windows box:
as opposed to:
Actually it's windows. I am using the local administrator account for the target windows server in users and users.local, and I did login to the target windows server via RDP using that account. My users entry look like:
BLAdmin rw,map= failed due to "Login not allowed for user"
Well, I would re-verify that the admin account is spelled correctly. Secondly, just because the account you are using has the ability to RDP in, doesn't mean that it has rights to log on locally. Check in the user rights assignments that the user account is not listed in "Deny Logon Locally." You may need to go as far as to list it in "Allow Logon locally," though I am confident you shouldn't have to do that.
I resolved the root problem - we needed a local user to define in users and users.local, because the one that we customarily use doesn't have access in this environment.
I still am curious as to what the rscd pass is, and where it's set? I didn't know I had one, and I don't think I know the pass?
Anyway, thanks for your help.
There should be a local user on the server named BladelogicRSCD. I am not aware of a time you would ever need to reset this password. It should not be allowed to logon locally (via user rights assignments) and never uses a password.
I've run into a few times you need to reset the passwd - you can use the secadmin command i think.
or, stop the agent, delete the bladelogicrscd account and start the agent - i believe the agent will re-create the user w/ the right local security policy entries.
Do you mean the password the the BladeLogicRSCD user that you get on windows?
You can change the password for it using the chapw utility
Look in the NSH commands reference or do a man chapw in network shell.
Do you have a script that updates chapw somewhere. I have an old script that bladelogic provided thats called passwd change nsh but it doesn't use chapw.
A type 2 NSH script job should do the trick.
If you make the parameter 1: %f and parameter 2: new password
Then the script would look like this:
chapw -p $2 -f $1