this BladeLogicRSCD account is in your domain and used by the domain controllers or on a member server ?
what is running against DCPDCPTEU4 when this happens via bladelogic ?
is DCPDCPTEU4 the only system that originates the failed authentication attempts ?
what service dependencies are set on the RSCD service ?
there were still a couple defects w/ the account lockout in 8.2 that are fixed by 8.3.03
Is BSA Apserver & RSCD agent version is different?
Is this RSCD agent installed on domain controller?
- Stop RSCD agent service
- delete BladelogicRSCD user
- Start RSCD agent service
- check BladelogicRSCD user is created
?that is not going to prevent the account lock from happening. we need to see why the account lock is happening.
Yes, agree to this fact. Maybe the account has either expired, or is non compliant as per the group policy on the server. We can try the steps I mentioned, and if that still doesnt work, we need to check for the password/account policy on the server.